SOCD test (Snap Tap checker)
This SOCD test shows whether your keyboard is cleaning opposing key presses, the feature sold as Snap Tap, Snappy Tappy or Rapid Tap, and which resolution mode it uses. You hold one key, tap its opposite, and the page reads exactly what the browser receives. Use it to confirm the feature is on, or to confirm it is off before a game that restricts it.
Key pair to test
Keys are matched by physical position, so the labels follow a US QWERTY layout. Switching pairs restarts the test.
Guided test
Keys as the browser sees them
released
released
- 1.Hold A.
- 2.Keep holding A. Tap D once and let go of D.
- 3.Let go of A.
Press Start, then follow the three steps. You will repeat them six times in total.
0 of 6 rounds done. Current: hold A, tap D
Use the physical keyboard you want to check and keep this tab focused. Each round advances on the key events themselves. Space, Backspace, slash and apostrophe are captured on this page so they cannot scroll or navigate away mid-test.
Result: Not tested yet
Run the guided test for a verdict. It needs 3 agreeing rounds in each direction, because one odd round is easy to cause by accident.
The result describes what the browser received, not which feature is switched on. Two keys counted as changing at the same instant when their event times were within 12 ms.
Free strafe
Alternate A and D the way you would in a game. Each change of direction is logged as an overlap (both keys held) or a gap (neither held). With SOCD cleaning on, every change should read about 0 ms. On a normal keyboard it doubles as a counter-strafe timing trainer.
Changes
0
Median
-
Within 12 ms
-
Last 5 seconds, newest on the right. A shaded column means both keys were held.
Recent changes
Press Start free strafe, then alternate the two keys.
Starting free strafe pauses the guided test. Pauses longer than a second between keys are not counted as a change.
What SOCD cleaning is
SOCD stands for Simultaneous Opposing Cardinal Directions. The term comes from fighting game controllers, where a stick or d-pad can report left and right at the same moment and the hardware has to decide what that means. A keyboard has the same problem with A and D, W and S, or the arrow keys, and some keyboards now settle it in firmware before the computer sees anything. Razer ships its version as Snap Tap, Wooting as Snappy Tappy, and SteelSeries as Rapid Tap.
The resolution modes
There is more than one way to resolve two opposite keys. The table shows what each mode does and what a browser receives when you hold A and then tap D.
| Mode | What the keyboard does | What the browser sees |
|---|---|---|
| No SOCD | Reports both keys as held. | A keydown for D while A stays down. |
| Last input priority | The newest key wins. | A up and D down together, then D up and a fresh A down together. |
| Neutral | Both keys cancel. | A up with no D down, then a fresh A down when D is released. |
| First input priority | The first key keeps control. | Nothing at all. |
| Absolute priority | One key always wins. | Last input behavior in one direction, nothing in the other. |
How this test detects them
You hold one key, tap the other while still holding the first, and release both, in both directions, three rounds each. The page records every keydown and keyup with the browser's own event timestamp and compares them. Last input priority has to show two signatures together. The old key's release and the new key's press land within 12 ms of each other, and when you let go of the new key the old one comes back on its own within 12 ms. Firmware sends both changes in one report, so they arrive together. A finger that slips off A while pressing D shows the first signature only, so it is not counted. The 12 ms window is wider than the 8 ms report interval of a 125 Hz keyboard, which matters if yours reports slowly; see polling rate explained.
First input priority is the awkward one, because it looks exactly like not pressing the second key. When nothing arrives, the page asks whether you pressed it, and only a yes counts. A verdict needs all three rounds in a direction to agree. If one key wins in both directions the result is absolute priority, and if the rounds disagree the page says it is inconsistent instead of guessing. Firefox with resist fingerprinting rounds timestamps to 100 ms, and the page warns you when every timestamp in a run is a multiple of that.
What this test cannot tell you
A browser only receives key events after the keyboard and the operating system have handled them. It cannot read the keyboard's settings, see which pair is configured, or measure how far a key is pressed. That rules out testing rapid trigger or actuation depth, which the guide on Hall effect switches and rapid trigger covers. It also means Wooting's Rappy Snappy, where the key pressed deeper wins, looks the same as last input priority here. The verdict describes the behavior in the events, not a brand feature.
A game can add its own handling of opposite directions, such as null binds or its own cleaning, and this page cannot see that. Missing keys have other causes too: a rollover limit can drop a key, which the ghosting test and the guide to NKRO explain. For the part of input delay a browser can see, use the latency test, and for unwanted double presses use the chatter test.
Games and rules
Some games and tournaments restrict this kind of input handling, so check the rules for yours. In August 2024 Valve announced that Counter-Strike 2 no longer allows it on official servers and that players using it can be kicked from a match. If you play something that restricts it, run the test to confirm the feature is off, and run it again after any change in the keyboard software. If you want it on, the same test confirms the keyboard is doing it. For help choosing a board for fast games, see best switches for gaming, and run the keyboard tester if a key does not seem to register at all.
Frequently asked questions
What does SOCD stand for?
Simultaneous Opposing Cardinal Directions. The term comes from fighting game controllers, where a stick or d-pad can report left and right at once. On a keyboard it means holding two opposite movement keys, such as A and D, at the same time. SOCD cleaning is the rule that decides what the keyboard reports when that happens.
Is Snap Tap the same thing as SOCD cleaning?
Snap Tap is Razer's name for its version of the feature. Wooting calls its version Snappy Tappy and SteelSeries calls its version Rapid Tap. By default these let the newest key win, which is called last input priority. SOCD is the general problem and last input priority is only one way of solving it, which is why this test reports a mode rather than a brand.
The result says no SOCD detected. Is the feature definitely off?
It means the browser saw both keys held together on the pair you tested, in every round, and a game receives the same thing from the keyboard. If you expected the feature to be on, check that it is enabled in the keyboard software, that the active profile includes it, and that the key pair it covers is the one you tested. Try the other pairs on this page. The test knows nothing about the keyboard beyond the key events it receives.
Why does first input priority need confirmation?
Because it produces no events at all. A keyboard that ignores the second key looks exactly like a visitor who never pressed it, or a key that has stopped working. When nothing arrives, the page asks whether you really pressed the key, and only a yes counts. If the same thing happens with a key you know works, the keyboard tester will show whether the key registers on its own.
Can this test check rapid trigger or actuation depth?
No. A browser receives key down and key up events and nothing about how far a key is pressed, so it cannot measure an actuation point or a rapid trigger setting. It can only see the result of SOCD cleaning on the events that reach it. Wooting's Rappy Snappy, where the key pressed deeper wins, produces the same events as last input priority, so this page cannot tell them apart.
Does it work on a non-QWERTY layout?
Yes. The page matches physical key positions, not the letters printed on the keys, so the pair you test is always the same two keys on the board. The labels on this page follow a US QWERTY layout, which means the key it calls A is the one in the QWERTY A position, whatever it is labeled on your keyboard.