Fast answer: do not start by setting every key to 0.1 mm. For CS2 and Valorant, a safer first Rapid Trigger profile is WASD at 0.7 to 1.0 mm actuation, Rapid Trigger reset around 0.2 to 0.5 mm, and 1.5 to 2.0 mm on the rest of the keyboard. For CS2, keep SOCD, Snap Tap, Snappy Tappy, Rappy Snappy, null binds, and other input-automation features off before joining Valve official servers.
I’d compare a saved baseline profile with one changed setting, then repeat the same holds and combinations. Unexpected releases or repeats are observations to investigate; they do not prove the reset or actuation value is too low. Browser timing is a comparison of this input path, not physical switch latency. WASD movement & strafe trainer · keyboard tester · keyboard latency test
If you are setting up a Hall Effect or analog optical keyboard for CS2 or Valorant, the hard part is not finding the lowest number in the software. The hard part is finding a setting that feels faster without making movement unpredictable. The common mistake is copying a 0.1 mm profile, then wondering why the character stutter-steps, stops walking, cancels defuse, or sends tiny movement inputs you never meant to send.
Start with settings that are fast but still predictable, then change one movement setting at a time. If a profile makes strafing feel sharper but also causes accidental A/D taps, early crouches, missed stops, or unwanted ability inputs, it is not ready for ranked yet.
Before You Change the Numbers
Rapid Trigger tuning is not about making every key as sensitive as possible. The better goal is to make movement keys release quickly while keeping hold keys reliable. Treat the keyboard like a set of per-key controls, not one global speed slider.
If reaching movement and ability binds comfortably matters more than switch travel, compare one-handed gaming keyboards with joysticks before making the whole board more sensitive.
If a new profile feels fast but creates accidental movement, missed holds, or unpredictable stops, raise the sensitivity back up. A slightly slower setting that behaves every time is better than an aggressive setting you cannot control.
Rapid Trigger, Actuation, Continuous RT and SOCD Are Different
Before changing a profile, separate the terms. If you do not separate them, you can accidentally copy a risky setting while thinking you are only making the keys faster.
| Term | What it changes | Practical risk |
|---|---|---|
| Actuation point | How far a key travels before the keyboard reports "pressed." | Too shallow can cause accidental presses from resting fingers. |
| Rapid Trigger sensitivity | How much upward movement resets the key after it is active. | Too sensitive can briefly release movement when your finger pressure changes. |
| Continuous Rapid Trigger | Lets Rapid Trigger behavior continue without returning above the original actuation point. | Can feel excellent for trained players, but it makes sloppy finger pressure more visible. |
| SOCD / Snap Tap | Decides what happens when opposite keys such as A and D are both active. | Can cross into input automation rules, especially in CS2 on Valve official servers. |
| Polling rate | How often the keyboard reports input to the PC. | Higher Hz is not useful if it causes instability or if the game/system path cannot benefit. |
Safe Starting Settings for CS2 and Valorant
There is no universal "best" number because finger pressure, switch wobble, keycap height, desk angle, wrist position, and game habits all change the result. A useful profile is the one that improves release timing without adding unintended input. The safest method is to start conservative, then lower settings only after a repeatable test.
| Profile | WASD actuation | Rapid Trigger reset | Other keys | Use when |
|---|---|---|---|---|
| Baseline FPS | 0.7 to 1.0 mm | 0.3 to 0.5 mm | 1.5 to 2.0 mm | You are new to Hall Effect, optical analog, or Rapid Trigger boards. |
| CS2 conservative | 0.6 to 0.8 mm | 0.2 to 0.5 mm | E, Shift, Ctrl, Space at 1.2 to 2.0 mm | You want cleaner counter-strafing without accidental defuse, walk, or crouch releases. |
| Valorant conservative | 0.7 to 1.0 mm | 0.2 to 0.4 mm | Abilities, walk, crouch, push-to-talk at 1.5 to 2.0 mm | You want sharp movement but still need reliable ability and walk-key control. |
| Aggressive trained FPS | 0.3 to 0.6 mm | 0.1 to 0.2 mm | Per-key tuning only | You have already tested for accidental releases and can hold keys steadily. |
| Avoid as default | 0.1 mm on every key | 0.1 mm on every key | Everything ultra-light | Looks fast in screenshots, but often creates accidental input for real players. |
Practical rule: set WASD first, then decide whether W and S really need the same Rapid Trigger behavior as A and D. Some players only enable Rapid Trigger on A and D because side-to-side strafing matters most, while W, Shift, Ctrl, and E must often be held cleanly.
Checks I Would Run Before Keeping a New Profile
I’d compare the same holds and combinations with the saved baseline and changed profile, then repeat them in the actual game. The following are checks to perform, not measured results from a particular test keyboard. WASD Movement & Strafe Trainer
- Watch a sustained movement hold for unexpected release events, then compare the baseline and another input path.
- Record A/D overlap as received by the page and compare it with the game and any input-priority setting.
- If an interact or defuse action cancels, compare the game binding and received hold separately before attributing it to reset sensitivity.
CS2 Profile Notes
CS2 is where the keyboard setting feels most obvious because movement accuracy and stopping behavior are tightly connected. Wooting's official CS2 guide recommends new analog keyboard users start around 0.7 mm WASD actuation, 1.5 mm for the rest of the keyboard, 0.5 mm Rapid Trigger sensitivity, Continuous Rapid Trigger off, and Tachyon Mode on for supported Wooting boards. That is a sensible baseline because it favors consistency before the lowest possible number.
If you play CS2, be careful with the E key. Very sensitive Rapid Trigger on the defuse/use key can interrupt a hold if your finger lifts slightly. The same applies to walk, crouch, jump, push-to-talk, and grenade binds. A faster movement key is useful; a canceled defuse is not.
Valorant Profile Notes
For Valorant, start from the keyboard manufacturer’s supported profile and change one key or setting at a time. If a hold or movement behaves unexpectedly, compare the baseline, game binding and input path before deciding whether a deeper setting or disabling Rapid Trigger helps.
CS2, Valorant, SOCD and Rule Safety
The safest wording is this: Rapid Trigger is not the same feature as SOCD / Snap Tap. Rapid Trigger changes when a single key turns on and off. SOCD / Snap Tap changes how the keyboard resolves two active directions.
CS2 warning: Valve's August 2024 update says certain movement or shooting input automation, including hardware-assisted counter-strafing, can be detected on Valve official servers and result in a match kick. Valve also specifically warned users to disable keyboard input-automation features such as Snap Tap before joining a match.
For CS2, my default recommendation is simple: keep adjustable actuation and Rapid Trigger if your keyboard supports them, but turn off SOCD, Snap Tap, Snappy Tappy, Rappy Snappy, null binds, and any setting that turns multiple movement actions into a single automated result. Rules can also differ between Valve matchmaking, FACEIT, ESEA, LAN events, and school or local tournaments, so do not copy a "safe" claim from a forum without checking your actual platform.
For Valorant, Riot's public support wording is broader: unauthorized hardware or software that gives an unfair advantage can lead to permanent bans. Treat that as the floor. Avoid macros and automation, check current tournament rules, and do not assume a feature is legal in every event just because it appears in keyboard software.
The Testing Workflow Before You Queue
A browser shows received key events and their timing. It does not measure travel in millimetres, raw USB polling or physical switch latency. Unexpected input can involve the profile, finger movement, firmware, mapping, focus or another software layer; compare one change under the same conditions.
- Create a separate FPS profile. Keep your normal typing profile deeper and less sensitive.
- Start conservative. Use 0.7 to 1.0 mm WASD and 0.3 to 0.5 mm reset before going lower.
- Disable SOCD-style automation for CS2. Do this before launching or queuing, not after a warning.
- Run the WASD Movement & Strafe Trainer. Perform 60 seconds of A/D counter-strafe drills and watch the live key telemetry strip to confirm you are not overlapping A and D or accidentally triggering W/S.
- Run the Keyboard Tester. Hold W, A, S, D, Shift, Ctrl, Space, and E for a full 5 seconds each with natural resting finger posture to confirm no micro-releases occur.
- Run the Keyboard Ghosting Test. Hold real game combinations: W + A + Shift, A + D, W + Space, Shift + Ctrl, and your ability keys.
- Run the N-Key Rollover Test. Confirm simultaneous input reporting after enabling any 8,000 Hz or Tachyon-style performance mode.
- Compare received-event timing on the same browser setup. Do not interpret this as physical switch, USB or full input-to-screen latency. Input Latency Checker
- Queue on a pad some evenings? Give it the same pre-match check with a controller tester — stick drift and worn buttons throw aim off just as fast as a bad Rapid Trigger profile.
- Play a repeatable drill. Use an offline CS2 map, deathmatch warm-up, Valorant range, or a movement routine. Watch for accidental releases more than raw speed.
Troubleshooting: What Your Bad Setting Feels Like
Use symptoms to choose a comparison rather than assign a cause. Save the baseline and change one setting; also check game binds, focus, connection and firmware when behavior differs.
| Symptom | Likely cause | Fix |
|---|---|---|
| The page or game stops receiving the intended hold | Profile, finger movement or input handling may contribute | Compare a deeper/default profile and another application |
| An unwanted side input appears | Resting contact, profile or mapping may contribute | Record which events arrive, then compare one profile change |
| A hold action cancels | The game action or received input may have changed | Compare game bindings and browser hold events separately |
| CS2 kick or automation warning | SOCD, Snap Tap, null bind, or hardware-assisted counter-strafe feature may be active. | Disable input automation in keyboard software and game config before queuing again. |
| Typing has unexpected input | Profile, repeat settings, focus or mapping may contribute | Compare the typing profile and another application |
| A combination is incomplete | Rollover, remapping or OS/browser/game interception may contribute | Test individual keys and the exact combination in another supported path |
Brand Names in Software & October 2026 Rapid Trigger Keyboard Prices
The original Razer Tartarus Pro already has advertised Rapid Trigger support, so that feature alone is not a reason to replace it. Our Tartarus V2 Pro upgrade and binding checklist separates the wider actuation range from the changed thumb controls and the combinations to verify in your game.
If you are deciding whether to replace an original Wooting 80HE, our 80HE+ hardware comparison and upgrade-cost guide separates the buying decision from profile tuning. Both generations support Rapid Trigger; a new model name alone does not establish a noticeable performance gain.
The names differ, but the categories are similar. Wooting uses terms such as Rapid Trigger, Continuous Rapid Trigger, Snappy Tappy, Rappy Snappy, and Tachyon Mode. Razer uses Rapid Trigger Mode and Snap Tap. Other Hall Effect boards may say RT, dynamic reset, FlashTap, Speed Tap, last input priority, neutral SOCD, or key priority. Do not tune by brand name alone. Ask what the feature actually does.
For one current hardware example, see our source-based Razer Huntsman V3 HE Magnetic analysis. It separates adjustable-actuation and Rapid Trigger features from input-priority controls and explains what a browser can and cannot verify after delivery.
The controls themselves are also moving off the desktop: Wallhack's K-001 puts actuation and Rapid Trigger adjustment on a physical dial instead of a software slider. After Wallhack cut the pre-launch price from $360 down to $279 ahead of its October 2026 preorder window, our Wallhack K-001 preorder decision guide covers the confirmed specs, the updated price context, and what to verify on delivery day.
| Keyboard / Keypad | Oct 2026 Price (USD) | Switch & Actuation Range | Software / Tuning Interface | SOCD / Priority Name |
|---|---|---|---|---|
| Wooting 80HE | $199.99 (PCR ABS) / $289.99 (Zinc) | Lekker L60/L45 v2 Hall Effect (0.1–4.0 mm, 0.15 mm RT) | Wootility Web (no background app required) | Snappy Tappy / Rappy Snappy |
| Wooting 60HE+ | $174.99 (Prebuilt) | Lekker L60 Hall Effect (0.1–4.0 mm, 0.15 mm RT) | Wootility Web | Snappy Tappy / Rappy Snappy |
| Razer Huntsman V3 Pro TKL / Mini | $219.99 (TKL) / $179.99 (Mini) | Gen-2 Analog Optical (0.1–4.0 mm) | Razer Synapse 4 + onboard shortcuts | Razer Snap Tap |
| Razer Huntsman V3 Pro Low-Profile TKL 8KHz | $229.99 | Low-Profile Analog Optical (0.1–3.2 mm, 8,000 Hz) | Razer Synapse 4 | Razer Snap Tap |
| Keychron Q1 HE | $219.00 | Gateron Double-Rail Magnetic (0.2–3.8 mm) | Keychron Launcher Web | Last Key Priority (LKP) / Snap Action |
| Wallhack K-001 | $279.00 (cut from $360 MSRP) | Custom Hall Effect (0.1–4.0 mm, 8,000 Hz wired) | Physical hardware dial + web utility | Hardware / Web SOCD toggle |
| Keychron C0 HE 8K / Epomaker HE30 | $59.99 / $49.99 | One-handed Hall Effect (0.1–3.8 mm, 8,000 Hz wired) | Web configurator | LKP / SOCD toggle |
RTINGS describes the core Hall Effect trade-off clearly: supported keyboards can define where the key actuates in its travel, but very low actuation can make accidental input more likely.
Official Rapid Trigger Video Explainer
This Wooting video is a short official visual explainer for the basic Rapid Trigger idea. Use it for the mechanical concept, then come back to the settings table above for the CS2 and Valorant workflow.
Watch: Rapid Trigger Explained
References for Settings and Rules
- Wooting CS2 guide for official CS2 Rapid Trigger baseline settings and feature definitions.
- Wooting Rapid Trigger setup guide for actuation, sensitivity, per-key Rapid Trigger, and Continuous Rapid Trigger behavior.
- Valve Counter-Strike 2 input automation update for the CS2 automation and Snap Tap warning.
- RTINGS Hall Effect keyboard explainer for adjustable actuation and accidental-press trade-offs.
- RTINGS Rapid Trigger measurements for release-latency context and measurement caution.
- Razer Snap Tap page for how last-input priority works on supported Razer keyboards.
- Riot VALORANT anti-cheat support page for Riot's general hardware/software cheating policy language.
Related Keyboard Tests
Related Guides
- Best Mechanical Keyboard 2026: 7 Gaming Picks Tested
- Keyboard Switch Types Guide for Gaming
- Keyboard Polling Rate Test: Check Keyboard Hz Online
- 5 Best TMR Gaming Keyboards 2026 Compared (vs HE)
- Input Latency Checker: Keyboard and Mouse Delay Guide
FAQ
What Rapid Trigger settings should I start with for CS2?
Start with WASD around 0.7 mm actuation, Rapid Trigger sensitivity around 0.5 mm, Continuous Rapid Trigger off, and the rest of the keyboard around 1.5 mm. Then lower WASD and reset in 0.1 to 0.2 mm steps only if accidental movement does not appear.
What Rapid Trigger settings should I use for Valorant?
For Valorant, start with the same conservative FPS profile: WASD around 0.7 to 1.0 mm, Rapid Trigger around 0.2 to 0.5 mm, and deeper actuation for ability, walk, crouch, and push-to-talk keys. Valorant movement benefits from clean release timing, but accidental inputs are more costly than a slightly slower setting.
Is Rapid Trigger banned in CS2?
Valve has prohibited hardware or script automation that turns multiple actions into one input on official CS2 servers, including Snap Tap-style input automation. Rapid Trigger and adjustable actuation are different because they change the press and release threshold of a single physical key, but you should keep SOCD, Snap Tap, Snappy Tappy, Rappy Snappy, and null-bind-style automation disabled before queuing.
Is Rapid Trigger the same as SOCD or Snap Tap?
No. Rapid Trigger changes when one key resets as you lift it. SOCD or Snap Tap decides what happens when two opposing keys, usually A and D, are active at the same time. That difference matters for game rules and for troubleshooting movement problems.
Can an online keyboard tester measure 0.1 mm actuation depth?
The browser can show which key events it receives, including unexpected presses or releases. It cannot measure physical travel depth or uniquely attribute an event pattern to actuation, reset, a switch fault or raw USB timing. Compare the same setup and actual game.
Is 0.1 mm actuation always best?
The minimum actuation value is not automatically useful for every key. Try the manufacturer’s supported starting profile, check accidental input and stable holds, and change one setting at a time.
Should I turn Rapid Trigger on for every key?
Usually no. Start with WASD or only A and D, then add other movement keys only if you can hold them reliably. Avoid very sensitive Rapid Trigger on defuse, walk, crouch, push-to-talk, and ability keys until you prove those keys do not release accidentally.
Final test before ranked: open the Keyboard Tester, hold your real movement combos, and watch for missed or accidental key events. A profile that tests cleanly is worth more than a screenshot with the lowest possible numbers.


Reader discussion
Comments
Share what worked, what did not, or what you would test next. Every comment is reviewed before it appears.
Loading approved comments…
Leave a comment
No account or sign-in is required. Links and HTML are not accepted.