keyboard.gripe

Find the dead, sticky, double-typing or mismapped key.

0 of 0 keys tested

Caps LockNum Lock

not pressed yet tested held down now chatter (count top right) awhat it typed (key)

Which keys are left?

On a phone or tablet?

Tap the box to bring up your on-screen keyboard. On-screen keyboards usually report little: often no code, a key of “Unidentified” and keyCode 229, so the board above won’t light up. A Bluetooth or USB keyboard works normally.

Last key

–

code: – physical position
key: – what it typed
keyCode: –
location: –
presses: –
held for: –
re-press gap: –
chatter: –

Click a key on the board to see its numbers.

Held & stuck keys

Held now0

Most at once0

A key that stays lit after you let go is stuck, or its key-up got lost.

repeat delay: –
repeat rate: –
max set: –

Hold one letter for 2 seconds to measure key repeat (set by your OS).

Timing (approximate)

Closest 2 keys–

Same-instant0pairs

polling hint: –
samples: 0
timestamps: –

Roll a palm across several keys or hold a few and press more. The smallest gap between two different keys hints at the keyboard’s polling interval (8 ms ≈ 125 Hz, 1 ms ≈ 1000 Hz). Browsers coarsen timestamps, so treat it as a hint, not a measurement.

Chatter / double press

Flag re-press under 40 ms

A key that types twice usually bounces: it goes down again a few milliseconds after it was released. Tap a suspect key normally 20–30 times. Human double-taps are rarely faster than ~70 ms, so anything under the threshold is the switch, not you.

Rollover & ghosting

Click a combo to highlight its keys, then hold them all down. If one won’t light up while the others are held, the keyboard is blocking (limited rollover; many are 6-key). If a key you’re not pressing lights up, for example S while holding Q, W and A, that’s ghosting.

Event log

key-ups every repeat capture Tab

event	code	key	keyCode	location	repeat	modifiers	time down	gap since release	at (s)

Nothing yet. Press a key.

Keys that may never show up

Fn / Globe is handled inside the keyboard or by the OS and almost never reaches a web page. Media, brightness and volume keys usually go straight to the OS too.
Windows key, ⌘ shortcuts, Alt+Tab, Ctrl+Alt+Del, ⌘+Tab, ⌘+Space are taken by the operating system first. Print Screen on Windows often arrives only as a key-up (it still counts here).
Browser shortcuts like Ctrl/⌘+W, T, R, N and L are left alone on purpose, so you can’t get trapped. Space, arrows, Tab, Backspace, Page Up/Down, Home/End and F1–F12 are captured so they don’t scroll or navigate, as long as Ctrl/⌘ isn’t held.
Mac: while ⌘ is held, macOS doesn’t send key-ups for other keys, so they’re released here when ⌘ goes up. Caps Lock reports “down” when it turns on and “up” when it turns off. F1–F12 act as media keys unless you hold fn (or change it in System Settings → Keyboard).
Capture more keys uses fullscreen plus the Keyboard Lock API, which lets Esc, Alt+Tab, the Windows key and similar reach the page. It works in Chrome, Edge and other Chromium browsers on desktop. Firefox and Safari don’t support Keyboard Lock; there, OS shortcuts stay with the OS. Hold Esc to leave fullscreen.
Phones: on-screen keyboards report limited info (often keyCode 229 and no code). Use the box above on touch devices, or connect a real keyboard.