Keyboard Tester
Only the focused test area is monitored after you choose Start. Tab leaves the area; Esc pauses the test.
Do not type passwords or confidential text. There is no need to enter a sentence.
Not detected does not mean broken. Some keys are absent or intercepted by your device, operating system, input method, or browser.
Changing the layout or number pad clears the observations.
Key positions detected: 0
Currently observed down: 0
Peak observed down: 0
Keyboard test area
Start the test, then press keys while this area has focus. Tab leaves; Esc pauses unless an input composition is in progress.
□ Not detected✓ Detected▣ Observed down
Key labels are examples, not a detection of your keyboard layout.
Loading…
The tester could not load. Retry or reload the page.
Observed key positions
No key positions detected yet.
| Code | Reference label | Observation |
|---|
Detected positions outside the selected diagram
Latest event details
Shows only the latest event received while this section is open and the test is active. Closing or pausing clears it.
Control and invisible characters are shown as code-point labels. Long key values are shortened.
Designed for physical keyboards. On-screen keyboards may not provide key-position events.
Fn, media keys, Print Screen, and some mode keys may not reach the browser.
Shortcuts with Ctrl, Meta, or Alt are not locked. Avoid reload, close-window, and system shortcuts during testing.
IME, dead keys, and AltGr can change which events are delivered. AltGr may produce more than one modifier event.
The peak is a browser observation, not an NKRO rating, latency measurement, or count of physical switches.
This tool does not save or send your key events. Observations are cleared on reload or when leaving the page. Standard site services may still use the network.
With a screen reader, use its focus mode when needed. The observed-position table provides a text alternative to the diagram.
How to test your keyboard
- Choose a reference layout and whether to show the number pad. The diagram does not automatically identify your keyboard.
- Choose Start, then press keys with the test area focused. Do not type passwords or confidential text.
- Use Tab to leave, Esc to pause, or Stop. Resume to continue or clear the observations for a new test.
What the result can tell you
Detected means that a key event with a known position code reached this test. Not detected is not a fault diagnosis. The displayed peak is a browser observation, not an NKRO rating or latency measurement. Reference labels may differ from the characters produced by your input layout.
Frequently asked questions
Does an undetected key mean my keyboard is broken?
No. The key may not have been pressed, may be absent, or may be handled by the device, operating system, input method, or browser. This tool cannot certify hardware condition.
Why is the displayed position different from the character I type?
The diagram follows KeyboardEvent.code, which identifies a reference position. KeyboardEvent.key describes the value reported for that event. Layouts such as AZERTY and QWERTZ can produce different characters at the same position.
Can this test every shortcut, Fn key, or media key?
No. Some keys and shortcuts never reach the page. Tab leaves the test area, and Esc pauses outside input composition. Ctrl, Meta, and Alt shortcuts are not locked and may still trigger their usual actions.
Are key events or typed text saved?
This tool does not save or send key events. It keeps an unordered set of observed key positions in this tab. Optional details show only the latest event and are cleared when closed or paused. Reloading or leaving the page clears observations. Standard site services may use the network.
Will it work with every keyboard and input method?
Only the events delivered to the focused test area can be observed. On-screen keyboards, IME composition, dead keys, and AltGr may behave differently. JIS and ABNT2 diagrams are references, not guarantees of complete device support.