Polling Rate to Milliseconds: The Actual Latency Math
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mouse Polling Rate TestA 1000 Hz polling rate gives you exactly 1 ms between USB reports, but that number is not your total input latency. The polling interval is only one slice of the full signal chain, which also includes the optical sensor integration window, the microcontroller debounce timer on the click switches, USB interrupt scheduling jitter on the host controller, and the display's own scan-out latency. Conflating polling interval with end-to-end latency is the single most common mistake made when comparing mice on spec sheets.
The Core Math: Polling Rate Converted to Milliseconds
The formula is straightforward: report interval in milliseconds equals 1000 divided by polling rate in Hz. That is it. No weighting, no correction factor.
| Polling Rate (Hz) | Report Interval (ms) | Reports per Second | Typical Use Case |
|---|---|---|---|
| 125 | 8.0 ms | 125 | Office mice, legacy USB hubs |
| 250 | 4.0 ms | 250 | Older gaming mice, some wireless |
| 500 | 2.0 ms | 500 | Mid-tier gaming, eSports default |
| 1000 | 1.0 ms | 1000 | Standard gaming, most flagship wired |
| 2000 | 0.5 ms | 2000 | Razer HyperPolling, select wireless |
| 4000 | 0.25 ms | 4000 | Razer HyperPolling 4K, Pulsar Xlite V3 |
| 8000 | 0.125 ms | 8000 | Logitech HERO 8K, Razer 8KHz devices |
So when someone asks what is 1000 Hz polling rate in ms, the answer is 1.0 ms per report. At 8000 Hz it drops to 0.125 ms. The polling rate response time improvement from 1000 Hz to 8000 Hz is 0.875 ms on paper. Whether your eyes and hands can resolve that difference under real conditions is a separate argument entirely.
What Polling Rate Does Not Measure
The report interval tells you how often the mouse sends a packet to the host. It says nothing about the following hardware stages, all of which add their own latency on top of the polling interval.
- Sensor integration time. Optical sensors like the PixArt PAW3395 and PAW3950 have a configurable frame rate that determines how long the sensor exposes the surface. At 26000 DPI the integration window shrinks, but at lower DPI settings it can sit at 4 ms to 6 ms independently of polling rate.
- Switch debounce delay. Mice using Omron D2FC-F-7N switches or Kailh GM 8.0 switches apply a firmware debounce window, typically 2 ms to 10 ms, to suppress contact bounce on actuation. Mice with optical switches such as Razer's 3rd-gen optical or the Lightforce hybrid optical mechanism skip mechanical debounce entirely because there is no contact bounce to suppress, which is a real latency advantage on click response, not just a durability claim.
- USB host controller scheduling jitter. USB Full Speed (12 Mbps) schedules interrupt transfers in 1 ms frames by design. USB High Speed (480 Mbps) uses 125 ยตs microframes, which is why 8000 Hz polling requires a High Speed connection and will silently fall back to 1000 Hz on a Full Speed port or hub.
- Driver and HID stack processing. Windows HID class driver adds roughly 0.2 ms to 1 ms of processing overhead before the coordinates reach the application layer. This is not adjustable through device manager; it is a kernel scheduling artifact.
- Display scan-out. A 240 Hz monitor adds up to 4.17 ms of display latency. A 60 Hz panel adds up to 16.67 ms. Arguing about 0.875 ms of polling headroom while running a 60 Hz display is a waste of time.
You can verify what polling rate your mouse is actually reporting to the OS right now with the Mouse Polling Rate Test. It reads the raw HID report timestamps directly in the browser and calculates your real-world interval, including jitter. If you are expecting 1.0 ms and seeing 1.4 ms average, the problem is usually a USB hub, a shared USB controller on a budget motherboard, or a background process hammering the HID stack.
High Polling Rates and CPU Load: The Real Trade-off
Jumping from 1000 Hz to 8000 Hz multiplies the number of USB interrupts the CPU must service by a factor of eight. On a modern desktop processor this is negligible. On a laptop with aggressive power management or a CPU already saturated by a game, the interrupt load from 8000 Hz polling can produce measurable frame time spikes. Logitech's HERO sensor firmware handles this by processing motion data on-chip and only queuing a report when displacement has actually occurred, which reduces effective interrupt load at 8000 Hz during slow or stationary movement. Razer's implementation is less conservative and will queue reports at full rate regardless of motion, which is why some users see CPU spikes with HyperPolling 8K enabled on mid-range laptops.
If you are chasing click latency specifically rather than motion latency, the switch type matters more than polling rate above 500 Hz. A mouse running Huano Blue Shell Pink Dot switches with a 4 ms debounce window on a 1000 Hz polling rate will register clicks slower than a mouse with Lightforce hybrid optical switches and zero debounce delay at 500 Hz. Check your actual click registration consistency with the Double Click Test to see if your hardware is the bottleneck or if the issue is elsewhere.
For a broader look at whether your entire input chain is performing as expected, the Reaction Time Test gives you a practical end-to-end measurement that includes display latency, your own neural processing time, and click registration, which is ultimately what matters in real use.
Setting Polling Rate Correctly in Software
Most mice expose polling rate through their own configuration software rather than through Windows device properties. The paths below cover the most common platforms.
- Logitech G Hub: Select device, go to Settings gear icon, then Onboard Memory, then Report Rate. Choose 125, 250, 500, 1000, or 2000/4000/8000 Hz depending on your model. Changes write to onboard memory and survive reboots without G Hub running.
- Razer Synapse 3: Mouse tab, Performance section, Polling Rate dropdown. Razer 8KHz requires the HyperPolling dongle or a compatible wired connection. The dongle has its own firmware updatable through Synapse under Devices, then your dongle name, then Firmware Update.
- SteelSeries GG: Mouse, Settings, Polling Rate. The Rival 600 and above support 1000 Hz; the Aerox 5 Wireless supports up to 1000 Hz over 2.4 GHz and drops to 500 Hz over Bluetooth by protocol limitation, not firmware choice.
- No software available: Some mice use a physical DPI/polling button cycle. Hold the DPI button for 5 seconds on many Zowie models to cycle through 125, 500, and 1000 Hz, indicated by LED color. Check your specific model's manual for the exact sequence.
Frequently Asked Questions
What is 1000 Hz polling rate in ms exactly?
1000 Hz polling rate equals a 1.0 ms report interval. The mouse sends one position packet to the USB host every 1 millisecond. This is the theoretical minimum interval; real-world jitter on most systems pushes the average to 1.05 ms to 1.2 ms depending on USB controller quality.
Does higher polling rate reduce input lag?
It reduces the polling component of input lag, which is one part of the total latency chain. Going from 125 Hz to 1000 Hz saves 7 ms, which is significant. Going from 1000 Hz to 8000 Hz saves 0.875 ms, which is below the threshold most humans can perceive in isolation. The practical benefit of 8000 Hz is smoother cursor interpolation at high movement speeds, not a perceptible latency reduction.
Why does my polling rate test show higher than expected ms values?
The most common causes are: a USB Full Speed hub in the signal path capping you at 1000 Hz maximum, a shared USB host controller being interrupted by another high-bandwidth device like an external SSD or webcam, or Windows power management putting the USB controller into selective suspend. Plug directly into a rear motherboard USB port, disable USB selective suspend in Power Options, Advanced Settings, USB Settings, and retest.
Is polling rate response time the same as click latency?
No. Polling rate response time refers to motion report frequency. Click latency is determined by switch debounce delay plus the polling interval at the moment of actuation plus USB processing time. A mouse with a 10 ms debounce timer on a 1000 Hz connection has worse click latency than a mouse with 0 ms optical debounce on a 500 Hz connection.
Can wireless mice match wired polling rate latency?
Yes, for 1000 Hz. Logitech LIGHTSPEED at 1000 Hz over 2.4 GHz consistently measures within 0.2 ms of wired performance in controlled tests. Razer HyperSpeed wireless also achieves stable 1000 Hz. Bluetooth is limited to 133 Hz on most implementations due to protocol constraints and is not suitable for low-latency gaming use.
Does polling rate affect the scroll wheel or only the sensor?
Polling rate affects all HID reports from the device, including scroll wheel delta packets. However, scroll wheel encoders on most mice are mechanical quadrature encoders that generate interrupts on the mouse's own microcontroller, not polled continuously. The encoder event gets queued and sent in the next available USB report frame. On a Logitech MX Master 3 with MagSpeed electromagnetic clutch, the wheel movement is detected by hall sensors rather than a mechanical encoder, which eliminates the contact noise issue but still sends data at the configured polling interval.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mouse Polling Rate Test