Controller polling rate test.

Free controller polling rate test for competitive gaming

Use this tool as a quick comparison between wired and wireless setups. The result is based on browser-visible Gamepad API frames and should be read as an estimate.

How the controller polling rate test works

Move a stick or press a button while the Gamepad API reports fresh frames. Controller Checker estimates samples per second from those timestamps and displays an approximate interval in milliseconds.

Keep the browser tab visible and move a stick continuously long enough to build a stable sample. Repeat the test rather than trusting the first peak value. Browser animation cadence and timer precision can cap or cluster readings even when the controller's underlying USB report rate is higher.

Wired versus Bluetooth controller polling rate and latency

USB, Bluetooth, 2.4 GHz adapters, operating-system scheduling, and browser frame timing all affect what this page observes. Compare the same controller and browser rather than treating the estimate as a universal hardware specification.

• Use the same USB port, receiver position, browser, and sample duration
• Keep wireless battery level and nearby radio interference consistent
• Compare average and stability, not only the highest reported Hz

Why polling rate is not the same as controller input lag

Polling rate describes how often input is reported. End-to-end latency also includes scan time, transport, game engine processing, display refresh, and rendering.

How to read controller Hz and millisecond report intervals

A theoretical 125 Hz interval is 8 ms, 250 Hz is 4 ms, 500 Hz is 2 ms, and 1,000 Hz is 1 ms. Browser-observed results can differ from those ideal values. A stable lower rate can feel more consistent than an unstable peak, and a high polling number alone does not prove lower end-to-end delay.

Frequently asked questions

Short, practical answers to help you read this test result and decide what to do next.

What is a good polling rate for a controller?

Most standard controllers report around 125 Hz, an 8 ms interval, while some wired or overclocked gamepads reach 250 Hz, 500 Hz, or 1,000 Hz. A stable, consistent rate usually feels better than an unstable high peak, so compare average and stability rather than the single highest number.

Is controller polling rate the same as input lag?

No. Polling rate is how often the controller reports input. End-to-end input lag also includes switch scanning, wireless transport, operating-system scheduling, game processing, rendering, and display response. A higher polling rate can reduce one part of that delay but does not guarantee a faster full response.

Why does my controller polling rate test show a lower number than advertised?

The test measures what the browser observes through the Gamepad API, which is capped by browser frame timing, animation cadence, and timer precision. The controller's raw USB report rate may be higher than the browser-visible value, especially over Bluetooth.

Does Bluetooth lower controller polling rate compared to USB?

Often yes. Bluetooth adds scheduling and radio overhead that can reduce the browser-visible report frequency and stability. For the highest and most consistent reading, test the same controller over a wired USB connection.