Skip to content
DeviceTestKit

Keyboard test

Which keys arrive, and which ones never do.

Everything happens on this device. Nothing is uploaded.

Waiting

Press any key

Each key lights while you hold it and stays marked once it has been seen. Whatever is left unmarked at the end is what to look at.

Keys

esc
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
F11
F12
~`
!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
win
alt
alt
win
menu
ctrl
prtsc
scroll
pause
ins
home
pgup
del
end
pgdn
↑
←
↓
→
num
/
*
−
7
8
9
4
5
6
1
2
3
0
.
+
enter
Not pressedSeenHeld nowNot on your keyboard

Readings

Progress
—
Most keys at once
—
Chatter
—
Key repeat
—
Last key
—
Held now
—

How to test your keyboard

Press every key once. Each one lights while you hold it and stays marked once it has been seen, so whatever is left grey at the end is a key that sent nothing. Set the size and layout to match your board, and click out any key you do not have, so the count can reach the end of a full keyboard test rather than stopping short. Then type normally for a moment and watch the chatter reading, which names any key sending one press as two.

Questions

Do you record what I type?

No. Nothing is sent anywhere and there is nothing to type into. The page keeps only which keys have arrived, and the report lists them in the order they sit on the board rather than the order you pressed them, so it cannot spell out anything you typed. All of it is gone when you close the tab.

Why is one of my keys not lighting up?

Three reasons, and a dead switch is only one. The board drawn here may not be yours, so check the size and layout buttons first. The system may have taken the key before the browser saw it, which is what happens to Fn and to some print screen keys. Or the key really is not reporting, which is what this page is for.

How do I test my keyboard for chatter or double typing?

Type normally for a while and watch the chatter reading. Chatter is a worn switch bouncing as it closes, so one press arrives as two, which is why it shows up as double typing. The reading names the key and how many milliseconds apart the two presses landed, and anything under twenty is not a finger, because no hand moves that fast.

Why does the board on screen not match my keyboard?

Because no drawn layout covers every board. Pick your size and whether your enter key is tall, then click any key you do not have and it drops out of the count. The marking works regardless, because keys are tracked by their position rather than by the picture.

Can I test my laptop keyboard?

Yes. Choose TKL or 60% depending on whether you have a nav cluster, then click out anything else your laptop leaves off, which is usually the right hand windows and menu keys. After that the count can actually reach the end.

Why can’t I test the Fn key?

Because it never reaches the browser. Fn is handled inside the keyboard itself, which turns it into a different key before anything is sent, so no website can see it. The keys it produces do arrive, so holding Fn and pressing a function key may light a different key, or send something this board has no place for.

Why do my browser shortcuts still work?

Deliberately. The page swallows keys so tab does not move focus and space does not scroll, but it leaves anything held with ctrl, alt or command alone. Without that you could not reload, close the tab or switch away, which is a worse problem than an untested shortcut.

How do I check a mechanical keyboard for stuck or double keys?

Press every key once and look for anything still unmarked, which is a key that sent nothing. Then watch the chatter reading while you type normally, since a switch that fires twice from one press names itself there. A key stuck down shows as held and stays lit until it releases.