What this keyboard test checks

Most online keyboard testers do one thing: they light up a key on screen when you press it, so you can spot a key that has stopped responding. That is genuinely useful, and this tester does it — but a dead key is only one of the four ways a keyboard actually fails. This test measures all four.

How to test your keyboard

1. Click anywhere on the tester panel first so the page has keyboard focus.
2. Press every key in turn. Each one turns amber while held and teal once it has registered a clean press.
3. Watch for red. A key that turns red has chattered — it sent two signals from what should have been one press.
4. Test rollover. Hold down four, five, then six keys at once and watch the “max keys at once” figure. Most membrane keyboards stop at 3–6.
5. Test auto-repeat. Hold any letter key down for two seconds. The repeat rate appears once enough repeats have been timed.
6. Check what is left grey. Any key still untested at the end either was not pressed, or is not registering at all.

Key chatter: the most common mechanical failure

Chatter, sometimes called double-firing, is when a single physical press produces two or more registered keystrokes. You press “n” once and get “nn”. It is the most common way a mechanical keyboard degrades with age, and it is the failure a simple lights-up tester cannot see at all — the key is registering, just too many times.

The cause is physical. A mechanical switch closes a metal contact, and metal contacts do not close cleanly: they bounce microscopically for a few milliseconds before settling. Firmware compensates with a debounce window, typically 5–20 ms, during which any further signal from that key is ignored. As a switch wears, oxidises or collects dust, its bounce period lengthens past the debounce window, and the extra bounce gets through as a second keystroke.

Fixing a chattering key

• Clean it first. Compressed air, or a contact cleaner made for electronics, resolves a meaningful share of cases because dust and oxidation are common causes. This is free and worth doing before anything else.
• Increase debounce. If your keyboard runs QMK, VIA or vendor configuration software with a debounce setting, raising it a few milliseconds masks the problem completely. The trade-off is a marginal increase in latency that most people cannot perceive.
• Replace the switch. On a hot-swappable board this takes seconds and costs pennies. On a soldered board it means desoldering, which is the point where many people decide to replace the keyboard.
• Remap around it. If the affected key is one you rarely use, remapping is a legitimate workaround.

Rollover and ghosting: not the same thing

These two terms are used interchangeably almost everywhere, and they describe different failures.

Rollover is how many keys a keyboard can report as held at the same time. “6KRO” means six simultaneous keys; “NKRO” means no practical limit. When you exceed the limit, extra keys are simply not reported — nothing appears.

Ghosting is worse and rarer: the keyboard reports a key you did not press. It happens on cheap membrane boards where keys share a wiring matrix without isolating diodes. Press three keys that form a rectangle in the matrix and the controller cannot distinguish that from a fourth key at the rectangle’s corner, so it reports a phantom keystroke.

A practical note: the standard USB keyboard protocol reports a maximum of six non-modifier keys, so many keyboards capable of NKRO report only 6KRO until you enable NKRO mode explicitly, often with a firmware toggle or a key combination. If this tester reports exactly 6, that is expected behaviour rather than a defect — modifier keys such as Shift, Ctrl and Alt are tracked separately and do not count toward the six.

Auto-repeat: what the number means

Hold a key down and, after an initial delay, your operating system starts repeating it automatically. This tester measures the interval between those repeats and reports the rate in characters per second.

Both the delay and the rate are operating-system settings, not keyboard hardware. On Windows they live under Keyboard properties; on macOS under Keyboard settings, where “Key Repeat” and “Delay Until Repeat” control them. Typical configured rates land somewhere between 10 and 30 characters per second.

This matters more than it sounds. A slow repeat rate makes holding Backspace or an arrow key feel sluggish. It also matters for anything that counts keystrokes: a spacebar speed test that does not filter auto-repeat will read your OS repeat rate rather than your actual pressing speed, which is why most spacebar counters produce inflated and inconsistent scores.

Reading your results

Laptop keyboards versus external keyboards

If an external keyboard passes this test and your laptop’s built-in keyboard fails it, the fault is isolated to the laptop’s keyboard assembly or its ribbon connection — not the operating system, drivers or ports. That is a genuinely useful diagnostic split, and it takes thirty seconds to establish.

Worth knowing before you plan a repair: laptop keyboards are rarely repairable at the individual key level. The switches are part of a single moulded assembly, so the standard fix is replacing the whole keyboard unit, and on many modern laptops that assembly is riveted to the chassis. Establishing whether the fault is the keyboard or the machine is still worth doing, because it tells you what you are actually buying.

When the keyboard is fine and something else is wrong

A keyboard test that passes cleanly rules out a large class of problems, which is often the most valuable outcome. If every key registers here but you still have trouble elsewhere, the cause is above the hardware layer:

• Layout mismatch — the keyboard sends a scan code, the OS decides what character that means. A US board on a UK layout swaps quotes, @ and the pound sign.
• Sticky Keys or Filter Keys — accessibility features that change how held and repeated keys behave, and that are easy to enable accidentally with a shortcut.
• Remapping software — PowerToys, Karabiner, AutoHotkey and vendor software all intercept keys before applications see them.
• Application-level capture — games and remote-desktop clients often grab input exclusively.
• Wireless interference or a flat battery — typically shows as intermittent dropped keys rather than one consistently dead key. Test wired if you can.

FAQ