🌐 EN

⌨️ Keyboard Test

Press each key to confirm your keyboard registers it correctly.

While the keyboard area below has focus, most browser shortcut keys are blocked. Note that a few browser-reserved keys β€” F5 (reload), F11 (fullscreen), F12 (dev tools), etc. β€” can't be blocked from a web page and will still behave normally.

Keys pressed: 0 Unique keys: 0
`
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
;
'
Enter
Shift
Z
X
C
V
B
N
M
,
.
/
Shift
Ctrl
⌘/Win
Alt
Space
Alt
⌘/Win
Ctrl
←
↑
↓
β†’
Esc
F5
F11
F12
Last key: β€” key: β€” code: β€” keyCode: β€”
Input history:
No keys pressed yet.
Hardware tests
GUIDE

Learn more

01

1. Why test your keyboard?

If you bought a used keyboard, built a custom one, or spilled liquid on it and suspect a key isn't responding, this tool lets you verify every key at once. The on-screen keyboard layout highlights the exact key you pressed instantly, so you can see at a glance which keys respond and which don't.

02

2. How to use it

Click the keyboard area once to give it focus, then press each key you want to check. As soon as you press a key, the matching on-screen key changes color, and it resets when released. Work through every key in order to spot any that don't react, and use "Reset" anytime to clear the counter and history.

03

3. key vs. code vs. keyCode

"key" is the actual character produced (affected by Shift and layout, e.g. "a" or "A"), while "code" reports the physical position on the keyboard (e.g. "KeyA") and stays the same regardless of layout (QWERTY/Dvorak, language). "keyCode" is an older numeric identifier that's no longer recommended by the standard but is still shown for reference and compatibility.

04

4. If a specific key doesn't respond

If one key never reacts, suspect a damaged physical switch or contact. On a wireless keyboard, check the battery and connection (Bluetooth/USB receiver) β€” try a wired keyboard to isolate the issue. On a laptop, also confirm another running app isn't intercepting that key combination as a global shortcut.

05

5. Conflicts with browser shortcuts

While the keyboard test area has focus, this tool blocks the default action (like typing into other fields or scrolling) for most keys so testing isn't interrupted. Keys the browser or OS reserves strongly β€” F5, F11, F12, Ctrl+W (close tab), and similar β€” often can't be intercepted by page JavaScript at all, so they'll behave as usual.

Frequently asked questions

I pressed a key but nothing highlighted on screen.
Click the keyboard test area first to give it focus, then try again. If it still doesn't respond, the key's physical contact may be faulty.
Why are the key and code values different?
"key" is the produced character (affected by layout/Shift), while "code" is the physical key position β€” they serve different purposes. Comparing both helps tell a layout issue apart from a hardware issue.
F5 or F11 reloaded/full-screened the page instead of just showing on the tester.
Those keys are reserved system shortcuts the browser controls directly and a web page cannot block. You can still confirm the on-screen key highlighted normally.
How do I clear the history and counters?
Click "Reset" to clear the keys-pressed count, unique key count, and input history back to their initial state.