How the conversion works

CS2 turns you 0.022° per mouse count at sens 1; Valorant turns 0.07°. To keep the same physical movement, the sens scales by the ratio of those yaws: 0.022 ÷ 0.07 = 0.3143. Your DPI stays out of it as long as it's the same in both games.

view rotation after 500 mouse counts, at sens 1

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)

CS2 sensValorant senscm/360
0.640.20181.2 cm
1.120.35246.4 cm
1.600.50332.5 cm
2.240.70423.2 cm
3.201.00616.2 cm

What you lose in the rounding, measured

This is the direction where precision goes away. CS2 holds five decimals and Valorant holds three, so a CS2 sens of 1.8 converts to 0.56571 and Valorant stores 0.566. That is a difference of about 0.05%. On a 30 cm turn it is a third of a millimetre of mouse travel, which is far below the point where a hand notices anything, so round it and stop thinking about it.

Valorant also has no config file. There is nothing to paste: the number goes into Settings, General, Mouse Sensitivity: Aim, typed rather than dragged, because the slider will not give you three decimals on its own.

Your CS2 sens is probably already a normal Valorant sens

The number shrinks to under a third, which reads like a big drop until you convert both pro ranges into physical distance. CS2 pros mostly run 0.8 to 1.3 at 800 DPI, or 65 cm to 40 cm per 360. Valorant pros mostly run 0.25 to 0.45, which is 65 cm to 36 cm. You are moving into a population that aims at the same speed you already do.

Two things do change. Valorant renders 103 degrees across a 16:9 screen against CS2's 106.26, so with cm/360 matched you cross the Valorant screen with about 3% less mouse movement and the game can feel marginally quicker for a night. And Valorant's Scoped Sensitivity Multiplier takes over the job of zoom_sensitivity_ratio_mouse: both default to 1.0 and both multiply hipfire, so carry your CS2 figure across unchanged rather than running it through the converter.

What changes between CS2 and Valorant

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.

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.

Your CS2 sens shrinks by about two thirds and Valorant rounds it to three decimals, so 1.8 lands on 0.566 rather than 0.56571. That rounding is under 0.2%, well below anything you can feel. Carry zoom_sensitivity_ratio_mouse across as Valorant's Scoped Sensitivity Multiplier; if you left both at 1.0, there is nothing else to change.

Questions

How do I convert CS2 sensitivity to Valorant?

Multiply your CS2 sens by 0.3143 (the ratio of the games' yaw values, 0.022 / 0.07). At the same DPI this keeps your physical mouse movement identical: 1.6 in CS2 becomes 0.503 in Valorant.

Does my CS2 scoped or ADS sensitivity carry over to Valorant?

Not by itself. In CS2, scoped weapons use zoom_sensitivity_ratio_mouse, also a factor on hipfire (default 1.0). In Valorant, scopes use the Scoped Sensitivity Multiplier, a factor applied to your hipfire sens (default 1.0). Convert hipfire with the multiplier above, then set Valorant's scoped value so it matches how you have CS2 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 Trainer

More 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.