Disable Multi-Plane Overlay (MPO)

By Han Mitchel·Updated Jul 31, 2026·11 min read

Creator of SmoothFPS

Multi-Plane Overlay (MPO) is a Windows display feature that hands compositing to your graphics hardware instead of the operating system. When it works you never notice it. When it misbehaves you get flickering, black screens that last a fraction of a second, stuttering that no in-game setting fixes, and overlays like Discord, GeForce Experience or Xbox Game Bar tearing or blanking. It affects NVIDIA and AMD alike, and it is worst on the setups people buy for smoothness: variable refresh rate (G-Sync or FreeSync), high refresh panels, and multi-monitor desktops.

This page shows you how to disable MPO, how to check whether it was actually your problem, and how to put it back if it was not. You will also see it written as multiplane overlay or multi plane overlay — same feature, same fix.

WHAT MPO ACTUALLY DOES

Windows draws your screen by combining separate layers — the desktop, a video, a game window, an overlay. Since Windows 8.1, the Desktop Window Manager can hand those layers to fixed-function hardware in your GPU as separate "planes" rather than blending them itself. That saves power and can cut latency, which is why Microsoft enables it by default.

The trouble happens at the moments the planes change: a video starts, a game goes fullscreen, an overlay appears, or the refresh rate shifts because VRR is doing its job. On some driver and firmware combinations those transitions are not clean, and what you see is a flicker, a black frame, or a hitch. Because it lives below the game, nothing you change inside the game makes any difference — which is exactly why people end up searching for this after trying everything else.

HOW TO TELL IF MPO IS YOUR PROBLEM

MPO is a likely suspect when the symptom follows a pattern like this:

The flicker or black screen happens when something on screen changes state — alt-tabbing, a video thumbnail starting to play, an overlay popping up, a game entering or leaving fullscreen. It is more common with G-Sync or FreeSync switched on, and often disappears entirely when you switch VRR off. It can appear on the desktop, not only in games. It survives a clean driver reinstall, because the driver is not the whole story. And it usually arrived with a Windows or driver update rather than with new hardware.

MPO is an unlikely suspect when the stutter is tied to load rather than to transitions: it gets worse as the scene gets busier, your GPU or CPU is pinned at 100%, or your temperatures are climbing while your clock speeds fall. That pattern is thermal or bottleneck-shaped, and turning MPO off will not touch it.

If you are not sure which of the two you are looking at, that is a measurement question rather than a guessing one — a sensor log will show whether your clocks were dropping at the moment of the stutter, which separates a thermal problem from a compositing one.

THE FIX: OVERLAYTESTMODE

Disabling MPO is a single registry value. OverlayTestMode is an undocumented Windows value — it appears in NVIDIA's support article rather than in Microsoft's documentation — and setting it to 5 tells the Desktop Window Manager to stop using overlay planes. It is fully reversible, and the steps below include exactly how to reverse it.

The value lives in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm and must be created as a DWORD (32-bit) named exactly OverlayTestMode, with the value 5. A restart is required — the Desktop Window Manager reads it at start-up, so nothing changes until you reboot.

WINDOWS 11 24H2 AND OVERLAYMINFPS

On Windows 11 24H2 and newer, OverlayTestMode=5 stopped reliably disabling MPO for many people. The companion value is OverlayMinFPS, a DWORD (32-bit) set to 0, created in the same Dwm key. Set both, restart, and re-test. If you are on 24H2 and only the first value did nothing, this is the missing half rather than a sign that MPO was innocent.

WHAT IT COSTS YOU

This is a trade, not a free win, and it is worth knowing what you are trading. Compositing in hardware exists to save power. With MPO off, the Desktop Window Manager does that work itself, so idle and video-playback power draw rise slightly. On a desktop you will not notice. On a laptop you may lose a little battery life during video playback — the case MPO was designed to optimise.

There is no meaningful frame-rate cost in games. MPO is about how finished frames reach your panel, not about how they are rendered, so disabling it does not reduce your FPS. What changes is the smoothness of the path to the screen, which is the entire point.

IF IT DID NOT HELP

Put it back. A fix that changed nothing is a fix you should not keep carrying, and leaving unexplained registry values behind makes the next problem harder to diagnose. Delete the value or values you created, restart, and the previous behaviour returns.

Then look at the shape of the symptom again. Stutter that scales with scene complexity, clocks that fall while temperatures rise, a GPU sitting idle while the CPU is pinned — these are different problems with different fixes, and the pattern is visible in a sensor log even when it is invisible on screen.

WHY THIS FIX IS SO WIDELY RECOMMENDED

MPO problems are unusual in that the symptom is dramatic and the cause is invisible. A black screen or a flicker looks like failing hardware, a dying cable, or a broken monitor. People replace DisplayPort cables and reinstall Windows over it. The actual cause is a composition feature doing something subtle at layer-change time, and there is no error message anywhere to point at it. That gap between how alarming the symptom looks and how small the cause is explains why this one registry value has become one of the most-shared fixes in PC troubleshooting — and why it is worth trying before you buy anything.