Polling Rate Test – Check Your Mouse Hz
Estimate your mouse polling rate in the browser by counting input events over a fixed window. Honest framing: browsers cannot read USB HID polling rate directly — this is an event-based estimate, not a hardware readout.
Polling rate test
Move your mouse in continuous circles inside the page during the 5-second window. The tool counts browser input events and estimates the report rate.
Why this is an estimate
Polling rate is a property of the USB HID link between mouse and PC — how many times per second the mouse reports its position (125, 500, 1000 Hz, and now 4000/8000 Hz on some models). Browsers have no API to read that link. They only see OS-processed input events, which the browser may also coalesce. This test counts those events over 5 seconds of continuous movement and divides by time — a reasonable estimate, but it can under-read if the browser batches events or if you move the mouse slowly.
How to get the most reliable estimate
- Move the mouse in continuous, medium-speed circles for the whole window — slow or paused movement produces fewer events.
- Close other tabs and background apps to reduce event batching.
- Run 2–3 tests and take the highest reading; throttling only ever reduces the count, never inflates it.
- For a true hardware reading, use your mouse vendor's software (Logitech G Hub, Razer Synapse, etc.).
What polling rate do you need?
500 Hz is fine for most players; 1000 Hz is the competitive standard. 4000/8000 Hz polling shows measurable latency reductions in controlled tests but needs a strong CPU and can add noise on some systems — differences beyond 1000 Hz are subtle in real games.
Frequently asked questions
What is polling rate?
Polling rate is how many times per second your mouse reports its position to the PC, measured in hertz (Hz). 1000 Hz means a report every 1 ms; 500 Hz means every 2 ms.
Can a website measure my real polling rate?
Not exactly. Browsers cannot read the USB HID link, so this page estimates polling rate by counting input events over a fixed window. It is honest about being an estimate — for a true hardware reading, use your mouse vendor's software.
Why is my estimate lower than my mouse's setting?
The browser may batch (coalesce) input events, especially under load or with slow mouse movement. Throttling only reduces the count, so the highest of several runs is the most trustworthy.
Is 1000 Hz better than 500 Hz?
Yes, measurably: it halves the report interval from 2 ms to 1 ms, reducing input latency. Beyond 1000 Hz, gains are real but subtle and need a fast CPU to avoid downsides.
Does polling rate affect DPI?
No. Polling rate controls how often position is reported; DPI controls how many counts each inch of movement produces. They are independent settings.
Do I need 8000 Hz polling?
Almost certainly not. It shows small latency reductions in lab tests, but most players cannot feel the difference over 1000 Hz, and it increases CPU load.
Does this test work on wireless mice?
Yes — the test counts whatever input events the OS delivers. Wireless links may add latency or drop reports, which an estimate can sometimes reveal.