VALORANT TO CS2.
Moving from VALORANT to Counter-Strike 2? Match how far your mouse travels for one full turn, instead of copying the same in-game slider number.
Match your physical aim.
For default hip-fire values only. Custom yaw, scoped sensitivity and ADS settings are not included.
Counter-Strike 2
TARGET GAME SENSITIVITY
VALORANT uses a different hip-fire yaw
With commonly used defaults, VALORANT uses 0.07° per count per sensitivity point while CS2 uses 0.022°. At equal DPI, multiply VALORANT sensitivity by roughly 3.1818 to preserve cm/360.
SOURCE SENS × SOURCE DPI × SOURCE YAW
÷ (TARGET DPI × TARGET YAW)
At 800 DPI, VALORANT 0.35 corresponds to about CS2 1.1136. Both have an estimated 46.7 cm per full 360° turn.
Compare common target DPI settings.
Changing DPI changes the in-game sensitivity needed to preserve the same cm/360. These values update with your inputs above.
| Target DPI | Counter-Strike 2 sensitivity | Physical cm/360 |
|---|---|---|
| 400 | — | — |
Use the number confidently.
- Check hip-fire sensitivity
Read your VALORANT general mouse sensitivity, not scoped or ADS multipliers.
- Keep or change DPI
Leave DPI unchanged for the easiest comparison. Enter a different target DPI if you are switching mice.
- Use the CS2 result
Apply the calculated number in Counter-Strike 2, then verify with one slow mouse swipe in a practice map.
What players ask.
Why not use 0.35 in both games?
The games use different rotation constants for mouse input. 0.35 in CS2 produces a much longer cm/360 than 0.35 in VALORANT at the same DPI.
Will the crosshair feel identical?
The same physical 360° distance does not guarantee identical perception: field of view, weapons, scopes, display setup and game movement can change how aiming feels.
Does it also convert scoped sensitivity?
No. This calculator only matches common default hip-fire yaw. Scoped and zoomed sensitivity settings may need separate tuning.