A key test is a quick way to check whether every key on your keyboard actually works by pressing each one and watching for a matching response. Instead of guessing why a letter never appears on screen or which shortcut silently dropped, you can run a browser-based key test that lights up an on-screen button every time you press the corresponding physical key. After running your fingers across the whole board, the keys that never lit up are your suspects — the dead, dirty, or failing ones. The same test can also expose sticky keys that stay lit after you release them, chattering keys that fire repeatedly, and ghosting problems where certain combinations of keys pressed together cause some presses to be silently dropped. Each press reports three pieces of information — the key value, the physical code, and the older numeric keyCode — so you can see exactly what your operating system reports. Everything happens locally in the browser, so nothing you type is uploaded to any server.
What a Browser Key Test Checks
A free keyboard tester displays a full QWERTY layout on screen and listens for keyboard events as you type on your physical keyboard. Every press is mapped to a button on that virtual board, so you get immediate visual confirmation that a particular key is reaching your computer. Held keys glow while you continue to hold them down, and each key you press leaves a permanent mark showing it has been tested, so by the end of a pass you can see at a glance which keys were reached and which were not.
The on-screen keyboard only listens while it is focused, which prevents keys like Space, Tab, Backspace, arrows, and the function keys from scrolling the page or jumping focus away. You can tab into the virtual board to start capturing presses, or click anywhere on it, and you can press Escape or click outside when you want to stop. The Keyboard Tester handles this whole workflow in one page, so you do not need to install anything, create an account, or load an extension. It works on Windows, macOS, Linux, and Chromebooks in any modern browser.
How to Run a Key Test Online
A practical key test takes only a few minutes. Work through these steps in order for a clean, repeatable result.
- Click or tab into the on-screen keyboard so it becomes active and starts capturing your key presses.
- 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.
- Read the last-key panel to check the key, code, and keyCode values reported for the key you just pressed.
- Look for any on-screen keys that never light up after you have pressed them — those are likely dead or failing keys.
- Click Reset to clear all tested marks and the last-key readout when you want to run a fresh test pass.
That single pass covers every standard key. If you want to go deeper, repeat the test with combinations held down — Shift plus a letter, Ctrl plus a number, two movement keys together — to expose rollover and ghosting limits in your keyboard or its controller.
Reading the key, code, and keyCode Values
Each press the browser reports carries three identifiers. They look similar but mean different things, and a key test surfaces all three so you can tell whether a problem is hardware, layout, or software.
| Identifier | What it shows | Example | Stability across layouts |
|---|---|---|---|
| key | The character or named key your layout produces | a, Enter, ArrowUp | Changes with language layout and modifiers |
| code | The physical position of the key on the board | KeyA, Space, ArrowLeft | Stays the same across layouts |
| keyCode | An older numeric identifier kept for compatibility | 65 for A, 32 for Space | Numeric and layout-independent |
When a key produces a different character than the one printed on the cap — for example typing an A on a keyboard set to a Cyrillic layout — the key value changes but the code stays KeyA. That single comparison usually tells you the hardware is fine and the layout or remapping is the cause. The keyCode field is most useful when you are remapping keys in software or troubleshooting older games that still rely on numeric IDs.
Problems a Key Test Can Catch
A focused test pass surfaces the four most common keyboard faults. Each one looks different on screen, which is what makes a visual key test more useful than simply typing into a text field.
| Problem | What you see during the test | Most likely cause |
|---|---|---|
| Dead key | The on-screen button never lights up, even after multiple presses | Dirty contact, broken membrane, loose cable, or full switch failure |
| Sticky key | The on-screen button stays highlighted after you release the physical key | Debris under the keycap, worn switch, or liquid residue |
| Chattering | A single tap produces several on-screen flashes in quick succession | Failing switch contacts, often a sign the key needs replacement |
| Ghosting | A combination of keys leaves some buttons dark even though each key works alone | Hardware rollover limit, especially on older or budget keyboards |
Holding two or three movement keys at once is the fastest way to find ghosting, because movement keys are the most common combination that exposes it in games. If one of the held keys silently disappears while the others stay lit, your keyboard cannot register that combination as a true simultaneous press.
Privacy and Safety During a Browser Key Test
Because the tool listens for key events directly in your browser, the question of what happens to what you type matters. The answer for the Keyboard Tester is straightforward: nothing leaves your device. There is no keystroke logging, no background upload, and no server-side recording of which keys you pressed. When you close or refresh the page, the session is gone.
This is also why it is safe to test even when you have sensitive text on screen. The page only listens while the on-screen keyboard is focused, and it does not capture input into other fields, so pressing keys during a test does not type anything into the page around it. You can run the test on a shared computer, a borrowed laptop, or a refurbished machine you have not yet trusted with personal data, and the only thing that changes is whether the keys on the physical keyboard work.
Tips for Getting Reliable Results From a Key Test
A few habits make the difference between a clean pass and a confusing one.
First, always start by clicking or tabbing into the on-screen keyboard. The tool only listens while it has focus, so if you start typing before the virtual board is active, the first few presses will go nowhere and may scroll the page instead.
Second, work through the keys in a consistent order, row by row, so you do not accidentally skip a key and miss a fault. Top row, then home row, then bottom row, then modifiers and arrows, then the function keys, is a pattern that covers most layouts without doubling back.
Third, run a second pass with common modifiers held down. Hold Shift and tap each letter to confirm the shifted character registers. Hold Ctrl or Alt and tap common shortcuts you actually use to confirm those combinations reach the browser.
Fourth, when you find a suspect, do not stop at the first failure. Press the key five or six times in a row, slowly. A flaky key may register once and then fail, and a sticky key may release properly after a few attempts. Note the pattern, not just the single failure.
Finally, click Reset between major passes — once after the bare-key sweep, again after the modifier sweep, and a third time after the combination sweep. A clean reset prevents an earlier success from masking a later fault on the same key.
For a deeper look, see Keyboard Tester Accuracy: How to Read the Results Right.
For a deeper look, see Try This Keyboard Tester Alternative in Your Browser.