Lower end-to-end input lag in competitive games on Windows 11 25H2 by tuning display mode, GPU scaling and background apps - measuring after each change.
Do not enable AMD Anti-Lag+ in multiplayer titles with anti-cheat; the standard Anti-Lag option is safe. Competitive game anti-cheat policies change - check the publisher's current statement before enabling third-party tuners.
Input lag in competitive games on Windows 11 25H2 comes mostly from **compositor overhead**, **mismatched refresh rate** and **unbounded FPS**. Switch to true fullscreen, enable low latency mode and cap FPS below your refresh - and measure every change.
In your game, enable the on-screen latency readout (CS2: Settings → Video → Advanced; Fortnite: Settings → Game → Latency Markers). Note the current end-to-end latency on a representative map. If the game lacks a readout, use the NVIDIA app overlay's PC latency metric.
Open **Settings → System → Display → Advanced display**. Set the refresh rate to the monitor's highest value. Running the desktop at 60 Hz while the monitor supports 240 Hz is a common silent regression after an update.
In the game's video settings, prefer **Fullscreen (Exclusive)** when available. On 25H2 the DWM compositor is efficient, but exclusive fullscreen still shaves a frame of latency in most engines. For games that only offer Borderless, go to the next step.
In the NVIDIA app → **Graphics → Program Settings**, enable **Low Latency Mode: Ultra** for the game. In AMD Software → **Gaming → Game profile**, enable **Radeon Anti-Lag**. Both cap the render queue and typically remove one full frame of latency.
If your GPU can push 400 FPS on a 240 Hz display, uncapped frames pile up in the queue and add latency. Cap FPS at (refresh - 3), so a 240 Hz display caps at 237. Set the cap in-game first; use RTSS or the vendor driver as a fallback.
Discord overlay, browser hardware acceleration, OBS preview and RGB software can all steal GPU time slices. Close them for your test, re-measure, then decide which ones to keep off during competitive sessions.
Open **Settings → Gaming → Game Mode** and confirm it is On. Then **Settings → System → Display → Graphics → Change default graphics settings** and leave **Hardware-accelerated GPU scheduling** at its current state - test both and keep whichever measures lower latency on your game.
Return to the same map and read the latency metric. Compare to baseline. Save your in-game video config and the NVIDIA/AMD per-game profile so a driver update that resets them is easy to restore.
Drop to Low Latency Mode: On instead. Ultra is more aggressive and costs a few percent FPS on GPU-bound games.
RTSS must be running before the game launches. Add RivaTuner Statistics Server to Windows startup, or set the cap in-game instead.
Open Task Manager → Processes during a match and sort by GPU. A background updater or antivirus scan is likely spiking at the same moment.
VBS has a small CPU cost but no measurable input lag impact in current builds. Leave it on for security; it is not the right lever.
They are equivalent at the same refresh and resolution. The cable does not add measurable lag.
Modern 2.4 GHz wireless gaming mice (Logitech Lightspeed, Razer HyperSpeed) are within 1 ms of wired. Bluetooth mice are not.
In the NVIDIA app or AMD Software, open the game's profile and reset Low Latency Mode / Anti-Lag to Default (or Off). Remove any RTSS or driver-level FPS cap. Return the display refresh rate to what you had before in Settings → System → Display → Advanced display. Re-enable background apps you closed from their startup settings.
Free · no account needed · tracks your progress