Keyboard Tester
Press a key. See it light up. Find the dead one in ten seconds.
Press any key on your keyboard. Every key you press stays marked, so you can work across the board and see what is left.
– untested
0 working
0 faulty
0 keys at once
- Last key
- press a key
- Character
- –
- Key code
- –
- Held
- –
A keyboard tester that shows you the key, not a status message
This keyboard tester checks every key on your keyboard from inside the browser. Press a key and the matching cap above sinks, the way the real one does under your finger. Keys you have already pressed stay marked, so you can work across the board at your own pace and see exactly what is left. A cap that never sinks is a key that never reached the browser, and that is usually the whole answer: one dead switch, found in about ten seconds, without installing anything.
There are three ways a keyboard goes wrong, and they are not the same problem. A key can be dead, and never report at all. It can be stuck down, reporting continuously while you are not touching it. Or it can chatter, firing twice from a single press. Most online testers only find the first one. This tester marks a stuck key after fifteen seconds of being held, and flags a second press landing within forty milliseconds of the last release as chatter, because no human double tap is that fast. Each of the three has a different cause and a different fix.
Pick the layout in front of you
Keyboards are not all the same shape, and a tester that only draws a standard American 104-key board is not much use if you are holding something else. Six layouts are drawn here, and each one has its own page with the tester already set to it:
- Full size keyboard test. All 104 keys, the number pad included. Press each one and the cap sinks; anything that stays up never reached the browser.
- TKL keyboard test. Eighty-seven keys: everything a full size board has except the number pad.
- 65% keyboard test. Compact, but it keeps the arrows. Press every key, including the right-hand column most people never check.
- 60% keyboard test. Sixty-one keys and nothing else. Everything the board dropped now lives on a layer.
- ISO keyboard test. The UK and European layout, with the tall Enter and the extra key beside the left Shift.
- Mac keyboard test. For a MacBook or a Magic Keyboard, including the modifiers macOS handles differently from Windows.
If your board is not quite any of these, test it anyway. The readout below the keyboard names whatever key actually arrived, including keys the drawn layout does not have, so a slightly unusual right-hand column or a manufacturer-specific key still tells you what you need to know.
What the numbers under the keyboard mean
Untested counts the keys this layout has that have not reported yet. It deliberately excludes keys a browser cannot see, so a healthy full size keyboard really can reach zero rather than stopping at four. Working counts everything that reported cleanly. Faulty appears only when something is chattering or stuck.
Keys at once is the most keys you have held simultaneously during this session, and it is the quickest way to learn something real about your hardware. A cheap membrane keyboard usually stops at two or three. A great many keyboards stop at exactly six, which is not a defect but the size of the standard USB keyboard report. Going past six means the keyboard has full N-key rollover. Try holding W, A, Shift and Space together, the combination games actually use, and see what survives.
The live readout, and the difference between a key and a character
Under the counters, the tester shows four things about the last key you pressed: its physical position, the character it produced, the legacy numeric code, and how long you held it.
The first two are the interesting pair. The position never changes. The character depends entirely on the keyboard layout your operating system is set to, which is why a UK keyboard on a US layout puts the at sign and the double quote in the wrong places and types a backslash where the hash should be. Nothing is broken in that situation and no amount of cleaning will help. If the position is right and the character is wrong, change the layout setting. If the position never appears at all, then it is the key.
Keys that will not report, and why that is normal
Some keys cannot be tested in a browser and are drawn with a dashed outline so you do not go hunting for a fault that is not there. The Fn key on a laptop is resolved inside the keyboard controller and never reaches the operating system at all. Print Screen is usually taken by the system or a screenshot utility first. The Windows and Command keys often open a system menu rather than reaching the page. Media and brightness keys are handled the same way on most machines. None of these silences means a failure, and none of them counts against the untested total.
When the test finds something
The pattern matters more than the individual key. One dead key with working neighbours points at that switch, or debris under it, or a bad solder joint. A whole row or column gone points at a trace or a controller pin, and on a laptop usually at the ribbon cable connector rather than the keys. A scattered but consistent set of failures suggests liquid that spread along the board. Every key dead means a cable, a port or a driver long before it means the keyboard.
Before opening anything, three cheap checks are worth the two minutes: plug the keyboard into another computer, try a different USB port directly on the machine rather than through a hub or monitor, and turn off Sticky Keys and Filter Keys if either has been enabled by accident. A keyboard that works on another machine has told you the fault is not in the keyboard.
- Keyboard ghosting test. Hold several keys at once. If one of them stops reporting, your keyboard cannot see that combination.
- N-key rollover test. Hold down as many keys as your fingers allow. The counter tells you how many your keyboard is willing to report at the same time.
- Key chatter test. One press, two characters. Chatter is a switch problem, and it is one of the few keyboard faults that gets worse over time.
- How to find a stuck key. A key held down without you touching it explains a surprising number of computer problems.
- Keyboard keys not working. Which keys failed tells you more than the fact that they failed. Test first, then read the pattern.
- Keyboard key codes. Every key press gives a browser three different values. They mean different things, and only one of them is about the physical key.
Buying a used keyboard, or checking a new one
The other reason to run a full pass is that the keyboard is not yours yet, or is brand new. A second-hand mechanical keyboard can look immaculate and still have a chattering switch that only shows up after twenty presses, and a freshly built or freshly soldered board frequently has one joint that did not take. Working across every key in order, rather than typing a sentence and calling it fine, finds both in a couple of minutes.
Privacy
Everything happens inside your browser. Key presses are not transmitted, stored or logged anywhere, there is no account and nothing to upload, and closing the tab ends the test with nothing left behind. That matters more than usual for a tool like this one, because the thing being measured is literally everything you type.
Frequently asked questions
How do I test if my keyboard is working?
Press keys on the board above. Each key you press sinks on screen and is counted as working. Work across the whole keyboard and watch the untested number fall to zero. Anything still untested at the end never reached the browser, which means it is either dead or a key the operating system intercepts, such as Print Screen or the Windows key.
Why is one key on my keyboard not working?
A single dead key with working neighbours is almost always the switch itself or debris underneath it, rather than anything to do with the computer. If a whole row or column is dead instead, the fault is more likely a broken trace or, on a laptop, the ribbon cable connector.
What is keyboard ghosting?
Ghosting is a keyboard reporting a key nobody pressed, because three keys held in a rectangle on the internal grid make a fourth intersection look closed. Modern keyboards avoid it by refusing ambiguous combinations instead, so what people meet today is usually blocking: a key going quiet while you are still holding it.
What is N-key rollover and do I need it?
N-key rollover means a keyboard can report any number of keys held at once, because each switch has a diode preventing the ambiguity that causes ghosting. It matters for games where movement, sprint, crouch and an action key are held together. For typing it makes no practical difference.
How do I know if my keyboard has anti-ghosting?
Hold several keys down at once and watch the keys-at-once counter above. Two or three is a typical membrane keyboard. Exactly six every time is the standard USB keyboard report format. More than six means full rollover.
How do I fix a stuck or repeating key?
First find it: any cap shown as pressed while you are not touching the keyboard is physically stuck, and after fifteen seconds it is flagged. Then press it firmly a dozen times, and if that fails, remove the keycap and clear the debris with compressed air. Dried liquid needs isopropyl alcohol and patience.
What causes a key to type twice from one press?
Switch chatter. Every mechanical contact bounces for a few milliseconds, and keyboard firmware normally ignores that window. As a switch ages or gets contaminated the bounce outlasts the window and one press produces two characters. The tester flags any repeat within forty milliseconds, which is faster than a human can double tap.
Does this keyboard tester work on a laptop keyboard?
Yes. Pick the tenkeyless layout for most laptops, or full size for a machine with a number pad. The one thing it cannot test is the Fn key, which is handled inside the keyboard and never reaches the operating system.
Does it work on a Mac keyboard?
Yes, and there is a Mac layout above that labels the modifiers correctly. Option reports as Alt and Command reports as Meta, because browsers describe keys by position rather than by legend. Command is often swallowed by macOS before the page sees it.
Can I test a wireless or Bluetooth keyboard?
Yes. Bear in mind that dropped and doubled keys on a wireless keyboard are usually the radio link rather than the switches: a genuine hardware fault kills the same key every time, while interference and weak batteries cause different keys to fail at random.
What is a key code and why does the test show one?
A browser reports the physical key position, the character your layout produces, and a legacy numeric code. Showing all three makes it obvious when a key works perfectly but types the wrong character, which is a keyboard layout setting rather than a fault.
Why does my keyboard test show keys I did not press?
If a key lights up on its own it is either physically stuck down or genuinely ghosting. Release everything and look at the board: anything still shown as pressed is stuck. If it only happens while several other keys are held, it is ghosting in the original sense, which is rare on current hardware.
How do I test the function keys?
Press F1 to F12 directly. If the brightness or volume changes and nothing appears, the row is in media mode and the keys work fine. Hold Fn and press them again to confirm. The persistent setting lives in the BIOS on most laptops and in System Settings on a Mac.
How do I test the number pad?
Choose the full size layout and press every pad key. Watch what the readout names: Numpad4 means the pad is sending digits, while ArrowLeft from the same key means Num Lock is off. If the pad moves the mouse pointer instead, the Mouse Keys accessibility feature is switched on.
Is my keyboard broken, or is it a driver problem?
Plug the keyboard into another computer. If the same keys fail there, it is the keyboard. If it works, the fault is on the original machine: a driver, a remapping tool, the keyboard layout setting, or an accessibility feature such as Filter Keys.
Does this send my keystrokes anywhere?
No. Every key press is handled inside your browser. Nothing you type is transmitted, stored or logged, and closing the tab ends the test with nothing left behind.