Mouse Polling Rate Explained (Hz, and What It Changes)
Polling rate is how many times per second your mouse tells the computer where it is. That is the whole concept. A 1000Hz mouse reports a thousand times a second, once every millisecond; a 125Hz mouse reports every eight milliseconds.
What people get wrong is assuming the number is a quality rating. It is not. It is a trade-off, and past a certain point the returns are small enough to be debatable.
What the numbers mean in practice
| Polling rate | Report interval | Where you find it |
|---|---|---|
| 125Hz | 8ms | Office mice, older hardware, battery-saving wireless modes |
| 500Hz | 2ms | A common default, and genuinely fine for most people |
| 1000Hz | 1ms | The standard for gaming mice, and the practical sweet spot |
| 4000–8000Hz | 0.25–0.125ms | Recent high-end mice; needs a capable CPU to be worth using |
The jump from 125Hz to 500Hz is the one most people can actually feel — 8ms of delay is perceptible as slight sluggishness when you move quickly. From 500Hz to 1000Hz the difference is subtle. Above 1000Hz, honest testing suggests most people cannot reliably tell in a blind comparison.
What polling rate is not
It is not DPI. DPI is how far the cursor moves per inch of hand movement — sensitivity. Polling rate is how often the mouse reports. They are independent, and changing one does not affect the other. People conflate them constantly, including in product marketing. If your cursor feels too fast or too slow, you want DPI, not polling rate.
It is not frame rate, either. A 1000Hz mouse on a 60Hz monitor still reports a thousand times a second; the display just cannot show every update. The reports still matter — games sample input independently of when frames are drawn — but the benefit is smaller than the numbers suggest.
And it is not a fix for stutter. If your mouse is stuttering, polling rate is almost certainly not the cause. Look at interference or the surface first.
How to check what yours is set to
Three routes, depending on what you have.
The mouse's own software is the most reliable. G HUB, Synapse, iCUE and equivalents all show the current polling rate and let you change it. This tells you what the mouse is configured to do, which is what you usually want to know.
A hardware button. Some mice cycle polling rate with a button underneath, often the same one that changes DPI when held. Check the manual — people change this by accident and then wonder why the mouse feels different.
Measuring it requires timing the gaps between movement reports, which needs either a dedicated utility or a browser page that timestamps every pointer event. Our mouse test shows movement and button behaviour live, which is what you want for diagnosing tracking problems — but for a precise Hz figure, a purpose-built polling rate utility on Windows will give you a more trustworthy number than any browser can, because the browser adds its own timing layer.
That last point is worth being clear about: any in-browser polling measurement is approximate. The browser batches and throttles events, and what you measure includes the browser's own scheduling, not just the mouse's. Treat browser figures as a rough indication rather than a specification test.
Should you turn it up?
If you are at 125Hz, yes — move to 500Hz or 1000Hz. That is a real, noticeable improvement and there is no meaningful downside on any computer made this decade.
If you are at 1000Hz, leave it alone unless you have a specific reason. Going to 4000Hz or 8000Hz has genuine costs:
- CPU load. At 8000Hz the system processes eight thousand interrupts per second from the mouse alone. On a mid-range CPU under load in a game, that can cost you more in frame time than it gains in input latency.
- Battery life. On a wireless mouse, high polling rates drain the battery dramatically faster — often less than half the runtime.
- Compatibility. Some older USB controllers and some motherboards behave badly above 1000Hz, producing stutter rather than smoothness.
There is a reason many competitive players stay at 1000Hz on hardware capable of far more.
When lowering it is the right answer
Counterintuitive but real. If your mouse feels worse at a high polling rate than a low one, drop it and see. Causes include a CPU that cannot keep up, a USB controller struggling, and — on wireless — a link that becomes unstable at high report rates in a congested environment.
On a laptop running on battery, dropping to 500Hz is a sensible default. You will not notice the difference in a spreadsheet, and you get meaningfully more runtime.
Check how your mouse actually tracks and clicks.
Open the mouse test →FAQ
Is 1000Hz enough for competitive gaming?
Yes. 1000Hz means a report every millisecond, which is well below the threshold at which people can reliably detect a difference in blind testing.
Plenty of professional players run at 1000Hz on mice capable of 8000Hz, because the CPU cost of the higher rate can cost more in frame stability than it gains in latency.
Does polling rate affect DPI or sensitivity?
No — they are completely independent. DPI controls how far the cursor travels per inch of hand movement; polling rate controls how often the mouse reports its position.
Changing polling rate will not make your cursor faster or slower. If that is what you want, change DPI.
Can I measure polling rate accurately in a browser?
Only approximately. A browser can timestamp pointer events, but it also batches and throttles them, so what you measure includes the browser's own scheduling.
For a trustworthy figure, use a dedicated polling rate utility on Windows, or simply read the setting in your mouse's own software.
Why does my wireless mouse drop to 125Hz on battery?
Because a power-saving profile has lowered it deliberately. High polling rates are one of the biggest drains on a wireless mouse's battery.
Most vendor software lets you set different polling rates for wired and wireless operation, or disable the power-saving profile entirely if you would rather have the performance.