Polling rate decides how often your mouse tells the computer where it is. It is one of the biggest factors in how responsive your cursor feels — and one of the easiest specs to misread. Here's what the numbers actually mean.
Polling rate is how many times per second your mouse reports its position to your PC, measured in hertz (Hz). A mouse at 1000Hz sends an update 1000 times a second — once every millisecond. At 125Hz it reports just 125 times a second, or once every 8 milliseconds.
The higher the polling rate, the more frequently the cursor's on-screen position is refreshed, which makes fast movements feel smoother and more immediate. It is a completely separate setting from DPI: polling rate is about how often the mouse reports, while DPI is about how far the cursor moves per inch. If DPI is still fuzzy for you, our what is mouse DPI guide covers it from scratch.
Quick definition: polling rate = updates per second. 1000Hz = one report every 1ms. Higher Hz means lower delay between your hand moving and the cursor catching up.
Each step up roughly halves the delay between physical movement and the position update reaching your system:
Put those numbers next to a monitor and the picture gets clearer. A 60Hz screen draws a new frame every 16.7ms, a 144Hz screen every 6.9ms, and a 360Hz screen every 2.8ms. At 125Hz your mouse can only feed one fresh position into most of those frames, and sometimes none at all, so fast flicks look like they "skip". At 1000Hz there are several mouse reports waiting for every single frame the monitor draws, which is why the jump from 125Hz to 1000Hz is so much more noticeable than the jump from 1000Hz to 8000Hz.
The catch is that the benefit shrinks fast as the numbers climb. Moving from 125Hz to 1000Hz cuts the reporting interval from 8ms to 1ms — a 7ms improvement you can genuinely feel. But going from 1000Hz to 8000Hz only trims that 1ms down to about 0.125ms. That final fraction of a millisecond is below what most people can perceive, and it is dwarfed by other delays in the chain: your monitor's response time, the game's own input processing, and network lag in online play all add far more than the microseconds you save.
Higher polling rates also cost CPU time, because the system has to process thousands more reports every second. On older or busier machines, an 8000Hz mouse can actually cause stutters or frame drops that wipe out any theoretical gain — a mouse that hammers the CPU 8000 times a second while a game is already pushing the processor hard is a recipe for micro-stutter. For this reason 1000Hz remains the competitive sweet spot: it is responsive, universally supported, and light on resources.
Curious what your mouse is really running at? Open the free Polling Rate Tester → and watch your live Hz reading in seconds.
Polling rate is not free on a wireless mouse. Reporting 8000 times a second keeps the radio busy, drains the battery faster, and demands a rock-solid connection to the receiver. A wireless mouse that comfortably lasts a working week at 1000Hz might need charging every day or two at 4000Hz. Many models also quietly drop to a lower rate when the battery runs low or when they enter a power-saving sleep, so the number you set is not always the number you get.
Stability matters more than the peak figure, too. A mouse that holds a steady 1000Hz is better to play on than one that spikes to 8000Hz but stutters down to 6000Hz and back under load, because inconsistent reporting is exactly what your hand notices as "off". When you test, watch the steadiness of the reading, not just the highest number it touches.
Most gaming mice let you pick a polling rate in their companion software — Logitech G HUB, Razer Synapse, SteelSeries GG, Corsair iCUE and similar apps all expose it, usually under a "Performance" or "Polling" section. Choose your rate, apply, and the setting is stored on the mouse.
Run the test a couple of times and watch the peak and average. Wireless mice on battery-saving modes sometimes drop their rate, so it is worth confirming rather than trusting the box. Polling rate is only one piece of responsiveness, though — if your clicks feel slow, the delay may be in the switch rather than the sensor, which our click latency guide explains.