Mouse Polling Rate Tester

Move your mouse inside the zone below to measure your real-time polling rate (Hz).

Advertisement
01.2KHzMove mouse
Waiting for input…
Peak Rate

Average

Jitter

Samples

Results may vary slightly — move the mouse steadily at a constant speed for the most accurate reading.

Move your mouse here

Shake left and right for best accuracy

Stability Graph

Hz readings over time — shows polling consistency (jitter)

Move your mouse over the tracking zone to begin…

Reference: Common Polling Rates

125 Hz

USB Legacy

250 Hz

Budget

500 Hz

Mid-Range

1K Hz

Standard

2K Hz

High-End

4K Hz

HyperPolling

8K Hz

Max

Advertisement

Need a faster mouse?

Upgrade to 4K or 8K Hz for a genuine competitive edge.

Affiliate links — we may earn a small commission.

Why Mouse Polling Rate Matters in FPS Games

Polling rate (measured in Hz) defines how many times per second your mouse reports its position to the operating system. At 125 Hz, the cursor updates every 8 ms. At the now-standard 1,000 Hz, that drops to 1 ms. At 8,000 Hz — offered by Razer's HyperPolling and Pulsar's Gen 3 technology — you get a new position update every 0.125 ms.

In competitive FPS titles like Valorant and CS2, the gap between pulling the trigger and your crosshair registering the movement is the sum of several latency sources: monitor refresh, GPU frame time, and critically, mouse polling interval. A 125 Hz mouse can introduce up to 8 ms of additional latency in the worst case — equivalent to dropping from 240 Hz to 125 Hz on your display.

From 1K to 2K Hz: Moving from 1,000 Hz to 2,000 Hz halves the worst-case polling latency from 1 ms to 0.5 ms. In practice, you'll notice smoother micro-adjustments — especially during flick shots where the mouse is accelerating quickly. Most pro players competing at the highest level now use 2K+ Hz mice.

4K and 8K Hz: At 4,000–8,000 Hz, the polling latency becomes negligible (0.125 ms). The real benefit at these rates isn't raw latency but positional accuracy — the mouse sends more data points per unit of time, so fast wrist motions are tracked more faithfully instead of being interpolated between two distant reports. Jitter (inconsistent polling intervals) is also dramatically reduced.

What this tool measures: This tester uses the browser'spointermove event andperformance.now() (sub-millisecond precision) to calculate the time between consecutive position reports. Since the OS driver fires events at the polling interval, dividing 1000 by the average interval gives a reliable Hz estimate. Move the mouse steadily left and right for the most consistent reading — erratic slow movements can produce false low readings.

How to Use the Mouse Polling & Latency Lab

1

Click the test area

Move and click so the page can sample event timing.

2

Read polling stats

Compare reported Hz against the manufacturer spec.

3

Iterate setups

Swap ports, disable HDR overlays, or test wired versus dongle receivers.

User Guide & Deep Dive — Mouse Polling & Latency Lab

User workflow for reliable numbers

Mouse Polling & Latency Lab is structured so you can move from inputs to defensible outputs without hunting for hidden options. Step 1 (“Click the test area”): Move and click so the page can sample event timing. Step 2 (“Read polling stats”): Compare reported Hz against the manufacturer spec. Step 3 (“Iterate setups”): Swap ports, disable HDR overlays, or test wired versus dongle receivers. Following that sequence reduces rounding drift: you lock the scenario first, then layer refinements (tax mode, compounding frequency, activity tier, or niche multiplier) only after baseline numbers look sensible. When you revisit a calculation weeks later, the same order of operations makes spreadsheets and screenshots easier to reconcile with what the UI showed.

How browser tests approximate hardware polling

JavaScript timers inherit OS scheduler granularity; micro-stutters from background tabs can add jitter. Use a clean profile and close heavy extensions.

Wireless mice add dongle firmware debounce—if numbers swing wildly, suspect RF interference before blaming sensor firmware.

Revisit Mouse Polling & Latency Lab whenever baseline assumptions shift—rates, calendars, population denominators, or hardware targets. The numbers you export today become the audit trail that makes tomorrow’s decision defensible to teammates, clients, or regulators reviewing your methodology.

Professional context, standards, and limits

Competitive FPS performance is a stack of human factors, display timing, and settings you can actually sustain across thousands of repetitions. Crosshair codes encode color, thickness, outlines, and center dot behavior; what reads cleanly on Mirage may wash out on Icebox or Nuke. Sensitivity math reduces to a measurable cm/360°, yet muscle memory still prefers whatever you have rehearsed for seasons. Frame-time and monitor latency tools help you reason about end-to-end click-to-photon delay, but real-world variance from fullscreen optimizations, Reflex, and driver settings will diverge slightly from any single formula. Treat pro settings as structured experiments: change one variable at a time, log outcomes in aim trainers or scrims, and revert when something feels worse under pressure.

Applying the built-in expert tip

Seasoned users pair the in-app insight—“Graph stability matters more than hitting 8000 Hz once—watch variance across USB ports and hubs.”—with external checks specific to their industry. For Mouse Polling & Latency Lab, treat that guidance as a hypothesis: note the assumption, measure the delta against real-world data you trust, and update defaults when your own history disagrees with generic benchmarks. Documenting those adjustments is what turns a quick answer into a repeatable workflow your team can audit.

Three adjacent tools from the same workflow—open in a new tab mentally, same privacy model here.

Frequently Asked Questions

No. It is a quick sanity check, not lab certification.

Event pipelines and timer APIs vary; compare using the same browser build.

Diminishing returns set in around 500–1000 Hz for many humans; stability beats peak bursts.