How to Check Your Mouse Polling Rate
Polling rate is how many times per second your mouse reports its position, in hertz. A 1000Hz mouse reports roughly every millisecond; a 125Hz mouse reports roughly every eight.
What polling rate changes
Polling rate sets how often new position data becomes available. Between reports, your computer has no idea the mouse has moved — the movement has happened physically but has not been communicated yet. A higher rate shortens that blind interval, which lowers the worst-case delay between your hand moving and the pointer following.
The effect is real but bounded. Going from 125Hz to 1000Hz removes several milliseconds of worst-case delay, which many people can feel. Going from 1000Hz to 8000Hz removes a fraction of a millisecond, which almost nobody can.
Measuring it honestly
A browser measures how frequently it receives pointer events, which tracks the hardware rate closely on a system that is not busy. It is an indicator rather than an instrument: browsers may batch events under load, which understates the true rate.
Move continuously while measuring. The reading counts reports per second, so any pause immediately pulls the number down and makes a fast mouse look slow. Read the peak value rather than the live one.
Why yours may be lower than advertised
The most common reason is simply that it is set lower. Many gaming mice ship at a conservative default and need their software, or an on-board button combination, to raise the rate. Checking the setting resolves most cases.
Beyond that, the port matters. Some hubs and front-panel connectors cannot sustain the highest rates. Wireless mice frequently use a lower rate on battery to extend life, raising it only when a performance mode is enabled.
When higher stops being better
Very high polling generates far more interrupts for the CPU to service. On some systems that overhead causes stutter which costs more time than the reduced latency saves, and the result is a setup that measures better and feels worse.
The practical approach is to test rather than assume. If 8000Hz introduces hitching that 1000Hz does not, the lower setting is the better one for that machine regardless of what the specification implies.
Test it yourself: Mouse Polling Rate Test
Frequently Asked Questions
What polling rate should I use?
1000Hz is the sensible default for gaming and is enough for almost everyone. 125Hz is the common office default and is noticeably less smooth for fast movement. Rates above 1000Hz give diminishing returns and can cause stutter on some systems.
Why does my mouse test lower than its advertised rate?
Usually because it is not set to the advertised rate — check the mouse's software or on-board profile first. Other causes are a USB port or hub that cannot sustain it, a wireless power-saving mode, or a busy system causing the browser to batch events.
Does polling rate affect aim?
Indirectly. It reduces the delay before your movement is registered, which makes tracking feel more immediate. It does not change accuracy on its own, and its effect is much smaller than sensitivity, sensor quality and practice.
Is polling rate the same as DPI?
No, and they are frequently confused. DPI is how far the pointer travels per inch of physical movement — a sensitivity setting. Polling rate is how often position is reported — a timing setting. Neither can be derived from the other.
Can a browser measure polling rate accurately?
It measures the rate at which the browser receives pointer events, which closely follows the hardware rate on an idle system. Close other applications, move continuously, and treat the peak figure as the useful one.
Sources: MDN — MouseEvent · MDN — Pointer events · MDN — performance.now()
Found an error on this page, or a result that does not match your hardware? Tell us and we will correct it.