Keyboard test

Check each key, hold combinations, and see exactly which signals reach your browser.

Tested keys0 / 1040%

Paused — start to capture keys.

Esc
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
F11
F12
`
1
2
3
4
5
6
7
8
9
0
-
=
⌫
Tab
Q
W
E
R
T
Y
U
I
O
P
[
]
\
Caps
A
S
D
F
G
H
J
K
L
;
'
↵
⇧
Z
X
C
V
B
N
M
,
.
/
⇧
Ctrl
⊞
Alt
␣
Alt
⊞
☰
Ctrl
Num
/
*
-
7
8
9
+
4
5
6
1
2
3
↵
0
.
UntestedTestedHeld
Held now
0
Most held together
0
Key presses
0
Hold repeats
0

Last key: No key yet

—

How testing works

How testing works

Testing starts automatically. Press every key on your physical keyboard. Hold a combination such as W + A + Space to check which keys arrive together. Green keys retain their tested state after release. Reset clears the results and starts a new session immediately.

The diagram uses an ANSI reference layout. Regional and remapped keyboards can differ. Fn, media keys and system shortcuts may be intercepted before the browser receives them. An unlit key alone does not prove a hardware fault. Esc pauses; pause before using navigation or language controls.

Key signals and results stay in this tab and disappear when you leave. No typed text or key signals are uploaded.

Questions

Can this measure keyboard latency or diagnose ghosting?

The simultaneous-key count shows only events received by this browser. Compare it with the keys you physically hold to spot missing signals. Browser events cannot reliably measure hardware latency, polling rate or certify NKRO. Hold repeats are normal operating-system repetition, not proof of switch chatter.