Which laptop keys can the tester detect?

It detects standard keys the browser reports as keyboard events — letters, numbers, symbols, modifiers like Shift, Ctrl, Alt and Meta, the arrow keys, Space, Tab, Enter, Backspace, and Escape. A few laptop-specific keys are handled by the firmware before the browser sees them, such as some Fn combinations, brightness or media keys, and certain lock keys, and those may not light up. That is a browser and operating-system limit, not a fault in your laptop keyboard.

Why does one of my keys not light up?

First make sure the on-screen keyboard is focused, since detection only runs while it is active. If the key still stays dark after that, it may be physically dead, dirty under the cap, or loose at the ribbon cable. It can also mean the press was intercepted by an operating-system shortcut before the browser received it, so try the same key in a plain text field to compare.

Does the tester record anything I type?

No. All key detection runs locally in your browser tab. The tool never records, stores, or sends anywhere the keys you press — there is no keystroke logging and no network upload. When you close or refresh the page, everything is gone.

What is the difference between key, code, and keyCode?

The key value is the character or name a key produces, like a or ArrowUp, and it changes with your language layout and any held modifiers. The code value is the fixed physical position of the key, like KeyA or Space, and it stays the same across layouts. The keyCode is an older numeric identifier kept for compatibility with software and games that still use it.

What should I do after I find a dead key?

Re-run the focused on-screen keyboard pass to confirm, then test the same key in a plain text field such as a blank notes document. If the key works there, an operating-system shortcut was probably swallowing the press. If it still does nothing, power-cycle the laptop and try once more before raising it with the manufacturer, the reseller, or a repair shop.

How to Test Keyboard on Laptop: Find Dead Keys Fast

A laptop keyboard test is a focused check that confirms every key — letters, numbers, modifiers, arrows, and function keys — actually registers a press, and a simple way to run one is the free browser-based Keyboard Tester. Open the page, click into the on-screen layout until it becomes the active element, then press each physical key on your laptop one at a time. Every key you press lights up the matching button on the screen and stays marked as tested, so by the end of a single pass you can see at a glance which keys never lit up at all. Those dark keys are your real suspects: they may be physically dead, dirty under the cap, loose at the ribbon cable, or swallowed by an operating-system shortcut before the browser ever sees them. Holding several keys at once exposes a different class of faults — rollover drops and ghosting — where certain key combinations silently miss a press, the kind of input lag a fast typist or gamer notices long before anyone else does. Because the tester listens for key events inside your browser tab and never types into any field, nothing you press is sent across the network or saved anywhere, so it is safe to run on a work laptop, a shared family machine, or any device where you would not normally type a password into a webpage.

Why Laptop Keyboards Deserve Their Own Test

Laptop keyboards live in their own category for reasons that do not apply to most external desktop boards. They are soldered into the chassis, so swapping them out is rarely a casual swap — it is usually a warranty repair or a full top-case replacement. They sit directly above the warmest part of the machine, which means crumbs, pet hair, and the occasional coffee spill collect on them far faster than a keyboard on a separate stand does. They also expose extra keys that desktop boards rarely carry: a row of compact function shortcuts tied to the Fn key, brightness and volume controls that share physical positions with F-keys, and on some models a fingerprint-reader key sitting right next to Backspace.

For all of those reasons, a full pass over the board is worth running at three specific moments: within the return window of any new, used, or refurbished laptop you have just bought; before you start a warranty claim, so you have a concrete list of faulty keys to hand to support rather than a vague "sometimes the t sticks"; and right after a spill or a heavy cleaning, so you can confirm nothing has worked its way under a keycap that is now partially stuck down.

Problems the Tester Helps You Catch

The on-screen layout in the tester is designed to mirror the keyboards you actually use, so a fault on the laptop maps directly to a fault on the screen. These are the categories of fault it surfaces most often.

Dead keys. A key that does not register no matter how hard or how squarely you press it. These usually show up after a long liquid spill, after a heavy drop, or as a slow failure on a board that is several years old.
Sticky or chattering keys. A key that stays lit after you lift your finger, or fires several times for a single tap. This points to mechanical issues — debris under the cap, a worn membrane, or a switch on the way out.
Ghosting and limited rollover. When you hold several keys at once, some presses vanish. Most consumer laptop keyboards cannot register more than two or three simultaneous keys in certain clusters, and the tester makes that limit visible.
Wrong-character keys. A key lights up but produces a different character than the legend on the cap. That almost always means the operating-system language layout or a remapping tool is configured differently from what the keys actually say, not a hardware fault.
Fn-related surprises. Some laptop-specific combinations — Fn + arrow for Home or End, brightness keys, the lock-key row — are handled by the embedded controller firmware before the browser gets a chance to see them, so they may never light up at all.

Running the Test on Your Laptop Keyboard

The whole pass takes a couple of minutes and needs nothing more than the laptop itself and a modern browser tab. Work through these steps once and the result is a complete map of every key on the board.

Open the Keyboard Tester in Chrome, Edge, Firefox, Safari, or any other current browser on the laptop you want to check.
Click or Tab into the on-screen keyboard so it becomes the focused element — without focus, the page cannot capture key events and your presses will do nothing.
Press each physical key on your laptop one at a time, working in a sensible order such as left to right, top row to bottom row, so you do not skip any.
Watch the matching on-screen key light up as you press and stay marked as tested after you release, then glance at the last-key panel showing the key, code, and keyCode values reported for that press.
When you have covered the whole board, look for any on-screen keys that never lit up at all — those are your dead or failing candidates.
To test for ghosting or limited rollover, hold three or four keys at the same time in different combinations — common trouble spots are WASD plus Space, the arrow cluster, and the bottom modifier row — and watch whether every key in the combo stays lit.
Click Reset to clear all the tested marks and the last-key readout when you want a fresh pass, for example after prying up and cleaning under a key that did not light up the first time.

Reading the key, code, and keyCode Readout

Each press reports three different identifiers, and reading them is the difference between knowing that a key works and knowing exactly what your operating system thinks that key is.

Field	What it shows	Stays the same across layouts?
key	The character or name a key produces, such as a, Enter, ArrowUp, or ?	No — it changes with the active language layout and any held modifiers
code	The fixed physical position of the key on the physical layout, such as KeyA or Space	Yes — it stays the same no matter which language layout is active
keyCode	An older numeric identifier that some games, accessibility tools, and legacy scripts still rely on	An older numeric identifier kept for compatibility

For ordinary laptop use the key value is all you need. The code value matters if you are remapping keys inside a game or a remapping tool — KeyA always means the A position even if your layout is set to AZERTY or Cyrillic. The keyCode value is the one to keep an eye on for older applications that ignore the modern code field and read keyCode directly.

What to Do When a Key Stays Dark

A single key that refuses to light up is a starting point, not a verdict. Work through a short checklist before declaring the keyboard faulty.

Confirm that the on-screen keyboard is still focused — click back into the on-screen layout and try the dark key a second time.
Compare against a plain text field like a new tab in a notes app — if the key works there, the press was likely captured by an operating-system shortcut before the browser received it.
Power the laptop down, disconnect the charger, and try the key again on a cold boot, in case a power-management setting is silencing the keyboard while on battery.
If the problem is sticky behavior rather than a dead key — the key lights up and refuses to go out — lift the keycap carefully, clean under it with compressed air or a soft brush, and click Reset to start a clean pass.
For repeat offenders, walk through a deeper test for dead or sticky keys that pays extra attention to switch types and membrane behavior.

If the same physical key is dark on a cold boot and in a plain text field, and cleaning does not change anything, you have a real hardware fault worth raising with the manufacturer, the reseller, or a repair shop.

Laptop Keys the Browser May Not See

The tool is honest about its limits, and the limits are mostly imposed by the operating system or the embedded controller on the laptop, not by the page itself. Use this table to read a dark key as information rather than as a verdict.

Scenario	How it shows in the tester	Why
Fn + function key for brightness, volume, or keyboard backlight	May never light up	Handled by the embedded-controller firmware before the browser receives any key event
Media keys on the function row	May never light up	Often reported as separate media keys outside the standard keyboard event set
Fingerprint reader, power button, or camera-disable key on the top row	Not in the on-screen layout at all	Not a regular keyboard key — it sends its own device event
Caps Lock or Num Lock on some machines	May or may not light up	Some firmwares suppress the lock-key event unless the operating system has asked for it
Any press that triggers an OS-level shortcut such as Win + L	One of the two keys lights up, the other does not	The shortcut was intercepted before reaching the browser tab

When a key falls into one of these cases, treat its darkness as information about how your laptop firmware handles keys rather than as evidence of a broken switch. Cross-checking the same key in a plain text field is the fastest way to find out which side is at fault, and once that picture is clear the next decision — clean, remap, replace, or claim under warranty — becomes much easier to make.