CS2 TO VALORANT.
Switching from Counter-Strike 2 to VALORANT? Match a familiar mouse travel distance so your full-turn movement stays consistent across games.
Match your physical aim.
For default hip-fire values only. Custom yaw, scoped sensitivity and ADS settings are not included.
VALORANT
TARGET GAME SENSITIVITY
CS2 → VALORANT means a smaller number
At equal DPI, multiply CS2 sensitivity by 0.022 ÷ 0.07 ≈ 0.3143. That is why VALORANT sensitivity values usually look much lower than CS2 values.
SOURCE SENS × SOURCE DPI × SOURCE YAW
÷ (TARGET DPI × TARGET YAW)
At 800 DPI, CS2 sensitivity 1.2 corresponds to about VALORANT 0.3771 with an estimated 43.3 cm/360 in both games.
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 | VALORANT sensitivity | Physical cm/360 |
|---|---|---|
| 400 | — | — |
Use the number confidently.
- Start with CS2 hip-fire
Enter your current CS2 sensitivity; custom m_yaw settings require a different assumption.
- Set your mouse DPI
If you use 800 DPI in CS2 and 1600 DPI in VALORANT, the target sensitivity also halves.
- Fine-tune in the Range
Use VALORANT practice range and check how movement feels around different targets after matching full-turn distance.
What players ask.
Is the CS2-to-VALORANT multiplier always 0.3143?
Only when using the default yaw constants and identical mouse DPI. The calculator accounts for different DPI values.
What if I changed m_yaw in CS2?
The basic calculator assumes the default CS2 m_yaw of 0.022. For customized yaw, use the full converter and enter your own value.
Is eDPI equivalent across CS2 and VALORANT?
No. eDPI is only DPI × sensitivity; yaw is different across games, so compare cm/360 for cross-game physical rotation.