Mouse DPI & Polling Rate Checker
Measure your mouse's real-time polling rate (Hz) with a live graph, and estimate effective DPI by tracking cursor movement against a known physical distance — all directly in your browser.
Desktop Hardware Required
This tool requires a physical keyboard/mouse to measure metrics accurately, so it isn't available on mobile or touch devices. Try one of these mobile-friendly tools instead:
This measures effective DPI — on-screen pixels per inch of real hand movement at your current OS pointer speed — not your mouse sensor's raw hardware DPI, since Windows/macOS pointer acceleration curves modify raw sensor counts before any webpage can see them. For best accuracy, set your OS pointer speed to its default/middle value and disable "enhance pointer precision" or mouse acceleration before testing.
# Mouse Hardware Demystified: Polling Rate (Hz) vs DPI vs Sensor Smoothing
Polling rate is how many times per second your mouse reports its position to your PC over USB — 1000Hz means up to 1,000 reports every second, each roughly 1ms apart. DPI (technically CPI) is how many sensor counts are generated per inch of physical movement — it controls sensitivity, not report frequency. Sensor smoothing is optional firmware-level filtering that averages out small movement variations, trading a little raw precision for a steadier, less jittery cursor path.
How polling rate affects input latency
At 125Hz, a report arrives every 8ms; at 1000Hz, every 1ms; at 8000Hz, every 0.125ms. Higher polling rates reduce the maximum time your PC might wait for your latest hand movement to register, which is why competitive players favor 1000Hz+ mice — but each report also costs a small amount of CPU interrupt overhead, which is why extremely high polling rates like 4000Hz-8000Hz can occasionally introduce micro-stutter on weaker or heavily-loaded systems if not configured carefully.
Important limitation: browsers (and the OS beneath them) often coalesce or cap how frequently pointer events reach a webpage, sometimes aligned to your display's refresh rate rather than your mouse's raw USB report rate. This tool uses the Pointer Events getCoalescedEvents() API where supported to recover extra samples, but the Hz shown here is the browser-observed event rate, not a guaranteed measurement of your mouse's true hardware polling rate — use manufacturer software for a fully authoritative reading.
# High Polling Rate Benchmark Guide
| Polling rate | Report interval | CPU overhead | Best paired with |
|---|---|---|---|
| 125Hz | 8ms | Minimal | Any display — legacy default |
| 500Hz | 2ms | Low | 144Hz+ displays |
| 1000Hz | 1ms | Low-moderate | 144-240Hz displays; the competitive standard |
| 4000Hz | 0.25ms | Moderate | 240-360Hz displays, modern CPUs |
| 8000Hz | 0.125ms | Higher | 360Hz+/540Hz displays, high-end CPUs |
# Benchmark Reference Table
| Polling rate (Hz) | Avg interval latency | CPU usage impact | Competitive suitability |
|---|---|---|---|
| 125Hz | 8ms | Negligible | Not recommended for competitive play |
| 500Hz | 2ms | Low | Acceptable for casual competitive play |
| 1000Hz | 1ms | Low-moderate | Standard for competitive FPS/esports |
| 4000Hz+ | ≤0.25ms | Moderate-higher | Enthusiast/pro tier, diminishing returns for most players |
Latency and CPU figures above reflect the mouse's theoretical USB report interval, not this tool's browser-measured Hz — see the limitation note above for why those two numbers can differ.
# Frequently Asked Questions
Browsers, operating systems, and the display's own refresh cycle can all coalesce or throttle how often pointer events are actually delivered to a webpage, so a truly fixed hardware polling rate can still show up as a fluctuating measured rate. Background CPU load and how consistently you're moving the mouse also affect the samples this tool can capture.
High polling rates above the standard 1000Hz USB limit require a mouse and receiver or cable specifically rated for it, enabled through the manufacturer's own configuration software rather than any operating system setting. Check your mouse manufacturer's software for a polling rate or report rate option, and confirm your USB port and any dongle both support the higher rate.
Technically, CPI (counts per inch) is the correct term for how many sensor counts a mouse reports per inch of physical movement, while DPI (dots per inch) originally described printer resolution. The gaming industry has used the two terms interchangeably for so long that mouse software and marketing almost universally use "DPI" to mean what is technically CPI.
Mousepad surface doesn't change your polling rate, since that's a fixed USB communication setting, but a low-quality, overly glossy, or inconsistent surface can cause your sensor to misread movement, leading to skips or jitter that this tool may flag as instability. A clean, consistent-texture pad generally produces steadier tracking regardless of DPI setting.