Why Is My Keyboard Typing Double Letters?
Double letters can come from switch chatter, a firmware setting, normal held-key repeat or software that duplicates input. Start by tapping the suspect key slowly in the double typing test, fully releasing it between taps. A short interval is a clue, not proof of a particular hardware fault.
Capture the symptom first
Make a short series of deliberate presses and compare your physical taps with the displayed events. Test a nearby key in the same way. Repeat in a plain text editor. Avoid rapid tapping during diagnosis: deliberate double taps can cross the detector's chosen threshold too.
The browser marks many auto-repeat events with repeat. Holding a key and seeing a stream of characters is expected when repeat is enabled. Extra non-repeat presses after one tap need a different investigation.
| Pattern | What to compare next |
|---|---|
| Extra events from one key in several applications | Another connection or computer; then the switch and its socket |
| Problem began after a firmware/profile change | Restore the documented default profile |
| Repetition begins only while holding the key | Operating-system repeat delay and rate |
| Duplicates occur only in one app | That app's bindings, macros, extensions and remote-input settings |
| A key stays active after release | Stuck-key test and focus-loss behavior |
What chatter and debounce mean
Mechanical contacts may change state several times as they settle. Firmware debounce filters those transitions. QMK supports multiple strategies, so debounce is not always a fixed wait added to every press. A too-aggressive setting can allow unwanted transitions through; a longer setting can change responsiveness.
If you changed firmware, return to the keyboard maker's supported configuration before modifying values. A detector cannot read the keyboard's debounce setting or distinguish electrical bounce from a macro solely from browser timestamps.
There is no universal “under 30 ms proves chatter” rule. Event scheduling, firmware features and input software affect the trace. Treat the threshold as a screening aid and compare with controlled physical taps.
If the fault follows the keyboard
First check the warranty and use the manufacturer's cleaning instructions. Do not pour alcohol into a switch as a general repair: materials, coatings and lubrication vary. Our cleaning guide starts with external cleaning.
On a confirmed hot-swap mechanical board, a compatible known-good switch can help isolate a fault. Disconnect power before changing parts and follow the board's instructions. If the problem follows the switch, that supports a switch fault; if it stays at the position, the socket, board or mapping still needs investigation. Do not force out a soldered switch or pry laptop keycaps.
What to send to support
Include the affected key, whether separate taps create extra events, connection mode, firmware/profile changes and whether the issue repeats on another computer. Avoid sending text you were typing when the fault occurred; the key name and reproduction steps are enough.
Sources
- QMK debounce documentation describes debounce strategies and configuration.
- MDN: KeyboardEvent.repeat explains held-key repeat.
- Testing methodology describes the limits of event-based diagnosis.