This CS2 to Overwatch 2 sensitivity converter takes the sensitivity you use in CS2 and returns the Overwatch 2 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 Overwatch 2 on 0.0066, 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 Overwatch 2 value is 3.33.
1.0 × (0.022 / 0.0066) = 3.33. Set Overwatch 2 to 3.33 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, Overwatch 2 uses 0.0066. 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 = Overwatch 2 sens × 0.0066Overwatch 2 sens = CS2 sens × (0.022 / 0.0066) = CS2 sens × 3.333The multiplier is 3.333, so every CS2 value becomes a larger number in Overwatch 2. That is not a faster sensitivity: Overwatch 2 moves fewer degrees per count, so it needs a bigger multiplier to produce the same turn.
Eight common CS2 values, the Overwatch 2 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 | Overwatch 2 sens | cm/360 at 400 DPI | cm/360 at 800 DPI | cm/360 at 1600 DPI |
|---|---|---|---|---|
| 0.5 | 1.67 | 207.82 cm | 103.91 cm | 51.95 cm |
| 0.8 | 2.67 | 129.89 cm | 64.94 cm | 32.47 cm |
| 1.0 | 3.33 | 103.91 cm | 51.95 cm | 25.98 cm |
| 1.2 | 4.00 | 86.59 cm | 43.30 cm | 21.65 cm |
| 1.5 | 5.00 | 69.27 cm | 34.64 cm | 17.32 cm |
| 1.8 | 6.00 | 57.73 cm | 28.86 cm | 14.43 cm |
| 2.0 | 6.67 | 51.95 cm | 25.98 cm | 12.99 cm |
| 3.0 | 10.00 | 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.
Overwatch 2 stores mouse sensitivity under Options > Controls > General. The sensitivity slider ranges from 1.00 to 100.00 with two-decimal granularity. Like VALORANT, OW2 uses a fixed 103-degree horizontal FOV that cannot be changed, removing one variable from cross-game conversions.
Heroes with scoped or zoomed abilities — Widowmaker, Ashe, Ana — have a separate Relative Aim Sensitivity While Zoomed slider (0%-100%) found in each hero's individual control section. At 100% the underlying sensitivity is unchanged, but the zoom FOV reduction still makes the view feel slower. There is also a High Precision Mouse Input toggle in gameplay settings; enabling it feeds sub-pixel data to the engine and can eliminate micro-stuttering in aim.
| Game | Setting | Menu range |
|---|---|---|
| CS2 | Mouse Sensitivity 0.10 - 8.00 (menu); unlimited via console | 0.1 to 8 |
| Overwatch 2 | Sensitivity 1.00 - 100.00 | 1 to 100 |
Of the eight CS2 values in the table above, 8 convert to a Overwatch 2 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.0066 / 0.022 = 0.3. Overwatch 2 5.0 becomes CS2 1.50, and both sit at 34.64 cm/360 at 800 DPI. The Overwatch 2 to CS2 converter has its own prefilled tool and table.
Keep your DPI the same and multiply your CS2 value by 0.022 / 0.0066 = 3.333. Example: CS2 1.0 becomes Overwatch 2 3.33; 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 Overwatch 2 uses 0.0066 degrees per count, so the same number turns your view slower in Overwatch 2: CS2 1.0 at 800 DPI is 51.95 cm/360, while Overwatch 2 1.0 is 173.18 cm/360. The matching Overwatch 2 value is 3.33.
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.
No. Overwatch 2 locks horizontal FOV at 103 degrees for all players. This means your cm/360 depends only on DPI and the in-game sensitivity value.
Per-hero. Each hero with a zoom ability has their own Relative Aim Sensitivity While Zoomed slider, so you need to set or convert them individually.
The two games use different yaw constants. Even though both have a 103-degree FOV, the same numeric sensitivity value produces a different cm/360 in each title. Use a converter to translate the value correctly.