Pressed, Tested and Untested Keys
Teal keys are currently held. Violet keys have registered at least one keydown event. Dark keys have not been registered during the current test. An untested key is not automatically a defective key.
Test every key on your computer keyboard in real time. See pressed keys light up, check multi-key combinations, track key repeats and inspect browser keyboard events in one professional testing workspace.
Click the test surface, then press your physical keyboard keys. Purple means tested; teal means currently held.
Software keyboards may send character input without individual physical key codes. Use an attached hardware keyboard for a full key test.
Browser limitation: Some system shortcuts, Fn combinations, brightness controls and media buttons may be intercepted before the website receives them. A missing browser event alone does not confirm broken hardware.
Understand which keys are currently active and how the browser reports each press.
Try common gaming and typing combinations. The test confirms only the keys whose browser events are received.
Rollover describes how many simultaneous key presses a keyboard can register. The live counter shows the maximum number of distinct keydown events observed together in this browser session.
If a combination fails, retry it in another app or native tester. Browser shortcuts, operating-system handling and keyboard matrix behavior can all affect the result.
View keydown and keyup messages, browser key codes, repeat flags and event timing.
| Time | Event | Key | Physical code | Location | Repeat |
|---|---|---|---|---|---|
| Focus the keyboard test area and press a key to display events. | |||||
Showing 0 events. Up to 120 recent events are kept in memory.
A complete test takes only a few minutes. Start with the letters and numbers, then check the larger keys, function row, navigation cluster and numeric keypad if available.
Gaming often requires several keys at once. A key combination may feel normal during typing yet behave differently when movement and action keys are held together.
Teal keys are currently held. Violet keys have registered at least one keydown event. Dark keys have not been registered during the current test. An untested key is not automatically a defective key.
The code value identifies a physical key position, while key reflects the interpreted value in the active keyboard layout. This is why the same position can display different characters on QWERTY and AZERTY keyboards.
The rapid-repeat indicator flags a second distinct press shortly after a release. Ordinary fast typing, accessibility settings and browser timing can create similar results. This is not a definitive mechanical-switch diagnosis.
Control, Alt/Option and Windows/Command labels vary between platforms. Some built-in laptop function keys and operating-system combinations never produce website-accessible events.
Connect your USB or Bluetooth keyboard through the operating system first. Browsers do not provide the brand, serial number or connection type through ordinary keyboard events. This tool tests input events, not device identity.
The tester only processes keyboard events while its capture area is focused. Event history stays in the current browser page until cleared or closed; this widget does not send event data to a server. Avoid entering passwords or private text while testing.
Click Start Testing and make sure the capture area has focus. Try the key in another app. Keyboard language, browser interception and physical issues can all affect the result.
Fn is usually handled internally by the keyboard and often never reaches the browser. Brightness, volume and system shortcuts may be reserved by your OS.
Check their physical codes. Left and right Shift, Ctrl and Alt can usually be distinguished by code and location, when the browser provides them.
Return focus to the capture area, release the key and try again. Switching tabs or changing focus can interrupt keyup events; the tester releases held states when focus is lost.
The visual tester is compatible with current desktop browsers that expose keyboard events, including Chrome, Edge, Firefox and Safari. Actual key detection varies with your operating system, keyboard layout and browser restrictions. On Android tablets, iPads and phones, attach a physical keyboard for reliable hardware key testing. On-screen keyboards may emit different or incomplete key codes.
Click Start Testing, press each physical key and watch the visual keyboard. Keys change color when the browser detects them. You can also inspect the event history and reset the session at any time.
It helps identify keys that are not generating expected browser input, but a missing event is not proof of damage. Retest in another app or operating system before determining whether the keyboard needs repair.
Yes. Choose a visual layout to match the general key arrangement. Exact manufacturer-specific layouts, ISO Enter keys and custom programmable layers may differ from this US ANSI reference.
You can check which simultaneously held keys produce observable browser events and track the largest detected chord. Browser software cannot independently certify NKRO, because keys suppressed by hardware or the OS may never be delivered.
The tester flags repeated keydown cycles occurring within a short period after a release. It is a timing clue only, not a validated measurement of mechanical bounce or switch health.
Usually not. Many Fn combinations are processed within keyboard firmware. Operating systems and browsers may reserve shortcuts such as Alt+Tab, Command+Tab and function keys.
The tool maps physical key positions and offers simplified QWERTY, AZERTY and QWERTZ display labels. Your active OS keyboard layout determines the actual key value received by the browser.
The page is responsive, and you can focus the mobile text field to open an on-screen keyboard. Software keyboards are not equivalent to physical keyboards; connect a hardware keyboard for meaningful switch testing.
The widget logs keydown and keyup events only while the test area or dedicated mobile test field is focused. The log is kept locally in page memory and is not uploaded by the widget. You can clear it whenever you like.
Not reliably with normal keyboard events. Browser event timing includes scheduling and OS delays, so it is not an accurate direct measurement of hardware polling rate or input-to-display latency.
Keyboard Tester by Gamepad Tester ยท Free browser-based keyboard testing ยท No installation needed
Sign in to your account