Test Your High Polling Rate Gaming Setup: 4000 Hz and 8000 Hz
Set your mouse to 4000 Hz or 8000 Hz in its companion software, then run the polling rate test above to confirm your system actually delivers it. Those rates are four and eight times the previous 1000 Hz standard, shrinking the maximum position-report interval to 0.25 ms and 0.125 ms respectively.1 High polling rates matter most when fast movement exposes gaps between reports; at 8000 Hz, the gap between physical mouse movement and screen response can be very small, though browsers and games still coalesce or align input around their own frame and event timing.
High polling rate gaming mice are now mainstream at competitive price points, but the number on the box is not always the number your system delivers. Testing your own configuration tells you whether you're actually getting what you paid for, and the tiers below help you judge the reading once you have it.
What to look for
- 4000 Hz to 8000 Hz interval drop 0.25 ms to 0.125 ms
Opens the Input Lag Test with this section's reference values shown at the top of the tool.
Open in the tool →What high polling rate changes in practice
At 1000 Hz, the cursor receives up to 1000 position updates per second. A fast 50 cm/s flick at 1000 Hz produces roughly 50 position updates, enough for smooth tracking. At 8000 Hz, the same flick produces around 400 updates, capturing micro-movements that would fall between reports at 1000 Hz. Consequently, high polling rate improves aim precision at high movement speeds rather than at slow deliberate movements. For players who perform rapid flick shots or micro-corrections in shooters, the improvement can be measurable. For slow-paced aiming or turn-based games, the practical difference is often small.1
For most gaming scenarios, the perceptible benefit depends on cursor speed, game engine input handling, frame pacing, and browser event timing. At higher speeds, 8000 Hz captures more movement samples between 1000 Hz report boundaries, meaning the cursor path can more closely follow the physical movement arc during the flick. Fast-paced shooters and battle royale titles are the use cases where high polling rate is most likely to matter; real-time strategy or role-playing games often have less time-critical aiming demands.
When the extra reports are easiest to notice
The benefit is easiest to notice during fast cursor movement, not during slow aiming. A flick shot, micro-correction, or rapid target switch creates more distance between 1000 Hz samples, so the extra 4000 Hz or 8000 Hz reports can keep the path smoother. In slower scenes, the same mouse may feel nearly identical at 1000 Hz and 8000 Hz. The practical threshold varies by player, but most testers report that the difference between 1000 Hz and 4000 Hz is more consistently noticeable than the difference between 4000 Hz and 8000 Hz, because the positional gap per report shrinks dramatically at each step but the perceptible smoothness gain diminishes.
System requirements for high polling rate
High polling rate increases USB interrupt frequency and OS input stack load. At 8000 Hz, the mouse can report 8000 times per second, and Microsoft’s USB endpoint descriptor documentation explains that interrupt polling frequency depends on the endpoint interval, device speed, and host controller.2 On lower-end systems or during CPU-intensive workloads, high polling rate can contribute to frame rate instability, so 8 kHz peripherals can add enough USB interrupt overhead to affect frame consistency on some systems.3 Building on this, browser measurement needs coalesced pointer events; MDN describes getCoalescedEvents() as a way to recover intermediate pointer positions that were merged into a single pointer event.4
Confirming that 8000 Hz is active on your system
Confirming the configured rate is actually delivered requires a measurement tool that uses getCoalescedEvents(). Set your mouse to 8000 Hz in companion software, open this tool in Chrome or Firefox, move steadily for 15 seconds, and read the average Hz. A reading near 8000 confirms the pipeline is working end to end. A consistent ceiling at 1000 Hz despite correct software settings can come from USB power management, so check Windows USB selective suspend and reconnect before testing again.5
Verifying high polling rate is active
Confirming that your mouse is actually reporting at 8000 Hz requires a tool that uses getCoalescedEvents(), which is what this tool does. Move your mouse steadily inside the tracking zone and read the Hz chart. A correctly configured 8000 Hz mouse should read near 8000 in Chrome, Edge, or Firefox. A ceiling at 1000 Hz despite selecting 8000 Hz in software can come from USB power management or other OS-level report coalescing, so check selective suspend settings and reconnect before testing again.45
After confirming 8000 Hz in this test, run the same check with your gaming applications open and active. Background processes and GPU load during gameplay can introduce OS scheduling jitter that does not appear in a standalone browser test. The Hz reading may show slightly more variance during gaming than during this clean measurement, which is normal. Persistent drops from 8000 Hz to 1000 Hz during gaming but not during this test often point to a local software or scheduling issue; identify and close the process that changes the input path before drawing conclusions about the mouse hardware.
Matching the polling test to your real gaming load
After the clean browser test, run a short session in the game or benchmark where input feels inconsistent. If the polling chart stays high in the browser but drops only under load, the mouse is probably capable and the bottleneck is system scheduling, CPU headroom, or game input handling. That distinction prevents unnecessary hardware changes. Running the test with your game launcher, voice chat, and streaming software all active replicates the real CPU and USB load during a typical session; if the chart holds near 8000 Hz under that combined load, the polling rate is stable enough for competitive play on your specific setup.
Treating the browser test and the in-game reading as two halves of one check prevents you from tuning the wrong layer. If the browser chart is solid but the game reading dips, the problem sits in system scheduling rather than the mouse hardware. If both dip, revisit the USB path, the polling profile, and power management together. Either way, you have narrowed the search before changing any settings.
When to use this
Use this to settle whether 8000 Hz is worth it for gaming, to understand what the Hz numbers mean for your specific gaming context, or to troubleshoot a reading below the rated spec.
Examples
Confirming 8000 Hz after configuring in Razer Synapse
Open the polling rate test, move the mouse for 10 seconds, read the average Hz. Should read near 8000. A result near 1000 Hz means USB selective suspend is active; disable it in Windows Device Manager, reconnect, retest.
Testing whether 4000 Hz vs 8000 Hz is perceivable
Set mouse to 4000 Hz, run test, note Hz reading. Switch to 8000 Hz, repeat. If both charts show expected values, you are getting the hardware difference.
- 1.
Razer, "Razer HyperPolling Wireless Gaming Technology," razer.com, accessed June 2026. https://www.razer.com/technology/razer-hyperpolling
- 2.
Microsoft Learn, "_USB_ENDPOINT_DESCRIPTOR (usbspec.h)," learn.microsoft.com, January 2021. https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/usbspec/ns-usbspec-_usb_endpoint_descriptor
- 3.
Abid Ahsan Shanto, "Your gaming mouse/keyboard might be wasting CPU cycles, not improving performance," xda-developers.com, February 2026. https://www.xda-developers.com/gaming-keyboard-mouse-8khz-polling-rate-performance-tradeoffs/
- 4.
Mozilla Developer Network, "PointerEvent: getCoalescedEvents() method," developer.mozilla.org, December 2023. https://developer.mozilla.org/en-US/docs/Web/API/PointerEvent/getCoalescedEvents
- 5.
Microsoft Learn, "USB Selective Suspend," learn.microsoft.com, accessed June 2026. https://learn.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-selective-suspend
8000 Hz Mouse Test: Is Your Mouse Reporting at Full Rate?
An 8000 Hz mouse is only as fast as its pipeline allows. Your mouse may be rated and configured for 8000 Hz, but the USB endpoint interval, Windows USB power policy, USB hub scheduling, and browser Pointer Events API together determine whether those reports arrive at the application. This test verifies whether your specific hardware and software combination is delivering close to the configured rate.
Move your mouse inside the tracking zone and read the Hz chart. A correctly configured 8000 Hz mouse on a compatible system should read close to 8000; 8000 reports per second corresponds to a 0.125 ms reporting interval.1 A ceiling near 1000 Hz usually means the browser or OS is exposing a lower-frequency path, so check browser support and USB power settings before assuming the mouse hardware is faulty.
What to look for
- Acceptable 8000 Hz reading range 7600 to 7900 Hz sustained
Opens the Input Lag Test with this section's reference values shown at the top of the tool.
Open in the tool →What can prevent 8000 Hz from reaching the browser
Four pipeline stages can cap your effective polling rate below 8000 Hz. The mouse firmware setting: if 8000 Hz is not selected in companion software, the mouse reports at a lower rate regardless of hardware capability. USB endpoint interval: the device's bInterval and the device/controller speed determine the polling period; high-speed USB can use 125 µs microframes, but host/controller support still matters.2 USB power management: Windows can selectively suspend idle USB devices, and Microsoft lists disabling selective suspend as a workaround for USB devices that become slow or unresponsive on a hub.3 USB hub/controller scheduling: interrupt transfers are scheduled and reserve bandwidth, so multiple periodic devices on a shared controller can reduce available scheduling headroom.4 Browser API support: browsers coalesce multiple pointer updates into one pointer event, and getCoalescedEvents() exposes the intermediate events needed to reconstruct higher-frequency movement.5
Eliminating each cause in sequence is the fastest diagnostic path. Start with companion software: confirm 8000 Hz is selected and applied. Then move the mouse to a direct rear motherboard USB-A port, bypassing any hub. Then disable USB selective suspend in Device Manager. After each step, reconnect and retest; improvement after a specific step identifies which cause was responsible for your starting ceiling.
Turning the checklist into a repeatable test
Write down the four-step sequence and run it the same way each time: check the companion software setting, move to a direct rear port, disable USB selective suspend, then verify browser API support. Documenting which step resolved the ceiling turns an ad hoc troubleshooting session into a repeatable protocol you can apply after every OS update or hardware change with the 8000 Hz polling rate check. If the ceiling returns after a Windows update, the same four-step checklist quickly identifies whether the update reset your power management policy or changed the USB controller behavior.
Diagnosing a 1000 Hz ceiling on an 8000 Hz mouse
Start with the most common cause: open Windows Device Manager, expand Universal Serial Bus Controllers, right-click each USB Root Hub, open Properties → Power Management, and uncheck "Allow the computer to turn off this device to save power." Reconnect the mouse and retest. If the reading improves to near 8000 Hz, USB selective suspend was contributing. If it remains near 1000 Hz, verify the polling rate setting in companion software and apply mouse or receiver firmware updates when available. Razer lists firmware requirements and Windows 11 high-report-rate optimizations for HyperPolling devices, and similar companion software may expose polling-rate and firmware controls for other mice.1 Consequently, connect directly to a rear motherboard USB-A port and retest.
Less common causes that survive the standard checks
If USB selective suspend, port selection, software settings, and firmware are all correctly configured and the chart still shows 1000 Hz, test a different USB controller or motherboard port. The USB endpoint interval is determined by the device configuration, device speed, and host controller type, so controller-specific behavior can separate a mouse issue from a host-side scheduling issue.2 Some motherboard USB controllers handle high-frequency interrupt transfers better than others; moving from a third-party ASMedia controller to an Intel-native USB port, for example, can resolve a persistent 1000 Hz ceiling that survives every software-side fix.
Browser requirements for 8000 Hz measurement
Measuring 8000 Hz requires a browser that exposes coalesced pointer events. MDN describes getCoalescedEvents() as returning the PointerEvent instances that were coalesced into a single pointermove or pointerrawupdate event, which lets applications access intermediate position changes for precise pointer tracking.5 WebKit's macOS implementation stores coalesced mouse events and propagates them to the web process so getCoalescedEvents() can return them.6 Without coalesced-event support, the browser collapses multiple hardware reports into a single dispatched PointerEvent, and the Hz chart caps near 1000 regardless of how fast the mouse is actually reporting; this is why browser choice matters as much as USB configuration when validating high-polling-rate hardware.
When the chart confirms 8000 Hz but in-game tracking still feels imprecise, the application may be processing a coalesced or lower-frequency input path, so checking the specific game's high-precision mouse settings determines whether the hardware configuration translates into any in-game benefit. Many modern titles include a "raw input" toggle that bypasses the operating system's pointer acceleration and scaling layers; enabling that option ensures the game reads directly from the HID device reports rather than from the processed cursor position, which is a prerequisite for any high-polling-rate advantage to manifest during actual gameplay.
Confirming the benefit reaches your application
A browser reading near 8000 Hz proves the measurement page receives high-frequency reports, but your game may still sample input differently. If the chart is stable yet the game feels inconsistent, test with the same polling rate in your actual game settings and compare against the browser baseline before changing hardware. Some game engines sample input once per frame regardless of how many USB reports arrived between frames, which means the effective polling rate is capped by the frame rate; at 144 FPS, the game processes input every 6.94 ms, so reports arriving between those sampling points improve positional accuracy but do not reduce the fundamental frame-aligned input latency.
Comparing the browser reading with the in-game sampling rate exposes the real ceiling before you buy new hardware. If the chart shows 8000 Hz but your game samples at 144 FPS, the extra reports refine position without shortening the frame gap. Knowing that boundary keeps expectations realistic and stops you from blaming the mouse for a frame-rate limit it cannot change.
When to use this
Use this test immediately after purchasing or configuring an 8000 Hz mouse, after changing USB ports, after OS updates that may have reset power management settings, or when tracking feels inconsistent despite having an 8000 Hz device.
Examples
New 8000 Hz mouse reads 1000 Hz out of the box
The mouse ships at a default polling rate lower than 8000 Hz. Open companion software, set polling rate to 8000 Hz, apply, and retest.
Mouse configured at 8000 Hz still reads 1000 Hz
USB selective suspend is the most likely cause. Open Windows Device Manager → USB Root Hub → Power Management → uncheck "Allow the computer to turn off this device to save power." Reconnect and retest.
- 1.
Razer, "Razer HyperPolling Wireless Gaming Technology," razer.com, accessed June 2026. https://www.razer.com/technology/razer-hyperpolling
- 2.
Microsoft Learn, "_USB_ENDPOINT_DESCRIPTOR (usbspec.h)," learn.microsoft.com, April 2021. https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/usbspec/ns-usbspec-_usb_endpoint_descriptor
- 3.
Microsoft Support, "USB devices may stop functioning correctly when multiple devices connected to the same USB hub go into selective suspend," support.microsoft.com, accessed June 2026. https://support.microsoft.com/en-us/topic/usb-devices-may-stop-functioning-correctly-when-multiple-devices-connected-to-the-same-usb-hub-go-into-selective-suspend-99b5ae85-69cb-4f94-adce-5698ba44804f
- 4.
The Linux Kernel Documentation, "The Linux-USB Host Side API," kernel.org, accessed June 2026. https://www.kernel.org/doc/html/v4.14/driver-api/usb/usb.html
- 5.
MDN Web Docs, "PointerEvent: getCoalescedEvents() method," developer.mozilla.org, December 2023. https://developer.mozilla.org/en-US/docs/Web/API/PointerEvent/getCoalescedEvents
- 6.
WebKit, "[Pointer Events] Implement getCoalescedEvents API (macOS)," github.com, accessed June 2026. https://github.com/WebKit/WebKit/pull/31046
CapyToolkit treats a sustained 7600 to 7900 Hz reading as correct hardware performance. Yes, a small variance below 8000 Hz is normal; OS scheduling jitter and browser event timing mean readings rarely hit exactly 8000.0.
Marginally. On modern CPUs, 8000 interrupts per second from the mouse represents a fraction of a percent of CPU time and has no meaningful effect on temperature.
Applications that do not use getCoalescedEvents() only receive one PointerEvent per browser dispatch cycle, capping their input rate near 1000 Hz regardless of hardware polling rate. This tool uses getCoalescedEvents() and shows the full rate.
Yes. The test measures any polling rate. A 4000 Hz mouse configured correctly should read near 4000 in the chart.
Intermittent drops to 1000 Hz usually indicate USB selective suspend activating during brief pauses in mouse movement. Disable USB selective suspend permanently in Device Manager.
Install from Microsoft Store