gizmobench

Keyboard Tester

Press any key and watch it light up on the map. Every key you have tested stays marked, so a dead key is simply the one that never comes on. Keys are matched by physical position rather than by letter, which means a non-US layout is read correctly instead of lighting the wrong cap, and the readout adds the three things a broken keyboard usually fails on: the exact code your board sent, how many keys it can report at once, and how fast it auto-repeats. It runs in the page, with nothing installed and nothing stored.

Press any key. Every key you test stays lit, so a dead key is the one that never comes on.Ready. Press a key or click the board, and browser shortcuts will be held back while you test.
Layout
Numpad
Keys tested
0 / 87
Repeat rate
hold a key to measure
Rollover
nothing held yet

Keys are matched by position, not by letter: the code beside each press is what your keyboard sent, whatever character your software layout turned it into. Nothing is uploaded and nothing is stored.

  • Last keywhat the browser received
    nothing pressed yet
  • Modifiers heldread from the same event
    none
  • Rollovermost keys reported down at the same moment
    nothing held yet
  • Not yet pressedthe keys still dark on the map
    Escape F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 Print Screen Scroll Lock Pause Backtick 1 and 69 more

While the cursor is in this box nothing is held back, so Tab, Space and Backspace behave normally. Keys are still recorded on the map above.

What this page holds back, and what it cannot

A web page may suppress some default actions and not others. These are the ones this tool suppresses while it has your keyboard, and the ones no page is allowed to touch. Nothing is suppressed while the cursor is in a text box or on a button.

KeysWhat they normally doIn this tool
F1 to F12Help, find, refresh and full screen. Held back here so F5 does not reload the page and F11 does not swallow the board halfway through a test.Held back
TabMoves focus to the next control. Held back so a Tab press lands on the map. Shift with Tab is always let through, so focus can move back out, and Esc releases the keyboard entirely.Held back
SpaceScrolls the page down. Held back so the board does not jump off screen every time you test the space bar.Held back
BackspaceUsed to mean back a page, and still does in some builds. Held back so a test cannot navigate away from itself.Held back
Slash and apostropheOpen quick find in Firefox. Held back so testing them does not drop a search bar over the page.Held back
Meta + WCloses the tab. The browser acts on it before the page is told, so no page can stop it.Cannot be held back
Meta + TOpens a new tab. Reserved by the browser in the same way.Cannot be held back
Alt + Tab and Meta + TabSwitch windows. The operating system takes these before the browser sees them.Cannot be held back
Ctrl + Alt + Delete and Meta + QHandled by the operating system, which never passes them on to anything.Cannot be held back
Fn, Power and most media keysActed on in hardware or firmware on most systems, so no key event reaches the page at all.Cannot be held back
What a browser can and cannot see. Every ordinary key reports, and this page holds back the shortcuts it is allowed to hold back, so F5 does not reload the test halfway through. The map is a picture of a layout, not a claim about yours: what counts is the code printed beside each press, because that is what your keyboard actually sent. Every key the browser reports is recorded with the code it sent. Fn, Power and most media keys never reach a web page on most systems, so a dark one there is not a fault. Rollover is the most keys the browser saw down at once, which some keyboards cap.

Common questions

Which keys cannot be tested in a browser?
Fn, Power and most media and brightness keys are handled in the keyboard's own firmware or by the operating system, so no key event ever reaches a web page. The Mac layout draws fn with a dashed outline for exactly this reason and leaves it out of the tested count, so it cannot make a working keyboard look faulty. A few combinations are reserved too: Cmd or Ctrl with W, T, Q and Tab are taken by the browser or the system before the page is told about them. Everything else, including every letter, modifier, arrow, function key and number pad key, reports normally.
Why does F11 not go full screen here?
Because the tool holds it back on purpose. Once you have engaged with it, by pressing a key or clicking the board, it suppresses the default action of F1 to F12, Tab, Space, Backspace, slash and apostrophe, so F5 cannot reload the page mid-test, Space cannot scroll the board off screen and Tab cannot jump focus away from it. Three things are never held back: anything with a Cmd or Win key down, Shift with Tab, which is how focus moves back out, and any key pressed while the cursor is in a text box or on a button. Ctrl is not exempt, so Ctrl with F5 or Ctrl with Space is held back the same as the bare key, and the browser still wins on anything it reserves for itself. Press Esc, anywhere except the typing box, to hand the keyboard back. The table under the tool lists every key it suppresses and every combination it is not allowed to touch.
What does rollover mean?
Rollover is the most keys the browser saw held down at the same moment. Press four or five keys together and the figure climbs; on many membrane keyboards it stops climbing around six, or stalls on particular combinations, because the switch matrix cannot tell some simultaneous presses apart. That ceiling is real and it is what gamers mean by n-key rollover. Read it as a floor rather than a specification, though: the operating system and the browser can each drop a key event, so the number is the most this page actually saw, not the most your hardware can do.
Does it work for a laptop keyboard or a Mac?
Yes. Pick ANSI for a US board, ISO for a UK or European one, which has the extra key beside the left Shift and the hash key next to the apostrophe, or Mac for Command and Option. The number pad is a separate switch, since most laptops do not have one. The map is a picture of a layout, not a claim about yours, so a laptop that is missing the navigation cluster simply leaves those caps dark. What matters is the code printed beside each press: that is what your keyboard genuinely sent, whatever the drawing shows.
How do I tell whether a key is actually dead?
Press every key once. Anything still dark, and still listed under Not yet pressed, did not report. Before calling it dead, check two things: that the key is not one of the firmware keys above, and that it is not being swallowed by a combination the browser reserves. If an ordinary letter or modifier stays dark while its neighbours light, the switch, the cable or the controller is the problem. Copy log gives you the recent run as plain text with timings, the last 400 events of it, which is the useful thing to attach to a warranty claim.
What is the repeat rate, and how is it measured?
Hold a key down and the operating system waits, then starts repeating it. The wait is the repeat delay and the speed afterwards is the repeat rate, and they are set separately in your system settings. This tool measures only the gaps between repeats, never the first gap, because that one includes the delay and would halve the answer. It reports the median of the recent gaps, so a single dropped frame does not distort the figure.
Why does it show KeyQ when I pressed A?
Because the two are different questions. Every event carries a code, which is the physical position on the board, and a key, which is the character your software layout produced there. On an AZERTY keyboard the position labelled A is the one a US layout calls Q, so the code reads KeyQ and the key reads a. Position is what a hardware test needs, so that is what the map marks. Both values appear in the Last key row, and the log records both.

Every key the browser reports is recorded with the code it sent. Fn, Power and most media keys never reach a web page on most systems, so a dark one there is not a fault. Rollover is the most keys the browser saw down at once, which some keyboards cap.