What polling rate is: the hidden floor on latency
Polling rate is how often your mouse reports its position and button state to the PC: at 125Hz that's every 8 ms, at 1000Hz every 1 ms. This interval sets a floor on input lag — no matter how fast you click, the PC doesn't know until the next report, so a 125Hz mouse starts every action with roughly 4 ms of average built-in delay.
Office and budget wireless mice mostly run at 125Hz; gaming mice standardize on 500–1000Hz, with 4000–8000Hz models now on the market. But what your mouse actually runs at is a matter of measurement, not the spec sheet — settings, hubs, and wireless conditions frequently drag real-world operation below the rating.
125Hz vs 500Hz vs 1000Hz vs 4000/8000Hz: tier by tier
The arithmetic is the honest starting point. Polling rate is reports per second, so the report interval is simply one second divided by the rate: 125Hz is one report every 8 ms, 500Hz every 2 ms, 1000Hz every 1 ms, 4000Hz every 0.25 ms, and 8000Hz every 0.125 ms. Because a click or a movement can land anywhere inside that interval, the average delay it adds is about half the interval: roughly 4 ms at 125Hz, 1 ms at 500Hz, 0.5 ms at 1000Hz, and a small fraction of a millisecond above that. Everything else in this section follows from those numbers.
125Hz is the USB default a mouse falls back to when nothing tells it otherwise, and it is what most office mice, budget wireless mice and Bluetooth connections run at. It is perfectly fine for spreadsheets and browsing. Where it shows is on a high-refresh monitor: a 144Hz display draws a frame roughly every 6.9 ms, so a 125Hz mouse cannot deliver a fresh position for every frame, and the cursor path during a fast flick looks like a string of beads rather than a line. In a shooter this is the tier where players genuinely feel the difference when they move up.
500Hz halves that interval to 2 ms and was the enthusiast standard for years. It supplies a new position for every frame up to 500 fps, which covers any monitor you are likely to own, and the average added delay drops to about 1 ms. For most people the jump from 125 to 500Hz is the largest single improvement in this whole discussion; the remaining steps are refinements.
1000Hz, one report per millisecond, is what practically every gaming mouse made in the last decade supports, wired or on a dedicated 2.4 GHz receiver. It is the tier where cursor motion stops being the bottleneck: at 1 ms granularity the position sampling is finer than any current display's frame interval, the added latency is around half a millisecond on average, and the CPU cost of handling a thousand small USB packets per second is trivial on modern hardware. This is the sensible default for almost everyone, and it is the number our mouse test should read back when you swing the cursor in fast circles.
4000Hz and 8000Hz shorten the interval to 0.25 ms and 0.125 ms. On paper that removes almost all of the remaining sampling delay, and in high-speed-camera comparisons the cursor trail is measurably smoother. In practice the gain is bounded by everything downstream: the display still refreshes at its fixed rate, the game still simulates at its own tick rate, and your own reaction time is measured in hundreds of milliseconds. Going from 1 ms to 0.125 ms saves under a millisecond, which is why returns diminish so sharply above 1000Hz.
Those tiers also carry real costs that the lower ones do not. The mouse must be able to do it, and on wireless models that usually means a specific high-speed receiver and, for wired use, the cable it shipped with, since an ordinary dongle will not carry 8000 reports per second. Wireless battery life drops noticeably, because the radio is transmitting eight times as often; vendors publish much shorter runtime figures for their 4K and 8K modes than for 1000Hz. The operating system and the game have to process eight times as many input events, which shows up as measurable CPU load in some titles, and there are well-documented reports of stutter or frame-time spikes in older games and in some engines that were never written with an 8 kHz device in mind. Windows itself was designed around far lower report rates, and while modern versions cope, the extra interrupt load is not free.
Who benefits, then? A competitive FPS player on a 240Hz or faster monitor, with a strong CPU that has headroom to spare and a game that is known to handle high polling well, may get a slightly smoother and more consistent feel from 4000 or 8000Hz. That is a narrow group. If you are not in it, set 1000Hz, confirm it with our test, and spend the attention elsewhere. If you are in it, try 2000 or 4000Hz first, and drop back the moment you see frame-time spikes; the difference between 4000 and 8000Hz is one eighth of a millisecond.
Measuring it: thirty seconds in the browser
Move your cursor in fast circles inside the test area of our mouse test and watch the max polling rate card. Under the hood we aggregate movement-event timestamps over a one-second window — and because browsers coalesce pointer events per frame, we use the getCoalescedEvents API to recover the true hardware report interval rather than your monitor's frame rate.
Slow movement generates fewer events and reads low, so move fast and continuously for an accurate figure. Repeat a few times and take the highest reading as your mouse's effective rate. Converging near a clean value — 125, 500, 1000 — is the expected, healthy result.
Changing it: where the setting lives
Gaming mice expose polling rate in their vendor software (Logitech G HUB, Razer Synapse, SteelSeries GG, and so on); some let you switch it in hardware with a bottom switch or DPI-button combo. Make a habit of re-measuring with our test after changing it — that's how you catch a setting that silently didn't apply.
If the spec says 1000Hz but you measure 125Hz, the usual culprits are: vendor software not installed (mouse running its default profile), a wireless mouse in power-saving mode, a USB hub in the path, or a poorly placed receiver. Moving the dongle to a front port or an extension cradle near the mouse fixes a large share of wireless cases.
How to change polling rate, by manufacturer
Polling rate is almost always a device setting rather than a Windows or macOS setting, so the place to change it is the mouse's own software or its hardware controls. The paragraphs below describe where the option generally lives for the major brands. Menu layouts change between software versions, so treat them as a map rather than a click-by-click path, and check the manual for your exact model if a setting is not where you expect.
Logitech gaming mice are configured in G HUB, where the report rate is a per-profile setting alongside DPI. Because it is per profile, a mouse can read 1000Hz in one game and 125Hz on the desktop if the profiles differ, so check the active profile when a measurement surprises you. Wireless Logitech mice may also cap the report rate when a battery-saver option is enabled, and some newer models unlock rates above 1000Hz only after a firmware update through the same software.
Razer mice use Synapse, where the polling rate sits in the Performance area next to sensitivity. Standard wired and HyperSpeed wireless models offer up to 1000Hz there. Rates of 4000 and 8000Hz require a compatible mouse paired with Razer's HyperPolling wireless dongle, or the supported wired connection, and only then do the higher options appear in the list.
SteelSeries mice are set in the GG application, inside its Engine section, where each device has a polling rate selector. As with Logitech, settings can be tied to a profile or a configuration slot saved on the mouse, so make sure the slot you are using is the one you edited.
Corsair mice are managed in iCUE. The polling rate is a device-level setting on the mouse's page, separate from DPI stages and lighting, and applying it writes the value to the mouse's onboard memory so it persists without the software running.
Zowie takes a hardware-only approach: most models have no software at all, and the report rate is chosen with a physical switch or a button on the underside of the mouse, typically stepping through 125, 500 and 1000Hz. Because there is no software layer to fail, a Zowie that reads 125Hz in our test almost always just has the switch in the wrong position.
Glorious mice use the Core software for polling rate and DPI, and many models also support changing the polling rate with a DPI-button combination, for example holding the DPI button while pressing a specific mouse button, so the setting can be changed without the software installed. The exact combination is model specific and is listed in the quick-start guide.
Generic and office mice with no software are usually fixed at 125Hz, and a minority ship fixed at 500Hz. A few allow a change by holding a button while plugging the mouse in, or via a hidden combination described in the manual, but many simply cannot be changed. If you need 1000Hz and the mouse cannot do it, no driver or Windows tweak will add the capability; the rate is decided by the mouse's firmware.
Whatever brand you use, the final step is the same: apply the setting, then open our mouse test and move the cursor in fast, continuous circles inside the test area. The max polling rate readout should climb to the value you just set. If it stays at the old figure, work through the usual suspects in order: connect the mouse or receiver directly to a port on the PC rather than through a hub or a monitor's USB ports, move a wireless receiver close to the mouse with a clear line of sight, confirm the profile or onboard slot you edited is actually the active one, and, for wireless models, make sure a battery-saver mode has not quietly overridden your choice.
How much do you actually need?
125Hz to 1000Hz is a real, perceptible upgrade — cursor motion is visibly smoother on high-refresh monitors and micro-adjustments in aim feel more consistent. If you game at all, set 1000Hz; virtually every gaming mouse supports it, so it costs nothing.
1000Hz to 8000Hz is a different conversation. Latency drops from 1 ms to 0.125 ms on paper, which is marginal against human reaction time (150–250 ms), and it costs real CPU usage plus occasional game-compatibility quirks. Unless you're a high-level competitive FPS player on a 240Hz+ monitor, 1000Hz is the rational resting point — 8000Hz is bought for want, not need, and that's fine as long as you know it.
Is a higher polling rate always better? Short answers to common questions
Does polling rate affect DPI or sensitivity? No. DPI is how far the cursor moves per inch of mouse travel; polling rate is how often that movement is reported. They are independent settings: raising the polling rate does not make the cursor faster, and raising DPI does not reduce latency. Set sensitivity by preference and polling rate for responsiveness, and adjust them separately.
Does a high polling rate help outside gaming? Only marginally. For browsing, office work and design, the difference between 500 and 1000Hz is not something most people can perceive, and 125Hz is adequate for pointing and clicking. If a mouse supports 1000Hz there is no reason not to use it on a wired connection, but there is also no reason to choose a mouse for its polling rate if you never game.
Why does my 1000Hz mouse read lower in a browser test? Browsers group pointer events and deliver them once per display frame, so a naive test would report your monitor's refresh rate instead of the mouse's report rate. Our test uses the getCoalescedEvents API to recover the individual hardware reports inside each frame, which is why it can read 1000Hz on a 60Hz display. Even so, very high rates such as 4000 or 8000Hz can still under-read in a browser because the event pipeline was not built for that volume. Two other common causes are a wireless mouse dropping into a power-saving state, and moving the cursor too slowly: fewer movement events per second means a lower reading. Move fast and continuously, and take the best of several runs.
Does polling rate matter on a 60Hz monitor? Less, but not zero. The display cannot show more than 60 positions per second, so the visual smoothness gain from 1000Hz is limited. Input latency still benefits slightly, though, because the game reads the latest position at the moment it builds each frame, and a 1 ms interval means that position is fresher than an 8 ms one. The practical advice does not change: 1000Hz costs nothing on a gaming mouse, so use it.
Can a high polling rate cause stutter? Yes, in specific circumstances. At 4000 or 8000Hz the system handles thousands of input events per second, and on a weaker or heavily loaded CPU, or in older games whose input code polls inefficiently, that can produce frame-time spikes or a stuttering cursor. 1000Hz very rarely causes this on modern hardware. If you see stutter after raising the rate, drop back to 1000 or 2000Hz and see whether it disappears; that test is more informative than any benchmark.
Is wireless polling as good as wired? On a dedicated 2.4 GHz receiver from a current gaming brand, yes: 1000Hz with latency indistinguishable from a cable is normal, and some models go higher with their special receivers. Bluetooth is the exception; it is designed around power saving and typically delivers around 125Hz or less, so use the receiver for games and Bluetooth for travel.