A keyboard tester on Windows checks which physical keys produce browser-visible key events, making it possible to spot dead, unresponsive, sticky, or ghosting keys without installing software.
Open the free Keyboard Tester in a modern browser on a Windows desktop or laptop, then focus its on-screen keyboard. It works with no installation, sign-up, or extension. The on-screen QWERTY layout lights the matching button when the browser reports a press, and a last-key panel shows details for the latest event.

What the Windows keyboard test actually checks
Each detected press leaves a mark on the matching on-screen button for the current test run. After a full-board sweep, buttons you never triggered remain visually distinct, while held keys glow during the hold. That makes the display useful for checking ordinary response, a key that stays active after release, and repeated firing from one tap. The last-key panel adds the operating system’s reported key, code, and keyCode values, so the test covers both visible response and the event details an application receives.
The results describe what reaches the browser. A missing event can indicate a failed key, but it can also result from focus or interception by Windows or the browser. The test is therefore most useful when you compare its result with a plain text field and with the same key tested individually and in combinations.
Run a complete keyboard test on Windows
Follow this sequence for a clear individual-key pass followed by a combination check:
- Activate the on-screen keyboard. Click it or tab into it so it has focus. Detection runs only while the on-screen keyboard is active, which means an unlit key does not automatically indicate a hardware fault.
- Press each physical key one at a time. Begin with letters, numbers, and symbols, then test modifiers such as Shift, Ctrl, Alt, and Meta, the arrow keys, Space, Tab, Enter, Backspace, Escape, and function keys. Watch the matching on-screen button light up and remain marked as tested.
- Read the last-key panel. Check the key value, code value, and keyCode reported for the key you just pressed. This is especially useful when a character is wrong, a game does not recognize a key, or you need precise details for a support request.
- Test rollover and ghosting symptoms. Hold several keys together and observe which on-screen buttons register. A key that works alone but disappears in a combination may point to a rollover or ghosting issue. Repeat the combination because an operating-system shortcut can also prevent the browser from receiving every press.
- Review every key that stayed dark. After the individual sweep, any physical key you pressed but whose on-screen button never lit is a suspect. Focus the tester again and compare that key in a plain text field before treating it as likely dead or failing.
- Reset for a fresh pass. Click Reset to clear all tested marks and the last-key readout. A clean run is useful after changing a layout, cleaning under a troublesome key, or beginning a second troubleshooting session.
Read the key, code, and keyCode panel
The three values in the last-key panel describe different parts of a keyboard event. Reading them together prevents a layout or remapping problem from being mistaken for broken hardware.
| Readout | What it represents | Example or behavior |
|---|---|---|
| key | The character or name produced by the press. | Values such as a, Enter, or ArrowUp can change with modifiers and the active layout. |
| code | The physical position of the key on the keyboard. | Values such as KeyA or Space stay the same across language layouts. |
| keyCode | An older numeric event identifier used by some software and games. | The displayed value is useful when checking compatibility with an application that still relies on the legacy identifier. |
If Windows uses a different language layout or an active remapping, the key value may differ from the keycap while the code continues to identify the same physical position. That is evidence of a mapping difference, not necessarily a failed switch. When documenting a game or application problem, record all three values because the affected program may depend on the character, physical code, or legacy keyCode.
Recognize dead, sticky, and ghosting keys
Use the pattern on the screen and in the last-key panel to narrow down a fault. The display provides symptoms rather than a complete physical diagnosis, so each observation has a sensible next check.
| What you see | Likely explanation | Next check |
|---|---|---|
| A pressed key never lights | It may be dead, dirty, disconnected, or intercepted before the browser receives it. | Restore focus, then compare the key in a plain text field. |
| A key stays actively highlighted after release | This is a sticky or stuck-key symptom associated with the key mechanism. | Clean it or arrange repair if the behavior continues. |
| One tap produces repeated events | The switch may be chattering. | Retest the key alone and note whether the repeated events continue. |
| The produced character is wrong | The active layout or remapping is a more likely cause than hardware failure. | Check the Windows layout and remapping, then compare key and code. |
| Keys disappear only when held together | There may be a rollover or ghosting issue, or the browser and operating system did not receive every event. | Test each key alone and then repeat the same combination. |
Before declaring a key dead, focus the on-screen keyboard again and press it once. If it appears in a plain text field but not in the tester, focus or a shortcut is more likely responsible than a failed key. If it fails by itself in both places, that is a stronger dead or failing-key signal. For an intermittent or combination problem, write down the exact key, its three readout values, its single-key result, and the combination that fails. The visible marks and last-key readout can be cleared, so keep a manual note before contacting support or using the result for a warranty claim.
Account for Windows and browser limits
Some keyboard problems look like hardware failures even when the physical key is working. Keep these browser-level limitations in mind during a Windows test:
- Expect browser-visible keys. The tester detects standard keyboard events, including letters, numbers, symbols, function keys, modifiers, arrows, Space, Tab, Enter, Backspace, and Escape. Some laptop Fn combinations, media keys, and certain lock keys are handled by the operating system or hardware before the browser sees them, so they may not register.
- Account for global shortcuts. A Windows or browser shortcut may consume an input before the tester receives it. If a combination is intercepted, test its constituent keys individually to confirm that each one works.
- Use a plain text field as a control. Pressing the same key in a basic text field shows whether Windows and the browser can deliver that event outside the tester. This is a useful comparison when focus or shortcut behavior is unclear.
- Keep focus during navigation-key tests. While the on-screen keyboard is focused, keys that could otherwise scroll or navigate the page, including Space, Tab, Backspace, arrow keys, and function keys, are held in place. You can click away or press Escape to leave.
- Read combination results at the browser level. Holding several keys reveals which events the browser accepts, which is useful for spotting rollover or ghosting symptoms. It is not a formal polling-rate or keyboard-latency benchmark.
Keep the test local and understand its scope
All key detection runs locally in the browser. The page never records, stores, saves, or transmits what you type, and there is no keystroke logging or network upload. Closing or refreshing the page removes the test state, while Reset clears the tested marks and last-key readout without ending the session.
The tester reveals which key events reached the browser, not why a signal was missing. It can distinguish a key that never registers from one that produces an incorrect value or fails only in a combination, but resolving the underlying cause may still require a layout check, cleaning, or repair. On Windows, combine the on-screen results with a plain-text comparison and record specific symptoms before seeking support.
A complete Windows pass combines focused individual-key checks, last-key values, combination tests, and a plain-text comparison before Reset starts the next clean run.