Loading...
A mouse polling rate test is used to measure how often a mouse reports its position to the computer. Polling rate refers to how many times per second the mouse sends position updates, and the unit is Hertz (Hz). For example, a polling rate of 125Hz means the mouse reports its position 125 times per second, while 1000Hz means it reports 1,000 times per second. In general, the more advanced the mouse, the higher the polling rate, and some expensive mice can even reach 8000Hz. Compared with wireless mice, wired mice usually have a higher polling rate ceiling and a more stable connection, but advances in modern wireless technology have made this gap much smaller. A low polling rate mouse often feels obviously choppy and granular in use, and the movement path can feel less continuous. This may not matter much for everyday office work, but it can feel very bad in games. If your polling rate test result is significantly lower than your mouse's theoretical polling rate, your mouse connection may be unstable or the sensor on the bottom of the mouse may be dirty.
Get an accurate reading in under 30 seconds with these three simple steps.
Click Start Test, or simply press Space to begin. Once started, the page enters sampling mode immediately and shows a start message.
While the test is running, move your mouse naturally anywhere within the visible page area. You do not need to keep the cursor inside a small box.
Read the Last Hz, Avg Hz, Min Hz, Max Hz, Stability, and Samples results. When you want to stop, press Space again or click Stop Test.
Click Start Test, or simply press Space to begin. Once started, the page enters sampling mode immediately and shows a start message.
While the test is running, move your mouse naturally anywhere within the visible page area. You do not need to keep the cursor inside a small box.
Read the Last Hz, Avg Hz, Min Hz, Max Hz, Stability, and Samples results. When you want to stop, press Space again or click Stop Test.
Every mouse on the market falls into one of six standard polling rate tiers. Knowing your tier from a mouse rate test helps you make informed decisions about upgrades, driver settings, and competitive configurations.
Reports position every 8 ms. The legacy USB HID default, found in basic office mice and many wired peripherals that ship without a gaming driver. Adequate for document editing, web browsing, and casual computing. Not recommended for gaming — the 8 ms polling gap is clearly perceptible as cursor sluggishness during fast movements. Representative hardware: Logitech M100, any basic OEM office mouse.
Reports every 4 ms. A middle ground that some budget gaming mice default to out of the box. The improvement over 125Hz is noticeable — cursor tracking feels smoother during moderately fast movements — but the 4 ms window is still significant enough that competitive players will feel it during high-speed flicks. Driver software on many mice allows upgrading from 250Hz to 500Hz or 1000Hz without hardware changes.
Reports every 2 ms. The minimum polling rate considered 'gaming grade' by most hardware reviewers and pro players. At 500Hz the cursor latency from polling becomes a minor factor compared to monitor refresh lag and human reaction time. Many mid-range gaming mice from Razer, Logitech, and SteelSeries default to 500Hz and can be pushed to 1000Hz via software. Suitable for most FPS, MOBA, and RTS gameplay.
Reports every 1 ms. The de facto standard for competitive gaming since the mid-2000s. Virtually all gaming mice from major brands (Razer, Logitech G, SteelSeries, Zowie, Corsair, Glorious, Endgame Gear) ship with 1000Hz support. At 1 ms polling latency, the contribution of the mouse to total system input lag is negligible for all but the most latency-sensitive applications. If your mouse reports 1000Hz on this test, you are getting the industry standard experience.
Reports every 0.5 ms. Introduced around 2022 by Razer (HyperPolling, up to 8000Hz on Viper 8K), Logitech (HERO 2 sensor mice at 2000Hz), and SteelSeries (Rival 600). The jump from 1000Hz to 2000Hz halves polling latency, but whether humans can perceive this improvement in real gameplay is actively debated. Independent tests show measurable latency reduction in high-speed aiming tasks; subjective feel improvements are reported by some but not all users. Requires driver software to enable.
Reports every 0.25 ms. Available on select flagship mice including the Razer Viper 8KHz (up to 8000Hz), Pulsar X2V2, and Endgame Gear XM2we. At this tier, the mouse polling interval is shorter than a single rendered frame at 4K/144Hz, meaning the cursor position is updated more frequently than the display can show. The primary benefit shifts from raw latency to smoother interpolation of cursor movement between frames. Requires a high-quality USB port — bandwidth demands at 4000Hz+ can cause issues on older USB controllers.
A browser polling rate test measures how quickly the page receives and processes mouse input events, not the raw hardware polling value reported at the USB, driver, or firmware layer. That makes it useful for estimating real-world behavior and broad polling-rate classes, but it can still differ from the theoretical rate shown on a product box, in driver software, or in a native hardware utility.
The gap usually comes from these layers working together:
For performance reasons, browsers do not guarantee that every hardware update is dispatched to the page as an individual event. Multiple input updates may be merged into a single pointermove event, especially during fast movement, so the page can observe a lower rate than the mouse is actually reporting.
Some browsers support pointerrawupdate or getCoalescedEvents, which can expose finer-grained input data. Others mainly provide pointermove or mousemove. Different support levels lead to different observed results.
The test page still has to update charts, gauges, and numbers. Those UI updates usually follow requestAnimationFrame, which is generally tied to display refresh. Even if the mouse is polling at 1000Hz, the presentation layer cannot display every sample with true hardware-level fidelity.
If the browser, page scripts, charts, extensions, screen recording tools, or other system processes are using CPU time, event handling can be delayed, queued, or partially dropped. That often pulls the measured polling rate downward.
Browser event timestamps use high-resolution timing, but precision may be reduced for security and privacy reasons in some environments. On very high polling-rate devices, small timing changes can become visible measurement error.
If the tab is not fully active, is partially hidden, minimized, or treated as background work, browsers may throttle requestAnimationFrame, timers, and parts of event processing. In those cases the reported result can drop sharply.
A browser test relies on sustained, natural movement to collect samples. If movement is too short, too slow, full of pauses, or constantly changing direction, the algorithm gets fewer stable intervals and the result becomes lower or noisier.
The operating system input stack, USB controller, driver, mouse firmware, wireless receiver distance, power-saving behavior, and the polling-rate mode selected in mouse software all influence the event stream that eventually reaches the browser. A web page cannot bypass those layers and read raw bus-level data directly.
A mouse advertised as 1000Hz, 2000Hz, or 4000Hz usually describes its target capability under good conditions. In real use, report intervals still fluctuate around that target, so a browser test should be treated as a close estimate rather than a hardware certification reading.
The stability score measures how consistent your mouse polling is over time. A raw average Hz number from the polling rate test tells you the speed; the stability score tells you the reliability. Even a 1000Hz mouse can perform poorly if its polling intervals are erratic.
The tool collects up to 200 consecutive polling interval measurements. The stability score is the percentage of those readings that fall within ±15% of the rolling average. For example, if your average is 1000Hz and 185 out of 200 readings are between 850Hz and 1150Hz, your stability score is 92.5% — rated Excellent.
A precise, privacy-friendly mouse Hz test built for competitive players and power users who need accurate, real-time hardware data.
This mouse Hz test calculates values from consecutive mousemove event timestamps with millisecond precision. A live rolling chart shows every reading as it happens — no delays, no smoothing that hides the truth.
After a few seconds of movement, the mouse rate test automatically maps your average to the nearest standard class: 125, 250, 500, 1000, 2000, or 4000Hz — so you instantly know which performance tier your mouse is in.
Beyond raw Hz, consistency matters. Our stability score tells you what percentage of readings fall within ±15% of your average — a low score can indicate USB bandwidth issues, driver problems, or hardware degradation.
Everything runs locally in your browser using standard Web APIs. No executable files, no browser extensions, no personal data ever leaves your device.
Touch devices are automatically detected and switched to touchmove measurement mode, with a clear note explaining the difference between touch sampling rate and mouse polling rate.
All measurements are computed locally. The tool never sends any data to external servers. What you see stays on your screen.
Small habits make a big difference when running a mouse rate test. Follow these tips to get the most reliable Hz readings.
Mouse polling rate is the frequency at which your mouse reports its position and button state to the computer, measured in Hertz (Hz). A polling rate of 1000Hz means 1,000 position updates per second — one every 1 ms. Higher polling rates mean lower cursor latency and smoother movement. A polling rate test measures this frequency so you know exactly what your hardware is delivering. This matters most for fast-paced tasks like FPS aiming or precise graphic design work.
For most competitive gaming, 1000Hz is the widely accepted standard. When you run a mouse Hz test on any mainstream gaming mouse, you should see readings around 1000Hz. Higher rates like 2000Hz and 4000Hz are offered by flagship mice and can theoretically reduce polling latency to 0.5ms or 0.25ms, though the perceptible benefit is debated even among professional players. For casual gaming and everyday use, 500Hz is perfectly adequate.
Several factors can cause your polling rate test result to read lower than your mouse spec. First, Windows limits USB interrupt frequency to 125Hz by default — you may need to adjust the USB polling interval in device settings or a driver utility. Second, USB hubs add latency that lowers the rate the OS sees. Third, your mouse driver software may be set to a lower polling rate. Fourth, browser tab throttling can skew results — always run the test with the tab active in the foreground.
Yes, marginally. Each position report requires the CPU to handle an interrupt and process the data. At 1000Hz this overhead is negligible on any modern processor. At 4000Hz or 8000Hz, some users on older hardware have reported a measurable CPU load increase (typically 1-3%), though this rarely impacts gaming or productivity. If you run an extremely CPU-limited system, testing at both 500Hz and 1000Hz and comparing the system's CPU usage during intensive tasks may be worthwhile.
DPI (dots per inch) controls the sensitivity of the sensor — how far the cursor moves on screen per inch of physical mouse movement. Polling rate controls how often the mouse reports that movement. You can have a high-DPI mouse with a low polling rate, or a low-DPI mouse with a high polling rate. Both settings affect the feel of the mouse, but in different ways: DPI affects cursor speed and precision, while polling rate affects input latency and smoothness of motion updates.
Yes. Most modern wireless gaming mice (using 2.4GHz proprietary receivers) transmit at 1000Hz wirelessly and the receiver bridges that to USB, so the OS — and this tool — sees the full polling rate. Bluetooth mice are different: the Bluetooth HID protocol typically caps the effective polling rate at around 125Hz regardless of the mouse's hardware capability. If you are testing a Bluetooth mouse and see ~125Hz, this is expected behavior of the wireless protocol, not a hardware limitation of the mouse itself.
Last Hz
--
Avg Hz
--
Min Hz
--
Max Hz
--
Stability
--
Samples
--
Click "Start Test" and then move your mouse anywhere on the current page
This panel now serves as a live chart and results display only. Once the test starts, you do not need to keep your mouse inside this box. Just move it anywhere within the current page to keep sampling.
Works on all modern browsers. For best accuracy, keep the browser tab active and move your mouse at a steady pace.
