Keyboard Test

Press physical keys to inspect what the browser receives.

The test reports KeyboardEvent data locally. key follows the active layout, while code identifies the physical key position.

The test reports KeyboardEvent data locally. key follows the active layout, while code identifies the physical key position.

Latest keyboard event

Waiting for input
Event
–
Key
–
Code
–
Location
–
Repeat
–
IME composition
–
Active modifiers and locks
–

Currently held keys

0

A key remains listed until a matching keyup event arrives. Focus changes clear the held-key state.

Unique keys or codes tested 0

Physical-key visualization

Start capture, then press keys on your physical keyboard. The visual layout is a generic PC reference and may not match your printed legends.

Capture is off

Press Escape while capture is active to record it and leave capture mode.

What this tool does

The keyboard test shows the KeyboardEvent values reported by the browser for each press and release.

It distinguishes the layout-dependent key value from the physical-position code and tracks simultaneous held keys.

How to use the tool

  1. Select Start key capture or click the keyboard area.
  2. Press and release the physical keys you want to test while the capture area remains focused.
  3. Compare key, code, location, repeat, composition and modifier information in the event panel.
  4. Press Escape to leave capture mode or reset the test before another run.

Useful applications

  • Check whether individual keys produce browser events.
  • Compare left, right and numpad variants of modifier or navigation keys.
  • Inspect keyboard layouts, dead keys and input-method behavior during web development.
  • Observe simultaneous key events as a practical browser-level rollover check.

Notes and limitations

  • Only keys delivered to the page can be shown; the browser or operating system may reserve shortcuts and media keys.
  • key describes the interpreted meaning for the active layout, while code normally describes a physical key position.
  • IME, dead-key and composition workflows can suppress or alter events, and virtual keyboards may provide limited code data.
  • A missing keyup can also result from focus loss, so this tool cannot prove the physical cause of a stuck-key fault.

Frequently asked questions

What is the difference between key and code?

key reflects the character or action produced by the active layout. code identifies the physical key position and is usually layout-independent.

Why is a key or shortcut missing?

The browser, operating system, firmware or another application may capture it before the page receives an event.

Can this confirm that a key is physically stuck?

No. It can reveal a keydown without a matching keyup while the page has focus, but focus loss or browser behavior can produce the same symptom.

Is this a definitive N-key rollover test?

No. It shows simultaneous events delivered through the browser and operating system, which is useful for comparison but not a certified hardware measurement.

Is typed input uploaded?

No. Event values and test state are processed only in the browser by this tool.

More tools in Utilities

View all tools in Utilities