How the mouse polling rate test works
Every time a mouse reports movement, the browser receives an input event with a precise timestamp. This mouse polling rate test collects those timestamps while you move the mouse, measures how many reports arrive in each short window, and converts that into reports per second: the polling rate in Hz.
In Chrome and Edge the test listens to pointerrawupdate, an event that fires for each raw input report instead of once per screen frame, and unpacks coalesced events so that reports bundled together are still counted one by one. In browsers without that event it falls back to regular pointer events, which can be capped by the browser.
How to run the polling rate check
- Plug the mouse directly into a USB port on the computer, not a hub, if you want to see its full rate.
- Move the pointer onto the pad and draw fast, continuous circles for five seconds. Do not stop: a mouse only sends a report when there is movement to report.
- Watch the Peak value. It is the best sign of the rate your mouse is set to.
- Look at the Likely setting box, which rounds your peak to the nearest standard rate: 125, 250, 500, 1000, 2000, 4000 or 8000 Hz.
- If you change the rate in your mouse software, press Reset and test again.
Reading your mouse polling rate checker results
| Peak reading | Report interval | Typical device |
|---|---|---|
| ~125 Hz | 8 ms | Office mice, default USB rate, many Bluetooth mice |
| ~250–500 Hz | 4–2 ms | Budget gaming mice, power-saving modes |
| ~1000 Hz | 1 ms | Standard for gaming mice, wired and 2.4 GHz wireless |
| ~2000–4000 Hz | 0.5–0.25 ms | High-end gaming mice and newer dongles |
| ~8000 Hz | 0.125 ms | Top-tier esports mice on a fast PC |
An average lower than the peak is normal: it includes moments where you moved slowly or changed direction. If the live value jumps around a lot even during steady fast movement, something on the system is interrupting input, such as a busy USB controller, power saving on the port, or wireless interference.
Why polling rate matters
Input delay
At 125 Hz the newest movement can be up to 8 ms old by the time the computer sees it. At 1000 Hz that drops to 1 ms. In fast games those milliseconds add up with display and game latency, so a higher rate makes aim feel more direct.
Smoothness on high refresh monitors
A 240 Hz or 360 Hz monitor shows a new frame every 4 or 3 ms. With a 125 Hz mouse, several frames in a row show no new cursor position, which looks like micro-stutter. 1000 Hz or more keeps the cursor moving on every frame.
CPU and battery cost
Each report wakes the system to process it. At 8000 Hz this is a measurable load and drains wireless batteries much faster. That is why many players stay at 1000 or 2000 Hz.
When the test shows a lower rate than expected
- Move faster. Slow movement means fewer reports, whatever the setting.
- Try another browser. Chrome and Edge give the most accurate mouse polling rate test results; Firefox and Safari often cap events.
- Change the USB port. Use a rear port on a desktop and avoid hubs and docks.
- Wireless: keep the receiver close to the mouse, ideally with the extension cable, and avoid Bluetooth mode for high rates.
- Close heavy apps. At 4000 Hz and above the browser needs spare CPU time to keep up.
Polling rate tells you how often the mouse reports; the DPI tester tells you how many counts each report covers. For button and wheel checks, open the main mouse tester.