How to Actually Test Your Mouse Polling Rate (And What the Numbers Mean)
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mouse Polling Rate TestBrowser-based polling rate tests are accurate enough for 95% of diagnostics, but they cap out around 2000 Hz due to JavaScript timer resolution limits, so any mouse claiming 4000 Hz or 8000 Hz needs hardware-level verification to confirm. The discrepancy comes from how browsers schedule input events: the underlying OS interrupt fires at the correct interval, but mousemove event timestamps get coalesced by the browser's compositor thread, compressing multiple hardware reports into a single frame. On a 4000 Hz mouse like the Razer Viper V3 HyperSpeed or Logitech G Pro X Superlight 2, you will routinely see a browser tool report 1800โ2200 Hz even when the mouse is functioning perfectly at spec.
What Polling Rate Actually Measures at the Hardware Level
Polling rate is the frequency at which the mouse's onboard MCU sends a position report packet over USB or wireless. At 125 Hz the host receives one packet every 8 ms. At 1000 Hz that drops to 1 ms. At 8000 Hz it is 0.125 ms. The sensor itself, typically a PixArt PAW3395, PAW3950, or HERO 25K, samples at a much higher internal rate (up to 12,000 frames per second on the PAW3395) and the MCU averages or interpolates those frames before packing them into the USB HID report.
USB full-speed HID has a hard ceiling of 1000 Hz because the USB frame period is 1 ms. Mice that advertise 2000โ8000 Hz get around this by using USB high-speed mode with microframes (125 ยตs intervals) or by sending multiple position deltas inside a single HID report, a technique Razer calls HyperPolling and Logitech implements in Lightspeed 2. If your USB controller does not support high-speed mode, the mouse firmware silently falls back to 1000 Hz and you will never see the difference in a browser test.
How to Run an Accurate Browser Polling Rate Test
Use the Mouse Polling Rate Test on this site. The tool samples mousemove event deltas over a 5-second window and calculates average and peak reported Hz. To get the most reliable reading, follow this exact procedure:
- Close every other browser tab. Background tabs trigger garbage collection pauses that steal timer budget and artificially lower your reading.
- Set your mouse polling rate in its companion software before testing. In Logitech G HUB go to your device, click the gear icon, select Report Rate, and choose your target value (125 / 500 / 1000 / 2000 / 4000 Hz depending on model). In Razer Synapse 3 it is under Performance, then Polling Rate. SteelSeries GG uses Settings, then Mouse, then Polling Rate. Apply and unplug/replug the cable or receiver to force the firmware to reload the setting.
- Move the mouse in slow, steady circles during the capture window. Fast flicks cause the sensor to engage motion prediction and can skew the delta distribution.
- Run the test three times and average the peak values. A single run is not statistically meaningful.
Expected browser-reported values versus hardware spec are shown in the table below.
| Hardware Polling Rate | Typical Browser Test Result | Acceptable Range |
|---|---|---|
| 125 Hz | 118โ125 Hz | 110โ125 Hz |
| 500 Hz | 470โ500 Hz | 450โ500 Hz |
| 1000 Hz | 920โ1000 Hz | 880โ1000 Hz |
| 2000 Hz | 1400โ1900 Hz | 1200โ2000 Hz |
| 4000 Hz | 1600โ2200 Hz | 1400โ2200 Hz |
| 8000 Hz | 1800โ2400 Hz | 1600โ2500 Hz |
If your 1000 Hz mouse reads below 880 Hz consistently, that is a real problem worth investigating. If your 8000 Hz mouse reads 2100 Hz, the tool is not broken and neither is your mouse.
Hardware-Level Verification for High-Polling Mice
To confirm 4000 Hz or 8000 Hz operation you need to bypass JavaScript entirely. The two practical methods are USB protocol analysis and OS-level event logging.
USB protocol analysis: A USB analyzer like the Beagle USB 480 or the cheaper OpenVizsla captures raw USB traffic. You connect it inline between the mouse and the host port, start a capture, move the mouse for 10 seconds, then count interrupt transfer packets in the 125 ยตs microframe slots. This confirms actual on-wire polling, not host-side event processing. This is what manufacturers use internally and it is the only ground-truth method.
OS-level event logging on Windows: Open an elevated PowerShell prompt and run Get-PnpDevice -Class Mouse | Select FriendlyName, DeviceID to confirm your device is enumerated as a high-speed HID device. Then use RawInput logging via a small C++ hook or the free MouseTester utility by MarkC. MouseTester plots interval histograms directly from WM_INPUT messages, which arrive before any browser compositor touches them. A genuine 4000 Hz mouse will show a tight histogram peak at 0.25 ms intervals. A 1000 Hz mouse stuck at 1 ms intervals is not operating at its rated spec.
On Linux: Run sudo evhz from the evtest package. It reads directly from /dev/input/eventX and reports instantaneous and average Hz with no browser in the path. This is the fastest sanity check available on any platform.
While you have the mouse open for inspection, it is also worth running a Double Click Test to rule out microswitch bounce issues that can inject spurious reports and distort polling measurements. Omron D2FC-F-7N switches with over 20 million actuations commonly develop contact bounce that looks like elevated polling in naive event counters.
Common Reasons Your Polling Rate Test Reads Low
- USB port is USB 2.0 full-speed, not high-speed. Full-speed ports (often labeled in white on older boards) cannot support sub-1 ms microframes. Plug into a USB 3.x port (blue or labeled SS) to enable high-speed mode for 2000+ Hz mice.
- Polling rate not saved in firmware. Some mice store the polling rate in volatile RAM and reset to 125 Hz after power cycle. Confirm in software that the setting persisted. Firmware update may be required.
- USB hub in the path. Most unpowered hubs re-enumerate devices at full-speed. Connect directly to the motherboard rear IO or a dedicated PCIe USB controller card.
- CPU parking and C-states. On Windows, aggressive C-state entry (C6/C7) introduces latency spikes that the browser test interprets as dropped reports. In Device Manager under Processor, disable C-State control, or set the Windows power plan to High Performance.
- Wireless receiver interference. A 2.4 GHz receiver sharing spectrum with a Wi-Fi router on channel 6 will drop packets. Move the receiver to a USB port on the opposite side of the chassis from the Wi-Fi antenna or use a short USB extension to position it away from interference.
If you are also testing keyboard input latency during this session, the Mouse Test tool can confirm basic HID connectivity before you dig into polling specifics.
Frequently Asked Questions
Is a browser polling rate test accurate enough for gaming diagnostics?
Yes, for mice rated at 1000 Hz or below. The browser result will be within 5โ10% of actual hardware polling and that is close enough to confirm whether your mouse is operating at 125 Hz, 500 Hz, or 1000 Hz. For 4000 Hz and 8000 Hz claims you need OS-level tools like evhz or MouseTester to get meaningful data.
My mouse is set to 1000 Hz but the test shows 750 Hz. What is wrong?
First suspect the USB port. Plug directly into a rear motherboard port, not a front panel header or hub. Second, check that your mouse firmware actually saved the setting by power cycling and reopening the companion software. Third, check Windows power settings: go to Control Panel, Power Options, Change Plan Settings, Change Advanced Power Settings, then set USB Selective Suspend to Disabled.
Does a higher polling rate improve aim?
At 1000 Hz versus 125 Hz, yes, measurably. The cursor position update latency drops from 8 ms to 1 ms, which matters at high sensitivity. Above 1000 Hz the benefit depends entirely on whether your GPU and monitor pipeline can render frames faster than 1 ms. At a 240 Hz monitor with a 4.17 ms frame time, the difference between 1000 Hz and 4000 Hz is largely masked by display latency.
Can I damage my mouse by running it at a higher polling rate?
No. Polling rate is a USB communication parameter controlled by the host and firmware. It does not affect the optical sensor hardware, the microswitch actuation mechanism, or the scroll encoder. The only cost is slightly higher CPU interrupt load, which on any modern processor is negligible even at 8000 Hz.
Why does my wireless mouse show a lower polling rate than the wired version?
Wireless mice use a radio protocol between the sensor MCU and the USB receiver dongle. That radio link has its own latency and packet scheduling, and most 2.4 GHz implementations cap at 1000 Hz effective report rate regardless of what the wired variant supports. Logitech Lightspeed 1 is 1000 Hz wireless; Lightspeed 2 reaches 2000 Hz wireless. Bluetooth HID is capped at 125 Hz by the protocol spec and is unsuitable for gaming use.
How do I test if my polling rate changes under load?
Run the Mouse Polling Rate Test while simultaneously running a CPU stress tool like Prime95 small FFTs in the background. Compare the result to a baseline idle test. A drop of more than 15% under CPU load indicates that interrupt handling is being deferred by the OS scheduler, which is fixable by setting the process priority of your game or application to High in Task Manager.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mouse Polling Rate Test