← Back to tools

Keyboard tester

Test keyboard keys and detect stuck keys.

Everything happens locally in your browser. Nothing is uploaded.
0

Total Key Presses

0

Unique Keys Pressed

0:00

Session Duration

0

Currently Pressed

Controls
Manage your keyboard testing session
Virtual Keyboard
Press keys on your physical keyboard to see them light up
Escape
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
F11
F12
BACKQUOTE
DIGIT1
DIGIT2
DIGIT3
DIGIT4
DIGIT5
DIGIT6
DIGIT7
DIGIT8
DIGIT9
DIGIT0
MINUS
EQUAL
Backspace
Tab
KEYQ
KEYW
KEYE
KEYR
KEYT
KEYY
KEYU
KEYI
KEYO
KEYP
BRACKETLEFT
BRACKETRIGHT
BACKSLASH
Caps Lock
KEYA
KEYS
KEYD
KEYF
KEYG
KEYH
KEYJ
KEYK
KEYL
SEMICOLON
QUOTE
Enter
Left Shift
KEYZ
KEYX
KEYC
KEYV
KEYB
KEYN
KEYM
COMMA
PERIOD
SLASH
Right Shift
Left Ctrl
Left Meta
Left Alt
Space
Right Alt
Right Meta
Right Ctrl
Key Press History
Recent key presses and releases (last 50 events)

No key presses yet. Start typing to see the history!

A practical guide to Keyboard tester

Keyboard Tester displays key, code, modifier, and event behavior as you press physical keys. It helps diagnose layouts, stuck modifiers, shortcut handling, and browser keyboard events.

Example: diagnose a shortcut mismatch

Press the intended combination, record key and code values, compare modifier state, and repeat with another keyboard layout.

Task-specific steps

  1. 1

    Focus the tester and press one ordinary key to confirm the page is receiving keyboard events.

  2. 2

    Test the affected key or combination while observing key, code, modifier state, repetition, and release behavior.

  3. 3

    Compare results with another browser, layout, or keyboard to separate hardware, operating-system, and application causes.

Options that affect the result

  • Key reports the interpreted character while code identifies the physical keyboard position.
  • Modifier and repeat states expose shortcuts, held keys, and auto-repeat behavior.

Limitations to know first

  • The browser and operating system reserve some shortcuts, so the page never receives every possible combination.
  • A browser event test cannot fully diagnose firmware, ghosting, rollover, accessibility remapping, or hardware electrical faults.

Questions specific to this task

Why are key and code different?

Key reflects the active layout and modifier result; code identifies a physical position such as KeyQ regardless of the printed character.

Why does a shortcut not appear?

The operating system or browser may intercept it before page JavaScript receives an event.