Rapid trigger resets a key the instant you lift slightly, so you can press again without releasing fully. Pick key A, tap it as fast as you can in bursts, and the page measures every release-to-press gap. Very short gaps that a standard switch's reset travel cannot produce are the signature of rapid trigger. Switch to key B to compare a second key, switch type or actuation setting. Repeat the keyboard latency test a few times for a more reliable reading.
First key you press becomes the test key
-- ms release → press
Last hold -- ms
Key A: tap the key you want to test.
Release-to-press gap histogram (ms, 2 ms buckets; A teal, B amber)
Tap key A in fast bursts; eight or more taps give a verdict.
Need 8+ taps
Need 8+ taps
Run the rapid trigger test on your keyboard to see how quickly an analog switch resets between taps. This free browser benchmark records your cycle time in ms, converts it into tap speed, and shows whether your gaming keyboard delivers the quick response its spec sheet promises. Tap one key on the keyboard, read the number, change a keyboard setting, then compare keyboard runs.
Click inside the test box so the page captures your keyboard, then tap one key such as A, D or Space as fast as you can with minimal finger travel. The tool times every press-to-press gap, so quick key re-actuation shows up as a short bar, and plots each cycle on a timeline. Choose a key you already configured in your keyboard software, because a key left on fixed actuation gives a mechanical reading instead of a true Hall Effect benchmark. Treat it as a quick diagnostic you can run on any keyboard before you touch another setting. A quick run of the keyboard layout detector often shows whether the cause is the keyboard or a setting.
Cycle time is the gap, in milliseconds, between one actuation and the next. Flutter CPS is the same measurement turned into taps per second, so a shorter gap means a higher number. Low latency between presses signals a fast reset, and the clicks per second readout lets you compare two runs on the same keyboard at a glance.
Some keyboard testers let you drag a threshold slider that decides which gaps count as faults. Lower values are stricter and higher values more forgiving, so retest at two settings before you trust a result. Watch the key health score as well: it falls with every flagged key, and a clean score tells you the keyboard's responsiveness is consistent.
A standard keyboard switch has fixed points: it actuates at one depth and must climb past a higher reset line before it can fire again. That gap is reset hysteresis, and it caps how fast you can re-press a key. Rapid trigger removes it from the keyboard. A Hall Effect sensor on the PCB reads the magnetic flux from a neodymium magnet in the stem, so the firmware always knows the exact stem position. It fires on any small downward move and resets on any small upward move, whatever the depth on any keyboard. Magnetic switches built this way track position continuously instead of crossing fixed lines. Try the keyboard debounce test next if you want another angle on how your keyboard behaves.
The actuation point is the depth where a press registers, and the reset distance is how far the key must rise before it can register again. On a fixed keyboard switch that distance is large; with rapid trigger it shrinks to about 0.1 mm of key travel. The lag it adds follows simple physics:
$$\text{reset delay (ms)} = \frac{\text{reset gap (mm)}}{\text{finger speed (mm/s)}} \times 1000$$
At a lift speed of 80 mm/s, a 1.0 mm gap costs 12.5 ms, while a 0.1 mm reset costs 1.25 ms, so you recover 11.25 ms of input delay on every release. Across a whole keyboard, that adds up.
A faster switch reset means faster stops. When you let go of a movement key, the game hears it sooner, so small finger motions turn into direct on-screen control. This performance gain is the entire point of the feature, and on the page it appears as a shorter gap between taps, which is the number to compare between runs.
Not every keyboard switch can do this. The table applies the formula above to example reset gaps at 80 mm/s; treat the gaps as typical values, because your keyboard hardware may differ.
| Switch type | Typical reset gap | Reset delay at 80 mm/s | Reset hysteresis |
|---|---|---|---|
| Hall Effect rapid trigger | 0.1 mm | 1.25 ms | None |
| Analog optical | 0.3 mm | 3.75 ms | None |
| Speed mechanical | 0.8 mm | 10 ms | High |
| Standard mechanical | 1.2 mm | 15 ms | High |
| Membrane / rubber dome | 1.8 mm | 22.5 ms | Severe |
Optical switches and magnetic designs reset almost instantly because nothing has to cross a fixed line. Mechanical switches with a metal contact leaf need a bigger gap, and a membrane keyboard sits at the bottom of the table because its membrane layer collapses a rubber dome and must release almost fully. Contact surfaces also oxidize with age, which matters again in the chatter section below.
Here is one run on a magnetic board in a rapid trigger analog switch test, tapping Space for eight cycles. The cycle times were 46, 49, 52, 47, 55, 50, 49 and 54 ms, an average of 50.25 ms with a best of 46 ms. These numbers illustrate how to read the output, not what your keyboard hardware will score.
Divide 1000 by the gap in ms:
$$\text{CPS} = \frac{1000}{\text{gap (ms)}}$$
The best tap gives 1000 ÷ 46 = 21.7 CPS, and the average gives 1000 ÷ 50.25 = 19.9 CPS. The 9 ms spread between the fastest and slowest cycles shows steady flutter rather than one lucky burst, so judge a keyboard on its average, not its peak. Consistent performance matters more than a single record.
Gamers get the most from this keyboard feature on keys that start and stop movement. In an FPS, better aim control comes from stopping the moment you decide to, so tune movement keys first on your keyboard and leave utility keys alone. Wooting, Razer and SteelSeries all ship rapid trigger keyboards, and a hot-swappable board lets you compare switches without soldering.
Set your WASD keys to 0.1 mm for both actuation and reset, which suits counter-strafing and jiggle peeks in tactical shooters, since each counter-strafe ends sooner. Rhythm games like osu! reward the same quick re-press. Keep grenade and ability keys at 1.0 mm or deeper, because a resting finger on an ultra-light key causes accidental presses.
Temperature swings and magnetic interference make Hall Effect baselines drift. Run your keyboard software's calibration tool every few weeks, once per keyboard, and update drivers first so the readings are reliable. If the readings still wander afterward, test again before blaming the keyboard or its hardware. An uncalibrated board gives uneven tap gaps, so recalibrate before you time the reset.
I just moved my A and D keys to a 0.3 mm reset and want proof that the setting helps before I queue for ranked matches. The decision is simple: keep 0.3 mm, or go to 0.1 mm and risk accidental presses. So I focus the test box, tap A ten times with the lightest finger motion I can, and read the gaps.
The ten gaps come back as 58, 61, 57, 64, 59, 62, 60, 66, 58 and 63 ms. They sum to 608 ms, an average of 60.8 ms, and 1000 ÷ 60.8 gives 16.4 CPS. The fastest tap (57 ms) is 17.5 CPS and the slowest (66 ms) is 15.2 CPS. I cross-check the first three gaps with a phone stopwatch on a slow-motion clip and they agree within a couple of milliseconds.
The number I watch is the reset step. By the formula, a 0.3 mm gap at 80 mm/s costs 3.75 ms and a 0.1 mm gap costs 1.25 ms, so tightening the setting should save about 2.5 ms per tap. That predicts an average near 58.3 ms, or 17.2 CPS, and a retest within a millisecond or two of that tells me the new setting took effect.
| Reset setting | Reset delay at 80 mm/s | Expected average gap | Expected CPS |
|---|---|---|---|
| 0.3 mm (measured baseline) | 3.75 ms | 60.8 ms | 16.4 |
| 0.1 mm (predicted) | 1.25 ms | 58.3 ms | 17.2 |
One trap: a chatter test at the common 80 ms default flags all ten of those legitimate gaps, so for rapid tapping I set the threshold near 40 ms. The estimate also assumes my finger lifts at 80 mm/s; at 40 mm/s the reset delays double, and the saving from 0.1 mm grows to 5 ms.
My judgement call: the 2.5 ms gain is real but small next to the 9 ms spread between my fastest and slowest taps, so finger consistency matters more than the setting. I take 0.1 mm for A and D only, and keep ability keys at 1.0 mm.
Rapid trigger timing measures how fast a key can legitimately fire twice, while a keyboard chatter test looks for the opposite: a key that fires twice by mistake. Chatter test tools flag any pair of presses closer than a threshold, commonly 80 ms, which makes it a quick key fault diagnosis for aging keyboards. Rapid trigger rewards short intervals and a chatter test punishes unintended ones, so run a keyboard chatter test after you shorten the reset gap, because ultra-sensitive settings can mimic a fault. Hall Effect keyboards rarely suffer switch aging, but a keyboard chatter test still catches firmware quirks.
Mechanical metal contact can oxidize or tire after millions of presses, so one press produces several make-and-break cycles. Cherry MX and Gateron switches are known to show it near end of life, especially on WASD. Dust and moisture inside the keyboard create tiny conductive paths on the PCB, and membrane boards wear out their conductive layer. Hall Effect designs have no metal contact at all, so key chatter is far less likely.
Start by cleaning the keyboard with compressed air, keyboard case open. If your firmware supports it, raise the debounce time a few milliseconds, which often removes double presses. A hot-swappable keyboard lets you replace the faulty switch, while a soldered one needs repair or warranty service. Run the keyboard chatter test again afterward to confirm.
Yes. Rapid trigger is legal in CS2 (Counter-Strike 2) and Valorant, and in major esports events, because every press still needs real finger motion and nothing is automated. Snap Tap is different: it overrides opposing inputs in software, which is why it drew bans. Check your own tournament's rulebook and your keyboard vendor's notes before you compete.
Reset speed is only one link in the chain. A keyboard with a 1000 Hz polling rate reports to your PC every millisecond, while 8000 Hz cuts that to 0.125 ms, and total latency also includes the switch, the firmware and the USB cable. Use the physical test above for the switch and a separate reporting-rate checker for the USB side. Good performance needs both. Weak hardware, a worn switch or a loose cable shows up as uneven cycle times on any keyboard.
Indirectly. It cannot see travel, but it can time how quickly a key fires again after releasing. Gaps a standard switch cannot physically produce point to rapid trigger. Treat the verdict as strong evidence, not a measurement of distance.
Rapid trigger may be off in the software, set to a large sensitivity, or your taps are lifting fully. Set sensitivity to 0.1 to 0.3 mm and try barely lifting.
Very light linear switches with short travel can get close. Check the gaps-under-15-ms count: a handful can be noise, dozens are not.
Yes. At 125 Hz every timing is quantised to 8 ms, so set the board to 1000 Hz or higher before testing.