Keyboard Tester
Press every key and see it light up. Finds dead and stuck keys and shows key codes.
Runs in your browser. Nothing is uploaded.
Orange = held now, green = worked. A key that never turns green is dead; one that stays orange is stuck. Browser shortcuts (like ⌘W) may still act.
Nothing yet. Click the page, then type.
How to test a keyboard
Click anywhere on the page and press every key. Each key turns green once it has registered; the one you are holding is highlighted. When you are done, any key still grey did not send anything and is likely dead or dirty under the cap. A key that stays highlighted after you let go is stuck.
Key codes
The table shows the key value, the physical code and the legacy keyCode for the last presses, useful for developers checking keyboard events and for confirming that a remapped key sends what you expect.
Keys the browser keeps
Some shortcuts are handled by the browser or operating system before the page sees them, for example closing a tab, switching apps, or media keys. Those may not light up here even though the key works.
Laptop layouts
The layout shown is a standard full-size layout. Compact and laptop keyboards have fewer keys and Fn combinations, which the page cannot see; test the keys you have and ignore the rest.
Ghosting and key rollover
Hold down several keys at once: each one you hold stays highlighted. If a key you add does not light up while others are held, the keyboard has hit its rollover limit or is ghosting. Many office keyboards can only report two or three keys together in some combinations, which matters in games where you hold W, A and Shift while pressing Space. Gaming keyboards often handle six keys or any number of keys at once. Try the combinations you actually use.
Wrong character but the key works
Compare the Key and Code columns in the table. Code is the physical key, Key is the character your layout turns it into. If Code is right but Key is wrong, for example @ and " are swapped or Y and Z, the keyboard is fine and the operating system is set to a different layout, such as UK instead of US or German instead of English. Change the input language or layout in your OS settings. If Code itself is wrong or missing, the problem is in the keyboard or its driver.
Related tools
All device tests- Code Typing TestType real JavaScript and Python snippets and see your WPM and accuracy.
- Microphone TestSee your mic level and waveform live, pick the right input, and record 5 seconds to hear yourself.
- Dead Pixel TestFull-screen white, black, red, green, blue, and grey to spot dead or stuck pixels and backlight bleed.
- Webcam & Camera TestTest your camera online: see if it works, its real resolution, frame rate and lighting. Flip the mirror, save a snapshot.
- Speaker & Headphone TestPlay a tone in the left, right, or both channels and a 40 Hz to 16 kHz sweep to find a dead side or crackle.
- Mouse Test: Clicks, Double Click & Polling RateCheck every mouse button and the scroll wheel, catch accidental double clicks from a worn switch, and measure the polling rate in Hz.
- Refresh Rate Test: Check Your Screen HzSee your monitor or phone's real refresh rate (60, 120, 144 Hz or more) and dropped frames, with a moving block to judge smoothness.
- Controller Tester: Buttons & Stick DriftTest an Xbox, PlayStation or any gamepad in the browser: every button, analogue triggers, stick drift and rumble.