This CS2 to Valorant sensitivity converter takes the sensitivity you use in CS2 and returns the Valorant value that produces the same physical turn — the same cm/360 — on the same mouse DPI. CS2 runs on a yaw of 0.022 degrees per count and Valorant on 0.07, so the number changes even though your arm movement does not. Example: CS2 1.0 at 800 DPI is 51.95 cm per full turn; the matching Valorant value is 0.31.
1.0 × (0.022 / 0.07) = 0.31. Set Valorant to 0.31 and both games compute to about 51.95 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: CS2 uses 0.022, Valorant uses 0.07. 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)CS2 sens × 0.022 = Valorant sens × 0.07Valorant sens = CS2 sens × (0.022 / 0.07) = CS2 sens × 0.3143The multiplier is 0.3143, so every CS2 value becomes a smaller number in Valorant. The turn itself does not change: Valorant moves more degrees per count, so it needs a smaller multiplier for the same cm/360.
Eight common CS2 values, the Valorant 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.
| CS2 sens | Valorant sens | cm/360 at 400 DPI | cm/360 at 800 DPI | cm/360 at 1600 DPI |
|---|---|---|---|---|
| 0.5 | 0.16 | 207.82 cm | 103.91 cm | 51.95 cm |
| 0.8 | 0.25 | 129.89 cm | 64.94 cm | 32.47 cm |
| 1.0 | 0.31 | 103.91 cm | 51.95 cm | 25.98 cm |
| 1.2 | 0.38 | 86.59 cm | 43.30 cm | 21.65 cm |
| 1.5 | 0.47 | 69.27 cm | 34.64 cm | 17.32 cm |
| 1.8 | 0.57 | 57.73 cm | 28.86 cm | 14.43 cm |
| 2.0 | 0.63 | 51.95 cm | 25.98 cm | 12.99 cm |
| 3.0 | 0.94 | 34.64 cm | 17.32 cm | 8.66 cm |
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.
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.
| Game | Setting | Menu range |
|---|---|---|
| CS2 | Mouse Sensitivity 0.10 - 8.00 (menu); unlimited via console | 0.1 to 8 |
| Valorant | Sensitivity: Aim 0.1 - 100 | 0.1 to 100 |
Of the eight CS2 values in the table above, 8 convert to a Valorant 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.07 / 0.022 = 3.182. Valorant 0.4 becomes CS2 1.27, and both sit at 40.82 cm/360 at 800 DPI. The Valorant to CS2 converter has its own prefilled tool and table.
Keep your DPI the same and multiply your CS2 value by 0.022 / 0.07 = 0.3143. Example: CS2 1.0 becomes Valorant 0.31; at 800 DPI both give 51.95 cm per 360-degree turn. The tool above does this and prints both cm/360 values so you can check they match.
No. CS2 uses 0.022 and Valorant uses 0.07 degrees per count, so the same number turns your view faster in Valorant: CS2 1.0 at 800 DPI is 51.95 cm/360, while Valorant 1.0 is 16.33 cm/360. The matching Valorant value is 0.31.
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.
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.