A wired DualSense, an Xbox pad over Bluetooth, and a generic USB controller all show different numbers in an online controller Hz test - and a low reading rarely means the controller is broken.
I published the full guide on KeyboardTester.click with the live gamepad tester, the honest browser-cap caveat, per-platform Hz tables, the wired-only overclock paths, source links, FAQ schema, and localized versions:
Controller Polling Rate Test: Check Your PS5/Xbox Hz (USB vs Bluetooth)
This Dev.to version keeps the practical diagnosis workflow.
Fast answer
Open the Gamepad Tester, connect your pad by USB or Bluetooth, press a button to wake the Gamepad API, then rotate a stick for 6-10 seconds and read the Hz panel.
One honesty note that most clone tools skip: the browser shows the effective in-browser update cadence (roughly 60-250 Hz, capped by the animation frame) plus jitter - not your controller's true USB hardware poll rate. Use it to compare connections and spot instability. For the real hardware number, check the controller spec.
Why the browser cannot read true 1000 Hz
A browser cannot read the USB bus directly. It reads how often the Gamepad API hands fresh controller data to the page, and that is gated by requestAnimationFrame. So even a pad reporting 1000 Hz to the OS will read far lower in any browser tool. The on-screen number is great for comparison and jitter, not for certifying hardware Hz.
Real polling tiers (hardware-level, from vendor and community testing)
| Controller | Typical USB Hz | Typical Bluetooth Hz | Notes |
|---|---|---|---|
| PS5 DualSense | ~250 Hz (up to ~1000 Hz via PC tools) | ~125-250 Hz | Native USB is ~250 Hz; PC tools push wired polling higher |
| PS4 DualShock 4 | ~250 Hz (1000 Hz via PC tools) | ~125-250 Hz | Classic DS4Windows / HIDUSBF wired-overclock target |
| Xbox Series / One | ~125 Hz | ~60-125 Hz | No reliable software overclock; wireless adapter beats Bluetooth |
| Switch Pro Controller | ~125 Hz | ~125 Hz | Fixed on console; ~125 Hz range on PC |
| 8BitDo / GuliKit (Hall) | ~250-1000 Hz (model dependent) | ~125-250 Hz | Some 2.4 GHz/wired models advertise 1000 Hz - verify per model |
| Generic USB gamepad | ~100-125 Hz | n/a | Budget pads often sit near 100-125 Hz regardless of marketing |
USB vs Bluetooth vs dongle
- Wired USB: most consistent and the right mode for any high-polling test. Use a direct motherboard/laptop port, not a hub.
- Bluetooth: convenient but usually lower and more variable. Do not judge a controller's ceiling from a Bluetooth reading.
- Xbox Wireless Adapter: steadier than Bluetooth on PC. Not a software overclock, just a better link.
- 2.4 GHz dongle (third-party): the advertised Hz only applies through that dongle, not Bluetooth.
Can you overclock a controller?
Only on PC, and only wired.
- DS4Windows - DualSense / DualShock 4, sets a higher poll interval (often 1000 Hz) at the desktop-driver level. Wired only; it does not change console behavior.
- HIDUSBF - a low-level filter driver that raises the USB poll interval on many wired HID pads. Powerful but unsigned-driver territory; back up first.
- Xbox controllers - no reliable software overclock path. The pad reports near 125 Hz and there is no supported way to raise it on PC.
- Bluetooth (any pad) - no dependable overclock. If you need higher polling, go wired or use a dedicated dongle.
Does it actually matter?
Higher Hz shrinks the worst-case wait before an input is reported:
| Polling rate | Worst-case wait | Who notices |
|---|---|---|
| 125 Hz | ~8 ms | Casual feels fine; competitive may feel it vs 250 Hz+ |
| 250 Hz | ~4 ms | Clear step up; practical sweet spot for most console pads |
| 500 Hz | ~2 ms | Diminishing returns begin |
| 1000 Hz | ~1 ms | Real for wired PC setups, worth it only if stable at high FPS |
Polling is one link in the input chain (engine, frame pacing, display refresh all add up). A stable 250 Hz beats an unstable 1000 Hz for most players.
Low reading? Rule these out first
- Caps around 60-125 Hz on every controller -> that is the browser animation-frame cap, not the pad.
- Wired much higher than Bluetooth -> normal; Bluetooth trades polling headroom for convenience.
- Numbers jumping wildly -> weak cable, USB hub, low battery, or background CPU load.
- Genuinely lower than the same model elsewhere -> old firmware, wrong profile, or a worn cable/port.
Related checks
Full guide with images, the per-platform tables, source links, FAQ, and Korean/Russian/Arabic versions: Controller Polling Rate Test: Check Your PS5/Xbox Hz (USB vs Bluetooth)
