What it does
Useful, focused capabilities
- KeyboardEvent.code physical-key view
- Held and previously tested states
- Simultaneous-key observation
- Repeat and location diagnostics
- Optional local CSV export
Device diagnostics · browser-local
Keyboard tester and key checker
Test physical keyboard events, held keys, simultaneous-key observations, repeats, codes, locations, fullscreen behavior, and export a local event log.
Work happens in the current browser. The route does not require an account or a server-side processing job.
Interactive browser workspace
Keyboard tester and key checker
The live tool is loaded in this browser only. This route does not need camera, microphone, or screen-capture permission for its main task.
Open this local tool →Browser compatibility
Requirements and honest fallbacks
JavaScript; a physical keyboard and trusted KeyboardEvent support for meaningful results.
- JavaScript
- physical keyboard
- trusted KeyboardEvent support
- Fullscreen API
- download support
Questions people ask
Clear answers and limits
Does this page capture everything I type?
Only trusted events while the test panel is focused are shown. The implementation does not transmit or automatically persist the log.
Why do some system shortcuts not appear?
The operating system or browser reserves them before the page receives an event.
Can this prove NKRO?
It can show combinations observed by this browser, but it cannot certify keyboard matrix behavior independently of the full hardware and software stack.
What is KeyboardEvent.code?
It identifies a physical key position such as KeyA or Digit1, while event.key describes the interpreted character or action.
Why is the visual layout ANSI?
It is a compact reference. Unmapped codes are still logged even when the user's physical layout differs.