The same mouse can report a higher rate to the computer than a browser test displays. Compare what the driver configured, what the browser observed, and what you felt in-game.
Keep moving the mouse briskly in the test area to collect enough active samples.
Move your mouse here to start
Move rapidly in circles for the most accurate reading
—
- Peak
- —
- Average Hz
- —
- Stability Score (%)
- —
- Samples
- 0
What the nominal rates mean
| Setting | Nominal interval | What to compare |
|---|---|---|
| 1,000 Hz | 1 ms | Use a stable baseline |
| 4,000 Hz | 0.25 ms | Check event-rate change and game frame times |
| 8,000 Hz | 0.125 ms | Check supported receiver/mode and compare system load |
The W3C Pointer Events specification describes how a browser may combine pointer motion updates. Even with coalesced events available, the browser stream depends on the browser, platform, and movement. The page therefore reports a browser-visible estimate. There is no single fixed maximum across browsers and configurations.
Compare performance with the same setup
Repeat the same sustained movement and DPI. Record average rate, stability, browser event mode, and game frame times at each setting. When validating device reports, use a native capture tool or an external measurement. Compare click-to-photon separately. Monitor refresh and system load affect what the player sees or feels, but no single refresh-rate threshold determines whether a mouse can report at 8K.
Open the polling rate tester for copies of the observed values, and compare DPI, eDPI, polling, and latency.