Valorant to CS2 Sensitivity: The Exact Conversion and Why It Feels Different
Convert your Valorant sensitivity to CS2 using the verified 3.18x yaw factor. Includes the formula, a conversion table, and notes on why CS2 still feels different after converting.
Multiply your Valorant sensitivity by 3.1818 to get the CS2 equivalent. That is the entire conversion. A Valorant sens of 0.4 at 800 DPI becomes 1.273 in CS2 at the same DPI.
The rest of this post explains why that number is correct and why CS2 might still feel off even after you paste it in.
The formula
CS2 Sensitivity = Valorant Sensitivity × (0.07 / 0.022)
CS2 Sensitivity = Valorant Sensitivity × 3.1818
Valorant uses a yaw value of 0.07 degrees per count. CS2 uses 0.022. Dividing one by the other gives you the factor. This assumes you have not changed m_yaw in CS2 from its default.
Conversion table
| Valorant sens | CS2 sens | cm/360 at 800 DPI |
|---|---|---|
| 0.20 | 0.636 | 81.6 |
| 0.30 | 0.955 | 54.4 |
| 0.35 | 1.114 | 46.7 |
| 0.40 | 1.273 | 40.8 |
| 0.50 | 1.591 | 32.7 |
| 0.60 | 1.909 | 27.2 |
| 0.80 | 2.545 | 20.4 |
cm/360 = 360 / (0.07 × Valorant sens × DPI) × 2.54. These values give you identical cm/360, meaning your mouse travels the same physical distance for a full turn in both games.
Why CS2 still feels different
Matching turn distance is not the same as matching game feel. After converting, you might notice:
Movement acceleration. CS2 has velocity-based acceleration on player models. Counterstrafing matters. In Valorant, movement stops almost instantly. This changes how you track targets even though your sensitivity is equivalent.
Sub-tick input. CS2 processes input differently from Valorant's 128-tick servers. Some players report slight input "smoothing" that affects micro-adjustments.
Crosshair placement habits. Valorant angles tend to be tighter with smaller peek windows. CS2 has wider site takes where you swing further. The same sens on paper can feel slow in CS2 because you are covering more area.
Scoped sensitivity. AWP zoom in CS2 uses a different multiplier than Valorant's Operator. Convert hipfire first, then adjust your scoped sens separately.
What to do after converting
- Open a deathmatch or aim_botz workshop map.
- Do five slow 180-degree turns. Check if you land on target consistently.
- Do five fast flicks to corners. If you overshoot, drop by 0.05 in CS2. If you undershoot, raise it.
- Play for 15 minutes before deciding to change it again.
eDPI comparison
eDPI only works within the same game because the yaw differs. But it is useful for quick comparisons:
- Valorant 0.4 at 800 DPI = eDPI 320 (Valorant scale)
- CS2 1.273 at 800 DPI = eDPI 1018 (CS2 scale)
Both produce the same physical turn distance despite the eDPI numbers looking different. This is why copying eDPI between games does not work.
Use the converter
Instead of doing this math manually every time, use the Mansone sensitivity converter. Select Valorant as source, CS2 as target, and paste your value. The tool also shows eDPI for both games when you enter your DPI.
If you are also switching DPI, the DPI converter recalculates your new in-game sens to match. And if you just changed monitors, run the FOV calculator to make sure your field of view still fits your viewing distance.
Yaw values (Valorant 0.07, CS2 default m_yaw 0.022) checked September 2026. If you find a discrepancy, report it.
Common questions
- What is the Valorant to CS2 conversion factor?
- Multiply your Valorant sensitivity by 3.1818. A Valorant sens of 0.4 becomes approximately 1.27 in CS2.
- Why does CS2 feel different even after converting?
- Different movement acceleration, tagging speed, and sub-tick rate affect how aim 'feels' beyond raw sensitivity. The conversion matches turn distance, not game feel.
- Do I need the same DPI in both games?
- Yes. The conversion assumes your mouse DPI stays constant. If you change DPI between games, the factor no longer applies.
Topics: sensitivity, CS2, Valorant, conversion, yaw