What Is a Good Controller Polling Rate?

Polling rate has become the number controller manufacturers put on the box, the way monitor refresh rate was a decade ago. 1000Hz stickers are now on pads costing less than a takeaway.

The honest answer to what counts as good is less exciting than the marketing: 500Hz is plenty for almost everyone, 1000Hz is a real but small improvement for a narrow set of games, and 125Hz is fine unless you play something where single frames decide outcomes. The bigger issue is that the number on the box frequently is not what the controller actually delivers.

What polling rate actually measures

Polling rate is how often your PC asks the controller for its current state, expressed in hertz. At 125Hz the PC asks 125 times a second, once every 8 milliseconds. At 1000Hz it asks every 1 millisecond.

Between those requests, your PC has no idea what your thumbs are doing. If you press a button just after a poll completes, that press waits until the next one.

That waiting period is the latency polling adds. On average it is half the polling interval, since your input arrives at a random point in the cycle. Worst case is the full interval.

Polling rate Interval Average delay addedWorst case125Hz8ms4ms8ms250Hz4ms2ms4ms500Hz2ms1ms2ms1000Hz1ms0.5ms1ms

Read the right-hand columns rather than the left, because that is where the diminishing returns become obvious. Moving from 125Hz to 250Hz saves you 2ms on average. Moving from 500Hz to 1000Hz saves you 0.5ms. The first upgrade is eight times more valuable than the last one, and both are sold with the same enthusiasm.

Put it next to your frame time

Milliseconds mean nothing in isolation. The comparison that matters is how long a single frame lasts on your setup.

• 60fps: 16.7ms per frame
• 120fps: 8.3ms
• 144fps: 6.9ms
• 240fps: 4.2ms
• 360fps: 2.8ms

Most game engines sample input once per frame. If you play at 60fps, your engine looks at the controller every 16.7ms regardless of whether the controller is reporting every 8ms or every 1ms. The extra reports get discarded.

This is the argument people make for polling rate being marketing nonsense, and it is about 80 percent correct. The remaining 20 percent is worth understanding.

Higher polling does not reduce your average latency much once you are past the frame time, but it does reduce how stale the sample is when the engine grabs it. At 125Hz, the state your engine reads could be up to 8ms old. At 1000Hz, it is at most 1ms old. Average latency barely moves. Consistency improves.

Whether you can feel that depends entirely on what you play.

What is good depends on what you actually play

Single player, anything: 125Hz is genuinely fine. Every console controller of the last fifteen years has shipped around this figure and nobody noticed. If someone tells you your Elden Ring experience is being held back by polling rate, they are selling something.

Competitive shooters: 500Hz is the sensible target. You are chasing consistency rather than raw speed, and the jump from 125Hz to 500Hz removes 3ms of average delay plus most of the variance. 1000Hz adds another 0.5ms, which is real but small.

Fighting games: this is where the case is strongest. At 60fps a one-frame link gives you a 16.7ms window, and some inputs are tighter. An 8ms polling interval can consume half that window on its own. 1000Hz is defensible here in a way it is not elsewhere.

Rhythm games: same logic. Timing windows are narrow and consistency matters more than average latency.

Racing and flight sims: polling rate is largely irrelevant. What matters for these is analog resolution and signal cleanliness, not how often the pad reports.

If you want the underlying mechanics in more depth, our explainer on controller polling rate and the 1000Hz claim goes further into how the numbers are derived.

What your controller probably does

Stock console controllers cluster around 125Hz to 250Hz depending on connection type and firmware. Xbox pads sit near 125Hz on most connections. PlayStation controllers report faster over USB than over Bluetooth. Switch controllers are around 125Hz.

Enthusiast pads from GameSir, Flydigi, GuliKit, 8BitDo and Razer advertise 1000Hz, usually over USB and their own 2.4GHz dongle, with Bluetooth falling back to something lower.

I am deliberately not giving you a precise table of per-model figures, because they change with firmware, they differ between operating systems, and they differ between connection modes on the same pad. A controller advertised at 1000Hz may deliver that only over its bundled dongle, only on Windows, and only after a firmware update.

Measure yours rather than trusting a spec sheet. A polling rate test counts the reports your PC actually receives per second, which is the only figure that matters to you.

Where advertised numbers go wrong

Three ways the box overstates reality.

Reporting rate is not sensor rate. A controller can send 1000 reports per second while its analog-to-digital converter updates the stick position 250 times a second. The other 750 reports contain the same value repeated. You get a fast stream of stale data, which looks identical on a polling rate counter and does nothing for you.

Connection mode changes everything. The advertised figure is usually the best case: wired, or over the proprietary dongle. Bluetooth on the same controller may be a quarter of that. If you play wireless over Bluetooth because it is convenient, the number on the box does not apply to you.

The host has to keep up. A 1000Hz controller behind an unpowered USB hub, sharing a root controller with a busy external drive, will not sustain 1000Hz. Neither will a system under heavy CPU load. Polling is a two-party arrangement.

The number nobody prints: consistency

Here is the thing worth caring about more than the headline figure.

A controller reporting at a rock-steady 250Hz feels better than one nominally at 1000Hz whose intervals wander between 0.8ms and 4ms. Your hands adapt to consistent latency very well and adapt to varying latency very badly. This is the same reason a stable 60fps feels better than an unstable 90.

Almost nobody measures this, because it requires looking at the distribution of report intervals rather than the average, and no manufacturer benefits from publishing it.

You can approximate it at home. Run an input lag test repeatedly and pay attention to the spread of your results rather than the best one. A pad producing results clustered within a few milliseconds is behaving consistently. One producing occasional large outliers has a timing problem, and that problem will bother you more than 4ms of extra average latency ever would.

Wireless, and what it costs

The polling conversation changes over a wireless link.

A proprietary 2.4GHz dongle can genuinely sustain high polling rates and adds very little over wired. This is why premium pads ship with one rather than relying on Bluetooth.

Bluetooth is a different situation. The connection interval is negotiated between the controller and the host adapter, and it is generally slower and more variable than either wired or a dedicated dongle. It also has to share the 2.4GHz band with your Wi-Fi, your neighbours' Wi-Fi, and the broadband noise that USB 3.0 devices emit. Our comparison of Bluetooth versus wired input lag covers the measured difference.

There is also a battery cost. Reporting 1000 times a second uses meaningfully more power than reporting 125 times a second. Several controllers that advertise 1000Hz wireless default to a lower rate to protect battery life, and you have to enable the high rate deliberately in their software. Worth checking if you bought a pad for the spec and never turned it on.

How to get more out of what you have

Before buying anything, work through the free improvements. Polling rate is usually not the limiting factor in a chain that includes your display, your frame rate and your engine's input handling.

Plug wired into a rear motherboard port rather than a front panel header or a hub. Check your controller's software for a polling rate setting you have not enabled. Update firmware, since manufacturers have shipped polling improvements post-launch. If you are wireless, move the dongle away from USB 3.0 devices, ideally on a short extension cable.

Then look at the rest of the chain. Display latency and frame pacing dwarf controller polling for most people. Our guide on input lag optimisation works through the whole path rather than one link in it.

So what should you buy?

If you already own a controller you like, do not replace it for polling rate alone. Measure what it does, enable any higher setting its software offers, and spend the money on your display or your frame rate instead.

If you are buying new and you play competitively, look for 500Hz or better over the connection you will actually use, and treat the presence of a 2.4GHz dongle as more important than the headline number. If you play fighting games, 1000Hz wired is a reasonable thing to want.

If you are buying new and you play everything else, buy on stick quality, build and comfort. Those you will notice every session. Half a millisecond you will not.