GamePad Gauge

Controller Polling Rate Test

Measure how frequently your browser receives updated controller input. Check observed Hz, timing intervals, and jitter for wired, Bluetooth, and wireless gamepads.

Connect your controller and press any button.

What is controller polling rate?

Polling rate is how often a controller's input state is reported, measured in Hz (updates per second). A polling rate of 125 Hz means roughly one update every 8 ms; 1000 Hz means roughly one update every 1 ms. That theoretical hardware rate is different from what a browser can actually observe — this tool reports the latter, labeled throughout as the observed update rate and observed update interval.

How to test your controller polling rate

  1. Connect your controller by USB, Bluetooth, or 2.4 GHz receiver.
  2. Optionally select its connection type above.
  3. Click Start 10-Second Test.
  4. Continuously rotate an analog stick for the full 10 seconds.
  5. Read the observed Hz and interval results.

How to read your results

Observed Hz is how many meaningful input updates your browser saw per second. Median interval is the typical gap between updates — a steadier, more useful number than the average when a few slow frames skew things. P95 intervalshows the gap that 95% of updates were faster than, which surfaces occasional slowdowns without being dominated by rare, extreme spikes.Jitter (median absolute deviation) describes how consistent the timing was — low jitter means a steady cadence, high jitter means the interval between updates varied a lot.

Controller polling rate vs input latency

Polling rate is only one link in the chain that makes up total input latency, which also includes game engine processing, rendering, and display response time. A higher polling rate can shorten the time between a physical input and when it's reported, but it doesn't by itself determine how quickly that input appears on screen — a controller with a very high polling rate can still feel no faster in a game bottlenecked elsewhere.

Wired vs Bluetooth controller polling rate

Connection method affects both the achievable update rate and its consistency. Wired (USB) connections generally support a higher, steadier rate. Bluetooth adds its own scheduling and radio overhead, which can lower the observed rate and increase jitter, particularly with wireless interference nearby. Actual behavior also depends on the controller model, operating system, and browser — run this test over both connections on your own hardware to compare.

Why does my controller show only 60 Hz, 120 Hz, or 144 Hz?

Browsers typically read gamepad state once per rendered frame, so the observed rate is effectively capped by your display's refresh rate and the browser's own frame loop — shown above as the browser refresh estimate. If your observed rate lands close to that ceiling, the controller's true hardware polling rate may well be higher than what the browser can report.

PS5 / DualSense controller polling rate

DualSense controllers support both USB and Bluetooth connections, and browser-observed behavior can vary meaningfully between them, as well as by operating system and browser. Rather than quoting a single guaranteed figure, run this test with your own DualSense over both connection types to see how it behaves on your setup.

Xbox controller polling rate

The same applies to Xbox controllers: wired and Bluetooth connections can produce different browser-observed rates depending on your OS and browser. Test both connection methods if you want to compare them directly rather than relying on a manufacturer-quoted number that a browser can't fully verify.

Which controllers does this work with?

Any of them. Unlike tools that rely on a recognized button layout, this test only tracks how often the browser observes a change inany reported axis or button — it doesn't need a "standard" mapping to work. That makes it brand-agnostic: Xbox, PlayStation, Nintendo Switch Pro Controller, and generic or off-brand USB/Bluetooth gamepads can all be tested the same way. If a controller doesn't connect at all, that's a detection issue rather than a mapping one — see Why Isn't My Controller Detected in the Browser?

Browser polling-rate test limitations

This tool cannot access raw USB HID data, so it can't measure true hardware interrupt frequency or end-to-end latency. Results reflect what the Gamepad API exposes through requestAnimationFrame, bounded by your display's refresh rate and general browser/OS scheduling. Treat the numbers here as a consistent way to compare connections and sessions on the same machine, not as an absolute hardware measurement.

Check every button, trigger, and analog stick with the Gamepad Tester. If the controller moves by itself near center, run the Stick Drift Test. Measure how far a stick must move before input begins registering with the Controller Deadzone Test. For what Hz actually measures and why a browser can't see the raw hardware number, read Controller Polling Rate Explained.

FAQ

What is a good polling rate for a controller?

For most players, anything from 125 Hz to 250 Hz feels smooth and is what wired Xbox and PlayStation controllers typically achieve. Higher figures like 1000 Hz are marketed mainly for competitive PC play, but the practical difference shrinks once display refresh rate and game engine timing are factored in.

How do I test my controller polling rate?

Connect your controller, optionally select its connection type above, click Start 10-Second Test, and continuously rotate an analog stick for the full window. The tool reports how often your browser observed a change in the controller's reported state.

Can a browser accurately test controller polling rate?

Not the raw hardware rate, no. A browser can only report how often it observes updated controller input through the Gamepad API, which is shaped by browser scheduling and display refresh rate. This tool measures that browser-observed rate, not the controller's true USB polling frequency.

Why does my 1000 Hz controller show only 144 Hz?

Browsers typically read gamepad state once per animation frame, so the observed rate is capped near your display's refresh rate — 60, 120, or 144 Hz, for example — even if the controller itself reports to the OS far more often.

Does a higher controller polling rate reduce input lag?

It can reduce one small part of total input lag, but polling rate is only one link in a chain that also includes the game engine, rendering pipeline, and display response time. A higher polling rate alone doesn't guarantee lower overall latency.

Is controller polling rate the same as input latency?

No. Polling rate describes how often new input state is reported. Input latency is the total time from a physical action to its effect appearing on screen, which polling rate contributes to but does not fully determine.

Is wired faster than Bluetooth for controllers?

Wired connections are generally more consistent and often support a higher update rate than Bluetooth, which can introduce more variable timing. Actual results depend on the controller, OS, and browser — run this test on both to compare your own hardware.

Can I test a PS5 DualSense controller?

Yes. Connect it over USB-C or Bluetooth and run the test. Browser-observed behavior for DualSense can vary by connection method, operating system, and browser, so results may differ between a wired and Bluetooth run.

Can I test an Xbox controller?

Yes. Xbox controllers work over USB or Bluetooth with any browser that supports the Gamepad API. Follow the same steps — connect, select connection type, and run the 10-second test.

Can I increase my controller polling rate?

Some controllers support higher native polling rates over USB via manufacturer software or firmware settings, and a wired connection generally allows a higher and steadier rate than Bluetooth. This tool can only show what your browser observes, not adjust the controller itself.