Exclusive Fullscreen vs Borderless Windowed for GPU Games? Flip Model, DWM Composition, VRR/HDR/Latency Trade-Offs & Troubleshooting

2026-10-25 ｜ GPU Repair ｜ About 15 minutes ｜ HK GPU Fix Editorial Team

重點摘要

Exclusive fullscreen hands the game direct control of the display, while borderless windowed runs through the Windows desktop compositor — but modern flip-model presentation and fullscreen optimizations have blurred that old divide. This guide compares latency, variable refresh rate, HDR, Alt-Tab speed, and multi-monitor behaviour, and explains how to troubleshoot mode-switch problems.

The Short Answer First

Exclusive fullscreen and borderless windowed are not two skins over the same behaviour. They are two different answers to one question: who owns the display while the game is running? In exclusive fullscreen, the game takes ownership of the display. It chooses the resolution and refresh rate, and its finished frames are flipped directly to the screen. In borderless windowed, the game remains a window on the desktop, and the Desktop Window Manager (DWM) — the Windows component that draws the desktop — composes the game window together with everything else on screen.

That distinction used to decide almost everything: latency, tearing, Alt-Tab speed, and whether a variable refresh rate display could do its job. On modern Windows, the distinction is blurrier than the menu labels suggest. A technology called the flip model lets a borderless game present its frames almost as directly as an exclusive game. A Windows feature called fullscreen optimizations quietly converts many exclusive-fullscreen games into an optimized borderless-style path. And DirectX 12 games do not offer classic exclusive fullscreen at all, so a "Fullscreen" label in a modern game may describe an emulated mode rather than the old exclusive path.

The practical consequence is that the menu label is a poor guide on its own. The right question is not "which label sounds faster?" but "which presentation path is this game actually using on this machine, and which trade-off matters most for this session?" A competitive player on a single monitor cares most about latency and a stable refresh rate. A streamer cares about capture reliability and instant Alt-Tab. A player with two monitors cares about what happens on the second screen. Each of those users can reasonably choose a different mode for the same game.

This article explains the machinery first, then compares the modes on latency, variable refresh rate (VRR), HDR, Alt-Tab speed, multi-monitor behaviour, and capture, and ends with symptom-based troubleshooting. Two neighbouring topics are deliberately kept short here because they already have their own guides: screen tearing as a mechanism is covered by article #155, and compatibility behaviour of older games is covered by article #187. Where those topics touch this one, this article summarises the point and points past it rather than rewriting it.

Who Owns the Display: Two Presentation Paths

Every frame a game produces must travel from the graphics card to the screen. The route it takes is called the presentation path, and the two classic paths differ in one decisive step.

In the classic exclusive path, used by DirectX 11 and earlier games in true fullscreen, the game asks Windows to hand it the display. The game's swap chain — the queue of finished frames waiting to be shown — flips its newest finished frame directly to the front buffer, the memory the display reads from. Nothing else is drawn in between. The game controls the resolution and refresh rate, so it can run at a refresh rate different from the desktop's. The desktop itself is effectively suspended while the game owns the screen, which is why Alt-Tab out of an exclusive game takes a visible moment: Windows must hand the display back, restore the desktop mode, and then hand it over again on return.

In the classic windowed path, the game draws into a window like any other application. DWM takes that window, together with the taskbar, other windows, and desktop effects, and composes them into a single desktop image that is sent to the screen. Composition is what makes overlapping windows, transparency, and instant switching possible, but in its legacy form it added a step between the game's finished frame and the screen. The game also inherited the desktop's resolution and refresh rate, because the desktop image has one resolution and one refresh rate. A game running at a lower internal resolution was scaled up into the desktop image rather than driving the display directly.

The older form of windowed presentation used a method called bitblt, or blt, in which each finished frame was copied into the composited desktop image. Copying costs time and can add a frame of delay between the game finishing a frame and that frame reaching the screen. It also meant the game's frame timing was at the mercy of the desktop's composition timing, so uneven frame delivery could read as stutter even when the game itself was producing frames evenly.

The Flip Model: Why Borderless Caught Up

The flip model changed the economics of the windowed path. Instead of copying each finished frame into the desktop image, a game using the flip model presents its finished frame directly, and the compositor hands that frame to the display without an intermediate copy. The frame still passes through the desktop's ownership of the display — the game does not own the display the way an exclusive game does — but the expensive copy step disappears, and with it most of the latency penalty that used to separate borderless from exclusive.

Modern games built on current graphics APIs use the flip model by default. The more interesting change is what Windows does for older games that were written before the flip model existed. On Windows 11, the "Optimizations for windowed games" setting converts eligible DirectX 10 and DirectX 11 windowed and borderless games to flip-model presentation. The practical effects are lower frame latency, working variable refresh rate in windowed modes, and Auto HDR support in windowed modes — benefits that used to require exclusive fullscreen. Games that already use the flip model gain little from the setting, because there is nothing left to convert. The setting is system-wide but can be turned off for a single game through that game's graphics settings, which makes it a useful controlled test: if a problem appears only with the setting on, the presentation conversion itself is implicated.

It is worth stating plainly what this means for old advice. Articles written before these optimizations that declare borderless "always slower" describe the legacy blt path, not the path a modern Windows machine actually uses for most games. The gap has not vanished for every game — implementation details still matter, and some games and drivers still behave better in one mode — but it has narrowed enough that the mode decision should be made by testing on the reader's own machine, not by repeating a slogan.

Fullscreen Optimizations: Exclusive in Name, Borderless in Practice

Windows 10 introduced a feature with a confusing name: fullscreen optimizations. When a DirectX 11 or earlier game requests exclusive fullscreen, Windows may instead run it through an optimized borderless-style path, as long as the game is the only visible application. The game still believes it is fullscreen, and the player still sees a fullscreen image, but underneath, the presentation path resembles the flip-model borderless path: fast Alt-Tab, no display-mode switch, and DWM still in ownership of the display.

This is usually a good trade. The player keeps most of the latency benefit of exclusive presentation and gains instant switching and overlay compatibility. It also explains a common confusion: two players can both select "Fullscreen" in the same game and observe different Alt-Tab behaviour, because one machine has fullscreen optimizations active and the other has them disabled, or because one game's engine requests a path the other does not.

Fullscreen optimizations can be disabled for a single game through the executable's compatibility properties ("Disable fullscreen optimizations"). That switch is a diagnostic tool, not a performance upgrade to apply blindly. If disabling it fixes a problem — for example, a game that stutters or shows incorrect colours only with optimizations on — then the optimized path is implicated for that game. If disabling it makes things worse, the optimized path was helping. Either result is useful evidence, and the test costs nothing except a restart of the game.

DirectX 12 and the Meaning of the "Fullscreen" Label

DirectX 12 does not support classic fullscreen-exclusive mode. A DirectX 12 game whose menu offers "Fullscreen" is not taking exclusive ownership of the display. Instead, Windows switches the display to the game's requested resolution and refresh rate while DWM remains in ownership, ready to compose again the moment another window appears above the game. The visible result looks like fullscreen, and the resolution and refresh-rate change is real, but the underlying presentation system is the modern flip path, not the old exclusive path.

This matters for troubleshooting in two ways. First, advice written for DirectX 11 exclusive mode — such as "switch to exclusive to fix tearing" — may not apply to a DirectX 12 game, because there is no exclusive mode to switch to. Second, a DirectX 12 game that misbehaves in "Fullscreen" but works in "Borderless" is usually revealing something about resolution switching, refresh-rate switching, or overlay interaction, not about exclusive ownership, since neither mode owns the display exclusively. The fix may be to match the game's resolution and refresh rate to the desktop's, or to disable a conflicting overlay, rather than to chase a mode that does not exist.

Latency and Frame Pacing: Where the Difference Actually Lives

Input latency is the time between a mouse movement or key press and the corresponding change appearing on screen. It is a chain: input sampling, game logic, rendering, presentation, and display scanning. The display mode affects mainly the presentation step, and its contribution depends on the path. The legacy blt path added a copy and a composition wait. The flip path removes the copy. Fullscreen optimizations bring the exclusive path close to the flip path. So on a modern machine, the mode difference in latency is usually small for games already on the flip path, and larger for older games still on the legacy path until Windows converts them.

Frame pacing is a separate quality from average frame rate. A game can report a high average frame rate while still feeling uneven, because some frames arrive late and others arrive twice. Presentation timing is one cause: if the compositor or the display waits for the next refresh while a frame is ready, or if a frame misses its presentation window, the visible rhythm breaks. Mode changes can expose pacing problems that were hidden before, because the presentation timing changes even though the game's rendering workload does not. That is why a mode comparison should be judged by feel over a sustained session and by low-frame-rate behaviour, not by a single average frame-rate number captured in a menu.

V-Sync interacts with both latency and pacing. With V-Sync on, the game waits for the display refresh before presenting, which prevents tearing but adds waiting time. With V-Sync off, frames present immediately, which reduces waiting time but allows tearing. In borderless mode, the desktop's composition historically forced a form of synchronization even when the game asked for none, which is one reason older borderless play could feel different from exclusive play with V-Sync off. The flip model changes that bargain, because a flip-model window can present without waiting in a way the legacy path could not. The exact behaviour still depends on the game, the driver, and the Windows version, so V-Sync settings should be re-tested after any mode change rather than assumed to carry over.

Variable Refresh Rate: The Mode That Changes the Rules

A variable refresh rate display adjusts its refresh timing to match the game's frame delivery, instead of demanding a fixed number of frames per second. When the game delivers frames unevenly, the display waits for each frame rather than repeating or skipping, which removes tearing without the waiting penalty of V-Sync and smooths out uneven delivery. The display technologies behind this are commonly known as G-Sync and FreeSync, and Windows also exposes a system-level variable refresh rate setting.

Historically, VRR worked reliably in exclusive fullscreen and unreliably or not at all in windowed modes, because the compositor's fixed desktop refresh rate stood between the game and the display. That history still shapes driver settings: graphics control panels typically offer VRR for "fullscreen only" or for "fullscreen and windowed". The windowed option extends VRR to borderless and windowed games, but it can also apply VRR behaviour to non-game windows, which can cause odd stutter when dragging or focusing ordinary windows. A sensible approach is to keep the global setting on fullscreen-only and enable the windowed option per game profile only for games that actually run borderless.

On modern Windows, the flip model plus the windowed-games optimization makes VRR in borderless a realistic proposition for DirectX 10 and 11 games, and DirectX 12 games already live on the flip path. Even so, VRR in borderless depends on the game's swap chain being configured to allow it, and on the driver applying the windowed setting. If VRR works in exclusive but not in borderless for a particular game, the first checks are the driver setting scope and whether the windowed-games optimization is on. If VRR works in neither mode, the problem is more likely the display connection, the display's own VRR setting, or the refresh-rate range than the mode choice. Note that VRR has a working refresh-rate range: below that range, the display cannot slow down far enough to match very low frame rates, and frame-rate limiting or a different V-Sync arrangement may be needed to keep delivery inside the range.

HDR: Switching Modes, Switching Colour Worlds

High dynamic range (HDR) changes what the display expects: brighter highlights, a wider colour volume, and a different tone-mapping curve. In exclusive mode, the game can switch the display into HDR mode when it starts and switch it back when it exits. That direct switch is one reason exclusive HDR historically behaved more predictably: the game and the display agreed on the colour world for the whole session.

In borderless mode, the game normally inherits the desktop's HDR state. If the desktop is in standard dynamic range (SDR) and the game wants HDR, something must negotiate the change without taking over the display, and that negotiation is where problems appear: a black screen on launch, a washed-out image because the game renders HDR values into an SDR desktop, or HDR that engages only after Alt-Tabbing away and back. Windows HDR calibration and Auto HDR add further layers: Auto HDR can upgrade an SDR game's output to HDR, but only on paths where Windows is allowed to intervene, which is one of the benefits the windowed-games optimization brings to borderless play.

The practical rules are simple. If HDR is a priority, decide the desktop HDR state before launching the game, and keep it consistent: either run the desktop in HDR and play borderless, or run the game exclusive and let it switch. Avoid changing the Windows HDR toggle while the game is running, because a mid-session colour-space change is a common trigger for a black screen or a stuck washed-out image. If a game launches to a black screen in one mode, switching modes is a legitimate test, but so is matching the game's resolution and refresh rate to the desktop's before judging HDR, because a combined mode-plus-HDR switch confuses the diagnosis.

Alt-Tab Speed, Multi-Monitor Behaviour, and Capture

Alt-Tab is where borderless wins most visibly. Because borderless never hands the display away, switching to another window is instant: the desktop is already there, and the game window simply loses focus. Exclusive mode must restore the desktop mode on exit and re-acquire the display on return, which takes a visible moment and can occasionally leave the game minimized, black, or crashed if another application grabs focus mid-switch. Fullscreen optimizations narrow this gap for converted games, but a game running the true exclusive path still pays the switch cost.

Multi-monitor behaviour follows the same ownership logic. In exclusive mode, the game owns one display, and interacting with a second display usually minimizes the game or forces a mode switch. In borderless, the mouse can move freely to the second monitor, and other applications remain usable without disturbing the game. There is a cost to watch for: a second monitor showing moving content — a video, an animated page, a monitoring tool updating rapidly — keeps DWM composing at that monitor's pace, and on some configurations that activity can disturb the game's presentation timing or hold the game's refresh rate to the second monitor's rate. If a game stutters only when the second monitor is busy, test with the second monitor showing a static desktop or temporarily disconnected before blaming the game or the graphics card.

Capture and streaming follow a similar pattern. Capture tools work by intercepting the game's presented frames or by capturing the desktop image. Exclusive mode can block or complicate capture, because the capture tool cannot easily reach frames that bypass the compositor, and some anti-cheat or overlay systems treat exclusive hooks as suspicious. Borderless is normally the easier capture target, because the frame passes through the desktop image the capture tool already reads. The trade is that overlays and capture hooks can themselves reintroduce latency or stutter, so a streamer who sees stutter only while capturing should test with capture disabled and with overlays disabled separately: the two are different suspects.

Mode Comparison Table

Troubleshooting by Symptom

Black screen when switching modes. A black screen on a mode switch usually means the display is being asked to change resolution, refresh rate, or HDR state and is not completing the change. Wait briefly before forcing anything: some displays take a few seconds to lock onto a new mode. If the image does not return, use the operating system's display reset shortcut, then relaunch the game in the mode that worked and change only one variable — resolution, refresh rate, or HDR state — before trying the new mode again. A mode switch combined with an HDR toggle is two changes at once and should be split into two tests.

Tearing in borderless but not in exclusive. Tearing means the display is showing parts of two different frames at once. The full tearing mechanism is explained in article #155; the mode-specific point is that legacy borderless composition used to hide tearing by forcing synchronization, while the flip path can present without waiting. Check first whether V-Sync is actually active in borderless — the setting may behave differently per mode — and whether VRR is active for windowed games in the driver. If VRR is off for windowed games, borderless has neither V-Sync waiting nor VRR smoothing, and tearing is the expected result rather than a fault.

Slow Alt-Tab or a game that stays minimized. If Alt-Tab out of a "Fullscreen" game is slow, the game may be running the true exclusive path rather than the optimized path. Check whether fullscreen optimizations are disabled for that executable, and whether another application is grabbing focus during the switch. If Alt-Tab is fast for other games but slow for one, the difference is in that game's path or its focus behaviour, not in Windows generally.

Second monitor appears to slow the main game. Test in stages: first make the second monitor static, then disconnect it, then reconnect it at the same refresh rate as the main display if the hardware allows. If the problem follows the second monitor's activity rather than its presence, the cause is composition load or a refresh-rate interaction, and the fix may be as simple as closing the moving content on the second screen while playing. If the problem persists with the second monitor disconnected, the mode is not the cause and the investigation should move elsewhere.

Washed-out colour or HDR that will not engage. Confirm the desktop HDR state before launch, confirm the display's own HDR setting, and avoid toggling HDR mid-session. Test the same game in exclusive mode: if HDR works there but not in borderless, the negotiation between the game and the desktop HDR state is the suspect, and running the desktop in HDR before launching the game in borderless is the workaround to test. If HDR fails in both modes, the display connection or the display setting is more likely at fault than the mode.

Stutter that appears only in one mode. Stutter confined to one mode points at presentation timing, not at rendering workload, because the game's rendering work is the same in both modes. Compare with the same V-Sync and frame-cap settings in both modes, and with overlays and capture off. If the stutter follows the mode even with identical settings, try toggling the windowed-games optimization or fullscreen optimizations for that game: a presentation-path change that removes the stutter identifies the path as the cause.

Choosing a Mode: A Decision Guide

For single-monitor competitive play where every frame of latency matters and switching away mid-match is rare, exclusive mode — or a DirectX 12 game's fullscreen label with fullscreen optimizations active — is the natural starting point, because it gives the game the most direct control of refresh timing. For streaming, recording, or any session involving frequent switching, borderless is the natural starting point, because capture and Alt-Tab reliability matter more than a small latency difference. For multi-monitor work, borderless is the only mode that keeps the second screen genuinely usable. For HDR play, choose the mode whose HDR negotiation is simplest on that machine: exclusive where the game switches cleanly, borderless with the desktop already in HDR where it does not.

None of these starting points is a verdict. The presentation path depends on the game engine, the graphics API, the driver, and the Windows version, so two machines can legitimately disagree about the same game. The reliable method is to test both modes in the same game, in the same scene, with the same V-Sync, frame-cap, resolution, and refresh-rate settings, and to judge by sustained feel and by whether the specific symptom under investigation appears or disappears. A mode chosen by slogan is a guess; a mode chosen by a controlled comparison is a decision.

Six Misconceptions, Corrected

"Borderless is always slower." That described the legacy blt path. On the flip path, the gap is small for most games and disappears for games already using flip presentation. Test rather than assume.

"Fullscreen always means exclusive." On DirectX 12 it does not, and on DirectX 11 with fullscreen optimizations it may not either. The label describes the window state, not necessarily the presentation path.

"VRR cannot work in borderless." It can, on the flip path, when the driver applies VRR to windowed games and the game's swap chain allows it. The historical limitation was real; it is no longer universal.

"Disabling fullscreen optimizations is a free performance upgrade." It is a path change with trade-offs: it restores the old exclusive behaviour, including slow Alt-Tab and capture difficulty. Use it as a test for a specific problem, not as a default.

"A black screen on mode switch means the graphics card is failing." Mode switches stress display negotiation — resolution, refresh rate, and HDR state — and a failure there usually implicates negotiation or settings, not hardware. Hardware becomes a suspect only when the symptom survives across modes, cables, and displays.

"Higher average frame rate in one mode proves that mode is better." Average frame rate hides pacing. A mode with a slightly lower average but steadier delivery feels better than a mode with a higher average and repeated late frames. Judge by sustained feel and by low-frame behaviour.

Frequently Asked Questions

Question: Should I always play in exclusive fullscreen for the lowest latency?

Answer: Not necessarily. On the modern flip path, borderless latency is close to exclusive latency for many games, and the difference is smaller than the difference made by V-Sync settings, frame caps, or overlays. Test both modes in the same game with identical settings, and choose by the result on that machine rather than by the label.

Question: Why does my DirectX 12 game still say "Fullscreen" if there is no exclusive mode?

Answer: The label describes the window state and the resolution and refresh-rate switch, not exclusive display ownership. DirectX 12 games run on the modern presentation path with DWM in ownership, even when the menu says fullscreen. Treat the label as a display-state choice, not as proof of the old exclusive path.

Question: Why does Alt-Tab work instantly in one game and slowly in another, when both say fullscreen?

Answer: One game is likely running through fullscreen optimizations or the flip path, while the other is running the true exclusive path. Check whether fullscreen optimizations are disabled for the slow game's executable, and whether another application grabs focus during the switch. The difference is in the presentation path, not in the label.

Question: Why does VRR work in fullscreen but not in borderless for one game?

Answer: VRR in borderless needs the driver to apply VRR to windowed games and the game's swap chain to allow it. Check the driver setting scope — fullscreen-only versus fullscreen-and-windowed — and whether the windowed-games optimization is on. If VRR works in neither mode, check the display connection and the display's own VRR setting before blaming the mode.

Question: Why does HDR look washed out in borderless but fine in exclusive?

Answer: In borderless the game normally inherits the desktop HDR state, so an SDR desktop with an HDR game produces a mismatch. Run the desktop in HDR before launching the game in borderless, or use exclusive mode where the game switches the display itself. Avoid toggling HDR while the game is running.

Question: Does a second monitor really affect the main game's refresh rate?

Answer: It can, on some configurations, because the desktop compositor serves both displays and moving content on the second monitor keeps composition active. Test with static content on the second monitor, then with it disconnected. If the problem follows the second monitor's activity, close the moving content while playing.

Question: Why does my capture software struggle with exclusive fullscreen but not borderless?

Answer: Capture tools reach borderless frames through the desktop image, while exclusive frames bypass the compositor and can be harder to intercept. Borderless is normally the easier capture target. If stutter appears only while capturing, test with capture off and overlays off separately, because each is a different suspect.

Question: Should I disable fullscreen optimizations for every game?

Answer: No. Disabling it restores the old exclusive path with slow Alt-Tab and harder capture, and it helps only games that misbehave on the optimized path. Use it as a per-game test for a specific symptom, and keep it enabled where it causes no problem.

Getting Help in Hong Kong

If a mode problem survives both modes, matched settings, overlay and capture tests, and a second display test — for example, black screens on every mode switch, or a display that never locks onto any requested mode — the problem may sit below the presentation layer, in the cable, the display, or the graphics hardware. Note which modes were tested, which settings were matched, and what the display does during the switch, and bring the machine in for inspection. HK GPU Fix is at Shek Mun, Dali Plaza, Room 1209. The phone number is 2186 8010 and WhatsApp is 6558 6806. There are no home visits and no Mong Kok shop. Inspection pricing follows the published three-tier range of HK$400 to HK$2,800, with a final quote after inspection.