What Are Snap Tap and SOCD? Diagrams, Game Rules and Analog Input

GearLab Hardware Column・Last updated: October 10, 2026

After Razer introduced "Snap Tap" in 2024 and Wooting followed with "Snappy Tappy," this feature, living in keyboard firmware, started a debate: Valve prohibited it on official CS2 servers and ESL banned it at LAN events, while other games and tournaments don't restrict it. What does it actually change, and why is it considered unfair? Can you still use your magnetic keyboard? And if you don't play shooters, where do magnetic switches help?

This article explains how SOCD works with interactive diagrams, lets you measure your own key overlap in the browser, summarizes the current rules by game and tournament, and finally shows how the "how deep is the key pressed" signal can help in racing games and everyday use.

1. How it works: what SOCD is and where it runs

SOCD stands for Simultaneous Opposing Cardinal Directions: holding A and D, or W and S, at the same time. Fighting-game controllers have to define what happens then, but a normal keyboard just reports "both keys are down" and lets the game decide; most games cancel the two directions out and the character stops.

Why does that matter in shooters? In games like CS2 you usually need to slow down before shooting accurately. The common technique is counter-strafing: while running left with A held, tap D to brake in the other direction. The hard part is timing: when you press D, A often isn't fully released yet, and during this overlap the game sees "directions cancelled," so acceleration the other way only starts once A is released.

Snap Tap (last input priority) lets the keyboard handle it: the moment you press D, the firmware treats A as released and sends only D. Wooting's Snappy Tappy works the same way, and its Rappy Snappy variant instead lets the deeper-pressed key win during the overlap (which needs an analog keyboard).

Try the timeline below: A is held first, D is pressed at 100 ms, and you set how late A is released. Switch modes and watch the direction the game actually receives (the bottom lane). "Play" runs the sequence in slow motion.

Where this logic runs along the input path is the heart of the controversy. Snap Tap runs in keyboard firmware; null binds (game scripts) and AutoHotkey-style macros run in the operating system or game config. To the game the effect is similar: one key action causes two effects, "release A" and "press D."

Valve's position is that it prohibits automation where a single input performs multiple player actions, whether it comes from hardware or scripts. That's why the CS2 rule covers keyboard features and null binds alike.

2. Test: measure your own key overlap

Rather than trust someone else's numbers, measure your own. The test below records the time between pressing the new key and releasing the old one: your key overlap. Click the test box, hold A, press D, then release A; then do the reverse (hold D, press A, release D). Repeat a few times as if counter-strafing.

How to read it: a positive overlap means you released the old key after pressing the new one, which is normal for human hands; the value varies with practice, actuation distance and polling rate, and there's no "right answer." If your overlap is close to 0, either your technique is very clean or your keyboard's SOCD feature is on, since it releases A for you the moment you press D. A web page can't tell which, so check your keyboard software; you can also toggle the feature and test again to compare.

3. What do games and tournaments say?

Positions differ and rules keep changing. The table below is what we found in public sources in October 2026; check the latest official rules before relying on it:

Sources: Dexerto: Valve cracks down on CS2 input automation, ESL Pro Tour announcement, Wooting: Rappy Snappy Tappy. Policies change; rely on official announcements.

• How to check whether it's on: Razer calls it Snap Tap and Wooting calls it Snappy Tappy (SOCD); other vendors use similar names, usually in the key or game-mode settings. Comparing the test above with the feature on and off is the most direct check.
• Kicked by mistake? The CS2 "input automation" kick is commonly caused by this kind of feature still being on; turn it off and reconnect. You don't lose any other keyboard features.
• Practice by hand anyway: even if a game allows it today, rules can change. Manual counter-strafe timing never goes to waste.

4. Beyond FPS: analog input on magnetic keyboards

Many people lump magnetic switches and Snap Tap together, but they're different things. Magnetic (Hall effect) switches can measure how deep a key is pressed, not just pressed or not; Snap Tap is firmware logic and doesn't need analog sensing at all. That depth signal is useful in games outside FPS.

Try the simulation below: the slider is the key's press depth. On the left is a conventional keyboard (it counts as "pressed" past the actuation point, so it's only 0 or 100%); on the right is analog input (the output follows the depth). "Slow corner demo" animates it.

• Racing games: a conventional keyboard gives full throttle or nothing. Some magnetic keyboards (Wooting, for example) offer a gamepad mode that maps key depth to stick-like analog values, which allows finer throttle and steering in racing games that support controllers. You need to enable that mode in the keyboard software, and results vary by game.
• Walk and run: in games that support analog movement, a light press can map to walking and a deep press to running, with no Shift needed.
• Typo prevention: for daily typing, keys you tend to hit by accident (the Windows key, Caps Lock) can be set to need a deeper press.

To learn more about Rapid Trigger and actuation settings, see What is NKRO? The Science of Magnetic Switches & Rapid Trigger, which has an interactive comparison.