Home / Tools / Keyboard Test

Online keyboard tester and key checker

Use the live matrix to confirm which physical key codes reach this browser. It covers standard typing keys, modifiers, navigation, arrows and numpad codes, keeps a local tested-key map and shows recent non-repeat input. It does not diagnose switch electronics or certify a keyboard specification.

How to run a complete keyboard check

  1. Click or tap the tester area so the page has focus.
  2. Press every letter and number once, confirming each matching matrix key lights.
  3. Check Space, Enter, Backspace, Tab, Caps Lock and both Shift, Ctrl, Alt and Meta keys.
  4. Test arrows, Insert, Home, End, Page Up, Page Down and Delete.
  5. Check the numpad with Num Lock both on and off if your keyboard has one.
  6. Reset the session, then repeat any suspicious key at least five deliberate times.
  7. Compare a missing key in a plain text editor and another current browser.
  8. Use the focused diagnostics for multi-key rollover or unwanted double typing.

What the live keyboard readings mean

Keys tested counts distinct physical codes received in this session. Held now shows codes whose keydown has not yet been followed by keyup. Last input lists recent non-repeat presses so normal held-key auto-repeat does not flood the history.

The matrix is evidence of browser-visible input now. It is not a hardware scan, electrical continuity test, latency benchmark or proof that every application will interpret the key identically.

How to interpret keyboard test results

ObservationWhat it establishesUseful next step
Each expected key lights and appears in historyThis browser received the tested physical codes during the session.Repeat the keys that matter most in your normal application.
One key never appearsThe page did not receive that code; the cause could be hardware, connection, remapping, focus or interception.Retest after reset, then compare a text editor, another browser and another port or computer.
A different code lightsThe browser received a physical code different from the position you expected.Check keyboard layout, firmware layers and remapping software.
A key remains shown as heldThe page has not observed its keyup event in the current focus state.Release it, switch focus away and back, then repeat; blur clears held state to avoid stale results.
Keys work alone but fail in a combinationThe individual switches can report, but that combination needs a simultaneous-input check.Open the Ghosting & Rollover Test and repeat the exact combination.
One tap sometimes enters twiceThe broad matrix cannot distinguish normal repeat, software duplication and switch chatter reliably.Use the Keyboard Chatter Test with its event-timing and repeat separation.

Use PASS, WARNING and FAIL honestly

PASS — browser input observed: the intended key lights and repeated deliberate presses reach this browser. This qualifies the tested path now, not the keyboard for all software or future use.

WARNING — compare conditions: a special key is missing, the shown code differs, or a symptom changes with focus, layout, browser, port or connection mode.

FAIL — repeatable missing input: after focus and software checks, the same ordinary key repeatedly fails here and in another application or computer. That is strong troubleshooting evidence, but repair decisions still depend on the hardware and warranty.

Physical code versus typed character

This tester uses KeyboardEvent.code, which identifies the physical key position exposed by the browser. A QWERTY-position key can still produce another character under AZERTY, QWERTZ, Dvorak or a custom layout. Remapping tools and firmware layers can also change what an application receives.

Use a text editor when the problem is the resulting character. Use this matrix when the question is whether a physical browser key code arrives at all.

Browser and operating-system limits

  • System shortcuts can take priority over the webpage.
  • Function layers may be handled entirely inside keyboard firmware.
  • Media and vendor-specific keys may not expose standard codes.
  • On-screen mobile keyboards do not behave like physical keyboards.
  • Remote desktop and virtual-machine software can transform or intercept keys.
  • This page cannot measure switch bounce electrically or guarantee timing accuracy.

Before replacing a keyboard

  • Reconnect it and try a direct USB port instead of a hub.
  • Compare wired, wireless and Bluetooth modes where available.
  • Disable remapping or macro software temporarily.
  • Check the operating-system layout and accessibility settings.
  • Test another computer to see whether the symptom follows the keyboard.
  • Use the same repeated key or combination before and after cleaning or configuration changes.

Choose the focused keyboard diagnostic

Keyboard Testing GuideGhosting / Rollover / NKRO TestChatter & Double-Typing TestMouse TestTesting MethodologyPrivacy

The broad tester answers “which physical codes reach the browser?” The rollover tool answers “which simultaneous combination is missing?” The chatter tool answers “did one deliberate press create suspicious duplicate browser events?” Keeping those questions separate avoids false hardware conclusions.

Keyboard test FAQ

Does this keyboard test record what I type?

The diagnostic processes browser key events locally to light the matrix and build the current session history. It does not need to upload typed key activity to function.

Why does the tester show a key position or code instead of the character I expected?

The matrix uses physical KeyboardEvent.code values. Keyboard layout, remapping software and input-language settings can make the character produced in a text field differ from the physical code shown here.

Why is a function, media or shortcut key missing?

The operating system, browser, firmware or keyboard function layer can intercept special keys and shortcuts before the webpage receives an event.

Can this test prove that a keyboard switch has failed?

No. A repeatably missing browser event is troubleshooting evidence, but comparison in another application, browser, port or computer is needed before blaming the switch.

Can I test NKRO on this page?

This page is for broad per-key checking. Use the dedicated Ghosting & Rollover Test for repeatable combinations, separate simultaneous-key counts and careful 6KRO or NKRO interpretation.

What if a key works in another app but not in the browser?

A browser shortcut, extension, focus state or operating-system command may be consuming it. Retest an alternative key, another current browser and the same key in a simple text editor.

LOCAL INPUT: key events are processed in the browser for this diagnostic; the tool does not need to upload typed key activity to function.

All toolsPrivacyReport a problem