Input TestsBrowser test

Keyboard Polling Rate Test

Check browser-observed keyboard event timing in single-key, alternating-key, and auto-repeat modes. See event Hz, intervals, consistency, and local history—not raw USB polling.

  • Browser-observed
  • No device permission
  • Optional history in this browser
  • No account or upload
Browser-observed measurement

Privacy-first. Tests run locally in your browser. We do not upload keystrokes, pointer paths, or media.

Use a focused physical keyboard and a modern browser.

Important

  • Browser KeyboardEvent timing does not expose raw USB/HID polling or matrix scan rate. Tap modes include human cadence; hold mode reflects OS/browser auto-repeat.
Test instrumentInput Tests

Tap one ordinary key repeatedly. The first non-repeat keydown becomes the target. This measures your browser-observed tapping cadence.

Focus this surface, press Start, then follow the selected mode.

Live browser tap cadence · —

Browser-observed KeyboardEvent timing — not raw USB/HID polling or matrix scan rate.

Fullscreen not supported

Observed keyboard event timing (frozen after stop)

Browser tap cadence

1000 / median accepted keydown interval

Latest live cadence

Throttled while capturing

Median interval
Mean interval
P95 interval
Minimum interval
Coefficient of variation

Lower = more consistent

Peak 1s keydowns
0
Valid keydowns
0
Auto-repeat events excluded
0
Other-code exclusions
0
Capture state
Ready

Local run history

Aggregate results stay in this browser only; raw event timelines are not uploaded.

No local history yet.

How to use

  1. Choose Single-key tapping to repeatedly tap one ordinary key, Alternating F / J to alternate F and J, or OS auto-repeat to hold one key and observe operating-system/browser repeat events. Select 5, 10, or 15 seconds.
  2. Focus the capture surface and press Start. Keep the tab focused for the whole run so the browser can deliver the events consistently.
  3. Tap an ordinary key such as A in single-key mode, alternate F and J in pair mode, or hold one key in repeat mode.
  4. Let the timer finish or press Stop to freeze the current result before inspecting it. Reset clears only the current capture and target.
  5. For comparisons, repeat the same mode and duration with the same keyboard, connection, browser, operating-system settings, and system load.

What the result means

  • Single-key and alternating-key cadence are browser-observed non-repeat keydown timings. The primary rate is 1000 / median accepted keydown interval: median is the representative middle gap, mean is the average gap, P95 is the slower tail, and minimum is the fastest single accepted gap—not a complete characterization by itself.
  • Coefficient of variation is relative interval variation within the run; a lower value means the accepted intervals are more consistent. Repeat mode reports an OS/browser auto-repeat stream rather than USB polling.
  • Single-key mode follows the first non-repeat keydown. Pair mode accepts a strict alternating F↔J sequence. Repeat mode isolates one target key's repeat events and reports its repeat interval, initial delay, and interval variation.
  • These are browser-observed KeyboardEvent timings. They include delivery and scheduling behavior; repeat mode reflects OS/browser auto-repeat. They are not USB polling, HID report frequency, keyboard scan rate, debounce, actuation, or end-to-end latency measurements.
  • Theoretical hardware report intervals are 125 Hz → 8 ms, 250 Hz → 4 ms, 500 Hz → 2 ms, 1000 Hz → 1 ms, 2000 Hz → 0.5 ms, 4000 Hz → 0.25 ms, and 8000 Hz → 0.125 ms. These reference intervals are not expected browser values, a score, or proof of hardware behavior.

Limitations

  • The measurement starts with KeyboardEvent records after keyboard firmware, the connection, the operating system, and the browser have already processed input.
  • Human tapping cadence is part of single-key and alternating-key results; these modes are not hardware polling measurements.
  • Auto-repeat mode is generated by operating-system and browser repeat timing, including its initial delay and steady interval.
  • Window focus, browser scheduling, system load, operating-system settings, and connection conditions can change which events arrive and when.
  • The page cannot observe raw USB/HID reports, matrix scan rate, debounce time, switch actuation latency, controller firmware timing, or end-to-end input latency.

Troubleshooting

The rate is blank
Focus the capture surface and produce enough accepted events for the selected mode. Reset and try again without switching tabs.
A 1000 or 8000 Hz keyboard reports a lower value
Tap modes measure human key cadence delivered to the browser, not the keyboard's rated USB report frequency. Use the hardware interval list only as a theoretical reference.
Repeat mode differs between computers
Repeat mode observes operating-system and browser auto-repeat behavior. Match the OS repeat settings, browser, and focus conditions before comparing runs.
Results vary between runs
Use the same mode, duration, key sequence, keyboard connection, browser, operating-system settings, and system load. Compare the aggregate local history entries after each stopped run.

Related tools

FAQ

Does this measure my keyboard's USB polling rate?

No. It measures accepted browser KeyboardEvent records and their timestamps, not raw USB/HID reports. A USB analyzer or other dedicated equipment is required for hardware polling evidence.

Why can the result be lower than my keyboard's rated frequency?

Single-key and alternating-key modes include human cadence plus browser and operating-system delivery, so they cannot reproduce a hardware report rate.

What does auto-repeat mode measure?

It reports the initial delay and steady repeat interval for the target key's OS/browser auto-repeat events. It is not a hardware polling measurement.

What do the 125, 500, 1000, 4000, and 8000 Hz references mean?

They are theoretical hardware report intervals: 8 ms, 2 ms, 1 ms, 0.25 ms, and 0.125 ms respectively. They are not equivalent browser-event expectations or proof of a device rate.

Which other keyboard checks should I use?

Use the Keyboard Tester for individual key registration and layout, the Keyboard Rollover Test for simultaneous keys, and the Keyboard Double-Press / Chatter Test for duplicate or chatter-like presses.

Is my key sequence uploaded?

No. The current analysis runs in the browser. Local history stores only aggregate run values such as mode, duration, rate, median interval, consistency, and count; raw event timelines are not uploaded.