What it cannot determine
A browser cannot inspect switches, circuits, scan rates, firmware, USB descriptors, or every matrix path. The summary is not hardware certification and does not prove that a keyboard is healthy or defective.
Guided diagnostic session
Keyboard Health Test
Run a guided keyboard check to verify key detection, look for suspicious double inputs, test simultaneous key combinations, and review the results in one session.
The complete session runs locally in this browser.
Guided diagnostic
Keyboard health session
- 1Key detection
- 2Chatter check
- 3Multi-key check
- 4Modifier keys
- 5Results
Step 1 of 5
Check key detection
Press the keys you want to verify. For a fuller check, work across the keyboard from left to right. You can continue without testing every key.
Keys tested0 / 104
Not tested104
Currently pressed0
Last key—
Swipe sideways to view the full keyboard.
- Esc
- F1
- F2
- F3
- F4
- F5
- F6
- F7
- F8
- F9
- F10
- F11
- F12
- Prt Sc
- Scr Lk
- Pause
- ~`
- !1
- @2
- #3
- $4
- %5
- ^6
- &7
- *8
- (9
- )0
- _-
- +=
- Backspace
- Tab
- Q
- W
- E
- R
- T
- Y
- U
- I
- O
- P
- {[
- }]
- |\
- Caps Lock
- A
- S
- D
- F
- G
- H
- J
- K
- L
- :;
- "'
- Enter
- Shift
- Z
- X
- C
- V
- B
- N
- M
- <,
- >.
- ?/
- Shift
- Ctrl
- Win
- Alt
- Space
- Alt
- Win
- Menu
- Ctrl
- Num Lock
- /
- ×
- −
- Home7
- ↑8
- Pg Up9
- +
- ←4
- 5
- →6
- End1
- ↓2
- Pg Dn3
- Enter
- Ins0
- Del.
One session, several observations
What the Keyboard Health Test checks
The guided workflow combines individual key detection, conservative duplicate-event screening, representative multi-key combinations, modifier positions, and the highest simultaneous count observed during the session.
How to get a more reliable result
Use normal presses, complete the chatter sample without deliberately tapping at maximum speed, try every guided combination, and press left and right modifiers separately. Repeat unusual observations in another browser.
Untested does not mean failed
Keys you skip are reported as “not tested.” The tool never changes an untested input into a failure, and it does not require all 104 displayed positions before you can continue.
Browser and system limitations
Operating-system shortcuts, browser controls, layout remapping, accessibility software, and focus changes can affect which events arrive. Meta/Windows keys are especially likely to be reserved.
When to use a specialized test
Use the individual Chatter Test for a longer timing sample, Ghosting Test for more known combinations, NKRO Test for progressive simultaneous counts, or Stuck Key Test for live release behavior.
Privacy
Key states, timing observations, combinations, and results stay in temporary React memory. They are not uploaded, logged, or written to local or session storage, and restart clears the entire session.