A dead key is a key that produces nothing at all — no character, no repeat, no response. It is different from a sticking key (one that will not stop) and different again from an intermittent key (one that works most of the time). Telling those three apart decides what you do next, so it is worth doing properly.
A dead key test answers two questions in about a minute: which keys are dead, and how many. That is the entire basis for every decision that follows — clean it, repair it, replace it, or claim warranty.
Dead, stuck or intermittent: know which one you have
- Dead — pressing it produces nothing, ever. Typically a broken trace, a failed switch, or a key that is simply not being scanned by the controller.
- Stuck — the key registers as held down even after release. Usually a keycap that is not returning, debris blocking travel, or a collapsed dome in a membrane keyboard.
- Intermittent — it works, then it does not, then it does. This is by far the most common category, and the one that wears people down, because a text editor gives you no way to reproduce it reliably.
Running a dead key test
Open the online keyboard tester and follow the same flow for all three cases:
- Choose your layout. Desktop 104-key includes the number pad; laptops have a compact layout. Picking the wrong one fills your untested list with keys that do not exist on your hardware.
- Turn Num Lock on if you want to test the numpad — otherwise those keys send navigation codes and the result is misleading.
- Click the page once so the browser window has focus, then press keys one at a time. Pressed keys turn green; the untested panel keeps a live list of everything still silent.
- Pay attention to the release, not just the press. A key that highlights when pressed but stays highlighted after you let go is stuck, not dead.
- For intermittent keys, press ten to twenty times. The tool tracks the total press count, so you can see whether the count matches how many times you actually pressed — a mismatch is your first hard evidence of a key firing twice.
When you are finished, copy the test result. You get a text report listing every key that never responded, which is exactly what you want to have in hand before contacting support or a seller.
Hardware or software? The three checks that settle it
Finding a dead key does not tell you why it is dead. These three checks do most of the work:
- Try the keyboard on another computer. If the same key is dead there too, the keyboard is at fault. If it works, the problem is in the original machine.
- Try another keyboard on the same computer. This is the reverse check, and together the two give you a clean answer with no guesswork.
- Open your system's on-screen keyboard (osk.exe on Windows, Keyboard Viewer on macOS) and press the suspect key. If the on-screen key highlights, the operating system is receiving something — which points away from hardware and toward the application or input method that is swallowing it.
One more quick test worth knowing: boot into BIOS or UEFI and try navigating with the arrow keys. If the keyboard works there but not in the operating system, the hardware and power are fine and everything points at drivers or software. With external keyboards this gives a cleaner signal than any other check.
Common causes, from most fixable to least
- A single dead key on a mechanical keyboard. Most often the switch itself — contaminated contacts or a failed solder joint. On a hot-swap board, pulling the switch and swapping in a spare settles it in under a minute.
- A single dead key on a laptop. Usually debris under the keycap or a broken scissor mechanism. A stuck foreign object can often be cleared with compressed air; a broken clip is a replacement-part job.
- A whole block of adjacent keys dead at once. This is a strong hardware signal — a broken row or column trace, or a damaged membrane or ribbon cable. In a laptop, it is the classic signature of a past liquid spill.
- Specific keys dead in every application. Check whether the key is remapped or disabled by a configuration utility, keyboard mapping tool, or game profile before assuming hardware failure.
- Multiple unrelated keys dead. Suspect the controller: a loose ribbon cable on a laptop, or a failed controller IC on a standalone board. Rare, but it explains scattered failures that have no physical proximity.
What to do with the result
- One dead key, keyboard under warranty: claim it. Attach the test report so the exact key is on record from the start.
- One dead key, mechanical, hot-swap, out of warranty: replace that switch. It is the cheapest possible repair.
- One dead key, membrane or soldered board: weigh it against the price of the keyboard. Repairs here usually cost more than the board is worth.
- A dead block or scattered dead keys: treat as a hardware failure. On a laptop, get it professionally assessed rather than opening the ribbon connectors yourself — the clips are fragile and the board-side connector is far more expensive than the keyboard.
Frequently asked questions
Can a dead key be a software problem?
Yes. A mapping utility, a vendor driver profile or an application-level shortcut can disable a key so completely that it looks dead. Test the same keyboard on another machine first — if the key works there, the operating system is your problem, not the hardware.
My key works in one app but not another. Is it dead?
No. A key that produces nothing in exactly one application is almost always that application's shortcut configuration or an input method intercepting it, not a hardware fault.
How do I test a laptop's built-in keyboard specifically?
Switch the tester to the laptop layout first, then press the built-in keys. For laptop-specific failure modes — including Fn lock and ribbon cable issues — switch the tester to the laptop layout first — the keyboard tester has a dedicated compact layout for it.
Does a dead key test work on wireless and Bluetooth keyboards?
Yes. The tester reads standard keyboard events, which are identical regardless of how the keyboard is connected — USB, Bluetooth or 2.4 GHz.
You cannot fix what you have not located. Run a dead key test first, write down the exact keys, and everything after that gets simpler.