One key at a time
Press and release a key inside the test area. The tool tracks each physical key separately by its position, so A and S never mix.
Press one key at a time. This tool watches the keys you press and flags unusually fast same-key repeats for review.
Runs locally in this page. Your key presses are not uploaded or saved after refresh.
Click here, then press one key at a time. Release before pressing again.
Press one key at a time in this test area. Release the key before pressing again.
This page watches the keyboard signals your browser reports for each physical key. It flags a key when the same key registers a second press unusually soon.
Press and release a key inside the test area. The tool tracks each physical key separately by its position, so A and S never mix.
Holding a key triggers the system's auto-repeat. The browser marks these repeat signals separately, and they are never treated as chatter.
Collect about 20 slow single presses on a suspected key, then compare across another app, browser or computer before deciding.
Normal observed — no unusually fast same-key repeat for this key in this session.
Review — a same-key repeat arrived between 30 ms and 80 ms. Fast but ambiguous: review this key with more slow presses.
Chatter candidate — a same-key repeat arrived within 30 ms, almost impossible to produce deliberately. Treat it as evidence to retest, not a confirmed fault.
Held repeat — automatic repeats produced while a key is held down. Counted separately and ignored for chatter detection.
These ranges are versioned in the methodology, not a universal hardware threshold.
A single fast key repeat is only evidence. Run a controlled round before trusting the result.
Press the suspected key one time, release it fully, then wait a moment before the next press. Collect about 20 presses on that key alone.
Keys you use most — Space, Enter, Backspace, or a letter — are more likely to show an issue. Test a few high-use keys in the same round.
Retest in a plain text field, another browser, or another computer. If a repeat only appears in one app, the keyboard may not be the cause.
Work through these in order. The page only sees the keyboard signals your browser reports; it cannot inspect firmware or the physical switch contacts.
| Cause | What it looks like | What to do |
|---|---|---|
| Holding and auto-repeat | Holding a key triggers system auto-repeat; the browser marks these as repeat signals. | Do not hold the key. Press once and release immediately. Repeat events do not count as chatter. |
| App or input method | Some editors, plugins, page scripts or input methods can produce a duplicated-input appearance. | Retest in a plain text field, another browser and another application. |
| Keyboard software / macros | Vendor software, macros, layers, rapid-fire or game profiles can generate repeated actions. | Pause macros and remapping, then restore them one by one while retesting. |
| Firmware / key handling | A vendor may ship firmware or key-handling settings that change how a model reports repeated presses. | Check updates only from the vendor's official software and support pages. |
| Switch or contact issue | Mechanical switch, dust, liquid, oxidation, hot-swap contact or PCB issues can be involved. | If under warranty, contact the vendor first. On a hot-swap keyboard, you may swap the suspect switch with a known-good key per vendor instructions. |
Opening a keyboard, replacing switches, using liquids, or changing firmware can damage the device or affect warranty coverage. Check manufacturer support and warranty options first.
It records keyboard input while the test area has focus and keeps it only in page memory. It cannot read switch contacts, firmware settings, connection quality, USB polling rate, system input latency or your device model. Some keys and shortcuts are handled by the browser or operating system before the page can see them, especially OS-level shortcuts, Fn combinations and some media keys. A clean round does not exclude an intermittent problem.
It is usually called double typing or key chatter: one physical key press appears as repeated input.
No. Holding a key can trigger operating-system auto-repeat. This page ignores those automatic repeat events when looking for chatter candidates.
No. It records what the browser reports about your key presses. It cannot read switch contacts, firmware settings, connection quality or the exact hardware cause.
code and key?code identifies the physical key position, while key shows the character or key value produced by the current layout. A hardware-oriented test needs both.
Retest that key slowly, try another app or computer, check keyboard software and firmware, then use official support or warranty options if it persists.
Some keys and shortcuts are handled by the browser or operating system before the page can see them, especially OS-level shortcuts, Fn combinations and some media keys.