What does polling rate mean?
A configured report rate is the target frequency at which a supported mouse connection can report input to the computer. Hertz (Hz) means reports per second. At an evenly spaced 1,000 Hz, successive reports would be 1 millisecond apart. This is an interval, not a measurement of the total time between your hand moving and a pixel changing.
The input path also includes the sensor, connection, operating system, application and display. A polling-rate number by itself cannot measure that entire path or prove sensor accuracy. DPI is a separate setting: it describes sensitivity in counts per inch, rather than how often input is reported.
125, 500, 1,000, 4,000 and 8,000 Hz: the interval comparison
The nominal interval is 1,000 ÷ frequency in Hz. These values are a mathematical reference, not a promise that every device, connection or application produces evenly spaced events.
| Configured rate | Nominal interval |
|---|---|
| 125 Hz | 8 ms |
| 500 Hz | 2 ms |
| 1,000 Hz | 1 ms |
| 4,000 Hz | 0.25 ms |
| 8,000 Hz | 0.125 ms |
Why a browser result can differ from the setting
A web page receives events delivered by the browser after the operating system has processed input. The browser may combine several movement samples into one dispatched event. Where available, this test reads the coalesced samples or uses the raw pointer stream; it does not count overlapping streams twice.
Event delivery, timestamp precision, system load, the browser and your movement can still affect the estimate. A trackpad may generate similar events. An estimate near a familiar rate does not identify your mouse, and a low estimate alone does not establish a hardware fault. Browser measurement is useful for comparisons under similar conditions, not USB hardware certification.
How to get a useful, repeatable observation
Change one condition at a time. A comparison is easier to interpret when the same mouse, movement, browser and test duration are used.
- Use a physical mouse, open the polling test and keep the tab visible. Close unrelated work that makes the machine busy.
- Start the session, then move continuously in circles inside the test area for the ten-second window. Avoid leaving the area or pausing.
- Read the average together with the valid sample count and movement span. Fewer than 20 samples or less than 0.2 seconds of sample span is insufficient data in this tool.
- Reset and repeat. If you change the report-rate setting, connection or browser, record that change rather than comparing unlike sessions.
How this test calculates the estimate
The average uses (valid samples − 1) × 1,000 ÷ the time from the first valid sample to the last, in milliseconds. For example, 501 valid samples spanning 1,000 ms yield an observed average of 500 Hz. The subtraction matters because 501 timestamps contain 500 intervals.
Pauses between the first and last sample stay in that denominator and lower the average. The session duration includes time before or after movement too, so it can be longer than the movement span. The median interval summarizes the latest 2,048 intervals; it can remain short even when a pause lowers the overall average.
Equal, decreasing or invalid timestamps are excluded. The chart plots successive session-average estimates, not a set of independently certified hardware reports. Stopping, hiding the tab or losing window focus ends the session; resetting removes the previous observations.
Which polling rate should you use?
Start with a rate officially supported by your mouse, connection and software. Compare how the applications you actually use behave at supported settings. There is no single best setting for every device and workload.
Moving from 1,000 to 8,000 Hz reduces the nominal report interval from 1 ms to 0.125 ms. That 0.875 ms interval difference is not a guaranteed reduction in total input latency, a frame-rate improvement or a promise of better aim. Device-specific battery use, CPU load and compatibility need to be checked with the manufacturer and your own workload.
If the observed rate seems lower than expected
First repeat with continuous movement. Then check the connection and the active report-rate setting in the manufacturer’s current software. Not every wireless mode, receiver or device supports the same settings.
- Try a supported direct connection or receiver placement recommended by the manufacturer.
- Compare another current browser with the same movement pattern and test length.
- If results change only when the system is busy, repeat under a lighter workload before blaming the mouse.
- If you need a verified USB report rate, use a suitable specialist measurement method. Do not treat this page as that certification.
Official references
Technical and manufacturer guidance consulted for this guide. Follow instructions for your own device and software version.