ControllerTest.io

Controller Polling Rate Test

Not connected
Press a button to connect
InputGamepad APIReads about every 4 ms
Keep turning a stickWith the Gamepad API, only a changed reading counts as a report
Round
0.0 / 10 s
Last 400 expected reports— / 400
—HzReports received per second
ArrivedMissingPausedCell —

Result

Not tested
Polling rate—
—Hz
The tier shows after 10 s
1252505001000200040008000 8421.5.25.125 Browser can't see
Top: tier (Hz)Bottom: interval (ms)
Measured—
Jitter—
Loss—
Gamepad API stops near 250 Hz. Try WebHID

Interval distribution

Time between two reports 0 intervals
Shortest—Median—99%—
The browser reads about every 4 ms, so it can't see shorter intervals
.12580000.2540000.5200011000250042508125
On timeLate, reports missedTier intervalInterval (ms) above, polling rate (Hz) below

Rounds compared

Rounds: 0
#ConnectionPolling rateJitterLoss
1Each round is saved after 10 s———
2Change the cable or USB port———
3Connect over Bluetooth———
4Change the distance to the receiver———
Kept on this page only, cleared on refresh

How to test

About 20 s
01
ConnectWired, Bluetooth or a 2.4 GHz receiver.
02
Use WebHIDPress the button above and pick the controller.
03
Wait 10 sWebHID: hands off. API: turn a stick.
04
Change and repeatRounds stack below.

TipXbox controllers on Windows can't use WebHID; with the Gamepad API, 250 Hz is the browser's ceiling.

How a web page reads controller reports

Two ways

A controller polling rate test measures the time between reports. The controller sends its state over and over at its own rate. With the Gamepad API, the browser takes a reading every few milliseconds; with WebHID, the page gets every report. The chart shows 16 ms of a 1000 Hz controller and how many reports each method catches.

Controller1000 Hz17
Gamepad APIEvery 4 ms5
WebHIDGets every one17
0481216 ms

Gamepad API

Chrome and Edge read about every 4 ms, and an unchanged reading looks like no report, so keep a stick moving. It tops out near 250 Hz, but every browser supports it.

WebHID

The page opens the controller as a HID device and timestamps every report, so the true rate shows even at rest. Chromium browsers only.

Xbox controllers

On Windows they use Microsoft's own driver instead of HID, so they never appear in the WebHID list. Gamepad API only.

Report receivedReport skippedOne browser readHow the signal reaches the page

Polling rate tiers

Interval = 1000 ÷ rate
TierInterval between reportsIntervalGamepad APIWebHIDLimit at this tier
125 Hz 8 ms Yes Yes
250 Hz 4 ms Yes Yes Gamepad API limit: Chrome and Edge read about every 4 ms
500 Hz 2 ms No Yes
1000 Hz 1 ms No Yes USB full-speed limit: one poll every 1 ms
2000 Hz 0.5 ms No Yes Needs USB high-speed
4000 Hz 0.25 ms No Yes
8000 Hz 0.125 ms No Yes USB high-speed limit: 0.125 ms, close to the page's 0.1 ms timer
Log scale: each tier down doubles the intervalThe result is the median interval, rounded to the nearest tier

When the result looks wrong

6 cases
CaseWhat you seeUsual causeWhat to do
Stuck at 250 HzThe API's ceiling; the pad may be fasterTest with WebHID
Far below specWith the API, a still stick sends nothing newKeep turning a stick, or use WebHID
Loss over 1%Interference, or too far from the receiverMove closer, or compare with a cable
High jitterBluetooth, a USB hub or a busy systemUse a rear USB port; close busy programs
Low wired rateSome only run at 125 or 250 Hz wired, or need a setting changedCheck the manual or the maker's app
No WebHIDFirefox and Safari lack it, and Xbox controllers on Windows never show upUse the Gamepad API, or Chrome or Edge
Expected reportsMeasured reportsAfter each change, run another round above

Frequently asked questions

10 questions

What is controller polling rate?

Reports per second

Polling rate is how many times per second a controller sends its state to the computer, in Hz. It's also called report rate. 1000 Hz means a report every 1 ms. The higher it is, the sooner button and stick changes reach the game.

Why does the Gamepad API stop at 250 Hz?

The browser's limit

Chrome and Edge read the controller about every 4 ms, and the Gamepad API only passes that reading on, so it can never show more than 250 Hz. Use WebHID to test the real controller polling rate.

Does WebHID need anything installed?

No

Click the button and the browser lists your devices; this page can only read the controller you pick. You can revoke access in the browser's site settings. Chrome, Edge and other Chromium browsers support it; Firefox and Safari don't.

Can I test an Xbox controller's polling rate?

Gamepad API only

An Xbox controller on Windows uses Microsoft's own driver instead of HID, so it never appears in the WebHID list. Only the Gamepad API works, where 250 Hz is the browser's ceiling.

Why is my third-party controller missing from WebHID?

Try D-input

Many third-party controllers start in XInput mode, which doesn't show in WebHID. Switch to D-input mode, often by holding Home with A or B (see the manual), then press the WebHID button again.

Is Bluetooth or wired faster?

Depends on the controller

Controllers differ a lot: some are faster wired, some over Bluetooth. Bluetooth usually has more jitter and loss. Run one round wired and one over Bluetooth, and compare them in Rounds compared.

Is a higher polling rate always better?

Diminishing returns

From 125 Hz to 1000 Hz, the time between reports drops from 8 ms to 1 ms, a clear difference. Above 1000 Hz each tier saves only a fraction of a millisecond and uses slightly more CPU.

Can this page overclock my controller?

No

A web page can only read reports; it can't change the rate a controller or its USB driver uses. Overclocking needs a driver-level tool. Afterward, run another round here to see the real result.

Why is the result lower than the spec?

Check the method

Use WebHID, check whether the controller needs an app or mode for its top rate, then try a rear USB port.

Is any data uploaded?

No

Report timing is calculated in your browser. Each round stays on this page only and is cleared when you refresh or close it. Privacy policy →