Polling rate is one of the most discussed and least understood mouse specifications. This guide gives you the actual numbers so you can decide what matters.
What polling rate is
Polling rate, also called report rate, is how many times per second your mouse tells your computer where it is. It is measured in hertz.
A 1000 Hz mouse sends a position report every millisecond. A 125 Hz mouse sends one every eight milliseconds.
It has nothing to do with DPI. DPI describes how far the cursor moves per unit of physical movement — sensitivity. Polling rate describes how often that movement is reported — freshness. You can have high DPI and low polling rate, or the reverse.
The actual latency numbers
Here is what each step buys you in worst-case delay before your movement is reported:
| Rate | Interval | Worst-case wait | Saved vs previous |
|---|---|---|---|
| 125 Hz | 8.0 ms | 8.0 ms | — |
| 250 Hz | 4.0 ms | 4.0 ms | 4.0 ms |
| 500 Hz | 2.0 ms | 2.0 ms | 2.0 ms |
| 1000 Hz | 1.0 ms | 1.0 ms | 1.0 ms |
| 2000 Hz | 0.5 ms | 0.5 ms | 0.5 ms |
| 4000 Hz | 0.25 ms | 0.25 ms | 0.25 ms |
| 8000 Hz | 0.125 ms | 0.125 ms | 0.125 ms |
The pattern is the important part. Every doubling halves the remaining delay, so every doubling delivers half the benefit of the previous one.
Going from 125 to 500 Hz removes 6 milliseconds. Going from 1000 to 8000 Hz removes less than one. The first change is noticeable; the second is not, for essentially anybody.
Put it in context
That 1 millisecond at 1000 Hz is one part of a much longer chain:
| Stage | Typical delay |
|---|---|
| Mouse polling at 1000 Hz | 1 ms |
| Operating system input stack | 1–4 ms |
| Game engine input processing | 1–16 ms |
| Render and present | 5–20 ms |
| Display at 144 Hz | 7 ms |
| Panel response and processing | 2–20 ms |
Total end-to-end latency on a good setup is somewhere around 20 to 40 milliseconds. Your polling rate is contributing one of them.
This is why upgrading from a 60 Hz to a 144 Hz monitor is transformative while upgrading from 1000 Hz to 8000 Hz polling is imperceptible. One removes about 9 milliseconds; the other removes below one.
When high polling rates actively hurt
Above 1000 Hz there is a real cost, and it is not theoretical.
Every mouse report is a USB interrupt your CPU must service. At 8000 Hz that is eight thousand interrupts per second, each one preempting whatever your processor was doing.
On a CPU-limited system — which describes most gaming systems at competitive settings — this measurably reduces frame rate. Reports of 5 to 10% frame rate loss at 8000 Hz are common, and in some cases higher.
You are trading roughly 0.9 milliseconds of input latency for several milliseconds of additional frame time. That is a losing trade, and it gets worse the more CPU-bound you are.
There is a second problem: not every game samples input fast enough to benefit. An engine polling input once per frame at 144 fps is looking at your mouse 144 times per second. Reporting at 8000 Hz means most of those reports are discarded before anything reads them.
What to actually set
1000 Hz for gaming. It is the sensible default, it is what most modern mice ship at, and the returns above it do not justify the cost.
500 Hz is fine for everything else, and genuinely indistinguishable from 1000 Hz for most people in most situations.
125 Hz is worth changing if you find yourself there. Many gaming mice ship at 125 Hz out of the box, and a surprising number of people never change it. This is the one adjustment on this page that you will actually feel.
Above 1000 Hz only if you have CPU headroom to spare, you have measured that it does not cost you frame rate, and you are competing at a level where you have already optimised everything else.
Check where you currently are with the polling rate test.
Stability matters more than the number
A stable 500 Hz mouse feels better than an erratic 1000 Hz one.
Consistent reporting is what your hand perceives as directness. When intervals vary — 1 ms, then 3 ms, then 0.5 ms — the inconsistency reads as stutter or weight, even though the average looks fine on paper.
The polling rate test reports a stability percentage alongside the rate for this reason. If yours is below about 55%, fix that before considering anything else. Common causes, in order:
- A USB hub or front-panel port. Plug directly into a rear motherboard port.
- 2.4 GHz interference. USB 3 devices emit noise right in the band wireless mice use. Move the receiver away, or use a USB extension to bring it out front.
- A damaged cable. Usually fraying near the strain relief where it leaves the mouse.
- Background CPU load. A saturated processor delays interrupt servicing.
- USB power management. Windows selective suspend can throttle a port. Disable it for that device in Device Manager.
Wireless is not the problem it used to be
Modern low-latency wireless from the major manufacturers runs at 1000 Hz and adds roughly 1 millisecond over wired. That is well below perceptual threshold for essentially everyone.
Bluetooth is a different matter — it typically runs at 125 Hz with variable latency, and is genuinely worse for gaming. If your mouse supports both, use the dedicated 2.4 GHz receiver rather than Bluetooth.
The summary
Set it to 1000 Hz. Confirm it is stable. Then stop thinking about polling rate and spend the attention on your monitor refresh rate, which is where the real latency is.