A keyboard input test is a quick check that confirms each key on your keyboard actually registers when pressed, using your browser's keyboard event API to map every physical press to a specific character, physical position, and numeric code. To run one, open a free browser-based keyboard tester, focus the on-screen keyboard, then press each physical key one at a time while watching for the matching button to light up on the display. Held keys glow while you hold them, and every successful press stays marked as tested, so when you finish running your fingers across the whole board you can see at a glance which keys never lit up. Those unlit keys are your dead-key suspects. A key that stays lit after you release it is sticky or chattering, and a key that produces the wrong character points to a layout or remapping problem rather than broken hardware. The whole test takes a couple of minutes and requires nothing more than a working browser tab, with no install, no sign-up, and no extension required.
What the Tool Detects During a Test
Every time you press a key, your operating system sends a keyboard event to the focused application, and a browser-based tester listens for those events and displays them in three forms. The on-screen QWERTY layout shows where the key lives physically, so you can immediately see whether the letter you pressed matches the letter that lit up. A side panel reports the same press as three values: the key value, the code value, and the keyCode. Together these confirm not only that the key fired but also how your operating system, your language layout, and any remapping software are interpreting it.
Beyond single keys, a good test also covers held keys, simultaneous presses, and the trickier corners of the keyboard like the function row, the modifier cluster, and the navigation block. Because every successful press stays marked on the layout, the test doubles as a visual checklist: anything you forgot to press stays dark, anything that misbehaved shows the wrong color or stays lit longer than it should, and the readout panel lets you confirm that the key the hardware produced is the key the software saw. For developers and gamers this is especially useful, because remapping tools, macro software, and game engines can disagree with the browser about what a given press actually means.
Common Reasons to Run a Keyboard Test
Keyboard testing is not just for people whose keys have stopped working. A few situations where a quick browser-based pass pays off:
- Buying used or refurbished hardware. A two-minute run across every key gives you proof of a fully functional keyboard before a return window closes.
- A specific letter has started skipping or doubling. You need an objective record of the fault before contacting support or filing a warranty claim.
- Liquid or debris under the keys. After a spill, or when crumbs work their way under the keycaps, a test pinpoints exactly which switches feel off.
- Gaming rollover and ghosting. Holding several keys at once reveals combinations that silently drop, which is common on older or membrane keyboards.
- After cleaning or a switch swap. A fresh pass confirms that the repair worked and that no new faults were introduced.
Most of these checks can be done in under five minutes, and the result is a record you can screenshot or write down for support. Because every press stays marked on the layout, you do not have to remember which keys you already tested: the tester holds the visual state for you until you click Reset.
How to Test Every Key on Your Keyboard
This walk-through uses the free Keyboard Tester tool, which runs in any modern browser and covers the full process from first press to a clean reset.
- 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, since 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.
For a fuller pass, work the keyboard in zones: number row, top letters, home row, bottom row, modifiers, arrows, function keys, then the navigation cluster. Hold Shift, Ctrl, Alt, and Meta briefly so each modifier registers as tested too. If you are chasing a ghosting problem, press three or four adjacent keys at once and watch the layout to see whether every press lights up.
Understanding the key, code, and keyCode Values
The three values shown for each press describe different layers of the same event, and reading them together is the fastest way to spot remapping or layout issues.
| Value | What it represents | Example | Behavior |
|---|---|---|---|
| key | The character or name the key produces | a, Enter, ArrowUp | Changes with language layout and modifier keys |
| code | The physical position of the key on the board | KeyA, Space, ArrowUp | Stays the same across all layouts |
| keyCode | An older numeric identifier | A specific number tied to each key | Kept for compatibility with older software and games |
If pressing the physical A key shows key a, code KeyA, and the matching numeric keyCode, your keyboard, layout, and software all agree. If the key value shows something different, like q, your layout is set to a non-QWERTY language and the hardware is fine. If the code value is wrong, the event came from a different physical key than you expected, which can happen with remapping tools or non-standard layouts. The keyCode value is the easiest to misuse because modern browsers keep it around mostly for compatibility with older applications and games, but the W3C KeyboardEvent specification treats it as deprecated, which is one reason the tester surfaces all three values side by side rather than picking a favorite.
Spotting Dead, Sticky, and Ghosting Keys
The on-screen layout tells a story once you know what to look for. The table below maps the visual symptom to what is most likely happening underneath.
| What you see | Most likely cause | Direction to take |
|---|---|---|
| Key never lights up | Dead, disconnected, or dirty switch | Clean under the keycap, reseat the cable, or replace the keyboard |
| Key stays lit after release | Sticky or chattering switch | Clean under the cap and check for debris; consider a switch replacement |
| Key fires repeatedly on a single tap | Mechanical bounce or failing switch | Test in a plain text field to compare, then service the switch |
| Combination of keys drops one press | Ghosting or limited rollover | Avoid that combination for gaming, or upgrade to an n-key rollover board |
| Key produces the wrong character | Layout or remapping misconfiguration | Check the OS language layout and any remapping software before suspecting hardware |
Always retest after any fix. A press that lights up only when you tap it firmly is a switch on its way out, and confirming the fault on a second pass is what turns a hunch into something you can send to support. If a key passes the single-press test but drops out when neighbors are held, the problem is electrical rather than mechanical, and the answer is a keyboard with higher rollover rather than any cleaning. Sticky and chattering switches can also mask themselves as ghosting, so isolating single keys first before testing multi-key combinations keeps your diagnosis honest.
Privacy, Browser Support, and Operating System Limits
Keyboard detection runs entirely in your browser tab. The tool never records, stores, saves, or transmits what you type, and there is no keystroke logging or network upload, so closing or refreshing the page wipes everything. That makes it safe to test even in situations where passwords or sensitive text would normally be a concern, because nothing you press leaves your device.
Compatibility is wide. The tool works on desktops and laptops across Windows, macOS, Linux, and Chromebooks in any modern browser, with no install and no extension required. A small set of keys are handled by the operating system or hardware before the browser sees them, including some laptop Fn combinations, media keys, and certain lock keys, so those may not register. That is a browser and OS limitation rather than a fault in your keyboard, and the same goes for keys that other applications intercept through global shortcuts. If you need a test that runs before the operating system loads at all, you can also test your keyboard in BIOS without special software to confirm the hardware itself.
To keep the session clean, the on-screen keyboard holds potentially disruptive keys like Space, Tab, Backspace, the arrow keys, and the function keys in place only while it is focused, so the page does not jump around while you test. Clicking away or pressing Escape releases that focus when you want to leave. For the cleanest run, close other apps that might grab global shortcuts, leave the tester tab focused throughout the pass, and avoid typing into any other field on the page until you are ready to reset.