Keyboard Tester

The visual keyboard shows QWERTY by default with layout options, but detection is layout-independent — it reports both the physical key position (event.code) and the character your layout produces (event.key), which is exactly what you need to diagnose a layout problem.

A few are intercepted by the operating system or the browser and never reach the page: the Windows or Command key alone, some function-key combinations, and screenshot or media keys. They are marked as untestable rather than shown as failing.

Partly. Holding several keys at once shows how many register simultaneously, which is how you find the rollover limit on a membrane keyboard.

The hardware is fine. If the browser sees the press, the switch, the cable and the driver have all done their job, so the fault lies in a shortcut, a remapping or a held modifier in the other program. Check whether Alt, Ctrl or a function lock is stuck on.

Yes. Anything the operating system presents as a keyboard — USB, Bluetooth or a laptop built-in — sends the same events to the page. What it cannot see are keys handled entirely inside the keyboard's own firmware, such as layer or macro keys that never send a standard code.

Yes. There is no account, no daily cap, no file-size tier and no watermark, because there is no server cost to recover. The site is funded by clearly disclosed partner recommendations on the Partners page, never by metering the tools.

No. Everything is processed by JavaScript running in your browser, on your device. You can verify it: open your browser's developer tools, switch to the Network tab, and use the tool. You will see no request carrying your data — because there is nowhere for it to go.