Free Keyboard Tester for Keys, Codes, Chords, Repeat, and Event Details
Press keys to see browser-reported key names, physical codes, locations, modifier states, repeat behavior, hold duration, and concurrent-key chords in real time.
Keyboard Tester for Keys, Codes, Chords, Repeat, and Event Details
Click here once, then press keys. The page will keep focus unless the browser intercepts the shortcut.
| Type | key | code | Location | Repeat | Hold / paint ms |
|---|
Built for a complete diagnostic workflow
Live keydown/keyup visualization
Keyboard Test workflow feature designed for practical browser use.
KeyboardEvent.key display
Keyboard Test workflow feature designed for practical browser use.
KeyboardEvent.code display
Keyboard Test workflow feature designed for practical browser use.
Left/right location reporting
Keyboard Test workflow feature designed for practical browser use.
Modifier-state tracking
Keyboard Test workflow feature designed for practical browser use.
Key-repeat detection
Keyboard Test workflow feature designed for practical browser use.
Hold-duration measurement
Keyboard Test workflow feature designed for practical browser use.
Concurrent-key chord counter
Keyboard Test workflow feature designed for practical browser use.
Maximum simultaneous keys observed
Keyboard Test workflow feature designed for practical browser use.
Rolling event log
Keyboard Test workflow feature designed for practical browser use.
Event-to-paint scheduling estimate
Keyboard Test workflow feature designed for practical browser use.
Copy and CSV export
Keyboard Test workflow feature designed for practical browser use.
How to interpret this keyboard test
A keyboard tester confirms whether the browser receives key events and how those events are labeled. This is especially useful for diagnosing swapped layouts, modifier problems, keys that repeat unexpectedly, or web apps that depend on KeyboardEvent.code rather than typed characters.
The key field represents the character or action after layout processing, while code is intended to identify the physical key position. That difference matters on alternative layouts and when software binds controls to physical positions.
Hold several keys together to explore simultaneous-key behavior. Browser and operating-system handling can differ, and some keyboards have hardware matrix limitations that appear only on particular combinations.
The event-to-paint estimate measures browser scheduling after the key event reaches the page. It is not a direct measurement of the keyboard’s electrical or wireless hardware latency.
What the browser can and cannot tell you
| Signal | What it represents | How to use it |
|---|---|---|
| key | Layout-aware character/action | Useful for text behavior |
| code | Physical-key style identifier | Useful for position-based shortcuts and games |
| location | Standard, left, right, or numpad | Distinguishes duplicate modifier keys |
| repeat | True after auto-repeat begins | Helps identify held-key repeat behavior |
| Event-to-paint | Browser scheduling estimate | Not the same as physical keyboard latency |
Build a better troubleshooting habit
Start with a baseline
Run the primary diagnostic before changing settings so you have a comparison point.
Repeat the test
One sample can be misleading. Repeat the check and compare the pattern, not only the best number.
Change one variable
When troubleshooting, change one device, browser, permission, cable, or setting at a time.
Separate browser from hardware
A browser result reflects only the parts of the input or output path that the page can observe.
Document the environment
Keep browser, operating system, device connection, scaling, or permission context with the result.
Use the next diagnostic
Open a related ready page when the result suggests a neighboring part of the device or browser stack.
Three quick questions
Finish with a quality review
Recent saved milestones on this device
Continue without a dead end
Free Keyboard Tester for Keys, Codes, Chords, Repeat, and Event Details: FAQ
Can this tester detect a broken key?+
If a key produces no browser event while other keys work, that is a useful signal, but operating-system shortcuts and browser-reserved keys can complicate testing.
What is the difference between key and code?+
key reflects the interpreted character or action, while code is intended to represent the physical key position.
Can it test multiple keys at once?+
Yes. The page tracks currently pressed keys and records the largest simultaneous chord observed.
Does it measure keyboard hardware latency?+
No. It can show event timing and browser scheduling after the event arrives. Use the dedicated keyboard latency page for repeated timing samples and interpret them carefully.
Why do some shortcuts not appear?+
The browser, operating system, accessibility software, or security rules can intercept certain combinations before the page receives them.
Use the result responsibly
This tool reports what a browser can observe or calculate in the current environment. Device firmware, drivers, operating-system processing, permissions, transport, display refresh, acoustic conditions, and browser implementation can add behavior that this page cannot isolate.
External technical reference: MDN: KeyboardEvent.code ↗.