Devices · Made a little simpler

Keyboard test

Test physical keys, left/right modifiers, navigation keys, and the numpad. See simultaneous-key counts, lock states, repeats, and a downloadable report.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device
Device idle

Start the test, then press keys and combinations.

Nothing is captured until you start.0 distinct physical codes received0 held now · maximum 0 together
CapsLock: Not observedNumLock: Not observedScrollLock: Not observed

Layouts show physical codes, not a language map. Location 1/2 identifies left/right modifiers; 3 identifies the numpad. Lock states are the last browser-reported values. Browser and operating-system shortcuts may never reach this page.

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

Keyboard test: how to use it

  1. Click Start keyboard test to focus the test area.
  2. Press keys and combinations, then inspect the received event details.
  3. Click Stop or move focus away to end the test.

Limits and notes

ANSI/ISO diagrams represent physical codes, not a language layout. Lock states are last observed event values. Browsers and operating systems reserve some shortcuts; Fn and hardware keys may not produce events. This cannot prove that every switch is physically healthy. Reports aggregate only events inside the focused test area.

How your privacy works →

Keyboard test: common questions

Why is Fn not lighting up?

Many keyboards handle Fn internally and never send it to the browser. Its absence here does not establish a hardware fault.

Are keystrokes tracked elsewhere?

No. Key listeners are limited to the active test area. Events are not sent to analytics or automatically saved to disk. A report is saved only when you choose to download it.

Why do some keyboard keys not appear?

The page only sees events delivered to its active focused area. OS or browser shortcuts, Fn handling, missing browser codes and a code absent from the selected diagram can explain a missing highlight. Inspect the received-keys table before treating the result as a hardware fault.

Does this keyboard test verify NKRO or ghosting?

No. It reports browser-received codes and their observed held set. Missing events, focus, OS shortcuts, fallback-code grouping and the input environment can affect the count. Controlled hardware testing is needed for a physical NKRO or ghosting conclusion.

Tool guides