Mouse Polling Rate and DPI Tester

Measure a mouse's actual polling rate in Hz and real DPI from a physical move, not the numbers printed on the box.

Every reading here is measured from real pointer events in this tab: your files and inputs never leave your device.

Capture surface

Move the mouse across this area for about five seconds.

Keep moving steadily, without lifting the mouse. The DPI and acceleration runs below lock the pointer to this same area.

Live rate 0 to 1000 Hz, last 5 seconds
Current
0 Hz
Average
0 Hz
Peak
0 Hz
Reads as
unknown
Median interval
0 ms
95th percentile
0 ms
Jitter
0 ms
Samples
0
DPI test
Units

Measure the distance on your desk or mousepad with a ruler first. Starting the run locks the pointer to the capture area, which is what makes the browser report raw sensor counts instead of scaled screen pixels. Click or press any key when you have finished the move.

Acceleration check

Move the mouse across the same physical distance twice, once slowly and once quickly. Without acceleration both runs report about the same number of counts, because counts track distance rather than speed.

slow 0 samples, fast 0 samples
Click test
Left0 down / 0 up
Middle0 down / 0 up
Right0 down / 0 up

Click anywhere in this pad with each button. The right button menu is suppressed here.

Double clicks
none detected
Switch bounce
none detected
Scroll test

Roll the wheel over this area. The page will not scroll while you do.

Wheel events
0
Delta mode
unknown
Notch size
no notches detected
Summary

Run any of the tests above and the full breakdown appears here, ready to copy.

Related tools

What it does

Measures four things about a mouse that manufacturer specs do not verify: actual polling rate in Hz from real pointer event timing, actual DPI (counts per inch) from a measured physical move, whether the OS or driver is applying pointer acceleration, and click and scroll health, including double-click intervals and switch bounce on worn buttons.

How to use it

Run each test in the live panel: move the mouse continuously for a few seconds for the polling rate reading, lock the pointer and move it a measured distance with a ruler for DPI, repeat that move once slowly and once quickly for the acceleration check, and click or scroll to record button and wheel behavior. Each run produces a JSON report that this page turns into a labeled breakdown.

Why this one

Most polling rate testers only show a live graph with no way to see the underlying numbers, and most DPI checkers just echo back whatever the mouse driver reports instead of measuring it. This measures polling rate and DPI directly from real browser events, entirely on your device, with no ads and no account.

FAQ
My mouse is rated 1000 Hz but this reads 125 Hz. Why?
Browsers commonly coalesce pointermove delivery to the display's refresh rate, so a page reading raw event timestamps can undercount a fast mouse. Use a Chromium browser, since it exposes getCoalescedEvents on pointer events, which recovers the individual hardware samples the display-rate events were bundled from.
How does the DPI test actually work?
With the pointer locked, movementX reports the mouse sensor's raw counts instead of scaled CSS pixels. Moving the mouse a known physical distance and summing those counts, then dividing by the distance in inches, gives the sensor's real counts per inch, which is what DPI means.
What does the acceleration check tell me?
It compares total counts from moving the mouse the same physical distance slowly versus quickly. If counts stay close between the two runs, movement is linear (1:1 with distance). If the fast run reports noticeably more counts, the OS or driver is scaling movement with speed, commonly called pointer acceleration or enhance pointer precision.

Keyboard shortcuts: press ? anywhere on this page to see them.