logo

Keyboard Chatter Check

Detect unintended rapid double inputs (chatter) by tracking very short keydown intervals.

Total keydown: 0 Suspected chatter: 0

Capture Area

FocusNot focused

Detection Settings

Threshold (ms)30 ms

Last event

No events yet.

Tip: If you hold a key, many browsers emit repeat keydown events.

Click the area, then repeatedly tap a single key to see if extra keydown events appear within the threshold window.

Try a problem key onlyAvoid holding the keyExport to share results

Last event

-

Click to start capturing

This area must be focused to receive key events.

Log

No events yet. Click the capture area and start typing.

Top Suspected Keys

No data yet
Keyboard chatter typically appears as unintended rapid double inputs. This page marks suspected chatter when the same key produces multiple keydown events within a very short time window.
• Per-key suspected chatter counter • Adjustable threshold window (ms) • Option to ignore auto-repeat • Shows fastest suspected repeat interval • JSON export for sharing/analysis
1) Click the capture area to focus. 2) Tap a single key repeatedly (do not hold). 3) Watch the suspected count and the fastest interval. 4) Increase/decrease the threshold until it matches your symptom. 5) Export JSON if you need to share results.
• Signal: browser keydown/keyup events • Heuristic: repeated keydown within the threshold window • Auto-repeat can inflate counts; enable “Ignore auto-repeat” • OS keyboard repeat rate and input method can affect results
• Diagnose a single problematic key on mechanical keyboards • Verify after switch replacement or cleaning • Compare behavior across browsers/OS • Provide evidence for warranty claims (export JSON)
Q: Why is my key flagged when I hold it? A: Holding a key triggers OS/browser auto-repeat; enable “Ignore auto-repeat”. Q: What threshold should I use? A: Start around 30–60ms. If you only want to catch obvious chatter, increase it; if you get false positives, decrease it. Q: Why does the result differ between browsers? A: Event timing and repeat behavior vary across OS/browsers, and input methods can add latency. Q: Does this prove hardware failure? A: Not by itself. It’s a best-effort browser heuristic; confirm by testing in multiple apps/OS and by disabling macros. Q: How do I get the cleanest test? A: Use a single key, tap (don’t hold), close heavy background apps, and keep the tab focused.