- What is your CS2 sensitivity?
- 1.5
0.471
Open with these values0.471
Result: 0.471Divide your CS2 sensitivity by 3.1818 and you get the Valorant setting with the same cm/360. CS2 turns 0.022 degrees per mouse count at sensitivity 1, Valorant turns 0.070 — the quotient of those two numbers is the whole conversion. Keep your DPI unchanged, or the result no longer holds.
| What is your CS2 sensitivity? | Result |
|---|---|
| 0.500 | 0.157 |
| 1.000 | 0.314 |
| 1.500Your value | 0.471 |
| 2.000 | 0.629 |
| 2.500 | 0.786 |
| 3.000 | 0.943 |
0.471
Open with these values0.314
Open with these values0.251
Open with these valuesValorant sens = CS2 sens ÷ (0.070 ÷ 0.022)
It is 0.070 divided by 0.022, the Valorant yaw over the CS2 yaw, and the converter guide checked on 25 August 2026 carries both numbers. The 0.070 is a community measurement that Riot has never published, which is why this page keeps the quotient instead of a rounded 3.18.
The conversion holds the mouse travel for a full 360-degree turn identical at one unchanged DPI. Change the DPI in either game and the match is undone.
This page divides. Going back the other way you multiply by the same 3.1818, so a Valorant 0.314 lands at almost exactly 1 in CS2.
The centimetres per 360 degrees match to the decimal, so your flicks land where your arm expects them. Movement, recoil and field of view still differ between the games, and most players settle within five percent of the converted value.
I typed my CS2 sensitivity straight into Valorant.
That turns you roughly three times too far. Divide by 3.1818 first.
I changed my DPI to fine-tune the converted value.
The conversion assumes one fixed DPI, and changing it rescales everything again. Set the DPI once and adjust only the in-game number.
3.18 is a rule of thumb someone in the community made up.
The factor is an exact quotient, 35/11. What the community measured is the Valorant yaw of 0.070, not the arithmetic around it.
| CS2 sensitivity | eDPI at 800 DPI | Valorant sensitivity |
|---|---|---|
| 0.8 | 640 | 0.251 |
| 1 | 800 | 0.314 |
| 1.5 | 1200 | 0.471 |
| 2 | 1600 | 0.629 |
| 3 | 2400 | 0.943 |
| 10 | 8000 | 3.143 |
CS2 and Valorant scale the same sensitivity number differently, so typing your CS2 value straight into Valorant turns you roughly three times too far. Converting keeps the physical mouse travel for a full 360-degree turn identical, which is the part your arm has memorised.
It is the quotient of the two games' yaw constants: Valorant turns 0.070 degrees per mouse count at sensitivity 1, CS2 turns 0.022. Dividing them gives 35/11, or 3.181818 repeating.
The mouse travel for a 360-degree turn is mathematically identical, so your flicks land in the same place. The overall feel still differs a little because the two games handle movement, recoil and field of view differently. Most players end up within five percent of the converted value.
No, and you should not. The conversion assumes the same DPI in both games; changing it scales everything again and undoes the match. Set DPI once, leave it, and adjust only the in-game number.
Multiply instead of dividing: a Valorant sensitivity of 0.314 becomes 0.314 times 3.1818, which is almost exactly 1 in CS2. The factor is the same in both directions because it is one ratio.
Information, not professional advice.
Diese Seite gibt es auch auf Deutsch.
Zu Deutsch wechseln