Skip to main content
Documentation menu
On this page

Keyboard

Stuck Key Detector

Watches for keys that go down and never come back up, with an adjustable hold threshold.

  • Available — Live on this site right now.
  • Browser Tool — Runs in the browser you are reading this in.
  • No Install — Nothing to download, no extension, no account.
  • Client-Side — Runs entirely on your device. No test data is uploaded.
  • Desktop — Needs a physical keyboard or mouse to be useful.

Live tool: /stuck-key-detector/

This page explains the tool. The tool itself is one click away and needs no sign-in.

Open Stuck Key Detector

What is this tool?

A stuck key is one the computer believes is still pressed after you have let go. It shows up as a runaway character, a game character that will not stop walking, or a modifier that turns every keystroke into a shortcut.

This page watches the keydown and keyup stream and measures how long each key stays down. If a key is held past the threshold without releasing, it is raised as a stuck-key candidate and named.

The threshold is yours to set — 1, 2, 3, 5, 8, 10, 15 or 30 seconds, with 5s as the default. Shorter thresholds catch problems faster but will also flag deliberate long holds.

How to use it

  1. Let it watchThe page starts in monitoring mode as soon as it has focus. You do not need to press anything to arm it — the panel reads Ready to Test until the first event arrives.
  2. Pick a thresholdChoose how long a key may stay down before it counts as stuck. Leave it at 5s (Default) unless you are hunting something specific; drop to 1s or 2s to catch a briefly latching modifier.
  3. Type normally, then stopType a sentence, then take your hands off the keyboard completely. Anything still reporting as held after you have stopped is the thing you are looking for.
  4. Read the logFilter with STUCK to see only flagged keys, or REPEAT to isolate operating-system auto-repeat. PAUSE MONITORING freezes the view so you can read it, Clear empties the log and RESET MONITORING starts a clean session.

What the results mean

A key flagged as stuck

A keydown arrived, the threshold elapsed, and no keyup followed. If your hands were off the keyboard, that is a real fault — mechanically stuck, contaminated, or held by software.

Repeat events

A long stream of repeats from one key is your operating system's auto-repeat doing its job, not a fault. The REPEAT filter separates them so they do not muddy the picture.

Flagged while you are holding it

That is correct behaviour. The tool measures hold time and cannot know whether your finger is still down. Release the key and the flag clears.

Nothing flagged

Every press you made was matched by a release within the threshold. No stuck-key behaviour reached the browser during the session.

What it can detect

  • Keys held past your chosen threshold with no keyup
  • Modifier keys that latch and stay active after release
  • Operating-system auto-repeat, shown separately so it is not mistaken for a fault
  • Which key is responsible, by name and code

Limits worth knowing

A browser can only report what the platform gives it. These are the honest boundaries of this page, so a result is never read as more than it is.

  • A stuck result does not automatically mean the keyboard is broken. Sticky Keys, a remote-desktop session that dropped a keyup, a macro utility or a game overlay can all leave a key logically down.
  • The tool measures time between events. It cannot see debris under a keycap, a bent stem or a spring that has lost tension.
  • Switching browser tabs interrupts the event stream, so the session resets rather than reporting a false stuck key.

Tips

  • Take your hands off the keyboard for a full ten seconds before reading the result. Most false positives are a finger still resting on a key.
  • If a modifier is the culprit, check the operating system's accessibility settings first — Sticky Keys produces exactly this symptom with perfectly healthy hardware.
  • A key that sticks only when warm, or only after heavy use, is worth catching with a longer session rather than a quick check.

Troubleshooting

The test resets whenever I switch tabs

Deliberately. A background tab stops receiving key events, and a keyup that arrives while the page is hidden would look like a stuck key. Keep the tab in front for the whole session.

Every key I hold gets flagged

Your threshold is shorter than the way you type. Raise it to 5s or 8s.

A key sticks in Windows but passes here

Suspect software. Sticky Keys, Filter Keys, a driver utility or a macro tool can hold a key down at a level the browser never sees as a fault.

How do I clear a physically sticky key?

Power down, remove the keycap, and clear debris with compressed air or isopropyl alcohol on the stem. Re-run this test afterwards to confirm the release is clean.

Ready to run it?

Watches for keys that go down and never come back up, with an adjustable hold threshold. Nothing to install, and it opens in this browser.