Keyboard Tester screenshot

Keyboard Tester

Show the key, physical code, modifier state and rollover of every key press in a focused field, without trapping Tab.

Privacy First
0 Runs
Updated 2026-11-22
Runs in your browser
Keyboard events only
No sign-up, no upload

Keyboard Tester

Show the key, physical code, modifier state and rollover of every key press in a focused field, without trapping Tab.

What the page does

The field listens for keydown and keyup events. Each press prints the key value, the physical code, the modifier flags and whether the browser marked the event as a repeat, and the panel counts the keys currently held.

Tab is deliberately not intercepted, so the page stays navigable. Space and the arrow keys are intercepted only while the field has focus, because they would otherwise scroll the page.

The page runs entirely in this browser tab; nothing is uploaded.

Click the field and press keys. The page shows the key value, the physical key code, which modifiers are down and whether the event is an autorepeat, and it keeps a count of the keys currently held at once.

The test reports what the browser delivered. A key that produces no event may be blocked by the operating system, the browser or a shortcut, and the page cannot tell which.

How to use Keyboard Tester

Click the field so it has focus. The first key press fills the large readout and the panel.

Hold several keys to see the rollover count rise. Release them and the count falls. Pause listening to let key presses pass without being recorded, and Reset to clear the readouts.

Why the code matters as much as the key

The key value is what the layout says the key produces: on a French layout, the same physical key reports "a" where a US layout reports "q". The code names the physical position instead, so a game binds to the code and a text field binds to the key.

Rollover is the number of keys the browser reported as held at the same time. It is a property of the browser, the operating system and the keyboard together, which is why the page prints the count rather than claiming a rating: a keyboard that claims n-key rollover and a browser that drops the sixth press produce a count of five.

What to Expect

Best for

  • Checking that every key registers
  • Seeing what a layout produces
  • Watching rollover on a gaming keyboard

Not ideal for

  • Certifying n-key rollover, which needs a hardware test
  • Testing a key that the operating system intercepts
  • Layout remapping, which this page does not do

What this tool keeps

  • The key, code and modifier flags of each event

What may need cleanup

  • Nothing: Reset clears the readouts

Common errors

  • Tab moves focus instead of being recorded, by design
  • A media key may produce no browser event at all

Example use cases

  • Press every key and check the readout changes
  • Compare the key and code on two layouts
  • Hold six keys and read the rollover count

Sample input

Shift held, then the A key pressed

Sample output

Key "A", code "KeyA", modifiers "Shift", held 2

Who this is for

  • Anyone checking a keyboard
  • Developers debugging key events

Frequently asked questions

Why does Tab not appear in the readout?

Because the page leaves Tab alone so a keyboard user can still move through the page. A test that trapped Tab would make the page itself unusable without a mouse.

Is the rollover count a keyboard specification?

No. It is the number of keys the browser reported as held at one moment, which depends on the keyboard, the operating system and the browser together. A hardware rollover test needs a dedicated device.

Why are space and the arrow keys intercepted?

Only while the field has focus, and only so they do not scroll the page away from the test. Every other key is untouched, and moving focus elsewhere removes the interception.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.