Keyboard Tester
Press any key and see it light up — a fast way to check every key works.
How to use the Keyboard Tester
- Click the keyboard area once so it has focus.
- Press each key — it lights up and shows its name and code.
- Watch for any key that does not respond or sticks.
About the Keyboard Tester
The keyboard tester listens for the browser’s keydown and keyup events, and the moment you press a key it lights up the matching key on an on-screen QWERTY layout. Next to the board it shows three labels for whatever you last pressed: the readable key name, the physical KeyboardEvent.code, and the legacy numeric keyCode — handy if you are debugging a shortcut or remapping keys.
It is a fast way to confirm every key on a keyboard actually works. A dead key never lights up, and a key that stays lit after you let go is stuck. That makes it genuinely useful when a laptop key feels flaky, or when you are buying a used keyboard and want to check the whole thing responds before you commit to it.
One catch: click the tester area first so it has keyboard focus, or nothing will register. Some keys are also swallowed by the operating system or browser — certain function keys, the Windows or Command key, and Print Screen may never reach the page. Remember this checks that the browser receives each key, which is exactly what matters for typing anywhere on the web. Also try the mouse tester and the typing speed test.
Frequently asked questions
Nothing lights up when I press a key — why?
The tester only sees keystrokes when it has keyboard focus. Click anywhere inside the keyboard area once, then press your keys and they will start registering.
Some keys never register — is my keyboard broken?
Not necessarily. The operating system and browser intercept certain keys before the page sees them, including some function keys, the Windows or Command key, and Print Screen. Those may not light up even on a perfectly good keyboard.
What do the code and keyCode values mean?
The code is the physical key’s identifier, such as KeyA, and it stays the same whatever your keyboard layout. The keyCode is an older numeric value kept for compatibility. Both help when configuring shortcuts or remapping keys.
Does this test the hardware directly?
No tool in a browser can read the hardware directly. It tests whether the browser receives each key press, which is precisely what determines whether you can type and use shortcuts on the web.
Is anything I type sent anywhere?
No. The tester runs entirely in your browser. Your key presses are only used to light up the on-screen keys and are never sent to a server or stored.