Tools
Mouse raw input test
Every mouse report shows up as a dot. Swipe fast and look for gaps: red dots mark spots where the sensor may have skipped.
Click to start
Your cursor will hide. Make fast swipes left and right. Press Esc to stop.
Event: pointermove with coalesced events (fallback).
Polling rate (median)
— Hz
Nearest standard: —
Stability
—%
Intervals within ±25% of median
Suspected skips
0
Of 0 reports
Interval jitter
— ms
Standard deviation
Max swipe speed
0 counts/s
Divide by your DPI to get inches per second.
Acceleration check
Start the test, then press S and do one slow swipe, press F and do one fast swipe over the same distance. Shortcuts: S = slow, F = fast.
Browsers can cap or merge reports above about 1000 Hz, so high readings are approximate and depend on the browser.
How to run the test
- Click the test area. The cursor hides while the test runs.
- Make steady swipes left and right, then a few fast flicks like you would in a game.
- For the acceleration check, press S and move slowly between two marks on your pad. Then press F and move fast between the same marks.
- Press Esc to stop and read the numbers.
What the results mean
- Polling rate (median): the typical number of reports per second the browser received, with the closest standard setting (125, 250, 500, 1000, 2000, 4000, or 8000 Hz).
- Stability: the share of report intervals within 25% of the median. Higher is steadier.
- Interval jitter: how much the time between reports varies, in milliseconds. Lower is steadier.
- Suspected skips: reports that break the pattern during steady motion. Turnarounds and the start and end of a swipe are not counted. A few after very hard flicks can be normal browser timing. Skips in every swipe are not.
- Max swipe speed: the fastest movement seen, in counts per second. Divide by your DPI to get inches per second.
When raw pointer lock is available, the test reads movement without OS pointer acceleration. If the browser does not support it, the test uses normal pointer lock and says so under the test area.
Limits: browsers may cap or merge reports above about 1000 Hz, so high polling readings are approximate. Results depend on the browser, and this is not a USB analyzer. Check the rate your mouse is set to in its own software.
What to try if you see skipping
- Clean the sensor window with a dry cotton swab or a puff of air, and wipe or wash the mousepad.
- Try another surface. Glossy, glass, and very worn pads can confuse sensors.
- Adjust lift-off distance (LOD) in the mouse software if it has the setting.
- Try a different DPI. Test again at a common value such as 800 or 1600.
- Plug the mouse or receiver into a different USB port, ideally one directly on the PC instead of a hub.
- For wireless mice, move the receiver closer with an extension cable and keep it away from other wireless devices.
- Update the mouse firmware through the maker's software.
- Lower the polling rate and test again. Very high rates can be harder on some PCs.
The polling-rate tester gives a simpler rate reading, and the polling rate guide explains the setting itself.
Common questions
What does a red dot mean?
It marks a report that broke the pattern of its neighbors while the mouse was moving steadily in one direction: a gap much longer than the usual interval, a sudden jump in movement, or a zero report mid-motion. It ignores the start and end of a swipe and the slowdown where you change direction, because reports naturally get sparse there. One red dot after a hard flick is not proof of a bad sensor. Red dots that repeat in the same spot of every swipe are worth looking into.
Why does my 4000 Hz or 8000 Hz mouse read lower?
Browsers can cap or merge mouse reports, often around 1000 Hz. The browser then hands the page fewer events than the mouse sends. Treat high readings as approximate and confirm the setting in your mouse software.
Which browser works best for this test?
Chromium-based browsers such as Chrome and Edge support pointerrawupdate and raw (unadjusted) pointer lock, which gives the most detail. Other browsers fall back to pointermove with coalesced events, and the page tells you which one is in use.
How does the acceleration check work?
You move the mouse the same distance twice, once slowly and once fast. Without acceleration, both swipes should give about the same number of counts. If the fast swipe gives clearly more counts, something is scaling movement by speed. Pick two marks on your pad so the distance stays the same.
Can I run this test on a phone?
No. It reads mouse reports, so it needs a computer with a mouse. Touch input does not produce the same data.
Related tools and guides
- Sensitivity converter — Convert sensitivity between Overwatch, Valorant, CS2, and other titles using documented yaw values.
- cm/360 calculator — Turn mouse DPI and in-game sensitivity into centimeters per 360° turn.
- eDPI calculator — Multiply mouse DPI by in-game sensitivity for a same-game comparison number.
- FOV converter — Convert horizontal and vertical FOV across 4:3, 16:9, 16:10, and 21:9. Includes Overwatch, CS2, and Valorant.
- Frame-time and Hz calculator — Convert FPS to milliseconds, compare that wait to the monitor refresh, and read a 1% low as a frame time.
- Mouse polling-rate tester — Measure how often the browser sees pointer events. Average and max Hz.
- Mouse polling-rate tester — Average and max Hz in the browser.
- Mouse sensors explained — What the sensor does and why it can skip.
- What mouse DPI is — Counts per inch, not reports per second.
- Gaming mouse pads — Surface matters for tracking.