Keyboard Double Click Test & Key Chatter Detector
This keyboard double click test flags repeated presses that arrive within your chosen threshold. Type a few deliberate taps and compare the gaps in milliseconds. A flagged pair is worth trying again: fast intentional taps, software settings and a worn switch can look similar in the browser. The score describes this session, not a hardware diagnosis. Keystrokes stay in your browser.
Why a key types twice
One press produced two characters because the switch contact bounced and the firmware counted both bounces as real presses. Every mechanical contact rattles for a fraction of a millisecond as it closes, so firmware hides it with a debounce window — usually 5–10 ms in which further signal from that key is ignored. A healthy switch settles inside that window; a worn one keeps bouncing past it, and the second bounce arrives as a genuine keypress.
That is why chatter feels random: it only surfaces when a bounce outlasts the debounce window, so a key can misfire twenty times a day and still test clean for fifty presses. Type a few paragraphs of normal text into the keyboard double click test rather than mashing one key.
Chatter is a different fault from a key that fires continuously. A key that streams characters while held is usually OS auto-repeat or a stuck stem — check that with the stuck key test. This page ignores the auto-repeat flag, so held keys never register as false chatter. If you do not yet know which key is at fault, run the full keyboard tester first.
What causes switch chatter
Contact oxidation and dirt is the most common cause on a board over a year old. A thin oxide film or a speck of skin dust makes the connection intermittent as it closes. This is the case cleaning genuinely fixes.
Mechanical wear comes next: the contact leaf loses tension after tens of millions of actuations. Cleaning buys time, but the switch will come back. Keys you hit hardest fail first — W, A, S, D and Space.
Firmware debounce set too short is the one people miss. Cherry specifies roughly 5 ms of bounce, and some boards set their window right at that edge — the switches are fine and the firmware is the problem. The tell is chatter on many keys at once.
Low voltage on a wireless board causes the rest: as cells drain, the signal the controller sees falls toward its logic threshold and marginal reads count as extra presses.
Setting the chatter threshold
The threshold is the gap below which two presses of the same key are treated as one press that bounced. The default is 80 ms, adjustable from 10 to 250 ms. Deliberate double-taps almost never land closer than 60–70 ms apart, even from fast typists, so 80 ms catches real chatter without flagging normal typing.
Drop it to 40–50 ms if you tap keys rapidly on purpose — gaming, osu!, rhythm games — and real presses are being flagged. Raise it past 120 ms only when diagnosing a badly degraded switch; some worn contacts bounce for 100 ms or longer.
An honest limit: this test only sees presses your keyboard actually reported. Bounces the firmware's debounce window already swallowed never reach the browser, so a clean result means "nothing got through", not "this switch is electrically perfect". Browser event timestamps also carry a millisecond or two of queueing jitter — irrelevant at 80 ms, but the reason these gaps are not lab figures. That jitter matters far more on the keyboard latency test.
How to fix chatter without replacing the switch
1. Blow it out. Pull the keycap and blast compressed air into the switch housing while actuating the stem twenty or thirty times. Dust on the contact leaf often comes straight out.
2. Use a proper contact cleaner. If air is not enough, one short spray of a residue-free contact cleaner such as DeoxIT D5 into the switch, then thirty actuations and a few minutes to dry. It strips the oxide film rather than displacing dust. Ignore the forum advice to flush switches with isopropyl alcohol mixed into hot water — it damages boards.
3. Raise the debounce time. On QMK, #define DEBOUNCE 5 in config.h is the default; raise it in 2 ms steps and most chatter stops between 8 and 15 ms. ZMK also defaults to 5 ms, and Keychron Launcher exposes bounce time with no compiling. Keep the lowest value that works — every extra millisecond is added input delay.
4. Block it in software. On Windows, a tool such as KeyboardChatterBlocker filters repeats below a per-key threshold, so you can guard one bad key at 100 ms and leave the rest alone. A workaround, not a repair.
5. Remap or swap. On a hot-swap board, swapping in a spare switch is a 30-second fix with no soldering. On a soldered board, remapping the key is usually the better trade.
Brand-specific notes: Keychron, Corsair, Ducky, Epomaker
Keychron. Most K, Q and V boards are hot-swap and QMK/VIA compatible, so you have both routes: adjust bounce time in Launcher, or drop in one of the spare switches that shipped in the box. Support sends replacement switches for a keyboard in warranty.
Corsair. Corsair's own double-typing procedure: clean the switches, replug the keyboard holding Esc to reset it, use a motherboard USB 2.0 port, update firmware in iCUE, and disable USB selective suspend. Older K70 and K95 boards are soldered, so software fixes matter more there.
Ducky. Classic boards are soldered; the One 3 line is hot-swap. Before blaming a switch, confirm no macro or DIP-switch profile is active.
Epomaker. Hot-swap and VIA-compatible across most of the range, so a switch swap plus a debounce bump covers nearly everything. Budget boards of any brand are likelier to have a too-short debounce window than genuinely bad switches.
Is chatter covered by warranty
Usually yes. A switch registering two inputs from one press is a manufacturing defect, not wear and tear, and most mechanical keyboards carry a one- or two-year warranty that covers it. Keychron, for example, covers repair or replacement of individual damaged switches and warrants replacement parts for 90 days or the remainder of the keyboard warranty, whichever is longer.
Evidence is what gets claims approved. Run the keyboard double click test, screenshot the affected key with its flagged gaps in milliseconds, and record a short video of one press producing two characters. A number is harder to argue with than "it types twice sometimes".
Two things void it in practice: lubing or desoldering switches yourself, and buying second-hand. And if a new keyboard chatters out of the box, do not accept it as normal for mechanical switches — it is not.
Frequently asked questions
My computer keeps typing two letters when I only press the key once. I changed the keyboard settings and nothing helped — what do I do?
Keyboard settings will not fix this, because it is not a settings problem. Windows repeat delay and repeat rate only affect a key you hold down; chatter happens on a single tap, inside the switch. Test the key here first — if you see flagged gaps under 80 ms, the hardware is bouncing. Then clean the switch, raise the debounce time, or swap the switch. If a second keyboard does the same thing, the fault is in software instead.
Can I fix key chatter without replacing the switch?
Often yes. Start with compressed air into the switch housing while actuating the stem thirty times, then a residue-free contact cleaner such as DeoxIT D5 if that fails — most chatter on an older board is oxidation or dust, not a dead switch. If cleaning does not hold, raise the firmware debounce time in 2 ms steps until it stops, typically at 8–15 ms. Ignore forum advice to flush switches with alcohol mixed into hot water; it damages boards.
Is this the controller at fault, or can chattering only be due to single keys malfunctioning?
If ten or more keys chatter, suspect the controller's debounce, not the switches. A defective switch is a local failure — one or two keys, usually the ones you hit hardest. Widespread chatter across a board points at a firmware debounce window set too tight for the switches it is filtering. The test for this is cheap: raise the debounce time in firmware. If the chatter clears across every key at once, it was never the switches.
Is it normal that a new mechanical keyboard has chatter keys?
No. A new keyboard should not chatter, and it is not an accepted characteristic of mechanical switches. New-board chatter almost always means one of two things: a defective switch that slipped through QC, or firmware with a debounce window too short for the switches fitted. Both are warranty defects. Test it, record the result, and return or exchange it rather than trying to clean a switch that has barely been used.
Is there a fix for key chatter, or do I need to buy a new keyboard?
Buying a new keyboard is the last option, not the first. If the board is in warranty, claim it — chatter is a defect. Out of warranty, a hot-swap board takes a spare switch in 30 seconds; a soldered board needs two joints desoldered, or replacement switches that cost a few dollars for ten. If neither appeals, remap the chattering key to a modifier where a duplicate input does no harm, or run a per-key chatter blocker.
My keyboard double presses only in some games — is that the keyboard or Windows?
If it happens on a second keyboard, or on the on-screen keyboard clicked with a mouse, it is not your keyboard. That pattern points at Windows or the game: check that Filter Keys and Sticky Keys are off in accessibility settings, reinstall the keyboard driver, and test in a new user profile. Real switch chatter follows the hardware — it appears in every application, and it disappears when you plug in a different keyboard.
Can a low battery make a wireless keyboard chatter?
Yes. As cells drain, the voltage the controller reads across the key matrix falls toward its logic threshold, and marginal reads get counted as extra presses — one Deskthority report saw chatter and doubled inputs appear around 1.15 V per cell, with bounce stretching to 30 ms. Charge or replace the battery and retest before you blame a switch. Wired-versus-wireless is the quickest check: if the chatter vanishes on the cable, it is power, not the switch.