Published 15 August 2026 · Last updated 15 August 2026
You press a key once and the computer receives it twice. Sometimes three times. It happens on one particular key, it comes and goes, and it gets worse over months. That is chatter, and it is one of the few keyboard faults you can diagnose fairly confidently from a web page, because the fingerprint is timing.
The keyboard chatter test logs each key event with its timestamp and flags duplicates that arrive suspiciously close together, so you can see whether a suspect key really is producing extra events and how far apart they land.
Why switches bounce in the first place
A key switch closes a mechanical contact. Two pieces of metal meeting at speed do not settle instantly — they make contact, separate slightly, make contact again, and repeat until the movement damps out. To an electrical circuit reading the contact thousands of times a second, one press looks like a rapid burst of on-off-on-off transitions before it stabilises.
This is contact bounce, and it is normal physics rather than a defect. It applies to mechanical switches, membrane domes and almost every other contact-based switch. On a healthy switch the bouncing settles quickly — typically within a few milliseconds, though the exact figure varies by switch design, actuation force and age.
Switches that do not rely on a metal contact closing — optical and Hall-effect designs, for example — do not bounce in the same way, which is one reason they are marketed as chatter-resistant. They have their own failure modes instead.
What debounce does
Keyboard firmware compensates with debounce: after it sees a key change state, it ignores further changes on that key for a short window, on the assumption that anything inside the window is bounce rather than a second real press.
The window length is a design decision, commonly in the region of 5 to 20 milliseconds depending on the firmware and the switch it was tuned for. The trade-off is direct:
- A short window reports the press sooner and allows very fast repeated taps, but lets more bounce through as the switch ages.
- A long window suppresses bounce reliably, but delays how quickly a genuine second press can be registered, and — in firmware that waits out the window before reporting at all — adds that delay to every press.
Chatter appears when a switch's bouncing outgrows the window it was tuned for. The firmware has not changed; the switch has.
Why chatter develops over time
New keyboards rarely chatter. The causes accumulate:
- Oxidation. Contact surfaces develop a thin oxide layer, which makes the electrical connection intermittent as it forms and breaks under pressure.
- Contamination. Dust, skin oil, food residue and — the classic — a spilled drink leave a film or particles between the contacts.
- Mechanical wear. Spring fatigue and worn contact leaves change the force and the geometry of the closure, so the switch bounces for longer.
- Corrosion after liquid damage, which can begin working weeks after the spill and often shows up on several adjacent keys.
Because these are progressive, chatter usually starts on the keys you press most — space, the WASD cluster, or whichever key a particular game or application hammers.
Chatter, double taps and software repeat
Three different things produce repeated key events, and they look different in a timeline:
| Chatter | Deliberate double tap | Key repeat | |
|---|---|---|---|
| Gap between events | Very short and irregular — often only a few milliseconds | Rarely closer than roughly 50 ms, because that is a limit of human motor control | A long initial delay, then a steady, very regular interval |
| Repeat flag on the event | Not set — each event looks like a fresh press | Not set | Set on every event after the first |
| Did you mean it? | No | Yes | You are holding the key down |
| Which keys | Usually one or two specific keys, repeatedly | Whichever key you tapped | Any key you hold |
The repeat flag is the cleanest discriminator. Browsers mark auto-repeat events, so a duplicate without that flag is not your operating system repeating the key — browser keyboard event timing covers what else each event carries and how its timestamp is produced. If you want to see repeat behaviour on its own, the key repeat rate test measures the initial delay and the repeat interval your system is actually using.
The 50 ms figure is a rule of thumb, not a hard boundary — some people can tap faster, and events separated by 30 to 60 ms are genuinely ambiguous. That is why a chatter test should report the pattern it found rather than pronounce a verdict: a run of duplicates under 15 ms on one key, appearing while you type normally, is strong evidence; a single close pair is not.
How to test for it
- Turn off any keyboard filtering first — Windows Filter Keys, macOS Slow Keys — because they suppress exactly the events you are trying to observe.
- Close remapping and macro utilities, and any screen-sharing or remote-desktop session, since these can duplicate or reshape events.
- Open the chatter test and type normally for a minute or two, then hammer the suspect key with single deliberate taps.
- Look at the intervals rather than the count. Repeated sub-15 ms duplicates on one key are the signature; occasional ones on many keys point at software instead.
- If possible, repeat on a second computer. Chatter follows the keyboard; software artefacts stay with the machine.
Fixes, cheapest first
- Clean and reseat. Compressed air around the switch, and — on a hot-swap board — pull the switch and reseat it. Bent or partially seated pins produce intermittent contact that looks exactly like chatter.
- Contact cleaner. A switch cleaner or electrical contact cleaner applied sparingly, with the keyboard unplugged and left to dry fully, can clear oxidation and residue. Use a product intended for electrical contacts; general solvents can attack plastics and lubricant.
- Adjust debounce in firmware. If the board runs configurable firmware such as QMK or VIA, or the manufacturer's software exposes a debounce setting, lengthening the window suppresses a mildly degraded switch. This masks the cause and slightly delays the reported press, so treat it as a workaround.
- Replace the switch. Trivial on a hot-swap board, a desoldering job otherwise. This is the actual fix for a worn switch.
- Replace the keyboard. Reasonable when several switches are chattering at once, when liquid damage has spread, or on a laptop keyboard where individual switches are not serviceable.
Accessibility settings cut both ways
Windows Filter Keys and macOS Slow Keys exist to help users whose hand movement produces unintended repeated or brief presses. Filter Keys can ignore repeated presses of the same key within a configurable interval; Slow Keys requires a key to be held for a set time before it counts.
Either can make chatter invisible — which is genuinely useful if you need the keyboard to work today and cannot replace it yet. Both also complicate diagnosis in two ways: they hide the evidence while you are testing, and they suppress legitimate fast input, so a keyboard that feels like it is "missing keystrokes" may simply have one of these turned on. Windows in particular can enable Filter Keys through a shortcut that is easy to trigger by accident.
Turn them off before testing, then decide deliberately whether to turn them back on.
What a browser test cannot tell you
A web page sees key events after the keyboard firmware, the connection and the operating system have processed them. It can show that duplicate events arrived and how far apart they were, which is a strong pattern — but it cannot inspect the switch, measure contact bounce directly, or prove which layer produced the duplicate. Read a result as "possible chatter detected on this key" rather than a diagnosis. The methodology page lists every limit.
Frequently asked questions
Is keyboard chatter a hardware or a software problem?
Usually hardware, in the sense that the switch contacts are producing extra transitions that the firmware's debounce window no longer suppresses. Software can imitate the symptom, though: remapping utilities, macro tools, screen sharing software and accessibility features can all duplicate or reshape key events.
Can chatter be fixed without replacing the switch?
Often, yes. Cleaning with compressed air, reseating a hot-swap switch, or a small amount of contact cleaner applied carefully can restore a contaminated or lightly oxidised contact. If the keyboard's firmware exposes a debounce setting, lengthening the window is another option, at the cost of a slightly later reported press.
How fast is too fast to be a real double tap?
There is no exact threshold, but deliberate human double taps rarely land closer than roughly 50 milliseconds apart, and repeated events separated by only a few milliseconds are difficult to produce on purpose. Very short gaps that appear without you meaning to double tap are the pattern worth investigating.
Does Windows Filter Keys fix chatter?
It can hide the symptom by ignoring repeated presses of the same key within a set interval, which is not the same as fixing the switch. It also delays or suppresses legitimate fast input, and it will distort the results of any chatter test, so turn it off before testing and decide deliberately whether you want it on afterwards.