Mouse / Polling Rate

Polling Rate Test

Move your mouse in circles inside the box for 2 seconds. We sample movement timestamps to estimate your polling rate in Hz.

Move your mouse here to begin

Polling Rate Guide

A mouse polling at 125Hz reports its position every 8 milliseconds. The same mouse set to 1000Hz reports every 1ms. That single setting is the difference between movement that arrives in eight stale chunks and movement that arrives continuously, and most people have never checked which one their mouse runs. The polling rate test estimates it in two seconds from nothing but your cursor movement.

The number is worth knowing because it silently degrades. Wireless mice drop to a lower rate to save battery, cheap hubs confuse USB negotiation, and driver defaults sit conservative. The spec sheet says 1000Hz. The report rate test tells you what today's answer is.

What polling rate means

Polling rate is how many times per second the mouse tells the computer where it is, measured in Hz. Each report is a snapshot, so 1000Hz means a thousand snapshots a second and a maximum staleness of 1ms. Report rate divides cleanly into interval. 125Hz means 8ms between reports, and 500Hz means 2ms. Higher rates give the cursor fresher data, and fresher data tracks your hand.

Four numbers matter in practice. Office mice run 125Hz, and mid tier gaming mice run 500Hz or 1000Hz. The frontier sits at 8000Hz, which Razer reached first with the Viper 8KHz in January 2021, reporting every 0.125ms. Standard buckets are exactly why the ClackLab test rounds to them. Hardware negotiates in fixed steps, with 125 and 250 in office gear. Gaming mice step up to 500 and 1000.

How the polling rate test works

Move your mouse in steady circles for two seconds. The engine records a timestamp for every mousemove event the browser delivers and studies the intervals between them. One report per 8ms produces a tight cluster of 8ms gaps, and the median of the fastest cluster becomes the estimate. That estimate then rounds to the nearest standard bucket.

Movement is the measurement, so the quality of your motion is the quality of your data. Slow drifting generates few events and starves the estimator, while smooth continuous circles at a comfortable speed produce a rich stream of reports. A mouse pad helps, since the sensor tracks more consistently over a proper surface than over a glossy desk. Do the test twice and trust a reading that repeats.

Does a higher polling rate actually help

Honestly, up to a point, and the point is closer than marketing suggests. Moving from 125Hz to 1000Hz is a real upgrade worth 7ms of data freshness, and everyone can feel a cursor that stops stepping in 8ms increments. Moving from 1000Hz to 8000Hz saves another 0.875ms, which is under one ninth of a single frame at 60Hz. Blind tests have repeatedly found few players who can tell.

The cost side is concrete. An 8000Hz mouse generates eight times the interrupts and eight times the CPU load, and on modest systems that load costs more performance than the freshness buys. Reviewers documented the trade across the first 8K generation. Competitive players on strong hardware take it anyway. Everyone else gets 99 percent of the benefit at 1000Hz, and power draw matters too. High rates drain wireless mice faster, and some drop the rate on battery to compensate, quietly undoing the upgrade.

Why your number sits lower than the box says

A wireless mouse reading 125Hz is the classic case, and the cause is a power saving profile rather than a broken unit. Vendor software exposes the setting, and switching to a performance profile restores the full rate at measurable battery cost. A second cause is the port itself, since a 1000Hz mouse behind a cheap unpowered hub can renegotiate down, and the fix is a direct connection. A third is sensor starvation, a test run by drifting the mouse too slowly to generate reports. The estimator reads that as a low rate even though the mouse is fine. Fast circles before slow ones settle which failure you have.

Polling rate test FAQ

How do I check my mouse polling rate?

Open the polling rate test and move the mouse in steady circles for two seconds. The estimator reads the intervals between movement reports and rounds to the nearest standard bucket. Run it twice and trust the reading that repeats, since a slow first pass can starve the estimate.

What report rate should my mouse run?

1000Hz for gaming, which means 1ms between reports and has been the competitive standard for years. Office mice at 125Hz are fine for desktop work, and the jump from 125 to 1000 is the one upgrade almost everyone can feel.

Is 8000Hz worth it?

Rarely. The Viper 8KHz in 2021 proved the engineering, and the gain over 1000Hz is under 1ms of freshness, while CPU load and battery drain rise measurably. Esports players with strong hardware take the trade, and everyone else should spend the difference on the monitor.

Does polling rate affect FPS or aim?

It affects aim more. A higher rate feeds fresher position data, so micro corrections during tracking land sooner, while frame rate depends on GPU and CPU load. An 8000Hz mouse actually costs some frame rate through interrupt load, and at 1000Hz the load is negligible.

Why does my wireless mouse read 125Hz?

Power saving. Many wireless mice drop their report rate on battery to extend runtime, and the test catches the drop instantly. Open the vendor software and lock the performance profile, then retest and watch the bucket jump.

Related tests

The mouse latency test measures the delay each report carries through your system. Mouse CPS grades the buttons rather than the sensor, and the reaction time test measures the only component in the chain that training can improve.