This Valorant to CS2 sensitivity converter takes the sensitivity you use in Valorant and returns the CS2 value that produces the same physical turn — the same cm/360 — on the same mouse DPI. Valorant runs on a yaw of 0.07 degrees per count and CS2 on 0.022, so the number changes even though your arm movement does not. Example: Valorant 0.4 at 800 DPI is 40.82 cm per full turn; the matching CS2 value is 1.27.
0.4 × (0.07 / 0.022) = 1.27. Set CS2 to 1.27 and both games compute to about 40.82 cm per 360.Both games turn your view by a fixed number of degrees for every count the mouse sends, scaled by the sensitivity value you type in. That per-count constant is the yaw: Valorant uses 0.07, CS2 uses 0.022. Your DPI stays the same, so the only thing that has to change is the in-game number.
cm/360 = (2.54 × 360) / (DPI × sensitivity × yaw)Valorant sens × 0.07 = CS2 sens × 0.022CS2 sens = Valorant sens × (0.07 / 0.022) = Valorant sens × 3.182The multiplier is 3.182, so every Valorant value becomes a larger number in CS2. That is not a faster sensitivity: CS2 moves fewer degrees per count, so it needs a bigger multiplier to produce the same turn.
Eight common Valorant values, the CS2 value that matches each one, and the shared cm/360 at three DPI settings. Every row is computed with the formula above; the cm/360 columns are the same for both games by construction, because that is the quantity the conversion preserves.
| Valorant sens | CS2 sens | cm/360 at 400 DPI | cm/360 at 800 DPI | cm/360 at 1600 DPI |
|---|---|---|---|---|
| 0.2 | 0.64 | 163.29 cm | 81.64 cm | 40.82 cm |
| 0.25 | 0.80 | 130.63 cm | 65.31 cm | 32.66 cm |
| 0.3 | 0.95 | 108.86 cm | 54.43 cm | 27.21 cm |
| 0.35 | 1.11 | 93.31 cm | 46.65 cm | 23.33 cm |
| 0.4 | 1.27 | 81.64 cm | 40.82 cm | 20.41 cm |
| 0.5 | 1.59 | 65.31 cm | 32.66 cm | 16.33 cm |
| 0.7 | 2.23 | 46.65 cm | 23.33 cm | 11.66 cm |
| 1.0 | 3.18 | 32.66 cm | 16.33 cm | 8.16 cm |
In VALORANT, your aim sensitivity lives under Settings > General > Mouse. The slider labeled Sensitivity: Aim accepts values from 0.1 up to 100 with two-decimal precision, so you can dial in something like 0.35 without rounding issues. VALORANT uses a fixed 103-degree horizontal field of view with no FOV slider at all, which simplifies cross-game conversions because there is no FOV variable to match.
Scoped sensitivity is handled by a separate Scoped Sensitivity Multiplier that scales from 0 to 1. At 1.0 your scoped aim moves at the same speed as hip-fire; lower values slow the reticle while zoomed. When converting from another title, the most common mistake is ignoring this multiplier and only matching the base value. That leaves your Operator or Marshal scope feeling wildly off.
Counter-Strike 2 exposes mouse sensitivity through Settings > Game > Mouse Sensitivity, where the in-game slider spans 0.10 to 8.00. You can bypass that cap with the console command sensitivity followed by any decimal value, giving you virtually unlimited precision. CS2 uses a fixed horizontal FOV of roughly 106 degrees with no way to change it, so conversions only need to account for the sensitivity coefficient and DPI.
Zoom sensitivity is controlled by zoom_sensitivity_ratio_mouse, which ranges from 0.1 to 3.0 in the menu. A value of 1.0 does not mean scoped and hip-fire feel identical — the zoom FOV reduction already slows the view, so 1.0 simply preserves the underlying ratio. Many players moving from VALORANT set this to 1.0 and wonder why scoping feels slower than expected.
| Game | Setting | Menu range |
|---|---|---|
| Valorant | Sensitivity: Aim 0.1 - 100 | 0.1 to 100 |
| CS2 | Mouse Sensitivity 0.10 - 8.00 (menu); unlimited via console | 0.1 to 8 |
Of the eight Valorant values in the table above, 8 convert to a CS2 value inside its menu range. If yours lands outside, keep the cm/360 and move DPI: half the DPI needs double the value, double the DPI needs half.
The reverse direction uses the inverted ratio 0.022 / 0.07 = 0.3143. CS2 1.0 becomes Valorant 0.31, and both sit at 51.95 cm/360 at 800 DPI. The CS2 to Valorant converter has its own prefilled tool and table.
Keep your DPI the same and multiply your Valorant value by 0.07 / 0.022 = 3.182. Example: Valorant 0.4 becomes CS2 1.27; at 800 DPI both give 40.82 cm per 360-degree turn. The tool above does this and prints both cm/360 values so you can check they match.
No. Valorant uses 0.07 and CS2 uses 0.022 degrees per count, so the same number turns your view slower in CS2: Valorant 0.4 at 800 DPI is 40.82 cm/360, while CS2 0.4 is 129.89 cm/360. The matching CS2 value is 1.27.
VALORANT locks FOV at 103 degrees. If your source game used a different FOV, the visual speed of camera rotation will feel different even at identical cm/360. Give yourself a few minutes of warm-up to adjust to the visual difference.
Yes. The scoped multiplier only affects zoomed weapons like the Operator and Marshal. If your source game has separate ADS values, convert the zoom sensitivity on its own rather than relying on the base conversion alone.
The in-game slider displays two decimal places, but you can edit the settings config file directly to get finer values. This is useful when a conversion produces a number like 0.3467 that the slider would round.
Yes. CS2 uses the same yaw value as CS:GO, so any sensitivity you used in CS:GO will produce the exact same cm/360 in CS2 without conversion.
The UI slider has a fixed range of 0.10 to 8.00 for most players. You can set any value above or below that range by typing the sensitivity command directly into the developer console.
It multiplies your base sensitivity while scoped. At 1.0, the underlying sensitivity value stays the same, but the narrowed FOV of the scope still makes your view turn more slowly per centimeter of hand movement.