Check Your USB Polling Rate: 125 Hz to 8000 Hz

Check Your USB Polling Rate: 125 Hz to 8000 Hz

Run the polling rate test above and the chart reads your mouse's actual report rate in Hz, the number of position updates it sends your computer each second: 125 Hz is one report every 8 ms, 500 Hz is one report every 2 ms, 1000 Hz is one report every 1 ms, 4000 Hz is one report every 0.25 ms, and 8000 Hz is one report every 0.125 ms.¹

Comparing your own reading against the rated spec is the fastest way to confirm your hardware and software settings actually match, before you troubleshoot a responsiveness problem that might not exist. The tiers below give you the reference numbers to judge that reading against.

How polling rate works in USB hardware

A mouse advertises its report interval in the USB endpoint descriptor. For full-speed interrupt endpoints, a bInterval of 1 maps to a 1 ms polling period, while bInterval values 8 to 15 map to an 8 ms period.² That is why 1000 Hz and 125 Hz are common historical tiers for USB mouse reports. Polling rates above 1000 Hz require USB 2.0 High Speed negotiation and a mouse that supports the shorter interval, so they are not simply a software setting applied to every USB mouse.²

On the browser side, user agents can coalesce multiple pointer updates into a single dispatched event for performance. The Pointer Events API exposes getCoalescedEvents() so applications can read the intermediate pointer updates that were merged into the dispatched event.³ Pointer Events Level 3 also defines pointerrawupdate for high-frequency pointer events, while warning that high-frequency listeners can affect performance.⁴ This is why a measurement page needs the right browser API support to show rates above the normal dispatched-event cadence.

Why browser support matters above 1000 Hz

A mouse can send 4000 Hz or 8000 Hz reports while the browser still receives fewer dispatched events. getCoalescedEvents() lets the page inspect the intermediate samples merged into one event, but support varies by browser and API path. If your chart caps at 1000 Hz despite a higher configured rate, check browser support before assuming the mouse is limited. Chrome, Edge, and Firefox support getCoalescedEvents() and can display rates above 1000 Hz; Safari does not implement this API, so readings on Safari will cap near 1000 Hz regardless of hardware capability.

Polling rate tiers and their practical impact

The interval math is straightforward: 125 Hz means an 8 ms gap, 500 Hz means a 2 ms gap, 1000 Hz means a 1 ms gap, 4000 Hz means a 0.25 ms gap, and 8000 Hz means a 0.125 ms gap.⁵ Higher rates can reduce the maximum report interval, but the practical benefit depends on the rest of the pipeline, including CPU headroom, game engine input handling, browser API support, and monitor refresh rate.

For competitive play, the choice is usually a tradeoff between smoother, more frequent position updates and extra system load. Logitech describes 500 Hz as suitable for serious gaming, 1000 Hz as competitive, and rates above 1000 Hz as mainly for professional esports or niche scenarios because they use more power and may affect performance.⁵ Razer describes 8000 Hz as reporting up to eight times more data per second than 1000 Hz and reducing theoretical input delay from 1 ms to 0.125 ms, but those figures describe the device-to-PC report interval rather than every player’s perceived in-game advantage.⁶

Why the highest rate is not always the best setting

The best polling rate is the highest stable rate your setup can deliver without instability. If 8000 Hz causes frame pacing issues, RF instability, or a 1000 Hz browser ceiling, 1000 Hz or 4000 Hz may be the cleaner practical choice. The goal is sustained delivery to the browser and game, not just the largest number in software. Running the polling rate test at each available setting and comparing the chart stability, not just the peak number, reveals which rate your specific hardware and USB path can sustain under real conditions.

When polling rate does not reach its rated spec

Three common factors can make a mouse read below its rated polling rate. First, the device must actually be configured for the higher rate in companion software or firmware. Second, USB bandwidth is shared across the bus, and Windows documents competition for bandwidth among USB client drivers, including interrupt transfers.⁷ Third, Windows USB selective suspend allows the hub driver to suspend an individual port to conserve power.⁸

Resolving each cause requires a targeted fix. Start with the mouse software and confirm the polling rate setting is applied. Then move to a direct rear motherboard port if you are using a hub or front-panel header. In Windows Device Manager, the USB Root Hub power-management path exists under Universal Serial Bus controllers, USB Root Hub properties, and the Power Management tab, where the “Allow the computer to turn off this device to save power” option is exposed. After each fix, reconnect the mouse and rerun this test to confirm whether the reading improved before moving to the next step.

Reading a ceiling as a setup clue

A repeated ceiling, such as 1000 Hz on an 8000 Hz mouse, is a setup clue rather than a final verdict. It tells you which part of the path is limiting delivery before you spend time on switch, debounce, or in-game settings that cannot fix a polling-rate ceiling. A ceiling that stays consistent across multiple test sessions points to a systematic limitation like browser coalescing or USB power management, while a ceiling that varies between sessions suggests intermittent contention from other devices or background processes competing for USB bandwidth.

Writing down the reading after each fix keeps the diagnosis honest when several changes overlap. If the chart rises from 1000 Hz to 4000 Hz after a port move and then to 8000 Hz after disabling selective suspend, you know both steps contributed. Skipping the note tempts you to credit the last change alone, which hides the earlier win and makes the fix harder to repeat on another machine.

When to use this

Use this as a reference when selecting a polling rate setting in mouse software, when diagnosing why USB polling rate drops, or when evaluating whether upgrading from 1000 Hz to 8000 Hz is worth it for your use case.

Examples