Which keys can it detect?

It detects standard keys your browser reports as keyboard events, including letters, numbers, symbols, function keys, modifiers like Shift, Ctrl, Alt and Meta, the arrow keys, Space, Tab, Enter, Backspace and Escape. A few keys are handled by the operating system or hardware before the browser sees them (for example some laptop Fn combinations, media keys, or certain lock keys), so those may not register — that is a browser and OS limitation, not a fault in your keyboard.

Why doesn't my key light up?

If a key stays dark after you press it, first make sure the on-screen keyboard is focused, since detection only runs while it is active. If it still will not light up, the key may be physically dead, dirty, or disconnected — a common sign of a failing keyboard. It can also mean the press was intercepted by the operating system or a global shortcut before the browser received it, so try the key in a plain text field to compare.

Is anything I type recorded?

No. All key detection runs locally in your browser. The tool never records, stores, saves, 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 layout and 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.

Keyboard Tester for Beginners: Run It Step by Step

A keyboard tester is a free browser tool that turns every key you press into a visible, on-screen reaction, so you can confirm at a glance whether each button on your physical keyboard actually works. You click into an on-screen QWERTY layout, then start pressing keys; the matching button lights up the moment the browser receives the event, and stays marked so you can see your progress across the whole board. Any key that never lights up is a candidate for a dead, dirty, or disconnected switch. Beyond a simple pass/fail, the tester also reports three values for each press — the character or name, the fixed physical code, and an older numeric keyCode — and lets you hold multiple keys at once to surface ghosting or rollover problems. For beginners, it is the fastest way to prove a keyboard is healthy before a return window closes, document a fault before opening a support ticket, or chase down an input issue that only seems to appear in games.

What the Keyboard Tester Actually Shows You

For a beginner, the most confusing part of any keyboard tester is not the testing itself — it is understanding what the screen is trying to tell you. The tester draws a familiar QWERTY layout inside the browser, and every key on that layout has three states: idle (not pressed recently), lit (currently held down), and marked (already pressed during this test pass). Held keys glow as long as your finger is on them, so a key that stays bright after you let go is doing exactly that — staying pressed — and that lingering visual is one of the clearest signals of a sticky or chattering switch.

The last-key panel sits next to the layout and updates the moment a new event arrives. Three values appear there for each press, and each one answers a different question about the key. You do not need to memorize them on day one, but knowing they exist saves you from misreading a "broken" keyboard when it is really a layout or remapping problem underneath.

How to Run Your First Keyboard Test

If this is your first time using a browser-based keyboard tester, the cleanest path is to follow the same five-step pass every time. Take it slow on the first round — accuracy matters more than speed, and a missed key looks identical to a dead key once the test is over.

Click or tab into the on-screen keyboard so it becomes active and starts capturing your key presses. Until the layout is focused, the browser will not receive most key events.
Press each physical key on your keyboard one at a time and watch the matching on-screen key light up and stay marked as tested. Work in sections — left hand, right hand, top row, function row, arrow cluster — so you do not miss anything.
Read the last-key panel to check the key, code, and keyCode values reported for the key you just pressed. If a value looks wrong, note it before moving on.
Look for any on-screen keys that never light up after you have pressed them — those are likely dead or failing keys worth investigating.
Click Reset to clear all tested marks and the last-key readout when you want to run a fresh test pass, for example after popping off a keycap to clean under it.

Reading key, code, and keyCode Without Confusion

The three values in the last-key panel look similar at first, and beginners often assume they are just synonyms. They are not — each one describes a different layer of the key event, and together they tell you whether a problem is hardware, layout, or software.

Value	What it represents	Changes with layout or language?	Common example
key	The character or named action the key produces	Yes	a, Enter, ArrowUp
code	The fixed physical position of the key on the board	No	KeyA, Space, ArrowUp
keyCode	An older numeric identifier still used by some software and games	No	65, 32, 38

A useful way to remember the difference: key is what you would see if you typed the key into a document, code is where your finger actually is on the board, and keyCode is the legacy number some older apps still expect. If your Space bar shows key = " ", code = "Space", keyCode = 32, the keyboard is reporting normally. If key shows the wrong letter but code still shows the right physical position, your operating-system layout or a remapping tool is the culprit — the hardware underneath is fine.

Spotting Dead, Sticky, and Ghosting Keys

The visual feedback in the tester is your diagnostic. There are three patterns beginners should learn to recognize, because each one points to a different kind of fault and a different fix.

A dead key is the simplest case: you press it, nothing lights up, and the last-key panel does not change. Common causes include dust or liquid under the keycap, a loose ribbon cable on a laptop keyboard, or a worn-out membrane on an older board. If a single letter suddenly stops working, the dead-key pattern is the first one to confirm.

A sticky or chattering key shows the opposite problem — it lights up and stays lit after you release it, or it fires several times for one tap. That lingering highlight is the visual signature of a switch that is not releasing cleanly. Cleaning under the cap often fixes it; if not, the switch itself may need replacing.

A ghosting or rollover problem only appears when you press several keys at once. Some keyboards cannot register every combination, so certain presses silently vanish. To check this in the tester, hold three or four keys at the same time — for example, W, A, S, and D — and watch whether all four stay lit. If one drops out while you are still pressing it, the keyboard has limited rollover on that cluster, which matters for gaming but rarely for typing. For a closer look at how to interpret patterns like these, the guide on Keyboard Tester accuracy and how to read the results right walks through common result shapes in more detail.

Common Beginner Situations Where a Test Helps

Most first-time users open a keyboard tester for one of a handful of reasons. Knowing which scenario you are in helps you decide what to do with the results once you have them.

You just bought a used or refurbished laptop or keyboard and want to confirm everything works before the return window closes. Run the full five-step pass and save a screenshot — if a key fails later, you have proof of the original fault.
A specific letter has started skipping, doubling, or not registering at all. Test that key first and watch the last-key panel. If it lights up but produces the wrong character, the issue is layout; if it does not light up at all, the hardware is the suspect.
You spilled liquid near the keys or crumbs have worked their way under the caps. Run the test, identify the affected keys, clean under each one, then click Reset and re-test the same area to confirm the fix.
You suspect ghosting during gaming. Hold common movement-and-action clusters and watch for dropped inputs.

What the Tester Will Not Catch

Honest limits are part of being a beginner-friendly tool. The tester only sees the keys your browser receives as keyboard events, which means a few categories are out of its reach by design. Some laptop Fn combinations, media keys, and certain lock keys are handled by the operating system or the keyboard's own firmware before the browser ever sees them — those may not register, and that is a browser and OS limitation rather than a fault in your hardware. If a key stays dark, the first step is to confirm the on-screen layout was actually focused when you pressed it; the next is to try the same key in a plain text field to see whether the operating system itself receives the press.

Quick Privacy and Trust Notes for First-Time Users

Beginners often worry about typing passwords or other sensitive text into a strange web page. You do not need to here: the Keyboard Tester listens for key events locally in your browser, never records or stores them, and never uploads anything to a server. When you close or refresh the page, every event is gone. Navigation keys like Space, Tab, Backspace, the arrows, and the function keys are caught only while the on-screen keyboard is focused, so your session will not get hijacked by the page scrolling or jumping away — and you can always click outside the layout or press Escape to leave. The tool works in any modern browser on Windows, macOS, Linux, and Chromebooks, with no install, no sign-up, and no extension required.