The fastest Rapid Trigger profile is not always the best profile.
If you set every key to 0.1 mm because a screenshot looked impressive, the keyboard may feel sharp for five minutes and then start causing tiny movement mistakes: unwanted A/D taps, canceled walk keys, missed crouch holds, or a defuse key that releases because your finger moved slightly.
I published the full source-backed version with FAQ schema, diagrams, references, and related browser tests here:
Rapid Trigger Keyboard Settings for CS2 and Valorant: Actuation, SOCD and Testing Guide
This DEV.to version keeps the practical tuning workflow.
Fast answer
Do not start by setting every key to 0.1 mm.
For CS2 and Valorant, a safer first profile is:
| Key group | Starting point |
|---|---|
| WASD actuation | 0.7 to 1.0 mm |
| Rapid Trigger reset | 0.2 to 0.5 mm |
| Other keys | 1.5 to 2.0 mm |
| CS2 SOCD / Snap Tap style features | Off before Valve official servers |
That profile is still fast, but it gives you room to find out whether your fingers are steady enough before you lower the numbers.
For CS2, keep Rapid Trigger and adjustable actuation separate from automation features such as SOCD, Snap Tap, Snappy Tappy, Rappy Snappy, null binds, or any feature that turns multiple movement actions into one automated result.
Rapid Trigger is not SOCD
This is the most important distinction.
Rapid Trigger changes when one key turns on and off. SOCD or Snap Tap changes what happens when two opposing keys are active at the same time.
The terms get mixed together because many Hall Effect and optical keyboards expose all of these settings in the same software panel.
They are different problems:
| Setting | What it changes | Common mistake |
|---|---|---|
| Actuation point | How far a key travels before it reports pressed | Setting every key too shallow |
| Rapid Trigger sensitivity | How much upward movement resets an active key | Making hold keys release accidentally |
| Continuous Rapid Trigger | Keeps dynamic reset behavior active deeper in the stroke | Enabling it before you can hold keys steadily |
| SOCD / Snap Tap | Resolves opposite directions such as A + D | Treating it like normal Rapid Trigger |
| Polling rate | How often the keyboard reports to the PC | Raising Hz without testing stability |
For a player, the difference is simple:
- Rapid Trigger can make one key release sooner.
- SOCD / Snap Tap can decide which direction wins when A and D overlap.
That second category is where rules become sensitive.
The profile I would start with
There is no universal best number. Finger pressure, keycap height, switch wobble, keyboard angle, wrist position, and game habits all change the result.
The first goal is not the lowest number. The first goal is:
Faster release without accidental input.
Here is the practical table I would use.
| 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, analog optical, or Rapid Trigger keyboards |
| 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 sharper movement but reliable ability control |
| Aggressive trained FPS | 0.3 to 0.6 mm | 0.1 to 0.2 mm | Per-key tuning only | You already tested for accidental releases |
| Avoid as default | 0.1 mm on every key | 0.1 mm on every key | Everything ultra-light | It looks fast, but often creates accidental input |
Set WASD first. Then decide whether W and S really need the same behavior as A and D.
Some players only enable Rapid Trigger on A and D because side-to-side strafing matters most. W, Shift, Ctrl, Space, E, push-to-talk, and ability keys often need to be held cleanly.
CS2 notes
CS2 is where the keyboard setting feels most obvious because movement accuracy and stopping behavior are tightly connected.
Wooting's CS2 guide recommends that new analog keyboard users start with:
- 0.7 mm WASD actuation
- 1.5 mm actuation for the rest of the keyboard
- 0.5 mm Rapid Trigger sensitivity
- Continuous Rapid Trigger off
- Tachyon Mode on for supported Wooting boards
That is a sensible baseline because it favors consistency before the lowest possible number.
The key I would protect in CS2 is E.
If your defuse/use key is set like a movement-tap key, a slight finger lift can interrupt a hold. The same logic applies to walk, crouch, jump, push-to-talk, and grenade binds.
A faster A/D release is useful. A canceled defuse is not.
Valorant notes
Valorant still benefits from clean press and release timing, but I would not treat it as a CS2 clone.
Movement, weapon accuracy recovery, ability use, and walk-key habits are different enough that a CS2 profile can feel too twitchy.
Start with the baseline FPS profile, then lower only A and D first.
If you get unwanted jiggle movement, stop walking while holding W, or accidentally cancel utility habits, raise the reset sensitivity slightly or disable Rapid Trigger on the key that must stay held.
The rule-safety part
The safest wording is:
Rapid Trigger is not the same feature as SOCD / Snap Tap.
Valve's August 19, 2024 CS2 input update warned against input automation that can include hardware-assisted counter-strafing on Valve official servers. It also told players to disable keyboard input-automation features such as Snap Tap before joining a match.
Wooting's April 2026 CS2 guide says Rapid Trigger, adjustable actuation, and Continuous Rapid Trigger are allowed, while Snappy Tappy and Rappy Snappy are prohibited on Valve servers.
For CS2, my default recommendation is simple:
- keep adjustable actuation if your keyboard supports it
- keep Rapid Trigger if it is tuned per key
- turn off SOCD, Snap Tap, Snappy Tappy, Rappy Snappy, null binds, and similar automation features before Valve official matchmaking
- check FACEIT, ESEA, LAN, school, or local tournament rules separately
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, avoid automation, and do not assume every keyboard feature is legal in every event.
Test before trusting the profile
A browser cannot measure physical switch travel depth. It cannot prove that a key is truly set to 0.4 mm or 0.1 mm.
It can still catch the problems that ruin a match:
- missed keys
- unexpected releases
- ghosted combinations
- rollover limits
- unstable timing after firmware or profile changes
The workflow I recommend:
- Create a separate FPS profile.
- Keep your normal typing profile deeper and less sensitive.
- Start with 0.7 to 1.0 mm WASD and 0.3 to 0.5 mm reset.
- Disable SOCD-style automation for CS2 before launching or queuing.
- Run a Keyboard Tester and press W, A, S, D, Shift, Ctrl, Space, E, R, number keys, and your game binds.
- Run a Keyboard Ghosting Test with real game combinations such as W + A + Shift, A + D, W + Space, and Shift + Ctrl.
- Run an N-Key Rollover Test after enabling any high-performance mode.
- Compare timing with an Input Latency Checker before and after polling or Tachyon-style changes.
- Play one repeatable drill in CS2 offline, deathmatch, Valorant range, or another movement routine.
Change one variable at a time. If you change actuation, Rapid Trigger sensitivity, SOCD, polling rate, and binds together, you will not know what caused the problem.
What a bad setting feels like
Rapid Trigger problems usually feel like "the keyboard is too sensitive," but the fix depends on which key is misbehaving.
| Symptom | Likely cause | Fix |
|---|---|---|
| Character stops moving forward while holding W | Reset is too sensitive on W, or finger pressure is unstable | Raise W reset to 0.3 to 0.5 mm, increase W actuation, or enable Rapid Trigger only on A/D |
| Accidental side steps or jiggles | A/D actuation is too shallow for your resting finger weight | Move from 0.1 to 0.4 mm, or from 0.4 to 0.7 mm, then retest |
| Defuse, interact, walk, or crouch cancels | Hold keys are set like movement tap keys | Disable Rapid Trigger on those keys or use 1.5 to 2.0 mm actuation |
| CS2 kick or automation warning | SOCD, Snap Tap, null bind, or hardware-assisted counter-strafe behavior may be active | Disable input automation in keyboard software and game config |
| Typing becomes error-prone | Gaming profile is too shallow for normal typing | Use separate typing and gaming profiles |
| Combos fail only when several keys are held | Rollover or ghosting limitation, not Rapid Trigger itself | Test ghosting and NKRO, then check firmware/input mode |
Brand names will differ
The category matters more than the brand name.
Wooting uses names such as Rapid Trigger, Continuous Rapid Trigger, Snappy Tappy, Rappy Snappy, and Tachyon Mode.
Razer uses names such as 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 name alone. Ask what the feature actually does:
- Does it change the press/release threshold of one key?
- Does it decide which direction wins when A and D overlap?
- Does it generate or collapse multiple actions into one result?
Those are different categories.
Official explainer
This Wooting video is a useful visual explanation of the basic Rapid Trigger idea:
Use it for the mechanical concept, then tune your own board with conservative per-key settings.
Sources I checked
- Wooting CS2 guide
- Wooting Rapid Trigger setup guide
- Valve CS2 input automation update
- RTINGS Hall Effect keyboard explainer
- RTINGS Rapid Trigger measurements
- Razer Snap Tap page
- Riot VALORANT anti-cheat support page
Final checklist
Before ranked:
- Use a separate FPS profile.
- Keep typing and utility keys less sensitive.
- Start at 0.7 to 1.0 mm WASD, not 0.1 mm everywhere.
- Tune A and D before touching every bind.
- Disable SOCD / Snap Tap style automation for CS2 official servers.
- Test your real movement combos before trusting the profile.
I maintain KeyboardTester.click, a browser-based hardware testing site. The full Rapid Trigger guide includes the diagrams, FAQ, sources, and related tests in one place:
