How to Test Your Keyboard for Dead Keys and Ghosting

In hardware talk, a dead key is a switch or membrane contact that no longer produces a reliable key-down event. In typing software, “dead key” can also mean a diacritic key that waits for the next character — that is a different concept. Here you care about keys that simply fail to light the tester when you press them.

• Never lights — strong sign of a failed switch, broken trace, or mis-mapped layer
• Intermittent — dirt, oxidation, failing solder, or a worn membrane dome
• Double-fires — chatter or debounce issues; feels like sticky repeats
• Works in OS, fails in game — often rollover limits or software focus, not a dead switch

Open the free keyboard tester and press every key once while watching the visual layout. Keys you have pressed should stay marked so you can finish a full sweep without guessing which ones you skipped. Laptop Fn combinations and media keys may not map 1:1 to a standard layout — note those separately.

If one key fails only after long sessions, heat and flex matter. Retest after the keyboard cools and again after a firm reseat of the cable or dongle. For pure typing throughput after the board is healthy, use the typing speed test and the WPM measuring guide.

A visual layout mirrors a common full-size or laptop-style board on screen. Each physical press highlights the matching on-screen key so you confirm both the mechanical click and the OS event.

• Coverage map — see untested keys at a glance
• Layout mismatches — ISO vs ANSI Enter, missing numpad, or compact 60% boards may not match the drawing exactly
• Focus proof — if nothing highlights, the page may not have keyboard focus
• Sticky state — held keys often stay lit while down so you can compare chorded presses

Click the page once before you start so the browser targets the tester, not the address bar. Close overlay chat widgets that steal keystrokes. Full-screen the tab if your OS uses the same shortcuts the test needs (for example Windows + letter combos that open apps).

Compact boards and layers (Fn + number row for F-keys) need two passes: base layer, then function layer if your firmware exposes those as distinct codes. Document which physical positions failed so a replacement search matches the same form factor.

Rollover is how many keys the keyboard can report at the same time. Marketing often says NKRO (n-key rollover) or “anti-ghosting.” Ghosting is the classic matrix failure mode: certain multi-key combinations produce a false third key or drop a real one because the wiring cannot uniquely identify every combination.

• 2KRO / 6KRO — common on cheap boards and some office keyboards; fine for typing, painful for complex game binds
• NKRO over USB — many modern mechanical boards report many simultaneous keys when the host and mode allow it
• Ghost key — a key you did not press lights up while holding others
• Dropped key — a key you are holding vanishes from the simultaneous set

In the tester, hold several keys together (for example WASD plus shift and space) and watch which ones stay active. If a gaming chord fails only on one board but works on another PC with the same game, compare rollover results between boards rather than blaming the title first.

Wireless dongles, Bluetooth profiles, and “office” vs “game” firmware modes can cap simultaneous keys. Retest wired if the board supports a cable. High-action games and certain music apps stress rollover more than email ever will.

Browser keyboard events expose several identifiers. They help you debug layout, remapping, and “wrong character appears” issues.

• event.code — physical position (for example KeyA, Digit1) even if the printed legend differs on a Dvorak or custom layout
• event.key — the character or named key the OS thinks you typed after layout and modifiers
• keyCode — legacy numeric code; still shown by many tools for compatibility, but modern code should prefer code / key

If you press the physical QWERTY “A” position and code is KeyA while key is something else, the switch works and your layout or remapper is intentional. If neither updates, the host never received a press — hardware, disconnect, or focus loss.

Macro software and vendor drivers can rewrite events before the browser sees them. Test in a clean profile or another machine when codes look wrong but the key clearly clicks. International layouts (AZERTY, QWERTZ) will show different key values for the same physical code — that is expected, not a defect.

Work from software and environment toward hardware so you do not replace a healthy board.

1. Retest in another browser or private window — extensions can inject or block keys.
2. Try another USB port, cable, or dongle — flaky power and half-seated connectors mimic dead keys.
3. Disable overlay and remote tools — Discord overlay, GeForce Experience, remote desktop can swallow input.
4. Check OS sticky keys / filter keys / language — accessibility and layout switches change behavior.
5. Clean around the switch — crumbs and liquid residue cause intermittent failures on membrane and mechanical boards.
6. Compare with a second keyboard — if both fail the same way, suspect the PC; if only one fails, suspect that board.

Mechanical hot-swap boards let you reseat or replace a single switch after you confirm the position. Membrane laptop keyboards are harder; intermittent keys after spills often need professional service rather than repeated online tests.

When the keyboard is fine but the mouse misbehaves, switch to the mouse tester and the mouse testing guide. Click rate and reaction checks live in the click speed test and reaction time tester.

Not every failed test means the whole board is trash. Match the fix to the failure mode and the cost of downtime.

• One intermittent key after crumbs — clean first; many “dead” keys recover
• Single mechanical switch, hot-swap plate — replace the switch; cheapest durable fix
• Widespread ghosting on a budget matrix — expected design limit; upgrade if games demand NKRO
• Multiple random failures after liquid — corrosion spreads; replacement is usually smarter
• Warranty period and clear defect — document with the tester and RMA rather than opening sealed units

Log date, browser, wired/wireless mode, and which physical keys failed. That note helps support tickets and future you when a “fixed” key dies again. Do not force liquids into switches while powered.

After repair or replacement, re-run a full visual sweep and a multi-key rollover chord you care about in games. Then confirm everyday typing feel with a short timed typing session so muscle memory settles on the new board.

A clean pass takes a few minutes and answers most hardware questions.

1. Open the free keyboard tester and click the page so it has focus.
2. Press each key once and confirm it lights on the visual layout.
3. Note any key that never highlights or that double-registers.
4. Hold multi-key combos you use in games or editors and watch simultaneous lights for ghosting or drops.
5. Read key, code, and keyCode for a suspicious key to confirm the OS event.
6. Retest wired or on another machine if results look wrong for an otherwise solid board.
7. Log failures with layout type (laptop, TKL, full-size) before you buy parts or file warranty.

Do not mash so hard you damage thin laptop scissor switches. Firm, normal presses are enough. Keep liquids away from the keyboard during testing — the tool cannot fix a shorted membrane.

Pair keyboard health checks with mouse and click tools when you are validating a whole desk setup. Generatr’s tester suite keeps input diagnostics in one place without installs.