Controller Polling Rate Test
This controller polling rate test counts how many reports your gamepad sends each second and shows the result in Hz, with the lowest and highest rate it saw.
Nothing connected yet. Wake your controller with a button press.
—Hz
Milliseconds between reports
- Lowest
- —
- Highest
- —
- Average gap
- —
- Reports counted
- —
- Method
- —
—Hz
Milliseconds between reports
- Lowest
- —
- Highest
- —
- Average gap
- —
- Reports counted
- —
- Method
- —
How to run the controller polling rate test
- Keep a stick moving. With your controller connected, press Start and roll one stick in steady circles. Many controllers stay quiet until something changes.
- Wait five seconds. The page collects every report in that window. Stay on this tab until it ends.
- Read the card. Average, lowest and highest rate land in the Wired or Bluetooth card you picked.
That is how to test controller polling rate on PC with nothing to install. A controller the page cannot see cannot be timed; the controller tester page covers that case.
What is a good polling rate?
250 Hz is good, and above 500 Hz few players feel a difference.
| Polling rate | One report every | Reports per frame at 60 fps |
|---|---|---|
| 125 Hz | 8 ms | 2 |
| 250 Hz | 4 ms | 4 |
| 500 Hz | 2 ms | 8 |
| 1000 Hz | 1 ms | 16 |
A polling rate tester for controllers gives you the first column. The other two show what the number buys: going from 500 to 1000 Hz saves one millisecond. Treat this page as a controller Hz test and match your average to a row.
What a browser can and cannot measure
Chrome and Edge refresh their controller data every 4 ms. The Standard method reads that data, so it stops near 250 Hz: a 1000 Hz controller still shows about 250, and the card says "At browser limit".
The Direct method listens to the device itself and has no such ceiling. Only Chrome and Edge on a computer offer it, and the browser asks your permission first.
This controller polling rate test names the method on every result. Two limits apply to both methods. A controller that only reports changes reads low when the stick pauses. A busy computer bunches reports together, which widens the chart without moving the average.
That is why a result can come out lower than the figure on the box.
Polling rate vs input lag
They are different things. Input lag is the whole trip from your thumb to the picture, and the report wait is one of its four parts.
- 1. Controller Reads the button and builds a report.
- 2. Report wait Up to 8 ms at 125 Hz, up to 1 ms at 1000 Hz. Polling rate sets this part and no other.
- 3. Game Uses the newest report in its next frame: up to 16.7 ms at 60 fps.
- 4. Screen Draws that frame. TVs outside game mode add the most.
So the number above is not a full controller latency test or input lag tester: timing a controller's internal input delay takes a sensor on the button. And if the game moves while your thumb is still, that is drift, which the stick drift test measures.
Wired vs Bluetooth
It depends on the controller, which is why the tool has two cards. Measure on the cable first. Then set Connection to Bluetooth, pair the controller and run it again. Both results stay side by side, and the status line says which link sent more reports.
Do not assume the cable wins: some controllers have a higher polling rate over Bluetooth than over USB. What Bluetooth usually loses is steadiness. A wide gap between Lowest and Highest points to radio interference, so move closer or unplug nearby USB 3 drives.
More controller tests
Frequently asked questions
Is a higher polling rate always better?
No. Past 500 Hz each step saves under a millisecond, and a wireless controller spends more battery to send the extra reports.
Why does my result change between runs?
Report timing is never perfectly even, and your computer handles reports between other work. A swing of a few percent is normal. Run it three times and keep the middle result.
Will this test make my controller faster?
No. The page only listens. The rate is set by the controller's firmware and its connection.
How accurate is a browser polling rate test?
The count is exact for the reports the browser received, and each one is timed to about a millisecond. With the Standard method, a result at 250 Hz may really be faster.