Keyboard Tester

How to use this keyboard tester

1. Click anywhere on this page so it has keyboard focus.
2. Press every key on your keyboard, one at a time — a good habit is to work row by row from top-left to bottom-right so you don't miss any.
3. Watch the grid: a key you've pressed at least once turns green (tested), and the key you're currently holding lights up purple (active).
4. Switch the Layout dropdown to see how the same physical keys are labeled under Dvorak, Colemak, or another layout, and switch Size to match your actual board — full size (100%), tenkeyless (80%), 75%, 60%, or 40%.

What this can (and can't) tell you

This keyboard tester confirms whether a key press actually reaches your browser as a keyboard event. If a key never lights up no matter how many times you press it, that's a strong sign of a genuine hardware problem — a dead switch, a disconnected membrane contact, or debris blocking the key.

It's a single-key test, though: it won't catch problems that only show up when multiple keys are held down together (see our Ghosting & NKRO Test for that), and it won't catch a key that registers correctly but doubles up on a single tap (see the Key Chatter Test).

Choosing the right layout and size

Set the layout to match what you actually type with, not necessarily what's printed on your keycaps — if you use an alternative layout like Dvorak or Colemak at the OS level, select it here so the on-screen labels match what you expect to see. Set the size to match your physical board: full size (100%) includes the numpad and full navigation cluster, tenkeyless (80%) drops the numpad, 75% compresses navigation into a single column plus arrow keys, 60% drops navigation entirely (keeping only the function row's row of number keys), and 40% drops the function row and number row too.

Common reasons a key won't register

A key that refuses to light up during this test almost always comes down to one of four causes: debris trapped under the keycap, a worn-out switch or membrane contact, a driver or operating-system setting getting in the way, or, on wireless boards, a dropped connection. Working through these possibilities in order, from simplest to most involved, usually settles the question well before you need to replace anything.

Debris and spills

Crumbs, dust, hair, and sticky drink residue are the single most common reason a specific key stops responding, especially on keys near where you eat or drink at your desk. Debris can physically block a keycap from traveling far enough to complete the switch, or coat a membrane contact so it no longer closes cleanly. Turning the keyboard upside down and tapping it gently, then running compressed air around the base of the affected key, resolves a surprising share of dead-key cases. For a full cleaning walkthrough, see our guide on how to fix a stuck keyboard key.

Worn or dead switches

Every switch has a finite lifespan. Mechanical switches are typically rated for tens of millions of keystrokes, but an individual unit can still fail early due to a manufacturing defect or a bent contact leaf, well before the rest of the board wears out. Membrane keyboards age differently: the rubber domes underneath the keys flatten and lose their snap over years of use, and a heavily used key can eventually stop making reliable contact even though nothing looks visibly wrong. Our piece on mechanical vs. membrane keyboards covers how these two designs age differently in more detail.

Driver and operating system issues

Not every dead key is a hardware problem. Keyboard remapping software, accessibility features like Sticky Keys or Filter Keys, or a stuck modifier key can all change what a keypress produces before it ever reaches this page. If a key fails here, it's worth briefly checking your OS keyboard settings and any remapping tools you have installed, and confirming no other key is physically stuck in the down position. This test reads the raw physical key position reported by your browser, so once software-level interference is ruled out, a key that still won't register is very likely a genuine hardware fault.

Wireless and Bluetooth dropout

Wireless keyboards add a few extra points of failure that wired ones don't have: a low battery, a receiver that's out of range or blocked by interference, or a connection that's dropped into a power-saving sleep state. Before concluding a key is physically dead on a wireless board, try fresh batteries, re-pair the keyboard, and move the USB receiver (or the keyboard itself) closer to rule out a connection issue rather than a switch issue. If the same key fails consistently across multiple pairing attempts and battery swaps, treat it as a hardware problem rather than a wireless one.

Browser-based keyboard tester vs. downloadable software

Most keyboard testing tools fall into two categories: a browser-based tool like this one, and a downloadable desktop application. Each has real tradeoffs worth knowing before you pick one.

The biggest advantage of a browser-based keyboard tester is that there's nothing to install. You open the page, click to focus it, and start pressing keys. There's no installer asking for administrator permissions and nothing left behind on your hard drive afterward. Because this tool runs entirely in your browser, no keystroke data ever leaves your machine. That matters more than it might seem: a testing tool is, by definition, something you run while pressing every key on your keyboard, and a downloadable app with logging or telemetry built in is in a uniquely sensitive position to capture more than you'd want it to.

Downloadable native applications do have one genuine technical edge: some are built to read raw HID (Human Interface Device) reports directly from the keyboard, bypassing the browser and operating system entirely. That can occasionally reveal information a browser can't, such as distinguishing between two keys that a particular OS or browser combination maps to the same code. For the overwhelming majority of everyday troubleshooting, though, a browser-based test covers what people actually need to know: does this key register, and does it register correctly.

If you're deciding between the two, a reasonable rule of thumb is to start with a browser-based tester like this one since it's instant and requires no trust decision, and only reach for specialized downloadable software if you're doing deep hardware-level debugging, such as diagnosing a custom keyboard build or firmware.

How professional reviewers and technicians test keyboards

Keyboard reviewers and repair technicians layer several methods together, precisely because no single test tells the whole story.

For rollover and ghosting, professional reviewers commonly use the same basic approach available to anyone: a visual on-screen keyboard that highlights which keys register while several are held down at once, often systematically working through many row-and-column combinations rather than just a handful of common ones. Our own Ghosting & NKRO Test uses this same principle, tracking the highest number of simultaneous keys your board has successfully reported. Our beginner's guide to NKRO and anti-ghosting explains what that number actually means.

For switch feel and consistency, technicians sometimes use a force gauge, a small instrument that measures how many grams of pressure it takes to actuate a switch, then compare that reading across multiple keys on the same board and against the manufacturer's stated spec. Wide variance from key to key can indicate manufacturing inconsistency, even when every key still technically works.

For debounce and chatter issues, a more involved test connects a keyboard to an oscilloscope or logic analyzer, which can see the exact electrical signal at the microsecond level, well beyond what any software-based test (browser or native) can observe. This is how chatter gets diagnosed with real certainty rather than an estimate, though it requires equipment most people don't have on hand, which is why software-based tests like our Key Chatter Test exist as an accessible first check.

Finally, a technician doing a physical repair will typically open the keyboard and visually inspect the switch matrix and PCB directly, looking for a cracked solder joint, corrosion from a spill, or physical damage that no software test, ours included, can see from the outside. A free browser-based test is genuinely useful for the same first question a professional starts with, does every key register correctly, but it's one layer of a larger diagnostic process, not a replacement for a full teardown when the stakes are high.

Mechanical vs. membrane keyboards: how testing differs

The way a keyboard fails, and how you go about testing for it, depends heavily on whether it's mechanical or membrane.

Membrane keyboards share more of their internal structure between keys: layered rubber sheets and a shared circuit layer sit underneath the whole board. That shared design means membrane keyboards tend to fail in clusters as they age; you might notice several nearby keys all going a little unresponsive around the same time, rather than one isolated dead key, because the underlying rubber domes and circuit traces are degrading together. It also means individual key repair generally isn't realistic on a membrane board: there's no single part to swap out.

Mechanical keyboards give each key its own independent switch, so failures tend to be isolated. If one key on a mechanical board stops registering while its neighbors are fine, that's a strong sign the fault is specific to that one switch, not the whole board. This isolation is also what makes mechanical keyboards easier to test in a targeted way: if you suspect a specific switch on a hot-swappable board, you can pull it and test it individually against a known-good replacement switch, something that isn't possible on a membrane board.

When you run this keyboard tester on a mechanical board, a single dead key with everything else working normally points toward that one switch. The same single dead key on a membrane board is still worth investigating on its own, but it's also worth testing the surrounding keys carefully, since membrane failures have more tendency to spread. Read more in our full mechanical vs. membrane keyboard comparison.

Testing a laptop keyboard vs. an external keyboard

A laptop's built-in keyboard and a separate external keyboard fail differently, and that changes what you can realistically do after this test flags a problem.

Laptop keyboards are almost always a low-profile scissor-switch design, built directly into the chassis and wired into the motherboard. They can't be opened and cleaned as easily as a desktop board, and in most cases a single keycap isn't designed to be removed without special tools or risk of breaking a fragile retention clip. A spill on a laptop keyboard is also a more serious event than a spill on an external one, since liquid has a much shorter path to the motherboard and other internal components. If this test reveals a dead or erratic key on a laptop, and basic compressed-air cleaning doesn't fix it, that's generally a case for a professional repair technician rather than a DIY fix.

External keyboards, whether mechanical or membrane, sit physically separate from the rest of your computer. A spill, a stuck key, or a failed switch is contained to the peripheral itself, with no risk to your actual machine, and replacement parts (or the whole keyboard) are inexpensive and easy to swap.

One practical workaround worth knowing: if this test shows your laptop's built-in keyboard has an unreliable key, plugging in (or pairing) an external keyboard lets you keep working normally while you decide whether a repair is worth it. You can then run this same test on the external board to confirm it's fully reliable before you rely on it daily, and it's worth checking your typing speed and polling rate on the replacement too, since those can differ meaningfully between a laptop's built-in board and an external one.