Skip to content
SPYLD.Gaming

Input Lag Explained and How to Reduce It

People chase five milliseconds in the driver while losing forty to a television picture mode. Here is the real budget.

MRMarcus ReyesPC Hardware & Performance Editor· 3 min read·Published · Reviewed by Dan Okafor

The short answer

Total input lag is the sum of peripheral polling, game engine processing, render queue depth, and display processing, with display processing frequently being the largest single contributor on televisions not set to game mode. Capping frame rate slightly below refresh rate and enabling game mode on the display address the two largest sources for most players. Driver-level latency settings produce far smaller improvements than either and should be configured last.

Verified and last updated August 12, 2026.

Time needed
13 min
Difficulty
Intermediate
Read time
3 min

Input lag discussions focus overwhelmingly on the smallest contributors. People agonise over driver settings worth two milliseconds while a television picture mode costs them forty.

Understanding the budget tells you where to spend effort.

Display processing dominates on televisions

A television not in game mode can add more latency than every other source combined. This is the first thing to check and the largest available improvement.

The latency budget

Where input lag comes from, ranked

The bottom two rows are where most discussion happens and where least improvement is available.

Frame rate is the big lever

Each frame is a slice of time during which input is sampled, processed and displayed. Higher frame rate means smaller slices.

Going from sixty to a hundred and twenty frames per second roughly halves that component of the delay. This is why competitive players care about frame rate beyond visual smoothness, and why a lower graphics preset that doubles frame rate genuinely improves responsiveness.

The high refresh guide covers the display side of the same relationship.

The V-Sync question, resolved

Traditional V-Sync holds finished frames until the display is ready, adding up to a full frame of delay. That reputation is deserved for that configuration.

Within a variable refresh rate setup it behaves differently, and the correct arrangement is:

  1. G-Sync or FreeSync enabled on display and driver
  2. Driver V-Sync on
  3. In-game V-Sync off
  4. Frame rate capped three to five below refresh rate

The cap keeps you inside the variable refresh window, where the display adapts to the game rather than the reverse. The latency penalty largely disappears while tearing is eliminated.

Turning driver V-Sync off feels like the low-latency choice and actually allows frames past the window, reintroducing the behaviour you were trying to avoid.

Render queue depth

The processor can run ahead of the graphics card, queuing frames. A deeper queue means older input by the time a frame appears.

Both vendors provide a control: NVIDIA's Low Latency Mode and AMD's Anti-Lag. Both help most when the graphics card is fully loaded with no frame cap.

With a cap already in place the queue is short and the additional benefit is modest. Set the cap first. The NVIDIA settings guide and the AMD guide cover the specifics.

What is not worth your time

Wireless versus wired peripherals. Modern gaming wireless is within a fraction of a millisecond. Bluetooth and generic wireless remain worse; purpose-built gaming wireless does not.

Polling rate above 1000Hz. The returns are far below perception for essentially everyone.

Registry tweaks and optimiser software. No measurable benefit and some cause instability.

The order to work through

  1. Display into game mode. Largest single gain on a television. The HDMI guide covers the related settings.
  2. Raise frame rate, including by lowering graphics settings if needed.
  3. Configure variable refresh rate correctly with a cap.
  4. Enable the driver latency setting.
  5. Stop. Everything past here is noise.

What works

    What doesn't

      Key takeaways

        Frequently asked questions

        What contributes most to input lag?

        For anyone playing on a television, display processing is usually the largest single contributor and can exceed everything else combined if the set is not in game mode. On a monitor already in a low-latency mode, the render queue and frame rate become the dominant factors. Identifying which situation you are in determines where the available improvement is.

        Does a higher frame rate reduce input lag?

        Yes, substantially, because each frame represents a slice of time during which input is sampled and displayed. Moving from sixty to a hundred and twenty frames per second roughly halves that component. This is why frame rate matters to competitive players beyond the visual smoothness it provides.

        Does V-Sync add input lag?

        Traditional vertical sync does, because it holds completed frames until the display is ready, adding up to a full frame of delay. Used correctly within a variable refresh rate setup, with a frame cap keeping you inside the refresh window, the penalty largely disappears. The configuration matters more than whether the setting is on.

        Are wireless peripherals slower than wired?

        Modern gaming wireless is effectively equivalent, with differences measured in fractions of a millisecond that are far below perception. This was a genuine concern years ago and is no longer one for purpose-built gaming peripherals. Generic wireless devices and Bluetooth remain considerably worse.

        About the author

        MR
        Marcus Reyes

        PC Hardware & Performance Editor

        Marcus has been building, breaking and repairing gaming PCs since 2011, first as a weekend favour for friends and then for eight years as a bench technician at an independent repair shop in Portland, where roughly a third of the job was diagnosing machines that "ran fine yesterday".

        CompTIA A+ certified8 years bench-repair experience400+ systems diagnosed and repaired
        All articles by Marcus

        Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.

        Keep reading