Why the browser is a good place to start
Every layer between your finger and a letter on screen can break: the switch under the keycap, the controller inside the keyboard, the cable or wireless link, the operating system driver, the keyboard layout, and finally the application you are typing in. Testing inside a word processor tells you only that the chain failed somewhere.
A browser page that listens for raw keyboard events cuts the chain roughly in half. Everything below the browser (switch, controller, cable, driver) either delivers an event or it does not. Everything above it (layout, application shortcuts, text expanders) can only change what the event means, not whether it arrives. That single split is what makes this test worth two minutes.
It cannot do everything. A handful of keys never reach a web page at all, because the operating system claims them first. PrintScreen is the usual example, and most Fn combinations are handled inside the keyboard itself and never become key events. Silence on those keys proves nothing.
Four checks, in order
- Open the keyboard test and press the key that is failing. Watch whether it lights up on the on-screen keyboard. If it does, the hardware delivered the press and your problem is above the browser: skip to check four.
- If nothing lights up, press the same key while holding nothing else, then press its twin on the other side of the board if it has one (left and right Shift, Control, Alt). A dead key on one side and a working twin on the other is a strong hardware signal.
- Unplug and replug the keyboard, or if it is wireless, plug it in with a cable. If the key comes back on a cable, the fault is the wireless link or its battery rather than the switch. If it stays dead on both, the switch or the keyboard controller is the most likely cause.
- If the key does register but produces the wrong character, open the key code viewer and look at the code value. That value describes the physical key and does not change with layout. A code that matches the key you pressed while the character is wrong means your keyboard layout, not your keyboard, is the problem.
What each outcome means
| What you see | Most likely cause | What to do next |
|---|---|---|
| Nothing at all, on this key only | Dead switch, or dirt under the keycap | Try the cleaning steps below before you replace anything |
| Nothing at all, on a whole row or block | A broken trace or ribbon connector inside the keyboard | On a laptop this usually means a keyboard replacement, not a repair |
| The key lights up, but nothing types in your app | The application, an overlay, or a shortcut is consuming the key | Test in a plain text field, then close overlays and macro software one at a time |
| The key lights up and the wrong character appears | Keyboard layout, not hardware | Change the layout in your OS settings and test again |
| The key repeats when pressed once | A worn or dirty switch bouncing, or an aggressive repeat delay | Check the repeat delay setting first, because that costs nothing |
Compiled by MyGearCheck from what the keyboard test is able to show. The cause column lists what is most likely, not what is certain: the browser sees the presence or absence of an event, and the rest is inference.
Before you replace anything: the cheap fixes
A key that has gone dead recently and gradually is more often obstructed than broken. Dirt under a switch stops the stem travelling far enough to actuate, and that looks identical to a dead switch from the browser's point of view.
On a mechanical keyboard, pull the keycap off with a puller and look at the stem. Press the switch directly with a fingertip; if it registers with the cap off, the cap or the stabiliser was binding, not the switch. On a membrane or laptop keyboard, do not force the cap off: the retaining clips are fragile and a broken clip is a worse problem than a sticky key.
Compressed air aimed under the key at a shallow angle clears most of what causes this. Hold the can upright so it does not spray liquid propellant onto the board.
If the key works in the browser test but not in one specific application, the culprit is almost always software you installed on purpose: gaming overlays, macro utilities, remapping tools and screen-capture software all register global hotkeys. Close them one at a time and retest between each one, because closing all of them at once tells you nothing about which one it was.
When it is a laptop key
Laptop keyboards are not user-serviceable in the way a desktop board is. The switch is a scissor or butterfly mechanism the size of a fingernail, the ribbon cable runs under the palm rest, and on many models the keyboard is riveted into the top case, which means a keyboard replacement is a top-case replacement.
That changes the calculation. Before booking a repair, run the test with an external USB keyboard plugged in. If every key works on the external board, the fault is definitively in the built-in keyboard and not in the operating system, which is exactly the evidence a repair desk will ask for.
An external keyboard is also a legitimate permanent answer on a desktop-bound laptop. It is not a fix, but it costs a fraction of a top-case replacement and it takes five minutes.
Documenting it for a warranty claim
If the keyboard is under warranty, the repair desk wants evidence that is reproducible, not a description. Run the keyboard test, press every key on the board, and use the copy summary button to put the result on your clipboard, or save it as an image. The summary names the test, the date, the browser and which keys never registered.
Pair that with the serial number and proof of purchase before you contact support. A claim that arrives with a dated, reproducible test result gets triaged faster than one that starts with a description of the symptom.
Frequently asked questions
Why does the keyboard test show nothing when I press Fn?
Fn is handled inside the keyboard itself and never becomes a key event. The browser cannot see it, and its absence from the test says nothing about whether it works. The same applies to most Fn combinations and to keys the operating system claims first, such as PrintScreen.
Does a key that works in the browser but not in a game mean my keyboard is fine?
It means the switch, the cable and the driver are all delivering the press, so the hardware is doing its job. What remains is software: a game with its own input handling, an overlay, or a remapping tool sitting in between. Test the same key in a plain text field to confirm.
My key types two characters when I press it once. Is that a hardware fault?
Usually yes. A switch that bounces sends two presses close together, which is the keyboard equivalent of mouse double-click chatter. First rule out the operating system's key repeat delay, which produces a run of repeats rather than exactly two, and then treat it as a worn switch.
Can a keyboard test in the browser detect a failing switch before it dies?
Not reliably. It can show you a switch that already misses presses intermittently, which is the stage right before failure, if you press the key many times and watch for gaps. It cannot measure actuation force or travel, which are the properties that degrade first.
Is it worth replacing a single mechanical switch?
On a hot-swap keyboard, yes: a replacement switch costs very little and pushes in by hand. On a soldered board it means desoldering, which is a real repair with real risk. Check whether your board is hot-swap before you buy anything.
Why does my keyboard type the wrong symbols after a Windows update?
An update can add or reorder keyboard layouts, and a layout change swaps which character a physical key produces. The key code viewer confirms it in one press: if the code matches the key you pressed while the character does not, the layout is the cause.
Does spilled liquid always kill a keyboard?
No, but it is the failure mode with the worst odds. Sugary liquids leave residue that keeps making contact intermittently after everything looks dry. If a key started misbehaving in the days after a spill, treat residue as the first suspect rather than a dead switch.
Should I test in a browser or use a dedicated keyboard tester application?
For separating hardware from software, the browser is enough and installs nothing. A native application can see a few keys the browser cannot, notably some system keys, which matters only if one of those is the key that is failing.