MOUSEDIAG

Mouse Polling Rate Test

Measure how many times per second your mouse reports its position — in Hz, up to ~10k — straight from the raw pointer samples your browser receives.

What polling rate means

Polling rate is how often your mouse tells the computer where it is, measured in hertz (Hz). At 1000 Hz it reports once every millisecond. Higher rates mean fresher position data and, in theory, lower input latency.

How this test works

Browsers fire pointermove roughly at your display's refresh rate but batch every raw hardware sample in between. We read those via getCoalescedEvents(), take the median time between consecutive samples in a short window, and convert it to Hz. Median — not average — keeps a momentary pause from dragging the number down.

How to run it

Pick a duration — 5, 10 or 30 seconds, or No limit — and press Start. The test goes fullscreen so the whole screen is the capture area, because high-rate mice can't be measured well in a small box. Sweep the mouse all over the screen as fast as you can. Click any mouse button to finish at any time (or press Esc); you'll get the peak and the average rate over the run.

Why honesty matters here

A browser can only see the event stream after the operating system and USB stack, so these readings run a little under dedicated hardware tools. We'd rather show you a trustworthy number than a flattering one.

FAQ

What is a good mouse polling rate?

1000 Hz (1 ms) is the long-standing standard and is plenty for almost everyone. Newer mice offer 2000, 4000, 8000 and even 10,000 Hz; the gains above 1000 Hz are small and mostly matter to competitive players with high-refresh monitors. This test supports rates up to ~10k Hz.

Why does the test go fullscreen and capture the whole screen?

High-rate mice need a lot of room to register clean samples — a small box fills up too fast at 4k–10k Hz. So when you press Start we go fullscreen and capture pointer movement across the entire screen. Move the mouse all over it for the best reading.

How do I stop the test?

Pick a duration (5s, 10s, 30s) and it stops automatically, or choose No limit and run as long as you like. Either way, clicking any mouse button finishes the test immediately and shows your peak and average. Pressing Esc (which exits fullscreen) also stops it.

Why does the browser show a lower rate than my mouse's rating?

Browser tests observe the event stream after the OS and USB stack, not raw sensor reports, so readings commonly run 10–20% under dedicated hardware tools. A 4000 Hz mouse may read ~3300–3700 Hz here. That gap is expected and honest.

Why is my rate capped near 1000 Hz?

We rebuild the full sample stream from getCoalescedEvents(). Chromium reconstructs every raw sample; Safari and Firefox often cap the reported stream near 1000 Hz, so higher-rate mice can't be distinguished there. Check the Support pill above.

How do I get the most accurate reading?

Move the cursor continuously and quickly in circles for a few seconds, on a desktop Chromium browser, with other heavy tabs closed. The Peak value reflects the best clean window we measured.