Introduction
In competitive FPS titles, every millisecond counts. Input latency—the delay between pulling a trigger or moving a mouse and the action appearing on screen—directly impacts reaction time, aim precision, and ultimately win‑rate. Studies of elite players show that a 5 ms reduction can shift a player from average to top‑tier performance, especially on high‑refresh‑rate monitors where frame intervals are already razor‑thin.
Windows 11 version 22H2 (2026) introduced Game Mode Pro, an OS‑level scheduler that elevates game threads to the highest CPU priority and synchronizes them with low‑latency GPU APIs such as DirectX 12 Ultimate and Vulkan. By cutting out OS‑induced jitter and aligning GPU command submission with the monitor’s refresh cycle, Game Mode Pro can shave 2–4 ms off the end‑to‑end input path, a tangible gain for FPS pros.
- Elevates game‑related CPU threads above background processes.
- Locks GPU command buffers to low‑latency pathways (DirectX 12 Ultimate, Vulkan).
- Reduces scheduler pre‑emptions that cause frame‑time spikes.
By enabling Game Mode Pro, you’ll see a measurable drop in input latency using tools like NVIDIA Reflex Analyzer or the Windows Latency Analyzer. The next sections will walk you through the exact registry tweaks, Power‑Plan adjustments, and validation steps to confirm you’re consistently hitting the lowest possible numbers on titles like Counter‑Strike 2, Valorant, and Apex Legends.

Step 1: Enable Game Mode Pro in Windows Settings
Game Mode Pro is the core of Windows 11’s latency‑reduction pipeline. By telling the OS to prioritize your foreground game, it locks CPU cores, defers background tasks, and synchronizes the graphics scheduler to the monitor’s refresh window. The result is a measurable drop of 2‑4 ms in input lag for titles like Valorant, CS2, and Overwatch 2—enough to swing a clutch round.
- Open **Settings** (Win + I).
- Navigate to **Gaming → Game Mode**.
- Toggle **Game Mode Pro** to **On**. The switch will read “Enabled – Optimized for competitive play”.
- Click **Apply** if prompted, then close Settings.
After activation, verify the feature is live by opening **Task Manager** → **Performance** → **GPU**. You’ll see a new “Game Mode Pro” line indicating the OS has switched the power‑profile. For an extra sanity check, launch a supported FPS, open the in‑game console, and run the built‑in latency counter (e.g., `net_graph 1` in CS2). The displayed “Input latency” should drop compared to a baseline run with Game Mode Pro off.

Step 2: Configure Advanced Scheduler Settings
The next lever in Windows 11 Game Mode Pro is the Advanced Scheduler. By tightening the OS’s timing granularity and telling the scheduler which cores should carry the game’s most latency‑sensitive threads, you can shave a measurable fraction of a millisecond off every shot. ExtremeTech measured that forcing the timer resolution down to 1 ms trims roughly 0.5 ms of input lag, while Tom’s Hardware showed a consistent boost when the process is pinned to the high‑performance P‑cores on a 13th‑gen Intel chip.

Here’s the exact sequence you’ll click through:
- Open Settings → Gaming → Game Mode Pro → Advanced Scheduler.
- Set **Timer Resolution** to the minimum 1 ms value.
- Click **Set CPU affinity** and select only the high‑performance cores (e.g., Intel P‑cores 0‑7).
- Slide the **Maximum CPU usage** knob up to 100 %.
After applying the settings, run a latency‑meter such as Nvidia Reflex Analyzer or the built‑in Counter‑Strike: 2 latency test. You should see a drop of 0.4–0.6 ms compared to the default configuration, which translates to a tighter 1‑tick window in 120 Hz competitive play. If the numbers don’t move, double‑check that the game’s process is indeed bound to the selected cores (Task Manager → Details → Right‑click → Set affinity). Keeping the “Maximum CPU usage” at 100 % prevents Windows from scaling the cores down during sudden spikes, ensuring the scheduler can deliver the 1 ms ticks consistently.
Step 3: Apply Power‑Plan Tweaks for Consistent Boost
A stable power plan is the backbone of any low‑latency setup. Windows 11’s default “Balanced” profile inserts a five‑minute idle timeout that can trigger micro‑stutters just when you need a smooth frame‑rate. Switching to the “High performance” plan removes that timeout, keeping the CPU and GPU at full throttle and shaving a few precious milliseconds off input lag.
- Open Settings → System → Power & battery → Additional power settings.
- Select **High performance**. If it’s hidden, click **Show additional plans**.
- Click **Change plan settings** → **Change advanced power settings**.
- Under **Processor power management**, set **Minimum processor state** to **100 %** and **Maximum processor state** to **100 %**.
- Expand **Graphics settings**, choose **Maximum performance** for your GPU.
After applying the tweaks, run a latency benchmark (e.g., NVIDIA Reflex Analyzer or AMD Radeon™ Chill test) while playing a competitive title like *Valorant* or *CS2*. Record the average input‑to‑display time, then repeat the test with the default plan. You should see a consistent 2‑4 ms reduction, confirming that the CPU no longer throttles and the GPU stays in its highest performance state.

Step 4: Pair with GPU Low‑Latency APIs
GPU‑level latency reducers are the final piece of the low‑input‑lag puzzle. NVIDIA Reflex and AMD Low‑Latency Mode sit directly in the driver stack, cutting the time a frame spends in the GPU queue before it hits the screen. When both Reflex and Windows 11 Game Mode Pro are active, the NVIDIA Reflex Analyzer records an average 1.2 ms reduction in Counter‑Strike 2. AMD’s Ultra Low‑Latency Mode trims frame‑time variance by roughly 0.8 ms on supported titles.
- Open **NVIDIA Control Panel** → **Manage 3D Settings** → **Global Settings**.
- Find **Low Latency Mode** and set it to **On** (or **On + Boost** for extra head‑room).
- Launch your FPS, open the in‑game graphics menu, and enable **NVIDIA Reflex** (often labeled “Reflex Low Latency”).
- Run the **Reflex Analyzer** overlay to confirm the 1.2 ms gain.

For AMD users, open **Radeon Software**, navigate to **Graphics → Advanced**, and switch **Low Latency Mode** to **Ultra**. Then, in the game’s graphics settings, toggle the AMD Low‑Latency option if it appears. The “Ultra” preset forces the driver to prioritize the most recent frame, shaving about 0.8 ms off the overall latency budget. Remember to keep the driver updated; each release refines the timing model used by the API.
Finally, validate your setup. Use the built‑in frame‑time counters in the game or external tools like **RTSS** to log average frame time and its variance. Compare a run with Game Mode Pro + Reflex/Low‑Latency enabled against a baseline run without them. You should see a tighter distribution and the millisecond‑level improvements quoted above—exactly the edge competitive FPS players need.
Step 5: Validate Latency Gains with Benchmark Tools
Before you declare victory, you need hard data to prove that Game Mode Pro actually trimmed your input lag. The most reliable way is to capture three independent measurements: Windows Performance Recorder (WPR) for OS‑level latency, NVIDIA Reflex Analyzer for GPU‑to‑display timing, and any built‑in in‑game overlay (e.g., Valorant’s 1‑ms counter). By comparing pre‑ and post‑tuning numbers, you can quantify the exact millisecond savings and verify that no regression slipped in.
Start WPR with the “Input Latency” profile (found under **Performance → Latency**). Click **Start**, perform a short 30‑second warm‑up in your target FPS, then click **Stop**. The generated .etl file can be opened in Windows Performance Analyzer, where the “Keystroke → GPU Submit” column shows sub‑millisecond values. Record a baseline run, apply your Game Mode Pro tweaks, and repeat the capture. Look for a consistent drop of 0.5 ms – 1.2 ms across the two runs; that’s the sweet spot most competitive players chase.
Next, fire up NVIDIA Reflex Analyzer (available through GeForce Experience). With the analyzer attached, run a 1‑minute match and note the “Average Reflex Latency” reading. Because Reflex measures the full path from input device to pixel, it validates that your OS‑level gains translate to real‑world FPS performance. Finally, enable the game’s native latency overlay (most eSports titles expose a toggle in the settings) and capture a quick screenshot during a high‑intensity firefight. Cross‑reference these three data points; if they all show a reduction, you’ve successfully tuned the pipeline.
- Run WPR with the "Input Latency" profile and save the .etl file.
- Open the file in Windows Performance Analyzer; record the Keystroke → GPU Submit time.
- Launch NVIDIA Reflex Analyzer, capture a 1‑minute latency sample.
- Enable the in‑game latency overlay and take a screenshot during peak action.
- Compare baseline vs. post‑tuning numbers; aim for ≥0.5 ms reduction across all tools.
Step 6: Troubleshoot Common Pitfalls
Even with Game Mode Pro fully enabled, hidden culprits can silently re‑introduce latency. Windows continuously runs telemetry threads that monitor performance counters, and many gamers forget that these background tasks can spike CPU usage during a match. Likewise, third‑party overlays—Discord voice chat, OBS streaming panels, or even in‑game voice‑chat apps—often spin up their own rendering loops, pulling the scheduler out of the low‑latency path you configured in Steps 1‑5.
- Open **Task Manager** → **Details** and locate `GameBar.exe`, `GameModeService.exe`, and any telemetry‑related processes (e.g., `DiagTrack.exe`). Right‑click → **End task** and set **Startup type** to **Disabled** via Services.
- Navigate to **Settings → Privacy & security → Diagnostics & feedback**. Switch **Diagnostic data** to **Required only** and turn off **Tailored experiences**.
- In **Settings → Gaming → Xbox Game Bar**, toggle **Open Xbox Game Bar using this button** off to stop the overlay from auto‑launching during gameplay.
Next, audit every overlay you run. Microsoft explicitly notes that “third‑party overlay software (e.g., Discord, OBS) can re‑activate background threads that negate Game Mode Pro benefits.” Disable the overlay while testing latency, then re‑enable it one at a time to isolate the offender. For Discord, turn off **Hardware Acceleration** under **Advanced → Hardware Acceleration**; for OBS, set **Process Priority** to **Below Normal** and enable **Game Mode Compatibility** in the **Settings → Advanced** tab.
Third‑party overlay software can re‑activate background threads that negate Game Mode Pro benefits.
Finally, verify driver parity. A mismatched GPU driver (e.g., a legacy version that doesn’t expose Reflex hooks) will cause Windows to fall back to the generic scheduler, wiping out your latency gains. Always run the latest WHQL‑certified driver from NVIDIA, AMD, or Intel, and double‑check that the driver’s **Game Ready** profile is active for your title. After cleaning up telemetry, silencing overlays, and confirming driver alignment, re‑run your latency benchmark (Step 5) to see the true impact of Game Mode Pro.
Conclusion & Next Steps
When Game Mode Pro is paired with NVIDIA Reflex, top‑tier FPS pros consistently shave 1–2 ms off their input pipeline—a margin that can flip the outcome of a 1‑v‑1 clutch on maps like Mirage or Bind. The 2026 esports latency study logged identical gains across five major titles, confirming that the Windows‑level scheduler and GPU‑level reflex sync work in harmony rather than at cross‑purposes.
Now is the time to put those numbers to the test on your own rig. Run the same suite of tools from Step 5—LatencyMon, FCAT, and the in‑game Reflex counter—both before and after applying the guide. Record the median frame‑to‑action time, then compare it against your baseline. If you see a consistent sub‑2 ms drop, you’ve unlocked the core benefit of Game Mode Pro.
Beyond the OS and GPU tweaks, a truly competitive setup squeezes every other source of delay. Consider the following next‑level actions to push latency even lower:
- Deploy a wired Ethernet connection and enable QoS on your router to prioritize game packets.
- Upgrade to a 240 Hz (or higher) low‑response panel with G‑Sync/FreeSync and enable ULMB or LFC for smoother frames.
- Fine‑tune Windows’ network stack: disable Large Send Offload, enable “Low‑Latency Mode” in the NIC driver, and set the TCP/IP auto‑tuning level to “highly restricted.”
- Use a dedicated USB polling rate of 1000 Hz for mouse and keyboard, and lock their DPI to a constant value.
Each of these steps adds a few tenths of a millisecond, but in the razor‑thin margin of elite FPS play, they add up. Keep a log of your latency readings after every tweak, and you’ll build a data‑driven roadmap that keeps you ahead of the meta.