Key chatter test

Inspect rapid repeat sequences separately from auto-repeat.

Browser-based estimateProcessed locally

Preparing

An unmarked key is not necessarily faulty; input methods and system shortcuts may intercept events.

Key codes not yet received: 104

Click to activate. Tab or Esc exits. System shortcuts may not reach this area.

Esc
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
F11
F12
PrtSc
ScrLk
Pause
`
1
2
3
4
5
6
7
8
9
0
−
=
Backspace
Tab
Q
W
E
R
T
Y
U
I
O
P
[
]
\
Caps
A
S
D
F
G
H
J
K
L
;
'
Enter
Shift
Z
X
C
V
B
N
M
,
.
/
Shift
Ctrl
Meta
Alt
␣
Alt
Meta
Menu
Ctrl
Ins
Home
PgUp
Del
End
PgDn
←
↑
↓
→
Num
÷
×
−
7
8
9
+
4
5
6
1
2
3
↵
0
.
Not receivedReceived · marked ✓Held down

Scroll horizontally to view the full diagram. Tab/Esc stops capture; when inactive, use arrow keys to scroll. Test with real keys.

Captures keys only in the activated test area; key data is not uploaded or saved automatically.

Held keys
0
Tested keys
0
Press count
0
Maximum held keys
0
Auto-repeat events
0
—

Notable intervals

Auto-repeat is separate; totals persist until Reset. Threshold: 1–500 ms. A short gap does not prove a faulty switch.

codePress countAuto-repeat eventsNotable intervalsValid release → press pairsMinimum (ms)

Recent event log

Keeping 0/200 recent events; 0 events received. Clearing the log keeps statistics.

Expand/collapse event list

How to use

Set an investigation threshold, activate capture and press each key normally several times.

Methodology

Compares each release → next press of the same key with your threshold. Focus loss, layout changes or input-method interference break the pair.