SensLab
Guides/fundamentals

Mouse Polling Rate — 1000Hz vs 4000Hz vs 8000Hz

Polling rate is the most-marketed mouse spec of the last few years. Here is what it really changes, what the trade-offs are, and what FPS pros actually use in 2026.

7 min read·Updated May 18, 2026

Polling rate is how many times per second your mouse reports its position to the PC. It is independent from DPI (which is spatial resolution) and from in-game sensitivity (which is a multiplier on rotation). All three combine to determine how your input feels — but polling rate is the only one that affects perceived latency.

The math

Polling rate, report interval, and maximum extra input latency
Polling rateReport intervalMax polling latency
125 Hz8 ms8 ms
500 Hz2 ms2 ms
1 000 Hz1 ms1 ms
2 000 Hz0.5 ms0.5 ms
4 000 Hz0.25 ms0.25 ms
8 000 Hz0.125 ms0.125 ms

Report interval = 1 / polling rate. The worst-case extra delay from polling alone is the report interval (your input arrives just after the previous report). Average delay is half that.

Going from 1000Hz to 8000Hz cuts the worst-case polling delay from 1 ms to 0.125 ms — a 0.875 ms improvement.

Whether that 0.875 ms is meaningful depends on the rest of your latency chain. Your monitor refresh interval is 4.2 ms at 240 Hz and 2.1 ms at 480 Hz. Your game engine's frame time is 4–8 ms at typical FPS. Polling rate is one small slice of total click-to-pixel latency.

What polling rate is not

  • Not the same as DPI. DPI is counts per inch (spatial). Polling rate is reports per second (temporal). Either can change without touching the other.
  • Not the same as sensor refresh. Modern sensors run at thousands of Hz internally — polling rate is how often the USB endpoint exposes that data to the OS.
  • Not a substitute for a good sensor. A noisy 8000Hz mouse is worse than a clean 1000Hz mouse. Sensor quality (PixArt PMW3950, Logitech Hero 2, Razer Focus Pro 45K Gen-2) matters more than polling.
  • Not a fix for high system latency. If your monitor is 60 Hz or your CPU is bottlenecked, going from 1000Hz to 8000Hz changes nothing you can feel.

Why 1000Hz dominated for two decades

1000Hz has been the gaming standard since the early 2000s because it hits a comfortable trade-off: report interval (1 ms) is below human perception, USB 2.0 handles it trivially, and CPU cost is negligible. Every game engine, every input library, every driver was written assuming 1000Hz was the ceiling.

Anything above 1000Hz only became practical in the last few years — first with the Razer Viper 8KHz (wired, 2020), then with HyperPolling-style wireless dongles. The hardware exists. The software stack is still catching up.

What 4000Hz and 8000Hz actually change

Two things, in order of importance:

  1. Smoother cursor movement on high-refresh displays. At 360 Hz / 480 Hz monitors, 1000Hz polling produces visible micro-stutter on slow mouse motion — fewer mouse reports per frame. 4000Hz+ produces enough samples per frame to look continuous. This is real and visible.
  2. Marginally lower input latency. 0.875 ms is below most people's motor threshold, but at the very top of competitive play it is one of the few remaining optimisations.

What 4000Hz / 8000Hz does not improve: aim accuracy in any measurable way, hit registration, or the feel of the mouse itself. If you cannot win duels at 1000Hz, you will not win them at 8000Hz.

The system cost

Higher polling rates have real costs that the marketing pages do not lead with:

  • CPU usage. Each mouse report is an interrupt the OS has to process. 8000Hz means 8000 interrupts per second; on lower-end CPUs this can cost 5–15% of one core under load and cause frame-time spikes.
  • Battery life on wireless. The Razer DeathAdder V4 Pro lasts ~150 hours at 1000Hz but drops to ~22 hours at 8000Hz. That is the dongle and radio working roughly 7× harder.
  • Reported rate < nominal. Independent testing shows that even on flagship setups, sustained 8000Hz is rare. Averages settle in the 6000–7500Hz range with oscillation tied to movement speed and OS scheduling.
  • USB hub interference. A 4000Hz+ mouse on a busy USB hub (with a webcam, hub, audio interface) can drop reports. 8000Hz mice should be plugged into a motherboard port, not through a hub.

Wired vs wireless 8000Hz

Until 2023, 8000Hz was wired-only — the Razer Viper 8KHz. Razer's HyperPolling Wireless Dongle then brought it to wireless, with a few caveats: the dongle must be in the box (it is for the Viper V3 Pro and DeathAdder V4 Pro) or bought separately, and battery life on the mouse drops sharply.

Other vendors (Logitech, ASUS, Pulsar, Glorious) have since shipped 2000Hz–8000Hz wireless products. The Logitech G Pro X2 Superstrike launched in February 2026 as Logitech's first wireless mouse in this tier. Expect more products at this rate by end of 2026.

Pro usage in 2026

1000Hz remains the dominant polling rate among CS2 and Valorant pros. Stability, compatibility across LAN-event hardware, and the absence of clear win-rate advantage keep it the default.

4000Hz is the growing minority. A meaningful number of CS2 and Valorant pros with high-end personal setups have moved up, citing smoother feel on 360 Hz+ monitors. 8000Hz is rarer — used by some pros at home and by streamers for content, less common at tournaments where rigs are standardised.

If you are below pro-tier reaction times (most of us), the polling rate you pick will not change your match outcomes. Pick for feel and battery life, not for the marketing.

Should you switch?

A simple decision tree:

  • You are on a 60–144 Hz monitor → stay at 1000Hz. Higher polling has nothing to render against.
  • You are on a 240 Hz monitor with a mid-range CPU → 1000Hz is right. The CPU cost of higher polling can cost more frame time than the polling saves.
  • You are on a 360 Hz+ monitor with a current-gen CPU and play wireless → try 2000–4000Hz. Real visible improvement in cursor smoothness, modest battery cost.
  • You are a tournament pro on the world stage → 1000Hz is still the safe default; the marginal latency win is not worth a single tournament-day driver bug.

How to check your current polling rate

  1. Open your mouse vendor software (G HUB, Synapse, Glorious Core, etc.) → polling rate is in the device settings.
  2. For an independent check: install MouseTester (free, Windows). Move the mouse in a circle for ~5 seconds. The reported polling rate vs target reveals if the OS is actually delivering what the mouse is sending.
  3. Watch CPU usage in Task Manager while moving the mouse. A noticeable jump (5%+) on one core when moving = polling is loading the CPU. Step down a rate if your game is borderline on frame time.

Convert your sens between these games

Dedicated pair pages with worked examples, reference tables, and pro stats for the most relevant conversions this guide covers:

Frequently Asked Questions

Put it into practice

Convert your sens with the math from this guide

Open the multi-game sensitivity converter and see your eDPI and cm/360 update live as you tweak the inputs.