Viewerframe Mode Exclusive <2024>

In Shared Mode, your input (mouse click/keypress) must travel:

Input → Game Engine → Render Frame → OS Compositor → Queue → Viewerframe

In Exclusive Mode:

Input → Game Engine → Render Frame → Viewerframe

By cutting out the compositor queue, you reduce latency by 1 to 3 full frames. For a 144Hz monitor (6.9ms per frame), that is a reduction of roughly 7-21ms. For a 60Hz monitor, that is a massive 16-48ms reduction.

You will rarely see a checkbox labeled "Exclusive Mode." Instead, you toggle this via:

For those writing raw graphics code:

At its core, Viewerframe Mode Exclusive refers to a rendering state where a specific viewport (or display window) takes full, uncontested control of the GPU’s frame buffer.

To understand "Exclusive," you must first understand the alternative: Shared or Composited mode.

When you activate viewerframe mode exclusive, you are telling the system: "Stop managing my window. I am taking over this screen region completely."

In the world of PC gaming and high-performance computing, milliseconds matter. Whether you are a competitive esports athlete, a 3D rendering artist, or a VR enthusiast, the way your graphics card communicates with your display dictates your experience. Among the myriad of settings hidden within graphics drivers and game engines, one phrase stands out for its technical weight and performance impact: "Viewerframe Mode Exclusive."

If you have ever dug through the configuration files of Unreal Engine games, tweaked rendering settings in OBS Studio, or troubleshooted VR headset stuttering, you have likely encountered this term. But what exactly is it? Why is "exclusive" better than "shared"? And how can you leverage it to shave crucial milliseconds off your latency?

This article dives deep into the architecture of display rendering, explaining the science, the benefits, and the practical applications of Viewerframe Mode Exclusive.