INPUT PERFORMANCE CHECK

Polling Rate Test

Measure your mouse's estimated polling rate in Hz with a fast browser test. Move your mouse in the test area to see an average, peak, sample count, and stability reading without a download.

  • Runs locally
  • No download required
  • Mouse-focused results
  • 10 or 20 seconds
01

TEST CONTROLS

Check your mouse polling rate

Use 10 seconds for a quick check or 20 seconds for a larger sample.

Use 10 seconds for a quick check or 20 seconds for a larger sample.

Fullscreen is optional. The same test works in this page without a permission prompt.

LIVE INPUT AREA

Move your mouse here

Ready
Start the test, then keep moving Small circles or a figure-eight pattern usually produces a more useful sample.

Keep the pointer inside this area. If it leaves, move it back and continue; you do not need to restart.

Ready to test. Connect a mouse, choose a duration, and start when you are ready.

02

LIVE RESULT

Your estimated mouse rate

Example result
1,000 Hz

Example only. Start the test and move your mouse to replace this with a browser-estimated reading.

Average 987 Hz
Peak 1,004 Hz
Samples 2,814
Stability 92%

Stable example

Event rate over time

Example trace

Example trace: a mostly even event stream around the 1,000 Hz range.

This is a browser-estimated event rate, not a direct reading of your mouse's USB report setting. Results can vary with your browser, operating system, CPU load, display refresh rate, driver, and movement pattern.

What do 125 Hz, 500 Hz, 1000 Hz, and 8000 Hz mean?

A mouse polling rate is measured in hertz, or reports per second. Use these common settings to compare a device utility with the browser's estimated event rate.

Common mouse polling rate settings and approximate report intervals
Setting Approximate interval How to read it
125 Hz 8 ms Baseline mode: about 125 reports per second.
500 Hz 2 ms A common middle setting with more frequent updates.
1,000 Hz 1 ms A common high setting for gaming and everyday use.
2,000 Hz 0.5 ms A higher-rate mode that can add event work.
4,000 Hz 0.25 ms A high mode where scheduling effects may be easier to notice.
8,000 Hz 0.125 ms Enthusiast mode; a browser estimate may be lower.

These are reference settings, not promises about the number shown here. Browser polling delivery can be lower or more variable.

How to test your mouse polling rate

The test answers one practical question: how frequently is this browser receiving movement events from your mouse? Match the conditions when comparing settings.

01

Connect the mouse

Connect the mouse you want to check and use a current desktop browser. Wired and wireless mice can both be tested.

02

Choose a duration

Run a polling rate test for 10 seconds as a quick check, or choose 20 seconds for more samples and a clearer range.

03

Move continuously

Select Start Test and draw small circles or a figure eight inside the marked area. Keep the pointer moving.

04

Read and compare

Review the rate, average, peak, samples, and stability. Repeat with the same motion after changing a setting, port, driver, or wireless mode.

What is a polling rate test?

This browser check estimates how often a mouse sends movement updates that reach a computer. The result is shown in hertz, or Hz. A reading near 1,000 Hz means the page observed roughly one thousand usable pointer-event intervals per second during the sample.

Use the check to compare settings, see whether a high-rate mode appears active, or investigate an inconsistent mouse. It is most useful when the same duration and movement pattern are used for every run.

This page does not inspect firmware, USB packets, wireless radio traffic, or a driver queue. It measures delivered browser events with local timing, so treat the number as a practical diagnostic signal rather than a laboratory reading.

A transparent browser-side measurement

The page listens for supported Pointer Events while you move a physical mouse. It measures the time between usable events with the browser's high-resolution clock and summarizes the polling sample locally.

Simplified estimate

Estimated Hz ≈ 1,000 ÷ average event interval in milliseconds

The polling reading uses valid intervals collected during the test. The first event, long pauses, and impractical timing values are excluded so a short pause does not dominate the summary.

Pointer Events

The tool prefers raw pointer updates when available and falls back to ordinary movement events. Browser support and scheduling affect the sample.

Robust summary

Average and peak summarize valid intervals. Stability reflects variation, so one unusually fast event does not define the result.

No movement upload

The movement stream is used for the current session only. No calculation API, account, or file upload is needed.

How to interpret a mouse Hz test

A useful polling result is repeatable, not simply the largest number on screen. Read the metrics together and keep conditions consistent.

A

Estimated rate

This is the page's rounded summary of the current event stream. Compare it with the mouse setting as an estimate, not a direct USB confirmation.

B

Average and peak

Average shows typical valid behavior. Peak shows the fastest observed portion after basic filtering; it can reveal bursts but is not a guarantee.

C

Samples

Samples shows how much timing data supports the result. Little movement can produce too few intervals even when the setting is correct.

D

Stability

Stability summarizes interval variation. Pauses, event batching, CPU activity, wireless conditions, or changing speed can lower it.

Keep the conditions matched

  • Use the same browser window, duration, port, and movement pattern for both runs.
  • Close heavy background applications when results change sharply.
  • For wireless testing, use a charged battery and keep the mouse near its receiver.
  • If a high setting feels no different, consider CPU load, display refresh, game support, and comfort.

Why can the result be lower than the mouse setting?

An advertised polling setting and a browser's observed event rate are related, but they are not identical measurements.

Event coalescing

Browsers and operating systems may combine or schedule updates differently. The page measures only events delivered to its active tab.

CPU and browser load

Heavy applications, background tabs, power saving, and a busy main thread can make timing less even. Reduce avoidable load and repeat.

Movement and focus

A stationary pointer produces no useful intervals. Pausing, leaving the area, or changing speed can lower sample quality.

Hardware and drivers

Ports, hubs, wireless interference, receiver placement, firmware, drivers, and device utilities can affect delivery. Check them before assuming a hardware fault.

For browser background, see MDN's Pointer Events and Fullscreen API references. They describe browser capabilities, not a direct hardware reading.

Your mouse movement stays in this page

The core measurement runs in the browser. It needs no account, download, movement upload, or server-side calculation request.

  • Timing is calculated with browser JavaScript during the current test.
  • Raw movement coordinates are not needed for the final result or intentionally stored after the test.
  • Copy Result shares the summary you choose, not a movement trail.
  • Analytics and advertising practices, if enabled, are described in the Privacy Policy.

Polling rate test FAQ

These answers cover common questions about comparing a mouse setting with a browser result.

How do I test my mouse polling rate?

Run a polling rate test by connecting the mouse, choosing 10 or 20 seconds, selecting Start Test, and keeping the pointer inside the area. Then review the estimated rate, average, peak, samples, and stability.

Do I need fullscreen for a polling rate test?

No. Fullscreen is optional. Focus Mode gives the card more space, but the normal page uses the same sampling logic.

Why is my mouse Hz test lower than the advertised setting?

The browser measures delivered pointer events, not the mouse's internal USB setting. Event coalescing, CPU load, scheduling, wireless conditions, drivers, and pauses can change the estimate.

Is 1000 Hz better than 500 Hz?

A higher setting shortens the interval between updates, but it is not automatically better. Compare repeatable results, CPU impact, game support, battery life, and comfort.

Can I run a mouse polling rate test on a phone or tablet?

It is intended for a physical mouse in a desktop-style browser. Touch events do not represent mouse polling rate; a mobile device may work only with a connected mouse exposed as a pointer.

Does this polling rate checker upload mouse movement?

No movement upload is needed. Timing runs in your browser, and the raw movement path is not intentionally sent to a server. See the Privacy Policy for other site data practices.

Why does my mouse polling rate change between runs?

Small changes are normal because timing, event batching, CPU activity, wireless conditions, and movement path can change. Use the same conditions and look for a repeatable range.

Can I test a keyboard or controller here?

No. This page measures mouse movement events. Keyboard and controller checks need different signals and separate tools.

Run a polling rate test in your browser

Choose a duration, keep moving, and use the result to compare mouse settings. Run it again whenever your setup changes.

Start the test