Mouse polling rate is one of those specs that sounds complicated but is actually simple once you understand it. It tells you how many times per second your mouse sends its position data to your computer. The higher this number, the faster your computer knows where your cursor is. For gamers and anyone doing precision work, this matters more than most people realise.
This guide will walk you through everything. You will learn what polling rate means, how to test it on Windows, Mac, and Linux, and how to make sense of the numbers you get back. You can test your mouse polling rate right now using our free online tool before reading further, so you have a real number to refer to as you go through this guide.
What Mouse Polling Rate Actually Means
Polling rate is measured in Hertz (Hz). A mouse set to 1000 Hz sends its position to your PC exactly 1000 times every second. That works out to one update every 1 millisecond. A mouse running at 125 Hz only updates every 8 milliseconds.
The difference between 1 ms and 8 ms might sound tiny. In real gaming scenarios, especially in fast FPS titles, that gap is the difference between your crosshair landing on target and missing by a pixel.
Here are the most common polling rate values and what they mean in practical terms.
125 Hz means your mouse reports every 8 ms. This is the minimum on most mice and feels noticeably sluggish in competitive gaming.
250 Hz means a report every 4 ms. Acceptable for casual use but not ideal for fast-paced games.
500 Hz means a report every 2 ms. A solid middle ground that most mid-range gaming mice use by default.
1000 Hz means a report every 1 ms. This is the standard for gaming mice and what most competitive players target.
2000, 4000, and 8000 Hz options now exist on high-end gaming mice from brands like Razer and Logitech. These push the update interval below 1 ms, though the real-world benefit depends heavily on your system’s ability to handle the increased data.
One important distinction worth understanding is the difference between polling rate and DPI. Polling rate controls how frequently movement data is sent to your computer. DPI controls how far your cursor travels per inch of physical mouse movement.
They are related but different. You can have a 1000 Hz polling rate with low DPI, or a high DPI setting with a slow polling rate. For the best experience, you want both optimised.
Before You Run the Test
A few quick checks before testing will make sure your results are accurate and consistent.
Connect your mouse directly to a rear USB port on your motherboard. Front panel ports and USB hubs can introduce timing inconsistencies that give you false low readings.
If you use a wireless mouse, test it in both wired and wireless modes separately. This shows you exactly how much latency your wireless connection is adding.
Open your mouse’s software before testing. Tools like Logitech G HUB, Razer Synapse, and SteelSeries GG let you manually set the polling rate. Set it to your desired value, apply it, and then run the test.
Close any heavy background applications. Browsers with many tabs, video players, and download managers can all create CPU and USB interrupts that skew your results.
Move your mouse in slow, steady circles during the test rather than random movements. Consistent movement produces more stable and readable data.
How To Test Your Mouse Polling Rate on Windows
Windows gives you several ways to check polling rate depending on how deep you want to go.
The fastest method is using a browser-based tool. Open our mouse rate test page, click start, and move your mouse in slow circles for about 15 to 20 seconds. The tool will display your average polling rate and peak rate in real time. Run it two or three times to confirm consistency.
The browser method is quick and requires no installation. It works for both wired and wireless mice. The only limitation is that browser performance and background system load can slightly affect readings, so running multiple tests gives you a more reliable average.
For deeper analysis, software tools like MouseTester record the precise timestamp of every single report your mouse sends. You can then view the data as a histogram or interval chart. A healthy 1000 Hz mouse will show intervals clustered tightly around 1.0 ms with very few outliers. A 500 Hz mouse will cluster around 2.0 ms. Wide spread in the intervals indicates instability.
If you want the most precise measurement possible, advanced users can inspect USB endpoint descriptors using device tree viewer tools. These show the exact polling interval your device is requesting at the hardware level and can reveal if a hub or USB controller is capping your rate below what the mouse software shows.
For troubleshooting on Windows 10 and 11, open Device Manager and look under USB controllers. Right-click each USB hub, go to Properties, then Power Management, and uncheck the option that allows Windows to turn off the device to save power.
Also go to your Windows power plan settings and switch to High Performance mode. Both of these changes prevent Windows from throttling USB reporting to save energy.
How To Test Your Mouse Polling Rate on Mac and Linux
Mac and Linux users have fewer dedicated tools available but can still get accurate results.
On macOS, a browser-based polling rate test is the most practical approach. Open the tool, move your mouse in steady circles, and record the average across multiple runs. Vendor software like Logitech G HUB for Mac can set report rate on supported models, but always verify the change actually took effect by running a test after applying it.
Third-party Mac mouse utilities generally adjust acceleration and sensitivity rather than true USB polling rate, so the browser test remains your most reliable verification method.
On Linux, the browser-based approach also works well for a quick check. For more detailed analysis, you can use the libinput debug-events command in a terminal to monitor event timestamps.
If the time difference between consecutive events clusters near 0.001 seconds, your mouse is running at approximately 1000 Hz. If it clusters near 0.002 seconds, you are at 500 Hz. Running this under a consistent CPU governor setting, such as performance mode, will give you cleaner data.
Regardless of your operating system, the interpretation of results is the same. Tight, consistent intervals mean stable polling. Wide, scattered intervals mean something in your chain, whether the mouse itself, the USB port, or the OS, is introducing inconsistency.
How To Read Your Results
Getting a number is only half the job. Understanding what that number means for your specific situation is what actually helps you improve your setup.
A mouse targeting 1000 Hz should show average readings between 950 and 1000 Hz. Some variation is completely normal. Modern operating systems and USB controllers are not perfectly deterministic, so a small amount of fluctuation is expected and harmless.
A 500 Hz mouse should average between 480 and 500 Hz under normal conditions.
What you should watch for is the difference between occasional spikes and persistent drops. Occasional spikes, where the measured rate briefly goes above or below your target, are normal and nothing to worry about. Persistent drops, where your 1000 Hz mouse consistently reads 250 Hz or lower, indicate a real problem in your setup.
The most common causes of persistent drops are USB power saving features throttling the connection, a USB hub limiting the report rate, wireless interference affecting the dongle, or outdated mouse firmware.
Jitter, which shows up as a very wide spread in your interval data rather than a tight cluster, usually points to driver contention, high background CPU usage, or DPC latency issues in Windows. Tools like LatencyMon can help identify which drivers are causing DPC spikes if jitter is your main problem.
On the question of whether higher is always better, the honest answer is that it depends on your system. On modern hardware with a clean Windows installation, 1000 Hz is almost always the right choice.
On older systems or those with high background load, 500 Hz can actually produce more stable and consistent results than 1000 Hz. Running the test at both settings and comparing the stability of your interval data is the best way to decide.
Comparison: polling rate vs DPI
| Aspect | Polling Rate | DPI |
|---|---|---|
| What it controls | Report frequency (Hz) | Cursor distance per inch |
| Impacts | Latency and responsiveness | Sensitivity and precision |
| Typical values | 125-1000 Hz, up to 8K on select gear | 400-3200+ for gaming |
| When to raise | To cut input delay or smooth micro-tracking | When you need finer granularity without high in-game sens |
Fixing Low or Inconsistent Results
If your test results are lower than your target rate or showing a lot of instability, work through these fixes one at a time, running the test again after each change.
Move your mouse to a rear motherboard USB port if you have not already. This is the single most effective hardware change for improving polling rate stability.
For wireless mice, move the USB receiver closer to the mouse using a USB extension cable. Keep it away from other wireless devices, Wi-Fi routers, and other USB devices that broadcast on the 2.4 GHz band.
Disable USB selective suspend in Windows power settings. This setting is designed to save power but it directly interferes with consistent USB polling.
Update your mouse firmware through your manufacturer’s software. Polling rate improvements and stability fixes are common in firmware updates, particularly on newer high-Hz mice.
Close RGB software, overlay tools like Discord and Xbox Game Bar, and any applications that are making frequent USB or HID calls while you test. These can compete with your mouse for USB bus time.
If you recently changed any BIOS settings related to USB behaviour, revert them. BIOS-level USB tweaks rarely improve polling rate and frequently cause instability.
How Often Should You Test
Test your polling rate any time you change something in your setup. Switching USB ports, updating firmware, adding a hub, or moving from wired to wireless are all reasons to run a fresh test.
If you play competitively, a quick monthly check is a good habit. OS updates and driver updates occasionally change USB power management behaviour in ways that affect polling rate without any obvious sign.
Always run at least two or three trials per configuration and use the average across those runs rather than a single reading. A single test can be affected by a momentary system spike that does not reflect your typical performance.
For the most accurate picture of your actual gaming performance, combine the browser-based test for quick checks with a logging tool for deeper interval analysis. The browser tool tells you if your rate is roughly correct. The logging tool tells you how stable and consistent it actually is over time.
You can run our free mouse polling rate test anytime to check your current setup. For more on how keyboard input timing affects your overall gaming performance, read our guide on reducing keyboard latency in gaming.