Polling rate is how many times per second your controller reports its state to your PC, measured in hertz. A 1000Hz controller updates every millisecond; a 125Hz controller updates every 8 milliseconds. This page measures your controller's input event frequency in the browser — with one important caveat about what browsers can and cannot see, explained honestly below.
What is polling rate?
Every USB or wireless controller re-sends its full input state — every button, stick, and trigger — on a fixed schedule. That schedule is the polling rate. At 125Hz the state refreshes 125 times per second (once every 8ms); at 1000Hz it refreshes every single millisecond. Higher rates mean the PC learns about your inputs sooner.
Polling rate is only one slice of total input delay. Your button press also travels through the controller's firmware, the USB or Bluetooth stack, the operating system, the game engine, and finally the display — each adding its own milliseconds. Upgrading from 125Hz to 1000Hz saves at most 7ms, which matters in competitive shooters and is invisible everywhere else.
Do not confuse polling rate with report rate marketing. Some controllers advertise "1000Hz polling" but only achieve it over wired USB, dropping to 125–250Hz on Bluetooth or 2.4GHz dongles. Always test in the connection mode you actually play in.
Can a browser really measure polling rate?
Honestly: no, not the true USB polling rate. Browsers cannot read USB descriptors or endpoint intervals — the W3C Gamepad API exposes the controller's input state but says nothing about how often the hardware reports it. Any website claiming to show your exact USB polling rate is estimating, not measuring.
What this page does measure is input event frequency: how often the browser observes the controller's state changing while you wiggle a stick or mash a button. On a wired 1000Hz controller in Chrome, you will typically see readings clustering near 1000 events per second; on a standard 125Hz controller, near 125. It is a useful approximation, not a laboratory instrument.
Two things skew the reading. First, the browser samples the Gamepad API on its own schedule (usually tied to the display refresh via requestAnimationFrame), so the number reflects the browser's observation rate as much as the hardware. Second, Bluetooth controllers often report at lower effective rates than their USB spec sheet claims. Treat the result as comparative — great for A/B testing wired versus wireless on the same controller — rather than absolute.
What polling rate do I need?
125Hz is the long-standing console standard, and it is fine for the overwhelming majority of play. At 8ms per update, polling contributes less delay than a typical 60Hz display frame (16.7ms) or average human reaction time (around 200ms). If you play casually or on console, you already have enough.
250–500Hz is the sensible enthusiast range on PC. Many modern controllers and adapters land here, shaving 4–6ms off the 125Hz baseline with no downsides. This is where diminishing returns begin: each doubling of the rate saves half the milliseconds of the previous doubling.
1000Hz is for competitive players chasing every millisecond in shooters and fighting games. The 7ms saved over 125Hz is real but small — roughly 3.5% of a typical human reaction time. It is worth having if your hardware supports it, but it will not fix bad aim, and it never compensates for a high-latency display or a drifting stick (rule that out first with a stick drift test).
How to reduce input delay?
Use a wired USB connection. It is the single biggest, cheapest latency win: wired eliminates Bluetooth's variable 7–15ms transport delay and usually unlocks the controller's maximum polling rate at the same time. Competitive players who must go wireless should prefer 2.4GHz dongles over Bluetooth.
Next, cut display and software delay, which dwarf polling differences. Enable your monitor's low-latency or game mode, disable vsync where tearing is tolerable (or use variable refresh rate), and close background apps that compete for CPU — streaming software and browser tabs with video are common culprits.
Finally, verify instead of guessing. Run the full gamepad tester to confirm every input registers cleanly, then work through our fix controller input lag guide for the complete checklist, from USB ports to in-game settings.
Frequently asked questions
Is 1000Hz polling always better than 125Hz?
Technically yes, practically it depends. The 7ms advantage is real but tiny next to display latency and human reaction time. On a 60Hz TV with vsync on, you will never feel the difference. On a 240Hz monitor in a competitive shooter, it is one more small edge stacked with others.
Why does my 1000Hz controller show ~125Hz on Bluetooth?
Because Bluetooth rarely sustains high polling rates. Most controllers drop to 125–250Hz effective over Bluetooth regardless of what the box advertises for wired mode. This is normal and expected — test over USB if you want the headline number.
Does overclocking my controller's polling rate help?
Tools like DS4Windows can push some controllers above their stock rate, but gains follow the same diminishing curve, and overclocking can introduce instability or get flagged by anti-cheat in rare cases. Try it only after you have fixed the bigger delays: connection type, display settings, and background load.
Does polling rate affect stick drift?
No. Polling rate is about how often the controller reports; drift is about what it reports — a false position from a worn sensor. A drifting stick at 1000Hz just reports its wrong position a thousand times per second. Diagnose drift separately before chasing latency numbers.