Mouse Polling Rate Test: Measure Hz, Jitter & Dropped Reports

Measure browser-observed mouse event rates and timing variation, with live intervals and jitter charts.

Mouse Polling Rate & Jitter Studio measures the timing between the pointer-move events your browser actually dispatches, unpacking any events the browser bundled together so a high-frequency mouse does not get misread at your display's refresh rate instead of its own report rate. It runs for a fixed six-second window, then reports percentile timing statistics, a full interval histogram, and a dropped-packet flag — a browser-observed measurement, not a substitute for a dedicated USB report-rate analyzer.

Recovering reports the browser would otherwise merge

Browsers batch multiple raw hardware mouse reports into a single dispatched pointer-move event per animation frame under normal conditions, which would make an eight-thousand-hertz mouse look like it is reporting at your monitor's refresh rate instead. This tool unpacks the coalesced-events list on every dispatched event to recover the individual timestamps the browser actually received, the only way a browser-based test can approach measuring a mouse faster than the display itself refreshes.

Every interval gets pushed into a fixed-capacity buffer sized for tens of thousands of samples, generous enough for several seconds of an eight-thousand-hertz mouse, so a long capture never silently grows an unbounded array or drops old data to make room for new.

How to test your mouse polling rate

1. Pick the 1,000, 4,000 or 8,000 Hz target closest to what your mouse is set to in its own software; the page then shows the browser-measured band to expect for that target.
2. Click the capture pad. Your cursor disappears and is held inside the page by pointer lock, which the timing needs.
3. Move the mouse in fast, continuous circles without pausing for the full six seconds; stopping mid-capture leaves gaps that read as slow reports.
4. Let the capture end on its own, or press Esc or Stop capture to end it early.
5. Compare instantaneous and sustained Hz with the expected band, then check the interval histogram and the dropped-report count; press Test again to repeat.

Two different hertz numbers, and why they can disagree

Instantaneous hertz is one thousand divided by the median interval between reports, a snapshot of the typical-instant reading. Sustained hertz instead divides the total sample count by the whole capture's elapsed time, smoothing over any bursts or gaps across the full window. A mouse with occasional dropped or delayed reports can show a healthy instantaneous number while its sustained number reads noticeably lower, exactly the gap this test is built to surface.

Alongside those two headline figures, the capture reports the minimum, maximum, mean, median, and ninety-fifth-percentile interval, so a single bad outlier does not get hidden inside one averaged number.

Mouse polling rate and report interval in milliseconds

• 125 Hz — one report every 8 ms.
• 250 Hz — one report every 4 ms.
• 500 Hz — one report every 2 ms.
• 1,000 Hz — one report every 1 ms, the usual default on gaming mice.
• 2,000 Hz — one report every 0.5 ms.
• 4,000 Hz — one report every 0.25 ms.
• 8,000 Hz — one report every 0.125 ms.
• The interval is only the gap between reports; total click-to-screen latency also includes the sensor, the game engine and the display, so halving the interval does not halve the lag you feel.

Why the reading usually undershoots the number on the box

Browser-based polling measurement is disclosed to undershoot a mouse's true hardware report rate by roughly fifteen to thirty percent, a known limitation of JavaScript timing and event-loop granularity rather than a defect in the mouse itself. Testing against the one-thousand, four-thousand, or eight-thousand-hertz target closest to your mouse's advertised rate gives context for whether a reading falls inside that expected undershoot band or looks unusually low even accounting for it.

The capture window runs for six seconds and stops automatically, long enough to build a stable histogram at any of the three target rates without risking the sample buffer filling up mid-test.

Getting a steadier reading from a 4000 or 8000 Hz mouse

• Plug the mouse or its receiver into a rear-panel USB port wired to the motherboard, not a hub, front-panel port or extension cable.
• Keep a wireless receiver close to the mouse, ideally on a short USB extension away from other 2.4 GHz gear.
• Close vendor suites such as Razer Synapse, Logitech G Hub or Corsair iCUE and other heavy apps before the capture.
• On a laptop, plug in and use a performance power mode so the CPU is not throttled while the capture runs.
• Use a Chromium-based browser such as Chrome or Edge: there the page listens to pointerrawupdate, which fires once per hardware report, while other browsers fall back to unpacking coalesced pointer events.

The histogram and the dropped-packet flag

• The interval histogram sorts every recorded gap into forty bins, giving an actual distribution shape rather than a single simplified stability bar, so a tight single spike reads very differently from a distribution with a second cluster of long gaps.
• Dropped-packet detection flags intervals that are anomalously large relative to the capture's own median, the signature of a missed USB report followed by a late one arriving a beat behind schedule.

What a six-second browser capture cannot tell you

• Nothing here counts literal USB reports at the hardware level; every number is derived from dispatched, coalesced browser events, one layer removed from the mouse's actual wire protocol.
• The disclosed fifteen-to-thirty-percent undershoot band is a known characteristic of browser-based timing, not a defect in your specific mouse, so a number inside that band is not a sign of a problem.
• The capture auto-stops at six seconds; a mouse with an intermittent issue that only shows up over longer continuous use will not necessarily surface it in one run.
• This tool only measures; it has no way to change your mouse's actual polling rate setting, which still has to be configured in the manufacturer's own software or a hardware switch.

Questions people ask about Mouse Polling Rate & Jitter Studio

Why is my measured polling rate lower than what is advertised on the box?

Browser-based measurement is known to undershoot a mouse's true hardware report rate by roughly fifteen to thirty percent because of JavaScript timing and event-loop granularity, not because the mouse itself is underperforming. A reading in that range next to your target hertz value is expected rather than a sign of a problem.

What exactly counts as a dropped packet in this test?

An interval between two consecutive reports that is anomalously large compared to the capture's own median interval, the pattern you would expect if one hardware report went missing and the next one arrived a beat later than it should have.

How long does one capture run for?

Six seconds, then it stops automatically. That is long enough at any of the three test targets, one thousand, four thousand, or eight thousand hertz, to build a stable histogram and percentile statistics without risking the sample buffer filling up.

How do I change my mouse's polling rate?

Use the manufacturer's configuration software, or a button or switch on the mouse if it has one; some wireless models also need a matching high-rate receiver. This page only observes the reports your browser receives, so running it never changes the setting — retest afterwards to confirm the new rate.

What polling rate should I use for gaming?

1,000 Hz is the common default and works well for most players. Higher rates shorten the gap between reports, but only help if your PC stays smooth at them; if a game stutters or input feels uneven at 4,000 or 8,000 Hz, step back down.

Does a higher polling rate increase CPU usage?

Yes. At 8,000 Hz the system handles eight times as many movement reports per second as at 1,000 Hz, which costs CPU time, and on wireless mice it usually drains the battery faster too. Older or busy machines feel it first, sometimes as stutter in games.

Is 8000 Hz noticeably better than 1000 Hz?

The report gap shrinks from 1 ms to 0.125 ms, so the most you gain is under a millisecond per update. Some players notice smoother tracking on very high-refresh monitors; many cannot tell the difference, and the extra CPU load can outweigh it on slower machines.

Related tools on BrakeTools

• Mouse DPI & CPI Accuracy Tester — Measure real pointer counts over a ruler distance, compare advertised DPI, and repeat calibration runs in your browser.
• Keyboard Chatter & Switch Tester — Detect duplicate key presses, rapid switch chatter, stuck keys and keyboard rollover locally.
• Monitor & Dead Pixel Tester — Inspect solid colors, grayscale, gradients, and geometry grids in a distraction-free full-screen display test.
• Gamepad Tester — Full controller diagnostic: buttons, stick drift, triggers, rumble, health certificate.

Content reviewed 2026-09-27.