Explore OGadget
Your everyday workbench

Keyboard Tester

See which key inputs register in your browser.

Available tool · Local processing
Keyboard input workbenchPhysical keys · Browser events
Click the keyboard area, then press physical keys.
UNIQUE KEYS0
LAST KEY—
INPUT EVENTS0

Ready. This is a visual US-style layout; other keyboard layouts can report different characters.

What this tester actually measures.

The tester listens for keydown and keyup events while its keyboard area has focus. It uses KeyboardEvent.code for the visual position and KeyboardEvent.key for the reported input. It does not measure electrical switch health, input latency, or polling rate. Browser and operating-system shortcuts remain available; Tab moves focus out of the tester.

Practical guide

Keyboard Tester: how to use the result

The keyboard tester shows the key events your browser receives while the test area has focus. It can help you describe a key that appears unresponsive, compare two keyboards or check whether a combination reaches a web application. The visual layout is a reference for positions; it does not change the layout configured in your operating system.

How to use this workspace

  1. Focus the keyboard test area before pressing keys. Start with individual letters and numbers so the event display is easy to follow.
  2. Press and release modifier keys, then try the combinations relevant to your task. Observe both the reported key and the highlighted position.
  3. Reset between passes. Use Tab to leave the test area and avoid trapping your normal keyboard navigation.

A practical example

On a non-US layout, the printed character and physical position may differ from the visual reference. The event can still be valid: KeyboardEvent.code represents a physical-position convention, while KeyboardEvent.key reports the interpreted input. Compare both values when explaining a layout problem.

How to interpret your result

A highlighted key confirms that an event reached this page. A missing event can mean the test lacked focus or a shortcut was handled earlier by the browser or operating system. It does not automatically establish a damaged switch or a limitation of the keyboard matrix.

Common mistakes and limits

This test does not measure polling rate, electrical debounce, wireless latency or switch force. Software keyboards on phones do not necessarily produce the same event sequence as physical keyboards. Use a connected physical keyboard for that comparison.

Make the comparison repeatable

Test one condition at a time and note which device, browser and connection you used. If an unexpected result appears, repeat the same action before changing settings. A second browser or another known-working peripheral can help separate an application or permission problem from a device problem. Keep those comparisons descriptive: this page observes what reaches the browser and does not have access to a laboratory measurement of the hardware.

Frequently asked questions

Why do some system keys never appear?

The operating system or browser can reserve shortcuts and special keys. Events intercepted there may not be exposed to the page.

Can this prove that my keyboard supports every key combination?

No. You can observe specific combinations that reach this browser, but a web page cannot certify every hardware and software condition.

Continue with related tools