The symptom was not reproduced during that observation. It may be intermittent; this is not a pass or failure.
Unexpected-input troubleshooting
Keyboard Pressing Keys by Itself?
Stop typing and watch which inputs reach this page, or run a guided press-and-release check for a key that appears continuously active.
Live state, durations, and release checks remain local.
Press/release monitor
Watch live key state
Hands-off observation
Watch without touching the keyboard
Start monitoring, then stop typing and observe the live state.
Currently detected as held0
Current keysNone
Longest current hold—No active hold
Recent release status—
Swipe sideways to view the full keyboard.
- Esc
- F1
- F2
- F3
- F4
- F5
- F6
- F7
- F8
- F9
- F10
- F11
- F12
- Prt Sc
- Scr Lk
- Pause
- ~`
- !1
- @2
- #3
- $4
- %5
- ^6
- &7
- *8
- (9
- )0
- _-
- +=
- Backspace
- Tab
- Q
- W
- E
- R
- T
- Y
- U
- I
- O
- P
- {[
- }]
- |\
- Caps Lock
- A
- S
- D
- F
- G
- H
- J
- K
- L
- :;
- "'
- Enter
- Shift
- Z
- X
- C
- V
- B
- N
- M
- <,
- >.
- ?/
- Shift
- Ctrl
- Win
- Alt
- Space
- Alt
- Win
- Menu
- Ctrl
- Num Lock
- /
- ×
- −
- Home7
- ↑8
- Pg Up9
- +
- ←4
- 5
- →6
- End1
- ↓2
- Pg Dn3
- Enter
- Ins0
- Del.
Modifier key state
Left and right positions are shown separately where the browser reports them.
Left ShiftReleased
Right ShiftReleased
Left CtrlReleased
Right CtrlReleased
Left AltReleased
Right AltReleased
Left MetaReleased
Right MetaReleased
Browser repeat events are counted as normal hold information. Blur or hidden-tab cleanup clears live state without creating a failed release result.
Hands-off comparison
First confirm that input is actually arriving
Start the observation, remove your hands, and avoid changing tabs. If an event appears, note whether one code remains held, the same code returns intermittently, or unrelated codes appear. The page records the symptom but cannot name its source.
A continuous key state can fit a physical/electronic hold, an accessibility feature, remapping, or a browser release artifact.
Compare outside the browser, then change one source at a time: external device, connection, macro/remapping, or remote-input software.
Possible sources
Unexpected input can begin in hardware or software
Browser events cannot distinguish these causes by themselves.
A — Active physical key path
The same code remaining active or returning hands-off can be consistent with a switch, contact, firmware, battery, Bluetooth, cable, or receiver path. The event does not reveal which one.
B — OS or software-generated input
Sticky Keys, macros, remapping, text expansion, application automation, and remote-control/input software can create keyboard events without a new intentional press.
C — Browser state artifact
A shortcut, tab switch, hidden page, or connection interruption may prevent the page from seeing a release. That stale browser state is different from observing fresh hands-off keydowns.
Cross-environment outcomes
Use where the symptom appears to narrow the source
Only this page looks held after focus changed
Treat the observation as a browser-state interruption. Repeat without leaving the page; do not infer a physically held key from the stale state.
Input appears in one application only
Inspect that application's shortcuts, automation, plugins, and text-input settings before changing keyboard hardware.
Input stops after an external keyboard is disconnected
The symptom is more localized to that device or connection path. Reconnect carefully, check battery/receiver state, and follow its documented support guidance.
D — Input follows the keyboard to another computer
A keyboard-level or connection-level source becomes more plausible when fresh hands-off input occurs in multiple applications and computers. This still does not identify a switch or circuit failure.
Modifier behavior
Check Sticky Keys and accessibility settings
If Shift, Ctrl, or Alt seems to remain active, review the operating system's accessibility features as well as remapping or shortcut utilities. Sticky Keys can intentionally keep a modifier active without a physically held switch. The live panel shows left and right modifier events where the browser reports them.
Hands-off isolation path
Change one possible source at a time
Repeat the observation after each step so you know which change mattered.
- 1
Observe without changing focus. Note continuous held state separately from fresh unexpected events.
- 2
Compare outside the browser. Check whether the same key or action appears in a simple application.
- 3
Review intentional software features. Check accessibility, macros, remapping, automation, and remote-input tools.
- 4
Separate connected devices. Disconnect an external keyboard or receiver when safe, then observe the built-in keyboard path alone.
- 5
Check the connection. Reconnect cables, review Bluetooth/battery state, and try another appropriate port.
- 6
Compare another computer. A symptom that follows the same keyboard is stronger isolation evidence, not a confirmed hardware diagnosis.
Privacy and limits
No background keyboard monitoring
The tool listens only while this page is open. Current holds, repeat counts, durations, and guided attempts stay in temporary memory. Observed browser input is not proof of a stuck switch, damaged circuit, virus, or other specific cause.