How the conversion works
Valorant turns you 0.07° per mouse count at sens 1; CS2 turns 0.022°. To keep the same physical movement, the sens scales by the ratio of those yaws: 0.07 ÷ 0.022 = 3.1818. Your DPI stays out of it as long as it's the same in both games.
Assumes the same DPI in both games; the number that transfers between games is the physical distance (cm/360). Most pros land between 25 and 55 cm.
Quick reference (at 800 DPI)
| Valorant sens | CS2 sens | cm/360 |
|---|---|---|
| 0.200 | 0.636 | 81.6 cm |
| 0.350 | 1.114 | 46.7 cm |
| 0.500 | 1.591 | 32.7 cm |
| 0.700 | 2.227 | 23.3 cm |
| 1.000 | 3.182 | 16.3 cm |
Why this switch is smaller than 3.18 makes it look
Tripling a number sounds like a big change to your aim. It is not, because the two games count sensitivity on different scales while their players end up moving their hands almost the same distance. Valorant pros mostly sit between 0.25 and 0.45 at 800 DPI, which works out to 65 cm and 36 cm per 360. CS2 pros mostly sit between 0.8 and 1.3, which is 65 cm and 40 cm. Those are effectively the same band.
So converting your Valorant sens does not drop you somewhere unusual in the CS2 population. It normally lands you mid-pack, and the multiplier is just the two scales disagreeing about what the number 1 means.
What the multiplier does not carry across
Your field of view changes, slightly. Valorant shows 103 degrees across a 16:9 screen and CS2 shows 106.26. With cm/360 matched, sweeping the CS2 screen from edge to edge therefore costs about 3% more mouse movement, because there is a little more world in view. Almost nobody names this difference out loud, and it is the usual reason a correctly converted sens still feels a touch slower on the first night. Give it a session before you change anything.
Your scoped sensitivity does not convert itself. Valorant applies the Scoped Sensitivity Multiplier to your hipfire number and CS2 applies zoom_sensitivity_ratio_mouse to its own. Both default to 1.0, so if you never touched Valorant's, leave CS2's alone and the AWP will behave like the Operator did. If you did change it, copy the same figure over rather than converting it, since both are multipliers of an already converted hipfire value.
You gain precision on this trip. Valorant's menu keeps three decimals; CS2 accepts five from the console or autoexec.cfg. Paste the full converted value rather than the rounded one you would get from typing into a slider.
What changes between Valorant and CS2
Valorant's hipfire value is Sensitivity: Aim, kept to three decimals. Scopes are governed by the Scoped Sensitivity Multiplier (default 1.0), which scales off hipfire. Pros mostly sit between 0.25 and 0.45 at 800 DPI.
CS2 reads sensitivity from the console or autoexec.cfg with up to five decimals, and raw input is always on. Scoped weapons use zoom_sensitivity_ratio_mouse (default 1.0). Pros mostly sit between 0.8 and 1.3 at 800 DPI, or double that at 400.
Coming from Valorant, expect your CS2 number to look three times bigger and to need more decimals: 0.35 becomes 1.11364, and CS2 keeps all five. Set zoom_sensitivity_ratio_mouse to match your Valorant scoped multiplier (both default to 1.0) so AWP flicks feel like Operator flicks.
Questions
How do I convert Valorant sensitivity to CS2?
Multiply your Valorant sens by 3.1818 (the ratio of the games' yaw values, 0.07 / 0.022). At the same DPI this keeps your physical mouse movement identical: 0.5 in Valorant becomes 1.591 in CS2.
Does my Valorant scoped or ADS sensitivity carry over to CS2?
Not by itself. In Valorant, scopes use the Scoped Sensitivity Multiplier, a factor applied to your hipfire sens (default 1.0). In CS2, scoped weapons use zoom_sensitivity_ratio_mouse, also a factor on hipfire (default 1.0). Convert hipfire with the multiplier above, then set CS2's scoped value so it matches how you have Valorant set up.
Do I need the same DPI in both games?
The simple multiplier assumes the same DPI. If you change DPI too, use the full formula: target sens = (source DPI × source sens × source yaw) ÷ (target DPI × target yaw). The converter above handles this automatically.
A converted number is a starting point; your hands confirm it. Run a couple of free rounds and feel whether the distance is right.
Test It Free in the TrainerMore conversions
All conversions live on the sensitivity converter. For finding a sens from scratch rather than porting one, read How to Find Your Ideal Mouse Sensitivity.