We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Test your keyboard for broken keys and ghosting issues. A free hardware diagnostic tool to check key functionality and responsiveness.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This online keyboard tester shows whether a physical key press reaches the browser. Press a key and its matching position on the on-screen ANSI-style keyboard is marked; a key held down is shown as active, and a key you have tested stays marked after you release it. Reset clears the marks and the most recent event so you can start another pass.
This is a check of browser-visible keyboard events, not an electrical or mechanical inspection. It is useful for a quick first pass when a key seems unresponsive, or for checking which positions the computer reports while you press them. A highlight means an event arrived; it does not prove the switch is reliable under every press or that the key will work in every application.
The latest event readout has four fields. key describes the key's meaning, such as a letter or a named action. That value can change with the active keyboard layout or modifier keys. code identifies a physical key position, which is why the virtual layout is matched by code rather than by the character printed on a key. location can distinguish positions such as left and right Shift or the numeric keypad. The legacy which field is shown as event information, but it is not the best field for identifying a physical key.
These field meanings follow the W3C UI Events specifications. The specifications support distinctions among key meaning, physical position, and location; they also document that some event values may vary or be unavailable depending on input and platform behavior. Checked September 29, 2026.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
The key grid is intended for a desktop-sized screen and a physical keyboard. Connect the keyboard you want to check, open the tester, and click the page once if needed to make sure it is ready to receive input. On a narrow mobile screen the visual grid is not displayed.
Start with a letter or number, then work through the main typing area, function row, navigation keys, arrow keys, and numeric keypad if those sections are present on your device. A key changes appearance while held and retains a tested mark after release. Skip keys your keyboard does not have.
The event panel updates with the most recent key, code, location, and which values. If a key does not highlight, press it again and compare nearby keys or its corresponding code. Use Reset Test to clear the marks and repeat with a fresh view.
For a modifier check, hold Shift, Ctrl, or Alt and tap another key. The visual state can show which positions generated events, while the event panel reports only the latest event rather than a sequence or combination summary.
Use cases
See how the tool fits into real work and everyday tasks.
Test that key several times and check other keys in the same area. If its event appears consistently here, the browser is receiving a press; continue by checking the application or system where the problem occurs. If it does not appear, reconnect the keyboard or try another port or device before concluding the key is physically damaged.
Walk across the keys and mark the positions that produce events. This can help you spot a key that needs a closer look soon after setup. The illustrated board is a common ANSI reference, so compare physical positions rather than expecting every regional layout or compact keyboard to look identical.
When you need to distinguish a left or right modifier, or a main-row number from the keypad, check the event's code and location fields as well as the highlight. These values describe the event the browser received and can help explain layout differences.
Q&A
Find concise answers to common questions and confusing cases.
No. It means this page did not show a matching browser event for that press. Try again, check that the page is ready to receive input, and compare other keys. Operating-system shortcuts, input methods, device mappings, or browser behavior can affect which events reach a page. Confirm a suspected hardware fault with another application or device test.
No. It highlights individual key events and shows the latest event fields; it does not count simultaneous key combinations or determine rollover capacity. A key appearing here should not be treated as proof of a specific anti-ghosting or N-key rollover capability.
The on-screen board is a US ANSI-style position reference. The event's key value represents meaning under the current layout and modifiers, while code represents a physical position. A non-US layout, remapping, or modifier can make those appear different.
Some keys are handled by the operating system or device before a browser event reaches the page. Fn combinations and special media keys are not guaranteed to be available to web pages, and this layout does not include every manufacturer-specific key. See the W3C event references above for the standards context.
Notes
Review scope, result limitations, and important precautions before use.
The page reports keyboard events received by the browser. It does not inspect the electrical switch, key feel, actuation force, chatter, response latency, rollover, or ghosting. A missed event alone cannot diagnose a failed switch, and a received event cannot certify that a key behaves correctly over time.
The pictured board follows a common ANSI arrangement and may not match your keycaps, regional layout, laptop, or compact keyboard. System-reserved shortcuts, input methods, virtual keyboards, Fn layers, and vendor-specific controls can change or prevent page-visible events. Use the marks as a preliminary observation and verify faults in the relevant application or with a separate hardware check.
Related
Discover related tools, collections, and available API capabilities.