Controller Polling Rate Test
Live peak/average rate and estimated interval with a rolling stability chart — compare wired and Bluetooth connections.
Connect your controller via USB or Bluetooth, then press any button on it.
Keep moving the sticks or tapping buttons — the pad must be forced to send at full speed
Readings are the frequency the browser receives, slightly below the hardware output — for reference only.
What is polling rate?
The number of reports a pad sends per second, directly tied to input latency: 1000 Hz = one report every 1 ms, 125 Hz = every 8 ms. For competitive play, higher is snappier.
USB wired · ~1000 Hz
Most stable — the esports choice
2.4G dongle · ~1000 Hz
Near-wired latency
Bluetooth (Xbox) · ~125 Hz
Standard Bluetooth HID default
Bluetooth (PS4/PS5) · ~250 Hz+
Can go higher, but fluctuates
How to measure the true peak
- 01 · Keep inputting
Keep circling the sticks or tapping buttons during the test — idle pads throttle their reports to save power.
- 02 · Watch the chart
The curve should settle into a flat line; big swings usually mean Bluetooth congestion or power saving. Plug in and retest wired.
- 03 · Third-party pads
Stuck at 125 Hz? Try D-Input mode (Home+A/B); enthusiasts can raise USB polling with tools like hidusbf.
About data stability
Browser caveat
Chrome ties input polling to the display refresh rate, so readings sit slightly below the hardware output — perfect for relative comparisons.
Power-saving interference
On battery, Windows throttles USB polling. If numbers look oddly low, plug the laptop in and retest.
Frequently asked questions
Is 1000 Hz really necessary?
For most players 250 Hz (4 ms) is already smooth. FPS (CS2, Valorant) and fighting-game players benefit from 1000 Hz (1 ms) in theory.
Why do I have to keep moving the sticks?
Controller protocols are event-driven: idle pads slow down their reports to save power. Moving the sticks forces full-speed packets and reveals the true peak.
Is 125 Hz over Bluetooth normal?
Completely. Standard Bluetooth HID polls at 125 Hz by default; PS4/PS5 pads can go higher but fluctuate more.
Third-party pad shows almost nothing?
Many third-party pads default to X-Input with a limited rate. Switch to D-Input mode (usually Home+A/B) to unlock full data.
How accurate is this tool?
The Web Gamepad API is capped by browser scheduling. The reading is the frequency the browser receives — slightly below the hardware output — ideal for before/after comparisons.