Skip to content

Mouse polling rate (Hz) test

Move your cursor in smooth circles to measure true browser-delivered report frequency.

Move mouse here

Sweep your mouse smoothly in wide circles without stopping. Continuous motion ensures your sensor transmits at its full USB report rate.

Source: pointermove + coalesced events · Samples: 0

Recent sample rates (last 32 intervals) Sweep steadily to classify
Waiting for pointer motion

How to use Mouse polling rate test

  1. Sweep continuously inside the dashed arena. Move your mouse in wide, steady circles inside Move mouse here to keep optical reports flowing without lifting or pausing.
  2. Check the active source and Hz readout. Watch Average (1 s), Current Hz, Peak Hz, and Matched tier settle across standard USB polling steps from 125 Hz to 8000 Hz.
  3. Inspect Jitter (SD) and Consistency. Review the 32-interval sparkline and Live metrics sidebar to verify clean USB delivery or spot wireless drops.
  4. Clear previous bursts between settings. Click Reset stats before testing a different DPI, port, or mouse so earlier peak values do not skew the sparkline.

Your camera, microphone and recordings stay on this device. Nothing is uploaded or streamed anywhere.

How does this tool measure 125 Hz to 8000 Hz polling rates?

Sweeping your cursor across the arena captures consecutive high-resolution pointer timestamps, drops duplicate stamps below 0.05 ms and pauses above 200 ms, and averages valid intervals across a trailing 1,000 ms window. This mouse Hz and jitter checker displays live throughput and tier matching locally without transmitting pointer telemetry.

Comparing pointerrawupdate vs coalesced pointermove events

On load, the arena checks "onpointerrawupdate" in window and prints the active callback path directly under the readout. When supported on desktop Chromium, it listens to the MDN pointerrawupdate Event Reference so high-speed USB reports arrive before display frame throttling.

If a browser omits pointerrawupdate, the listener falls back to pointermove and prevents double-counting by returning early whenever raw mode is active. Both paths inspect getCoalescedEvents() so multi-sample bundles delivered inside a single callback still unpack every hardware timestamp into the ring buffer.

Filtering duplicate stamps and stationary cursor pauses

Mice stop emitting movement packets the instant your hand pauses, so raw gap math would collapse toward 5 Hz between circles. computePollingStats discards any interval outside 0.05 ms to 200 ms and trims the rolling array from 1,500 down to the newest 1,000 timestamps.

That range keeps genuine 8000 Hz (0.125 ms) reports while ignoring zero-delta duplicate coalesced timestamps and dead air between sweeps. While checking sensor consistency on a new mouse, you can also open the Mouse double-click and switch test to confirm clean switch actuation alongside polling stability.

Reading interval jitter, consistency, and standard Hz tiers

Six readouts in Live metrics summarize short-term and 1-second stability: Current Hz averages the last 10 intervals, Average (1 s) tracks the full 1,000 ms window, and Peak Hz remembers your highest sustained spike. Min interval, Jitter (SD), and Consistency measure how evenly USB packets arrive over time.

Sub-millisecond timing math behind Jitter (SD)

Every interval relies on monotonic browser clock precision specified by W3C High Resolution Time Level 3. Jitter (SD) computes the population standard deviation across all valid intervals inside the active 1,000 ms window and rounds to 0.01 ms.

Consistency turns that standard deviation into an intuitive 0% to 100% score using Math.round((1 - jitterMs / mean) * 100). Meanwhile, Recent sample rates (last 32 intervals) plots the latest 32 intervals as vertical bars capped at 8000 Hz and scaled against your active peak, making sudden wireless stalls easy to spot.

Matched tier snapping from 125 Hz to 8000 Hz

Because browser scheduling adds tiny variance around nominal USB intervals, computePollingStats matches Average (1 s) to standard tiers whenever it falls within ±18% of 125, 250, 500, 1000, 2000, 4000, or 8000 Hz. Whenever erratic sweeping pushes your average outside every ±18% band, the header displays Sweep steadily to classify.

Standard USB tier Ideal report interval ±18% matched band Typical interface and hardware
125 Hz 8.00 ms 102.5 Hz – 147.5 Hz Office wired mice, Bluetooth Low Energy, laptop trackpads
250 Hz 4.00 ms 205 Hz – 295 Hz Power-saving wireless dongles and adjustable gaming modes
500 Hz 2.00 ms 410 Hz – 590 Hz Mid-range 2.4 GHz receivers and low-CPU gaming profiles
1000 Hz 1.00 ms 820 Hz – 1180 Hz Standard esports wired and flagship 2.4 GHz wireless mice
2000 Hz – 8000 Hz 0.50 ms – 0.125 ms 1640 Hz – 9440 Hz High-speed 4K/8K dongles and wired 8000 Hz gaming sensors

Paired peripheral debugging benefits from checking input keyboards alongside high-rate mice. Use our simultaneous key press latency and NKRO check to confirm multi-key matrix stability during the same USB port check.

Why 4000 Hz and 8000 Hz mice read lower inside browsers

Even when Windows USB firmware polls an 8K dongle every 0.125 ms, a browser tab sits downstream of operating system compositor limits and frame coalescing. Depending on OS scheduler settings and browser flags, callbacks often batch reports before JavaScript reads MDN PointerEvent getCoalescedEvents API entries.

Display refresh clamping on macOS and Firefox

On macOS and many Firefox builds, system compositors align pointer delivery to your monitor refresh rate, often clamping readings around 60 Hz, 120 Hz, or 144 Hz. Desktop Chromium on Windows exposes raw high-frequency USB timestamps much more reliably when pointerrawupdate is available, though tab backgrounding or battery saver still throttles delivery.

Sensor velocity, DPI saturation, and USB hub bottlenecks

Optical mice only transmit HID updates when sensor pixel counts change, meaning slow cursor drift at 400 DPI cannot fill 4,000 or 8,000 slots per second. Raising DPI to 1600 or 3200 and sweeping wide continuous circles ensures every 0.25 ms or 0.125 ms interval contains fresh motion data.

Unpowered USB hubs and front-panel case headers also share single root bandwidth and inject interval jitter. Plugging a 2.4 GHz wireless receiver into a direct rear motherboard USB port on an extension cable shortens radio distance, and you can also check audio subsystem interference during USB polling spikes if high-Hz sweeps trigger USB bus contention.

Diagnosing wireless interference and DPC latency spikes

Under the W3C Pointer Events Level 3 model, coalesced input delivery still shares the browser’s main event loop with rendering and audio tasks. Background RGB controller suites, Wi-Fi 2.4 GHz congestion, or high CPU interrupt latency produce jagged bars in Recent sample rates (last 32 intervals) and drag Consistency below 80%.

  • Isolate wireless interference: Move a 2.4 GHz USB dongle within 15 cm to 30 cm of your mousepad away from routers or USB 3.0 drives, which emit broadband 2.4 GHz noise.
  • Test direct motherboard ports: Bypass monitor USB hubs and unpowered splitters whenever Jitter (SD) jumps above 1.50 ms on a wired 1000 Hz mouse.
  • Check system interrupt load: If high-rate cursor sweeps introduce faint static or stuttering on USB DACs or onboard sound, rule out speaker driver crackle during high-Hz sweeps while lowering polling from 8000 Hz to 1000 Hz.

Tip: Click Reset stats immediately after switching DPI steps, toggling 1000 Hz vs 4000 Hz, or moving USB ports so prior peaks do not flatten the 32-interval sparkline scale.

Questions

Why does a 4000 Hz or 8000 Hz gaming mouse read closer to monitor refresh rate?

Firefox and macOS browsers commonly clamp or coalesce pointer callbacks to your display refresh cadence, typically 60 Hz to 144 Hz. Desktop Chromium builds expose higher USB report rates when pointerrawupdate is supported and enabled inside a secure HTTPS tab.

Why does slow cursor movement lower the measured polling rate?

USB mice only transmit an HID packet when the optical sensor accumulates movement counts, rather than sending empty zero-delta frames at idle. Moving very slowly at low DPI misses 1 ms or 0.125 ms report slots and drops Average (1 s) below your configured tier.

How does the tool calculate interval jitter and consistency percentage?

Jitter (SD) computes the population standard deviation of consecutive valid intervals inside the trailing 1,000 ms window, rounded to 0.01 millisecond precision. Consistency compares that deviation against the mean interval using 1 minus jitter divided by mean, expressed from 0% to 100%.

What is the difference between pointerrawupdate and coalesced pointermove events?

Standard pointermove fires once per animation frame and bundles intermediate hardware reports inside getCoalescedEvents(). When supported by Chromium, pointerrawupdate dispatches unthrottled raw pointer batches immediately without waiting for monitor VSync.

How does matched tier detection classify 125 Hz through 8000 Hz mice?

The classifier compares your trailing 1-second Average Hz against seven standard USB tiers: 125, 250, 500, 1000, 2000, 4000, and 8000 Hz. Whenever the average stays within plus or minus 18% of a tier, Matched tier locks onto that nominal rate.

Why do Bluetooth mice usually cap near 125 Hz compared to USB dongles?

Bluetooth Low Energy prioritizes battery efficiency with negotiated connection intervals typically spaced near 7.5 ms to 15 ms, capping report frequency around 90 Hz to 133 Hz. Dedicated 2.4 GHz USB receivers and wired cables support 1000 Hz to 8000 Hz polling.

Updated