Skip to content

Keyboard test

Press every key on your keyboard and watch it light up here. Keys you have already tested stay highlighted, so it is easy to spot the ones that never respond.

0 of 104 keys tested

Click anywhere on this page first, then start pressing keys.

EscF1F2F3F4F5F6F7F8F9F10F11F12
`1234567890-=Backspace
TabQWERTYUIOP[]\
CapsASDFGHJKL;'Enter
ShiftZXCVBNM,./Shift
CtrlWinAltSpaceAltWinMenuCtrl
PrtScScrLkPause
InsHomePgUp
DelEndPgDn
Num/*-
789+
456
123Ent
0.
event.key
event.code
keyCode
Location

Key events are handled locally by this page and never leave your browser. Nothing is logged, saved or sent anywhere.

How to use the keyboard tester

  1. Click once anywhere on this page so the browser sends key events here.
  2. Press every key in turn. A key turns blue while held and stays green once it has been registered at least once.
  3. Work through the whole board. Anything still grey at the end either was not pressed, or is not responding.
  4. Press Reset to clear the highlights and start again.

The layout above is a full-size US keyboard. If yours is a laptop or a compact model, some keys simply will not exist — a tenkeyless keyboard has no numeric keypad, and most laptops have no dedicated Scroll Lock or Pause. Ignore those and concentrate on the keys you actually have.

Reading the key codes

The four values under the keyboard describe the last key you pressed:

  • event.key — the character produced, which depends on your keyboard layout and on whether Shift is held.
  • event.code — the physical key position, independent of layout. This is what the highlighting uses, and it is why the tester works with any language.
  • keyCode — the legacy numeric code, kept for compatibility with older software.
  • Location — distinguishes duplicated keys: 1 is the left Shift, Ctrl or Alt, 2 is the right one, and 3 means the numeric keypad.

If event.key disagrees with the letter printed on the keycap, your operating system is set to a different keyboard layout than the hardware. That is a settings problem, not a broken keyboard.

Keys that cannot be tested in a browser

A few keys never reach the page, and their absence does not mean they are broken:

  • Fn — processed inside the keyboard itself. No application on any operating system can see it.
  • Media and brightness keys — usually intercepted by the operating system before the browser gets a chance.
  • Print Screen — captured by the screenshot tool on many systems, so the browser sees only the release.
  • The Windows or Command key — opens the system menu and takes focus away from the page.

Diagnosing common keyboard faults

A key does nothing at all

First rule out software: try the key in a plain text editor as well. If it is dead everywhere, and other keys work, the switch or the membrane under that key has failed. Before assuming the worst, remove the keycap if you can and check for debris — on membrane keyboards a single crumb is enough to break contact.

A key repeats or fires on its own

This is switch chatter, usually caused by dirt or by a worn contact. Clean first with compressed air and isopropyl alcohol on a cotton bud. On a hot-swap mechanical keyboard the switch can be replaced in seconds; on a soldered board or a laptop it is a repair job.

Several keys fail together

Keys that fail in a group — a whole row, or a diagonal set — point at the matrix wiring or a ribbon cable rather than individual switches. On a laptop this is often a partially seated or corroded keyboard ribbon connector, which is a common outcome after a liquid spill.

Nothing works at all

Try the keyboard on another computer, and try another keyboard on this one. That single swap tells you immediately whether the fault is the keyboard, the port or the driver. For wireless models, replace the batteries before anything else — falling voltage causes erratic behaviour long before the keyboard stops completely.

Frequently asked questions

Are my keystrokes recorded or sent anywhere?

No. The page listens for key events in your browser purely to light up the on-screen layout, and nothing is stored or transmitted. Even so, as a general habit you should never type a real password into any web page that is not the login form it belongs to.

Why does nothing happen when I press the Fn key?

The Fn key is handled inside the keyboard controller itself and never reaches the operating system as a key event, so no software can see it. This is normal on every laptop and is not a fault.

A key lights up on screen but types the wrong character.

The key is electrically fine — this is a keyboard layout mismatch. The physical key labelled Z on a German or French keyboard sits where a US layout expects a different letter. Change the input language in your operating system settings to match the printing on your keyboard.

Several keys stop working when I hold others down.

That is key ghosting, and it is a hardware limit rather than a defect. Cheap membrane keyboards share wiring between groups of keys and can only register a few simultaneous presses. Keyboards advertised as having N-key rollover do not have this limit.

One key repeats by itself or stays stuck down.

Usually debris or sticky residue under the keycap. On a mechanical keyboard, pull the keycap and clean around the switch with compressed air and isopropyl alcohol. On a laptop, a can of compressed air at an angle often clears it — but a switch damaged by liquid usually needs replacing.

Why is my Windows key not detected?

Pressing it opens the Start menu, which moves focus away from the browser before the page can register the release. The key press itself is normally recorded, but the layout may stay lit until you click back onto the page.

Other tests on HardwareProbe