Quick answer: polling rate is how often your mouse reports to your PC. At the gaming standard of 1,000Hz, that's every millisecond. Going higher, to 4,000Hz or 8,000Hz, shaves off fractions of a millisecond, costs CPU time and battery, and can even make some games run worse. For most players, 1,000Hz is plenty.
Here's what the number means, and when the bigger ones are worth it.
What polling rate actually is
Your mouse doesn't stream movement continuously. It sends updates at a fixed rate. Tom's Hardware lays out the maths:
| Polling rate | Updates per second | Delay between updates |
|---|---|---|
| 125Hz | 125 | 8ms |
| 1,000Hz | 1,000 | 1ms |
| 8,000Hz | 8,000 | 0.125ms |
125Hz is the old default. The Godot engine team notes the USB standard long set mice at 125Hz, polled every eight milliseconds. 1,000Hz became the gaming standard, and Tom's Hardware notes that nearly every ultralight esports mouse now advertises up to 8,000Hz.
The same maths applies to any device that quotes a polling rate, controllers included: it's reports per second, and the delay is one second divided by that number.
Polling affects both how smooth movement looks and, more importantly, click latency: how quickly your click reaches the game.
The case for more, and the catch
The jump from 125Hz to 1,000Hz is a real improvement. Tom's Hardware calls it "definitely noticeable", cutting the gap from 8ms to 1ms. The jump from 1,000Hz to 8,000Hz cuts the gap by the same factor, but now you're saving less than a millisecond. Tom's Hardware doubts most players can feel that, and points out you'd need at least a 240Hz monitor before any extra smoothness is more than perceived.
Then there are the costs:
- CPU load. More reports per second means more work for your PC. Tom's Hardware warns that without a solid gaming CPU, the performance hit can outweigh the latency gain.
- Battery life. On wireless mice it drops hard. Tom's Hardware's examples include the Corsair Sabre v2 Pro Wireless going from 120 hours at 1,000Hz to 21 hours at 8,000Hz, and the Razer Basilisk V3 Pro 35K from 150 hours to 28.
- Game compatibility. This is the sneaky one.
When high polling breaks games
The Godot team wrote about exactly this problem on Windows. Higher polling means Windows receives far more mouse events, and if a game can't process them fast enough, the frame rate can "drop to the single digits." Godot says the threshold is roughly 1 to 2kHz on most current CPUs, depending on single-core speed. The cause is partly how Windows delivers two kinds of mouse events, legacy and raw input, at once.
Godot fixed this in its own engine, and the before-and-after numbers show how bad it can get. On a high-end test PC with an 8,000Hz mouse, a captured-mouse scene went from under 1 FPS to 1,703 FPS after the fix. Godot notes that the gains were smaller at 2kHz on that fast CPU, but bigger on slower and laptop processors. Other games and engines may handle it differently, but it shows why a fancy mouse can make a game stutter.
What to set
- Start at 1,000Hz. It's the long-standing gaming standard, and nothing above is guaranteed to feel better.
- Try higher only with the hardware for it: a strong CPU and a 240Hz-plus monitor.
- If a game stutters when you move the mouse, drop the polling rate in your mouse's software before blaming the game.
- On wireless, watch your battery. At 8,000Hz you may be charging most days.
Some mice need a separate dongle or dock to reach 8,000Hz, so check what yours supports. As for keyboards at 8,000Hz, Tom's Hardware's verdict is "absolutely not."
Reporting notes