Average Controller Input Lag: 2026 Benchmark Data

Controller latency is one of the most misunderstood specs in gaming, partly because the numbers manufacturers advertise measure something narrower than what you actually feel. A controller advertising "1ms" is describing its polling interval, not the delay between your thumb moving and something happening on screen, which is a much longer chain.

This piece lays out what the real figures look like in 2026, what each part of the chain contributes, and how to measure your own setup rather than trusting a spec sheet.

What "input lag" actually means

The number that matters to you is end-to-end latency: the total time from your physical input to the resulting change appearing on screen. That's the sum of several stages.

The controller's own processing and polling interval. How often the controller reports its state, and how quickly it registers a press internally.

Transmission to the host. Wired, 2.4GHz dongle, or Bluetooth, each with different characteristics.

Operating system and driver handling. Including any translation layers like Steam Input or DS4Windows.

Game engine processing. The game has to receive the input and act on it, typically on its next update tick.

Render and display. Your frame rate and monitor add the largest share for most people.

The critical insight is proportion. Controller-side latency is genuinely small compared to the display and frame-rate side, which is why obsessing over polling rate while gaming at 60Hz on a slow TV is optimising the wrong end of the chain.

Connection type: the biggest controller-side variable

This is where the meaningful differences sit.

Wired USB is the baseline and consistently the lowest-latency option. It's also the most consistent, which matters as much as the average, since variable latency is more noticeable than slightly higher stable latency.

2.4GHz proprietary dongles have closed the gap substantially. Good implementations now perform close to wired, and several manufacturers advertise sub-millisecond or near-wired figures for their own dongle systems. In practice a quality 2.4GHz connection is effectively indistinguishable from wired for the vast majority of players.

Bluetooth is consistently the slowest of the three and the most variable, typically adding several milliseconds over wired, with more jitter. It's perfectly fine for slower games and couch play, and it's the main reason competitive players avoid it. Our wired vs wireless analysis goes deeper on the mechanics.

The practical hierarchy is simple: wired ≈ good 2.4GHz dongle < Bluetooth. If latency matters to you, the connection choice is worth far more than any spec on the box.

What polling rate actually contributes

Polling rate gets marketed hard, so it's worth doing the arithmetic.

A 125Hz controller reports every 8ms. That's the rate many Xbox-licensed controllers operate at on console, and it's the one polling figure large enough to genuinely matter.

A 1000Hz controller reports every 1ms, the modern PC standard and what most quality controllers now offer over wired or dongle connections.

An 8000Hz controller reports every 0.125ms.

So moving from 125Hz to 1000Hz removes up to 7ms of worst-case delay, which is a real, perceptible improvement. Moving from 1000Hz to 8000Hz removes at most a further 0.875ms, which sits below the threshold most people can detect and well under the duration of a single frame even at high refresh rates.

For context, one frame lasts about 16.7ms at 60fps, 6.9ms at 144fps, and roughly 4ms at 240fps. An 8000Hz polling improvement is a fraction of a single frame at any of those. Our breakdown of 8000Hz polling covers why the marketing outpaces the benefit, including the CPU overhead it introduces.

Console versus PC

An underappreciated distinction. Many Xbox-licensed controllers report at roughly 125Hz when connected to a console, regardless of what they're capable of on a PC. So a controller advertising 1000Hz or 8000Hz polling may deliver a fraction of that on your Xbox.

PlayStation and Nintendo don't publish comparable polling specifications, and console-side input handling is generally less exposed to users than on PC. The practical consequence is that console players have far fewer latency levers to pull: connection type and display are essentially the whole story, and polling rate marketing is largely irrelevant to them.

The layers people forget

Two software factors can dwarf the hardware differences.

Translation layers. Running Steam Input, DS4Windows, or a remapping tool inserts processing between your controller and the game. Usually the cost is small, but stacking multiple layers adds up, and it's one reason our advice elsewhere is to collapse to a single input path. Our input lag optimisation guide covers the chain in detail.

Display and frame rate. A television in a non-game mode can add tens of milliseconds, an order of magnitude more than any controller difference. If you're chasing latency and haven't enabled game mode on your display, that single toggle will do more than any controller purchase.

What players can actually perceive

Worth grounding the numbers in perception, since that's what decides whether a difference is worth paying for.

Human reaction time to a visual stimulus sits in the region of 200 to 250ms for most people, with trained competitive players faster but still far above the millisecond scale. That doesn't mean small latency differences are meaningless, because consistency and feel matter separately from raw reaction speed, but it does set the scale.

What players reliably notice is change and inconsistency rather than small absolute values. Switching from wired to Bluetooth is often perceptible because it's a step change plus added jitter. A controller whose latency varies unpredictably feels worse than one that's consistently a couple of milliseconds slower, because your timing can't adapt to a moving target.

What players generally cannot perceive in blind conditions is a sub-millisecond difference, which is precisely the range 8000Hz polling operates in. That's why the honest framing is that ultra-high polling is a specification rather than an experience, while connection type and display latency are things you can genuinely feel.

The practical upshot: spend effort on the things that produce step changes- connection type, display game mode, frame rate- and treat sub-millisecond specs as tiebreakers at most.

Why published figures vary so much

If you compare latency numbers between sources, you'll find they disagree, and there are legitimate reasons.

Different testers measure different things: some measure controller-to-PC only, others measure full end-to-end to a display. Test rigs, sample games, and frame rates differ. Firmware versions change behaviour. And manufacturers typically quote best-case figures under ideal conditions, on their own dongle, wired, with nothing else connected.

This is why treating any single published number as definitive is a mistake, and why measuring your own setup is more useful than comparing spec sheets. Relative comparisons within one methodology are meaningful; absolute numbers across different methodologies often aren't.

How to measure your own latency

Rather than trusting averages, test your actual setup. An input lag test measures what your controller and connection are delivering, which is the only figure that reflects your hardware, drivers, and connection combined.

The most useful way to use it is comparatively. Test wired, then over Bluetooth, then over your dongle if you have one, and see the difference on your own system. That tells you whether switching connection type is worth it for you far better than any published average, and it also flags problems, since an unexpectedly poor result often points to interference, a bad cable, or a driver issue rather than the controller itself.

Realistic expectations

Pulling it together: controller-side latency differences between a good wired connection and a good 2.4GHz dongle are small enough that most players won't distinguish them. Bluetooth is measurably worse but still perfectly playable for most games. The jump from 125Hz to 1000Hz polling is worth having; the jump beyond that is marginal. And for the overwhelming majority of players, display settings and frame rate contribute more latency than the controller ever will.

If you're a competitive player optimising seriously, go wired, use a 1000Hz-capable controller, enable game mode, run the highest frame rate you can sustain, and keep your input chain free of unnecessary software layers. That combination gets you essentially everything available.