Estimated polling rate
Estimated Hz is the median of stable 250 ms measurement windows observed during active movement. It is the main browser-visible rate for the run, not a direct hardware reading.
Live mouse signal analyzer
Mouse Polling Rate Test
Measure the polling rate your browser observes from your mouse. Run a 5, 10, or 15 second test with no download, then compare estimated Hz, consistency, and report interval.
Browser-observed estimate — not hardware telemetry or an end-to-end latency measurement.
Start the test
Choose a duration, then move the mouse in steady circles after you start.
A physical mouse works best. Touch and pen input are ignored. A trackpad may send mouse-like events, but its result does not represent an external mouse's hardware polling setting.
Coordinates are used only briefly in browser memory for the short trail, then cleared. They are never saved or sent.
What is mouse polling rate?
Mouse polling rate is how often a mouse can report movement to a computer, measured in hertz (Hz). This browser test estimates the pointer-event rate it can observe; it does not read mouse firmware, the USB controller, or the configured hardware setting.
Common configured rates and their ideal reciprocal report intervals. Real browser observations will vary.
| Polling rate | Ideal report interval |
|---|---|
| 125 Hz | 8 ms |
| 250 Hz | 4 ms |
| 500 Hz | 2 ms |
| 1000 Hz | 1 ms |
| 2000 Hz | 0.5 ms |
| 4000 Hz | 0.25 ms |
| 8000 Hz | 0.125 ms |
How to use the polling rate test
Choose a duration, press Start, then move the mouse steadily inside the measurement area until the timer ends. The estimate uses the median of stable 250 ms window rates; gaps over 40 ms split the sample into separate movement segments.
- 1
Choose a duration, then move the mouse in steady circles after you start.
- 2
Keep a smooth, continuous motion. Brief pauses are removed from the estimate.
- 3
Use a wired or stable wireless connection, keep this tab focused, move continuously, and repeat several runs. Close heavy background work and disable power saving when comparing settings. A stable cluster of runs is more useful than a single peak.
A physical mouse works best. Touch and pen input are ignored. A trackpad may send mouse-like events, but its result does not represent an external mouse's hardware polling setting.
Understand your polling rate result
Your estimated polling rate and supporting metrics.
Consistency
Consistency shows how closely eligible measurement windows cluster around the estimated rate. Compare several runs; a stable cluster is more useful than one unusually high peak.
Estimated report interval
Report interval is the reciprocal of estimated Hz. Closest common rate places the estimate near a familiar tier, but it does not prove that tier is configured on the mouse.
What is a good mouse polling rate?
There is no single best setting for every mouse or system. Use stable repeated results, device support, display and game behavior, processing load, and battery needs to choose a rate.
125–250 Hz
125–250 Hz uses longer 8–4 ms nominal report intervals and can suit basic pointer use or power-saving profiles. It may feel less smooth on faster displays.
500–1000 Hz
500–1000 Hz shortens the nominal interval to 2–1 ms and is a common balance for general and gaming use. Confirm the rate stays stable in the apps you use.
2000–8000 Hz
2000–8000 Hz reduces the nominal interval from 0.5 to 0.125 ms, but each step saves a smaller fraction of a millisecond. Device support, browser delivery, CPU work, game behavior, and battery use can limit the practical benefit.
Polling rate, gaming, and input latency
Report interval is the reciprocal of polling rate: 125 Hz is about 8 ms, 500 Hz is 2 ms, 1000 Hz is 1 ms, and 8000 Hz is 0.125 ms. This interval is not the same as click latency, display latency, or total system response time.
2000–8000 Hz reduces the nominal interval from 0.5 to 0.125 ms, but each step saves a smaller fraction of a millisecond. Device support, browser delivery, CPU work, game behavior, and battery use can limit the practical benefit.
Troubleshoot low or unstable results
If the estimate is unexpectedly low, retry with larger continuous sweeps, keep the tab visible, try another browser, reconnect the mouse, and review its vendor software.
Use a wired or stable wireless connection, keep this tab focused, move continuously, and repeat several runs. Close heavy background work and disable power saving when comparing settings. A stable cluster of runs is more useful than a single peak.
Browser measurement and privacy
Browser-observed estimate — not hardware telemetry or an end-to-end latency measurement.
How browser sampling works
The tester prefers raw pointer updates when the browser exposes them, otherwise it uses coalesced samples or standard pointer movement. Technical details show which observable path was used.
Private by design
Processing happens in your browser. Timing samples stay in bounded memory for the current run. Coordinates are used only briefly to draw the short local trail, cleared when it pauses or ends, and never sent to a server, analytics event, or persistent storage.
Mouse polling rate questions
Why is the result lower than my mouse setting?
Browsers, operating systems, USB scheduling, power modes, CPU load, and movement patterns can all affect delivered events. Repeat the test and compare several results instead of treating one run as a hardware certificate.
Is a higher polling rate always better?
No. Higher rates shorten the nominal report interval, but the gains diminish and can add processing or battery cost. Use the highest stable rate that works well with your mouse, system, and software.
Does polling rate affect DPI or sensitivity?
No. Polling rate controls how often reports are sent; DPI and sensitivity control how far the pointer or view moves. A different report cadence may feel smoother, but it does not change the configured DPI or sensitivity by itself.
How do I change my mouse polling rate?
This page cannot change your mouse setting. If your device supports selectable rates, use its vendor software, hardware button or switch, or a saved onboard profile, and follow the documentation for that exact model.
Are mouse movements or results uploaded?
No. Timing samples stay in bounded browser memory for the active run. Coordinates are used only briefly to draw the short local trail, cleared when the trail pauses or ends, and never uploaded or saved.