Output
Held keys; transitions; repeat intervals
Measure OS key repeat intervals; browsers cannot expose USB keyboard polling rate.
Keyboard Repeat Rate Test · At a glance
Quick answer: Measure OS key repeat intervals; browsers cannot expose USB keyboard polling rate. The measurement is key-repeat cadence generated by the operating system.
The test loads when you open it. Device access is requested only after you choose to start.
Detailed guide
Held keys; transitions; repeat intervals
Focused physical key presses
KeyboardEvent.code; keydown and keyup
Runs on your device; no tool-result upload
The tester records browser key-down and key-up events, tracks held keys, and separates operating-system repeats from fresh presses. Short intervals are clues to investigate, not proof of a defective switch.
The measurement is key-repeat cadence generated by the operating system. It is different from how frequently USB hardware reports state.
Holding a key produces an initial delay followed by operating-system-generated repeats. Those intervals show repeat speed, not USB polling frequency. A high-polling-rate keyboard can still repeat text slowly. Use the log to separate repeats from real releases and new presses. Physical polling needs lower-level instrumentation.
Check OS repeat-delay and repeat-rate settings if intervals change. Browser scheduling can add variation.
System shortcuts and some special keys are intercepted before a web page receives them. USB polling frequency, analog actuation distance and physical rapid-trigger settings cannot be read from keyboard events.
No. Ordinary browser keyboard events do not expose USB report frequency. The page is explicitly a repeat-rate test despite its legacy polling-rate URL.
Click the test area to focus it, then press and release the keys you want to inspect. Try simultaneous combinations for a ghosting check.
No. Open the interactive tool above in a modern browser. The instructions and explanations are available even with JavaScript disabled; running a test needs JavaScript.
Power settings, background tasks, browser scheduling, operating-system input processing and device settings affect measurements. Compare repeated attempts with identical settings rather than the single highest score.