SOCD & Snap Tap Test

What is this tool?

SOCD stands for simultaneous opposing cardinal directions — what happens when you hold A and press D without letting go. Some keyboards resolve the conflict in firmware: they release the held key for you so the new direction takes effect instantly.

That behaviour is marketed as Snap Tap or Rapid Trigger SOCD cleaning, and it is the reason CS2 now kicks players for it. This test tells you whether your keyboard is doing it, using only what the browser can observe.

It runs as a guided state machine: hold the first key, press the opposite, release the first, then hold still while it observes. Three trials are collected per pair before a verdict is offered.

How to use it

1. Start with the A / D pairThe page counts you in and then shows HOLD A. Hold it down and keep holding.
2. Press the opposite key while still holdingPress D without releasing A. This is the moment the whole test hinges on — what your keyboard does in the next few milliseconds is the answer.
3. Release the first key, then waitLet go of A while D stays down, then keep your hands still for the observation window. The tool records the timing of every transition with millisecond precision.
4. Repeat three timesRetry trial re-runs one that went wrong, Skip this trial moves past it. A trial where you released too early or lost focus is discarded rather than counted, so the sample stays clean.
5. Then test the other axisPress Test the W / S pair and repeat. Some keyboards apply SOCD handling to one axis only, so testing both is worth the extra minute.

What the results mean

Last-input priority (Snap Tap style)

The held key was released automatically within about 25 ms of the opposite press, with no action from you. If it also re-actuated when you released the opposite key, that is the full Snap Tap signature. This is the behaviour CS2 bans.

Neutral SOCD filtering

The opposite key only reached the browser after you released the first, with a human-scale gap of 80 ms or more. Consistent with a keyboard that cancels both inputs while they conflict.

First-input priority

The opposite key arrived in the same instant the first was released — within roughly 15 ms — as if it had been held back and then let through. The first key kept priority for as long as it was down.

No resolution

Both opposing keys reported as held at the same time until you released them. The browser saw no filtering at all, which is what an ordinary keyboard does.

Confidence, and INCONCLUSIVE

Agreement across all three valid trials gives HIGH confidence; two out of three gives MEDIUM. Fewer than two agreeing trials returns INCONCLUSIVE and asks for more runs rather than guessing.

What it can detect

• Automatic release of a held key when its opposite is pressed
• Re-actuation of the original key when the opposite one is released
• Which of the four resolution modes your keyboard's observed behaviour matches
• The fastest takeover gap seen, in milliseconds
• Whether the A / D and W / S axes behave the same way

Limits worth knowing

A browser can only report what the platform gives it. These are the honest boundaries of this page, so a result is never read as more than it is.

• The page has its own section titled “What a browser can and cannot see”, and it is the honest frame for every result here. A browser cannot inspect keyboard firmware, so verdicts are phrased as “consistent with” observed behaviour, never as a claim about what your firmware contains.
• A clean result does not prove your keyboard has no SOCD feature. It may be switched off, may apply to other keys, or may need a mode toggle to activate.
• Timing comes from browser event timestamps. Sub-millisecond firmware behaviour can be smoothed by operating-system and browser scheduling.
• Gamepads and controllers are not tested here. This measures keyboard key events only.

Tips

• Test both axes. Applying SOCD handling to A / D but not W / S is a real and common configuration.
• If you play CS2, run this before a match. A HIGH-confidence last-input result is the behaviour that gets players kicked.
• Retry rather than push through a fumbled trial — a discarded trial costs nothing, but a sloppy one lowers confidence in the verdict.

Troubleshooting

Related documentation

• KeyboardRapid Trigger TestTimes the full press-release-press cycle over five seconds and isolates the reset gap.
• KeyboardAnti-Ghosting TestChecks whether simultaneous key presses all arrive, and how many your board can hold at once.
• KeyboardCS2 Bind GeneratorBuild binds on a visual keyboard and export a clean autoexec.cfg that stays inside Valve's rules.
• KeyboardKeyboard Polling Rate TestMeasures the auto-repeat rate in Hz while you hold a key, with jitter and consistency.
• KeyboardOnline Keyboard TestThe keyboard tester on the home page — press keys, watch them light up.