Keyboard lab · SOCD and counter-strafe

Snap Tap & SOCD Test

Shows whether your keyboard lets go of A for you when you press D, and times your own counter-strafes.

Snap Tap benchA and D only · keys are not stored

Hold A. Without letting go, press D. Then release both. Test the keyboard profile you actually play on — many boards only do this in a game mode.

    —
    Not run yet

    The result names the behaviour, not the feature. We can see that a key was released for you; we cannot see which setting did it.

    Browser timestamps are deliberately coarsened, but the two cases are not close: a hand needs tens of milliseconds to lift a key, a keyboard needs none. Riot and Valve have both moved against keyboards that do this in competitive play, and tournament platforms set their own rules — check the one you queue on.

    Keep and share this result

    Save the numbers to your private Device Passport in this browser, or copy a card that shows exactly what was measured.

    Open passport

    Nothing is uploaded unless you contribute. Cards and links contain only the numbers shown above.

    Words on this page
    SOCD (Snap Tap)

    Simultaneous opposing cardinal directions: what a keyboard does when two opposite keys, such as A and D, are held at once. "Last input wins" releases the older key for you, which is what Snap Tap and similar modes are sold on.

    What the result actually measures

    The bench records A and D as they reach the page. A keyboard with SOCD handling sends a real key-up for A a fraction of a millisecond after D goes down, while your finger is still on A; a hand needs tens of milliseconds to lift, so the two are an order of magnitude apart. The second module times the gap between A coming up and D going down across ten counter-strafes.

    Measurement boundary: The page sees what the keyboard sends, not which setting sent it: Snap Tap, an SOCD mode, a driver macro or a software tool all look the same. Browser timestamps are coarsened for privacy, which does not matter at this scale but rules out sub-millisecond claims.

    How to interpret the output

    Last input wins

    A release for A arrived a fraction of a millisecond after D went down while A was held: the keyboard resolved the pair for you. That is the behaviour Snap Tap and SOCD modes are sold on.

    Both directions registered

    The keyboard sent both keys and let the game decide. Counter-strafing is then on your fingers, which is how most competitive rules want it.

    Counter-strafe gap

    A small, steady positive gap is the skill. Negative gaps mean both directions were held for a moment; in most shooters those cancel into no movement for that instant.

    Troubleshooting unexpected results

    Nothing is recorded

    Click inside the test area first so it has keyboard focus, and use the physical A and D keys — the page reads key positions, so AZERTY and other layouts work too.

    The result changes between runs

    Many keyboards apply SOCD only in a game mode or on one profile, and some only for keys you assigned. Test the exact profile you queue with.

    Frequently asked questions

    Is Snap Tap allowed in competitive games?

    Riot and Valve have both moved against keyboards that release a key for you in competitive play, and tournament platforms set their own rules. Check the rules of the game and platform you queue on before you rely on it.

    Can the page tell which keyboard feature did it?

    No. It sees a key-up that no finger made; Snap Tap, a vendor SOCD mode, a driver macro and a software tool all produce the same signal.

    Does it work on AZERTY?

    Yes. The test reads the physical key positions where A and D sit on a US layout, so on AZERTY press Q and D.

    Are my keystrokes stored?

    No. Only A and D are listened to, only while a test is running, and nothing leaves the page.