Tools
Valorant to CS2 sensitivity
CS2 sensitivity = Valorant sensitivity × 0.07 ÷ 0.022. At the same DPI that is a multiply by about 3.182. Valorant 0.314 is CS2 1.000. Leave m_yaw at 0.022. Changing m_yaw to “fix” the conversion breaks the 360 you just matched.
Slider 0.01–5. Yaw 0.07°/count.
CS2 sensitivity
1.050
Matched cm/360
32.99 cm
Same DPI on both sides. Hipfire only. CS2 yaw 0.022°/count.
How this pair converts
new = old × (0.07 ÷ 0.022). Same DPI. m_yaw stays 0.022.
Valorant yaw is 0.07° per count at sensitivity 1.
Both games turn the same amount per mouse count, so the number carries over 1:1.
CS2 world FOV is fixed (90° horizontal on 4:3, about 106.26° on 16:9). Valorant is fixed 103° on 16:9. The converted slider matches the turn, not the picture width.
cm/360 = (360 ÷ (yaw × sensitivity × DPI)) × 2.54. The converter keeps that distance equal.
Valorant 0.330 at 1200 DPI, the pair that matches my Overwatch 3.5, is CS2 1.050. Use the number for a swipe test, not as a rank setting.
Common questions
What is the Valorant to CS2 sensitivity multiplier?
About 3.182 at the same DPI. Multiply your Valorant sensitivity by 0.07 ÷ 0.022, so Valorant 0.40 becomes CS2 1.273.
Should I change m_yaw in CS2?
No. Keep the default m_yaw of 0.022, which this converter is built on. Changing it throws off the conversion.
Does 4:3 stretched change my CS2 sensitivity?
No, your cm/360 stays the same. Stretched resolution can make horizontal movement feel faster because the image is wider, but the mouse distance for a full turn doesn't change.
Reverse this pair on CS2 to Valorant sensitivity. All seven games, including titles not listed here, stay on the shared converter. Measure a 360 in how to find your sensitivity.