Mouse Polling Rate Estimator

Estimate your mouse polling rate by measuring pointermove timing jitter in the browser.

Samples

0

Estimated Hz

-

Median interval

-

Jitter (std dev)

-

Move Area

Press Start, then move your mouse around inside the area.

Tip: Use consistent, smooth movement for best stability.

Browser and OS scheduling can affect results; treat this as an estimate.

Press Start

Last interval

No samples yet.

Interval Histogram (0-20 ms)

No samples yet

Start and move the mouse to collect samples.

Why does polling rate not reach 1000 Hz?

Browser measurements are estimates and depend on system load, scheduling, and display refresh. Use longer stable movement tests and compare multiple USB ports before concluding hardware failure.

Polling rate is how often the mouse reports updates, for example 125, 250, 500, or 1000 Hz. In the browser we observe pointermove timing and estimate Hz from the median interval.
• Works entirely in the browser with no installs. • Median-based Hz estimate plus jitter. • Histogram view for interval distribution. • JSON export of raw intervals. • Useful for quick sanity checks after driver or USB changes.
1) Click Start. 2) Move your mouse continuously in the area for 3-10 seconds. 3) Check the estimated Hz and jitter. 4) Export JSON if you need to share the raw intervals.
• Source: pointermove events captured in a single element. • Estimate: 1000 / median(interval_ms). • Jitter: sample standard deviation of intervals, which requires enough samples. • Browser and OS scheduling can clamp event frequency, often near display refresh.
• Verify 125, 250, 500, or 1000 Hz after changing mouse software settings. • Compare USB ports or hubs for stability. • Spot heavy jitter caused by CPU load or background apps. • Quick check when troubleshooting aim or feel inconsistency.
Q: Why do I only see about 60-125 Hz? A: Many browsers coalesce pointer events, and your display refresh rate and system load can limit event delivery. Q: How many samples do I need? A: More is better. Aim for a few seconds of steady movement so the median and jitter stabilize. Q: Why is jitter shown as "-"? A: Collect more samples by moving longer to reach the minimum sample count. Q: Does DPI affect the result? A: DPI changes how far the pointer moves per report, but it should not change report frequency. Very slow movement can still reduce event delivery. Q: I am on a touchpad or stylus. Does this still work? A: It will show event timing, but it may not represent mouse polling rate. Check the detected pointer type hint. Q: Tips for more stable readings? A: Close heavy apps, keep the tab focused, and move the mouse smoothly at a consistent speed.