Device Tests
Keyboard Tester
Keyboard Tester is part of Toolspire and is ready as soon as this page loads. Press each key once. It lights up on the keyboard, and a key that stays down after you let go is flagged. Nothing you type is saved or uploaded.
On this page
What you can do here
A key that lights up
Pressed keys are filled in. Keys you have already tried stay tinted, so you can see what you still have not pressed.
Stuck-key warning
If a key is still down after four seconds, the page says so.
Repeat counter
Holding a key on purpose increments Repeats, which is also how you spot a key that chatters.
Physical codes
The log shows codes such as KeyA and ShiftLeft, which stay stable across layouts.
The sequence
How to test a keyboard
- 1
Click the page
Make sure the cursor is not in a text field. Those swallow keys on purpose.
- 2
Press every key once
Each key should light up and then go dark when you release it.
- 3
Watch for a key that stays lit
A key that is still highlighted after you have let go, and that the warning names after four seconds, is sticking.
- 4
Try a modifier
Shift, Ctrl, Alt and the Windows or Command key each have their own place on the diagram.
Worth knowing
- Keyboard Tester on Toolspire: draws a full keyboard and lights each key as the browser reports it, including function keys, modifiers and arrows.
- A key held for more than 4 seconds is called out, which is how a stuck key usually shows up.
- Counts auto-repeat events separately from real presses, so a chatty key is visible.
- Keeps a short list of the latest keys and their
KeyboardEvent.code, the physical key rather than the character. - Runs entirely in the page. Keystrokes are not stored and not sent anywhere. Leaving the tab releases every “held” key.
A key does nothing
- The cursor is in a field — click the grey page background and try again.
- A browser shortcut — Ctrl, Alt and Command combinations are left alone so the test does not steal refresh or tab switching. Press the key on its own.
- Fn on a laptop — function keys may be media keys until you hold Fn, or the other way round. That is a firmware setting, not a dead key.
- The switch — spill, dust or a worn switch can kill one key. If the same key fails in another app, the keyboard is the problem.
Code and character
The diagram uses the physical position (KeyQ), not the letter your layout prints. On an AZERTY keyboard the key in the Q position still reports KeyQ while the character is A. That is why the log shows both.
FAQ
Questions about Keyboard Tester
Where does Keyboard Tester run?
How do I find a stuck key?
Are my keystrokes uploaded or saved?
Why did Ctrl and Alt not light the letter keys?
Does it work with a non-US layout?
My function keys change the volume instead. Is that a fault?
Keep going
Related tools
Last updated Report a problem or suggest a feature