Why do 3D apps or screen recordings slow down in HiDPI?

HiDPI can substantially increase the number of pixels an application has to render. A desktop that looks the same size can therefore need more graphics work, especially in a 3D viewport or while recording the screen.

For the scaling background, see how HiDPI affects rendering work.

For example, 2560 × 1440 HiDPI normally renders at 5120 × 2880 before scaling to the display. That is four times as many pixels as 2560 × 1440 LoDPI. It does not mean every application will run four times slower: the effect depends on the application's rendering work and the Mac's available resources.

Reduce the rendering workload

To find a useful balance:

• Compare HiDPI and LoDPI at the same logical size with recording stopped. Then repeat with recording running to separate the two costs.
• Try a smaller HiDPI desktop size in Display Mode. This reduces the rendering surface while retaining HiDPI text, but makes interface elements larger.
• If the application offers a viewport render-resolution or quality setting, lower that setting to reduce its 3D workload without changing the whole desktop.
• If recording is the main trigger, compare lower capture dimensions or frame rates in the recording application.

Check virtual-screen presentation

If you use a virtual screen only to obtain another desktop size, compare ordinary mirroring with streaming. Streaming is useful for its rotation, crop and video filters, but introduces a different capture and presentation path. If you do not need those features, mirroring may perform better on your setup. Check the actual mode and refresh behavior after changing the presentation method. This is not a guarantee for every Mac or display.

For a delayed or jittery pointer, compare the same physical display with virtual mirroring or streaming stopped. Then compare another input device, such as the built-in trackpad, while keeping the display mode and refresh rate consistent. A delay shared by both input devices points beyond that one mouse. It does not identify the exact cause. A reported refresh rate alone does not measure pointer-to-screen latency, and changing a cable or port is not a universal cure.

If an oversized virtual HiDPI desktop produces intermittent colored flashes or other artifacts, compare a smaller HiDPI size or a working native mode with the same workload. A mode appearing in the list does not establish that it is stable on your setup. If the smaller mode is stable, use it while narrowing the issue. That comparison alone does not prove the Mac, cable or monitor is faulty. Increasing the virtual-resolution limit permits larger modes but does not guarantee reliable rendering.

Compare sustained graphics activity

When investigating heat or sustained load, compare CPU activity and GPU activity separately, with the same applications, display arrangement and desktop size. Also compare the app’s menu or Settings window open and closed. A warm Mac with low BetterDisplay CPU usage does not by itself identify which rendering work is responsible. The selected macOS display mode can remain active after BetterDisplay quits.

If the extra GPU load appears specifically while BetterDisplay’s interface is visible, compare your macOS Reduce transparency setting in both states if that is practical for you. Do not assume that reducing transparency always lowers graphics work. An improvement in this comparison does not establish the cause of unrelated Electron-app artifacts or a general fix for virtual-screen performance.

LoDPI can improve performance at the cost of interface detail. BetterDisplay cannot guarantee the same rendering quality and speed simply by exposing another mode. See HiDPI and HiDPI refresh-rate limits for the distinction between logical size, rendering size and available output modes.