One click, two clicks registered. Or the opposite: you mash the button and half of it goes missing. If either has ever happened to you, there’s a good chance debounce time is involved. Most people never even know the setting exists.

Do not worry, it’s a lot simpler than it sounds.

Nobody can give you one perfect number, because every switch behaves a bit differently. This is a rough guide, based on what makers and guides suggest:

Debounce time	What it feels like	Who it suits
About 0 to 2 ms	Fastest response, but a real chance of double clicks	Drag clicking, very fast clicking, people who have tested their switch
About 2 to 4 ms	Quick and mostly clean	Casual gaming, and competitive players who like it snappy
About 4 to 8 ms	Safe against accidental double clicks	Everyday use and relaxed gaming
9 ms and up	Feels slower, can swallow fast clicks	Rarely worth it if responsiveness matters

We suggest 0 ms for highly competitive play, 2 to 4 ms for casual gaming, and 4 to 8 ms for relaxed gaming. Some guides recommend 4 ms or higher to avoid double clicks. And some other guides call 4 to 8 ms normal for regular clicking, and says drag clicking and butterfly clicking often use 1 ms or less.

Think of dropping a ball on the floor. It does not just land, it bounces a few times before it settles. The metal contacts inside a mechanical switch do something similar when they meet. They flutter for a split second, and your mouse can read that flutter as several clicks.

So the mouse waits, ignores the flutter, and counts one click. That wait is debounce time. If you are curious how the switch is built, what are mouse switches goes through it.

It’s in milliseconds. You click, a tiny timer starts, and anything that button sends before the timer ends gets thrown away.

Short timer: quick repeated clicks pass through. Long timer: noise gets blocked better, but two real clicks close together can get blocked as well. Glorious points out that a higher debounce time can make it harder to reach a high clicks-per-second count.

Probably not, and I would be surprised if it did. A few milliseconds is a sliver of one frame on a gaming monitor, and your own reaction time is far bigger. Nobody loses a fight over 2 ms versus 4 ms.

Double clicks are what really get on your nerves. A debounce time that’s too short can turn clean clicks into messy ones, and that hurts more than a millisecond ever could. If that’s what you are dealing with, our double-click guide goes through the causes and fixes.

Plenty of mouse software has a debounce setting, but the names and ranges differ. These examples come from the makers’ own pages. They are documentation, not our testing.

The Glorious Model O 2 Wireless lists a range of 4 to 16 ms, adjustable in software, with a default of 10 ms. Pulsar’s mouse software has a Debounce Time (ms) setting for double clicking, and its support page says to raise the value if the mouse double clicks on a single press. LAMZU’s software, as described on Fnatic’s support page, goes from 0 ms to 20 ms in its Key Response Time section.

One detail from Pulsar’s page stuck with us: at over 10 ms, it says the switches are considered defective. So if you need a huge number just to stop double clicks, the switch is probably the problem and not the setting.

Start with the default. No double clicks? Try going a little lower. Double clicks? Go a little higher. Gravastar suggests steps of under 2 ms.

Then test. Click a few dozen times, slow and fast, in a click tester or any app that shows each click. If you see double entries or missing clicks, step back. Our testing guide has a few simple routines. Oh, and jot down your old value before you change it.

We ran the team tests using the Asus ROG Harpe Ace Aim Lab Edition and the GravaStar Mercury M2 to see how their switches handle aggressive input. With the Asus Aim Lab mouse, we pushed the debounce values down to 4ms and even tested at 2ms to leverage its fast optical switches, while on the GravaStar Mercury M2, we experimented between 4ms and 8ms to find the right balance for its mechanical setup. The entire focus was to monitor how both sensors and switches behave when subjected to rapid-fire clicking, tracking exactly where the hardware hits its limit.

The testing quickly highlighted the trade-offs of lower latencies. On the Asus Aim Lab edition, dropping down to 2ms did not cause double-clicking due to the optical design, but we did notice a couple of missed clicks during extreme angle snaps where the bounce mask was too tight. On the other hand, when the GravaStar Mercury M2 was dialed down to 4ms, it started registering noticeable double clicks during jitter tests, which forced us to bump it to 8ms where the double-clicking stopped entirely, though it felt just a fraction less snappy.

Debounce time is a short pause that lets your mouse ignore noise after a click. Too short risks double clicks, and too long makes the mouse feel slower and can swallow fast clicks. Around 4 ms is a sensible place to start for most players, and you can adjust from there.

Shopping? A debounce setting is nice, but it should not be the reason you buy. Look at the build, the switches and how the clicks feel. What makes a good gaming mouse covers that, and our beginner buying guide keeps it simple if you’re new.

---

Everything on this page comes from our team’s own experience, along with feedback from Amazon buyers and other verified users. We try to be straight about what we have seen, but experiences differ, and something that felt great to us would not necessarily feel the same to you. Fit, feel and habits are personal, so treat our advice as a starting point, not a promise.

We also pay attention to what real owners keep saying, not just what a spec sheet promises. If something looks great on paper but users keep flagging the same issue, we will mention it.

---