Mouse Polling Rate Test
Measure how often your mouse reports its position to the computer. Press start and move the mouse in fast circles inside the box; after a second or two you get the rate in Hz and the nearest standard setting.
- Runs in your browser
- Nothing is uploaded
- Free, no sign-up
Move the mouse here in fast circles.Click or press Start, then keep it moving. Each second the box counts how many position reports arrived.
Press Start, then move the mouse in fast circles inside the box.
How to test your mouse polling rate
- Close other heavy programs and unplug any second mouse so only the one you want to test is moving.
- Press Start (or just click in the box) and move the mouse in fast, wide circles. Keep it moving the whole time: a mouse only reports when it moves, so pauses lower the count.
- After two or three seconds, read Measured rate. The Nearest standard box rounds it to the rate your mouse is most likely set to: 125, 250, 500, 1000, 2000, 4000 or 8000 Hz.
- For a wired mouse, try a different USB port if the rate is lower than expected. For a wireless mouse, test with the receiver close to the mouse and then with the cable, if it has one.
- Press Stop to keep the result on screen, or Reset to start a new run after changing a setting in your mouse software.
What your polling rate means
Polling rate is how many times per second the mouse sends its position to the computer. 125 Hz means a report every 8 ms, 500 Hz every 2 ms, 1000 Hz every 1 ms. A higher rate makes the cursor track more smoothly and reduces the delay between a hand movement and the screen, which matters in fast games. For office work, 125 Hz is unnoticeable.
- 125 Hz: the USB default and what most office and wireless mice use to save battery. Normal unless you have a gaming mouse set higher.
- 500 Hz: common on older gaming mice and on many wireless gaming mice.
- 1000 Hz: the usual gaming setting. Almost every gaming mouse supports it.
- 2000-8000 Hz: new high-rate mice. Only reachable on a cable or a dedicated high-rate receiver, and only measurable here in a browser that counts every report (see the note under the graph).
The measured rate is normally a little under the nominal one, for example 980 Hz for a 1000 Hz mouse, because the computer drops the odd report and the mouse does not move in every slot. A reading far below the setting, or one that swings around, points to a slow USB port, a bad wireless link or a busy computer.
How the polling rate test counts reports
Browsers normally bundle all the mouse movement that happens between two screen refreshes into one event, so a simple counter would never read more than your refresh rate, usually 60 or 144. This test uses the coalesced events feature of the Pointer Events API, which hands over every report the mouse made inside each bundle, each with its own timestamp. The rate is taken from the median gap between those reports, which is steadier than counting per second, and the count per second is shown too so you can see dips. Chrome, Edge and Firefox support coalesced events; Safari counts only one event per frame, so the result there caps at the refresh rate.
Any polling rate test, including the ones in mouse software, only measures while the mouse is moving fast enough to produce a report in every slot. Slow movement shows a lower number because the sensor has nothing to report. That is why the instructions say fast circles.
Does a higher polling rate help?
Going from 125 Hz to 1000 Hz cuts the worst-case input delay by about 7 ms and makes the cursor noticeably smoother on a high-refresh monitor, so it is worth turning on if your mouse supports it. Going from 1000 Hz to 4000 or 8000 Hz saves under a millisecond more and costs CPU time in some games, so it is mostly for competitive players with powerful computers. If a game stutters after you raise the rate, drop back to 1000 Hz. To check the other side of mouse precision, measure your sensor with the DPI analyzer, and check the buttons and wheel with the mouse tester and the scroll test.
Common problems and fixes
The rate is stuck at 125 Hz on a gaming mouse
Open the mouse software (Logitech G Hub, Razer Synapse, SteelSeries GG, Corsair iCUE, Glorious Core) and set the polling rate to 1000 Hz. Some mice have a switch on the bottom or a button combination for it; check the manual. Then press Reset here and move again.
The reading is half of the setting
A mouse set to 1000 Hz that reads 500 is usually on a slow USB hub, a keyboard pass-through port or a USB 2.0 port shared with other devices. Plug it straight into the computer. On wireless mice, the lower rate can be the battery-saving mode or a weak signal: move the receiver closer.
The rate jumps around
The computer is busy. Close other programs, stop downloads and pause video, then test again. Wireless interference from USB 3 ports, Wi-Fi routers or other 2.4 GHz devices near the receiver also causes an unstable count.
The result never goes above my screen refresh rate
Your browser is not reporting coalesced events, so it caps the count at one per frame. Use Chrome, Edge or Firefox. The note under the graph says whether coalesced events are on.
Frequently asked questions
What is mouse polling rate?
What polling rate should my mouse be?
Why does the test show less than 1000 Hz?
Can I measure a wireless mouse here?
Can this test measure 4000 or 8000 Hz?
Does polling rate affect DPI?
Last updated