What debounce actually is

A mechanical mouse switch is two metal contacts. When they meet, they don’t touch cleanly — they bounce: for a few milliseconds the circuit flickers open/closed/open/closed before settling. Left unfiltered, one press would register as a burst of presses.

Debounce is the firmware’s answer: after the first edge, wait a fixed window — commonly 4–16ms depending on vendor and setting — and ignore everything until it expires. The press you feel is real; the delay is the firmware making sure it was only one.

That makes debounce an honest trade: every millisecond of bounce tolerance is a millisecond added to input lag, and every millisecond removed is a millisecond closer to phantom clicks.

The double-click fault — the signature failure

Switch contacts wear. The spring loses tension, the contact surface pits and oxidizes, and a switch that once settled in 2ms starts bouncing for 8–20ms — straight past the debounce window it was designed around. The symptom everyone knows: single clicks that double-register — files open twice, drags drop mid-move, burst fire where you clicked once.

It’s progressive and it’s mechanical: frequency climbs over weeks, and it survives driver reinstalls because it was never software.

How the fault shows up in a click test

Run our click test and watch two numbers:

• Ignored presses. Sub-25ms press pairs are the debounce floor catching impossible timings — a healthy finger and a healthy switch almost never produce them, so a count that keeps climbing on single clicks is the fault announcing itself.
• Dwell range. A healthy press holds 50–120ms fairly steadily. A bouncing switch produces erratic dwell — some presses releasing almost instantly as contact flickers, others normal. A dwell range of e.g. 4–180ms across deliberate identical presses is suspicious.

One honest caveat before you blame hardware: a web page sees delivered events, so a genuinely erratic result still deserves a second test on another machine or a desktop click-counter before you order a soldering iron.

The fixes, in order of effort

1. Raise debounce in vendor software — if your mouse exposes it (Razer, some Pulsar/Lamzu tools do), 10–20ms masks early-stage bounce for free, at a small latency cost.
2. OS double-click window — widening the OS’s double-click speed lets phantom second-presses land outside it: cosmetic relief for file managers, useless for games.
3. Compressed air / cleaning — occasionally effective when debris, not wear, is the cause. Cheap enough to try once.
4. Switch replacement — the real fix. Omron/Kailh switches are a few dollars; the solder work is a 20-minute job for anyone comfortable with an iron, or any repair shop.
5. Hot-swap boards — some mice take socketed switches; future replacements become plug-in work.
6. Warranty/RMA — if the mouse is young, double-clicking is a known defect class. Use it.

If you’re picking settings rather than fixing a fault: don’t run 0ms debounce on a mechanical switch — you’re borrowing speed from your future self. And for the rest of the latency picture, the input lag chain shows where debounce’s milliseconds sit relative to everything else.

Frequently asked questions

What is mouse debounce time?

A deliberate delay — typically 4–16ms — where the mouse firmware waits for a mechanical switch's contacts to stop bouncing electrically before counting the press. Without it, one physical press would register as several. Some mice expose the setting; 0ms buys a hair of speed at the cost of double-clicks as the switch wears.

Why is my mouse double-clicking on single presses?

Classic worn-switch symptom. The microswitch's spring contacts degrade with use and bounce worse than they did new — events that once settled inside the debounce window now spill past it and register as extra presses. It's progressive: occasional double-clicks that get more frequent over weeks are the switch, not software.

Can I fix a double-clicking mouse without opening it?

Sometimes, temporarily: raise the debounce time in the vendor software if offered (trades a few ms for a wider bounce tolerance), or adjust the OS double-click speed so phantom seconds land outside the window. Compressed air into the button gap occasionally clears debris-related bounce. The durable fixes are switch replacement, hot-swap sockets, or warranty — switches are wear parts.

How do I test my mouse for double-click faults?

Two signatures to look for: clicks registering pairs of presses a few milliseconds apart (one physical press → two counted), and erratic dwell time — press durations jumping between near-zero and normal. Our click test shows both: sub-25ms presses get counted as 'ignored', and the dwell range exposes unstable actuation.