Mouse Double Click Test
Find out whether your mouse is firing two clicks from one press — every press and release is timed inside this page, and nothing leaves your browser.
The time axis is compressed on purpose: a 4 ms gap and a 4-second gap have to share one strip, so segment width follows a saturating curve rather than a linear scale. Read the printed numbers, not the pixel widths.
| Button | Clicks | Suspected | Rate | <20 ms | Shortest gap | Shortest press | Verdict |
|---|
Everything is measured in this page: click timings are never uploaded, never stored between visits and never sent anywhere. The pad needs a real mouse — keyboard activation produces a click with no press or release timing to measure.
⏱ Your system's double-click interval
Separate from switch chatter: this measures the window your operating system treats as one double click. Click twice in the box, then again with a slightly longer pause each time, until a pair stops being counted as a double.
No pairs recorded yet.
The true threshold sits between those two numbers, so the result is an estimate bracket, not an exact figure — the browser only tells us whether a pair was counted, never what the setting is. Windows defaults to 500 ms (Control Panel → Mouse → Buttons); macOS ships around the same (System Settings → Mouse). Keep the mouse still between the two clicks, because moving more than a few pixels cancels the double on most systems.
How to run it, and how to read the result
- Click 30+ times with the button you suspect, at a normal, comfortable pace. Do not butterfly- or drag-click while testing — those techniques really can produce sub-70 ms gaps, and the tool will honestly flag them.
- Read the trace left to right. Each click is one dip. The upper line means the button is released; the lower line means it is held. The number above the upper line is the gap since your last release, and the number below the lower line is how long you held the button.
- A healthy click looks like a wide upper segment (200 ms or more), a 50–150 ms lower segment, then another wide upper segment. Chatter looks like a press, a hair-thin gap, then another press — drawn in red.
- Check the verdict. It stays blank until one button has 20 timed gaps, because a single flag proves nothing. Healthy means zero flags; early signs means one lone flag, or under 3% of gaps flagged; failing means two or more flags and 3% or higher.
- Test the other four buttons, then repeat the whole thing while dragging: press inside the pad, move the mouse a few centimetres, release. Some worn switches only misbehave under sideways load, which is exactly why files get dropped mid-drag.
- If the verdict is failing, press Copy report before you contact support. The click count, flag count and shortest recorded gap are the reproducible evidence a warranty claim needs.
What chatter actually is, and why it appears overnight
Inside almost every mouse button is a tiny mechanical switch — an Omron D2FC or one of its many clones — where a sprung copper leaf snaps against a fixed contact. That snap is not clean. The leaf physically bounces off the contact several times before it settles, opening and closing the circuit for a few hundred microseconds. Every switch does this, brand new, out of the box.
The mouse's firmware hides it with a debounce window: once it sees an edge, it ignores any further change on that input for a fixed time, typically 8–20 ms. A healthy switch settles in well under a millisecond, so the debounce swallows the bounce whole and the computer sees one clean click.
Wear changes the timing, not the mechanism. Contact surfaces oxidise, the leaf loses tension, and the plating pits. The bounce that used to last 0.3 ms starts lasting 5 ms, then 15 ms. Nothing at all happens until the bounce outlasts the debounce window — and then the extra edge escapes and becomes a real second click reported to the operating system. That is why chatter seems to appear from nowhere and then get worse fast: you are watching a threshold being crossed, not a slope.
The same wear also causes the mirror-image fault. A worn contact can bounce on release too, so the button momentarily reports as let go in the middle of a drag — the file lands in the wrong folder, the window snaps back, the text selection collapses. This page flags that separately as a runt press: a press shorter than 12 ms, far below anything a finger produces.
Reading the gap distribution
- Under 20 ms — no finger releases and re-presses a switch this quickly. There is one deliberate exception: drag-clicking works by dragging a fingertip across the shell so friction vibrates the switch, and that produces genuine sub-millisecond gaps on a perfectly healthy mouse. If you are clicking normally and this column has counts, the switch is firing on its own.
- 20–70 ms — suspicious. Chatter reaches this band as it worsens, but so do drag-clicking and butterfly-clicking. Click normally and re-test before concluding anything.
- Over 100 ms — that's you. Deliberate fast clicking lives here, and so does every normal double click.
- Shortest press under 12 ms — release bounce, the drag-dropping variant of the same fault.
When it isn't the switch
If every button flags at once, five switches did not fail on the same afternoon. Look at these instead: macro or remapper software with a double-click binding, an accessibility "click assist" or sticky-click feature, a remote desktop / VM / screen-share layer re-injecting input, a KVM switch, a failing USB cable or hub, or a wireless mouse on a low battery in a congested 2.4 GHz room. Try the mouse on a different machine — the fault follows the hardware, and only the hardware.
If one button flags and the rest are clean, that is the classic dying switch. Your options, cheapest first: raise the debounce time in the mouse's own configuration software if it exposes one (Razer Synapse, Glorious Core and VIA-compatible firmware do; most stock drivers do not) — 12–20 ms buys weeks or months at the cost of that much extra click latency; open the switch and burnish the contact, which is fiddly and temporary; or replace the switch, which is a few pennies of parts and the only permanent fix. Hot-swappable mice make that a 30-second job. And if the mouse is under warranty, claim it — chatter is a recognised defect and the report from this page is the evidence they ask for.
Before you trust a failing verdict
- Browsers deliberately blunt their clock. Chrome rounds timestamps to 0.1 ms, Firefox and Safari to 1 ms. A gap printed as 0 means "under one millisecond", not exactly zero. The measured resolution of your browser's clock is printed under the pad.
- Some browsers still navigate on the side buttons. The pad cancels the default action, but a few builds handle back/forward above the page and will move you through history anyway. If the page changes when you press button 4, that is the browser, not your mouse.
- Trackpads and touchpads report as a mouse but have no mechanical click switch on most laptops. Tap-to-click can still produce genuine doubles — that is a driver sensitivity setting, not a failing part.
- Releases outside the window are discarded. If you press inside the pad and the window loses focus before you let go, that click is dropped rather than recorded with a bogus multi-second hold time.
- Suspecting the sensor or the USB link instead? The mouse polling rate test measures how often your mouse actually reports, which is a different fault with different symptoms.
FAQ
How do I know if my mouse is double-clicking on its own?
Click the pad above 30 or more times at a normal pace with the button you suspect. Every press and release is timed to the millisecond, and any second press that lands within 70 ms of the previous release is flagged red. A finger cannot press again that fast after letting go, so a red flag during ordinary clicking means the switch fired twice on its own.
What causes a mouse to double click?
The metal contacts inside the click switch physically bounce apart for a fraction of a millisecond every time they close. Mouse firmware hides that with a debounce window, usually 8 to 20 ms. As the switch wears, the bounce lasts longer, and once it outlasts the debounce window the extra edge escapes as a second click. It is a mechanical fault inside the switch, not a Windows or driver problem.
Can I fix mouse chatter with software?
Only as a stopgap. Some mice expose a debounce or click-latency setting in their configuration software, and raising it to 12 or 20 ms hides a mildly worn switch at the cost of that much extra click latency. It buys weeks or months, it does not repair the contacts. The real fix is replacing the switch, or replacing the mouse.
What is a normal gap between two separate clicks?
For deliberate repeat clicking most people land between 120 and 250 ms from release to next press, and the fastest sustained normal clicking sits around 60 to 80 ms. Genuine switch chatter looks nothing like that: the second press almost always arrives less than 20 ms after the release, and often under 5 ms. That is why the sub-20 ms count is shown separately.
My mouse only double clicks when I drag something. Is that the same fault?
Yes, and it is usually the same switch. A worn contact often chatters on release rather than on press, so the button briefly reports as let go part-way through a drag and the file, window or text selection is dropped. Test it by pressing inside the pad, moving the mouse, then releasing — any press shorter than 12 ms is flagged as a runt press.
Is a recorded double-click rate enough for a warranty claim?
Usually, yes. Support teams want something reproducible, and a click count, a suspected double-fire count and the shortest recorded gap is exactly that. Use the copy button to grab a plain-text summary, add your mouse model, the purchase date and which button is affected, and send it with the claim.