It's a chain, not one setting
Fix the big three first: Reflex on, V-Sync off with FPS capped just under your refresh, and Windows actually running your monitor at its real refresh rate. Those are the first checks that usually matter most.
Input lag isn't one setting — it's a chain, from the moment you move your mouse to the moment a new frame hits your eye. Every link adds milliseconds. Most guides throw 20 tweaks at you with no sense of which ones matter. Here they are, ranked by how much they actually move the needle.
🥇 The big three (do these first)
Turn on Reflex / GPU low-latency mode
If your game has NVIDIA Reflex (or the AMD/Intel version), turn it on. It stops the GPU from queuing frames ahead of your inputs — the single biggest, easiest latency win there is, bigger than any registry tweak.
V-Sync off, cap FPS just under your refresh
For a competitive low-latency baseline, start with V-Sync off and cap your framerate a few FPS below your refresh (e.g. 141 on a 144 Hz panel) if your display tears. If you use VRR, follow the sync mode recommended for your monitor and GPU instead of copying a blanket setting.
Actually run your monitor at its real refresh rate
Sounds obvious, but Windows quietly defaults plenty of 144/240 Hz monitors back to 60 Hz. Check Display Settings → Advanced display. Going 60 → 240 Hz alone removes more felt lag than every micro-tweak combined.
✅ The small stuff (real, but minor)
- Mouse polling rate — 1000 Hz is plenty. Chasing 4000/8000 Hz can cost more CPU than the latency it saves.
- Frame pacing / stutter — steady frametimes feel lower-latency than a high-but-spiky average. Smoothing your 1% lows beats chasing peak FPS.
- Background load — a maxed-out CPU delays your inputs. Close the real hogs (not "every background app").
- Wired peripherals + a good USB port — wireless is fine these days, but a flaky port or hub adds jitter.
🚫 What doesn't help (skip it)
- Random "input lag" registry packs — mostly do nothing measurable.
- Sketchy mouse "acceleration fix"
.regfiles — often just break things. - Disabling services wholesale — no measurable latency win, plenty of collateral.
If a fix can't tell you which millisecond it removes, be skeptical.
🧭 Use Optimizationmaxxing for the last mile
Open Optimizationmaxxing, run Diagnostics first, and keep the before numbers. Browse Tweaks one at a time, read the source and recovery path, apply only what matches your hardware, then check Your Tune after a real game. Snapshot-backed changes can be rolled back from the app when the result is not worth keeping.
The practical rule: start with Reflex, your sync mode, and your real refresh rate — get those right before touching anything advanced. The fiddly remaining edge cases (DPC latency, frame pacing, power-plan behavior) are what Optimizationmaxxing is for: it probes your actual latency, applies only documented changes, and snapshots each so you can roll back.