This CS2 to Apex Legends sensitivity converter takes the sensitivity you use in CS2 and returns the Apex Legends 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 Apex Legends on 0.022, 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 Apex Legends value is 1.00.
1.0 × (0.022 / 0.022) = 1.00. Set Apex Legends to 1.00 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, Apex Legends 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)CS2 sens × 0.022 = Apex Legends sens × 0.022Apex Legends sens = CS2 sens × (0.022 / 0.022) = CS2 sens × 1The two constants are identical, so the multiplier is 1: copy your CS2 value into Apex Legends unchanged. The converter still shows both cm/360 figures so you can confirm the match.
Eight common CS2 values, the Apex Legends 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 | Apex Legends sens | cm/360 at 400 DPI | cm/360 at 800 DPI | cm/360 at 1600 DPI |
|---|---|---|---|---|
| 0.5 | 0.50 ✱ | 207.82 cm | 103.91 cm | 51.95 cm |
| 0.8 | 0.80 ✱ | 129.89 cm | 64.94 cm | 32.47 cm |
| 1.0 | 1.00 | 103.91 cm | 51.95 cm | 25.98 cm |
| 1.2 | 1.20 | 86.59 cm | 43.30 cm | 21.65 cm |
| 1.5 | 1.50 | 69.27 cm | 34.64 cm | 17.32 cm |
| 1.8 | 1.80 | 57.73 cm | 28.86 cm | 14.43 cm |
| 2.0 | 2.00 | 51.95 cm | 25.98 cm | 12.99 cm |
| 3.0 | 3.00 | 34.64 cm | 17.32 cm | 8.66 cm |
✱ Outside the Apex Legends menu range (1 to 8). Keep the same cm/360 by changing DPI instead: halving DPI doubles the required Apex Legends value, doubling DPI halves it.
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.
Apex Legends places mouse sensitivity under Settings > Mouse/Keyboard. The slider runs from 1.0 to 8.0 and accepts one-decimal increments. Unlike most tactical shooters, Apex has a horizontal FOV slider from 70 to 110, and changing it directly affects how your sensitivity feels — a wider FOV makes the same cm/360 appear visually slower because each degree of rotation covers less screen space.
ADS sensitivity uses a per-optic multiplier system. Each magnification tier has its own multiplier that scales off your hip-fire value, so swapping a 1x Holo for a 3x Ranger changes your scoped speed automatically. There is also a global ADS Mouse Sensitivity Multiplier that scales all optics together. The most common conversion error is matching only hip-fire and ignoring the per-optic layer, leaving high-zoom scopes feeling inconsistent.
| Game | Setting | Menu range |
|---|---|---|
| CS2 | Mouse Sensitivity 0.10 - 8.00 (menu); unlimited via console | 0.1 to 8 |
| Apex Legends | Mouse Sensitivity 1.0 - 8.0 | 1 to 8 |
Of the eight CS2 values in the table above, 6 convert to a Apex Legends 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.022 = 1. Apex Legends 1.5 becomes CS2 1.50, and both sit at 34.64 cm/360 at 800 DPI. The Apex Legends to CS2 converter has its own prefilled tool and table.
Keep your DPI the same and multiply your CS2 value by 0.022 / 0.022 = 1. Example: CS2 1.0 becomes Apex Legends 1.00; 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.
Yes. CS2 and Apex Legends both use a yaw of 0.022 degrees per count, so the same number gives the same cm/360 at the same DPI: 1.0 at 800 DPI is 51.95 cm/360 in both games. Check the cm/360 readout anyway, because DPI or a changed in-game multiplier can still break the match.
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.
It changes how the sensitivity feels visually but the raw cm/360 for hip-fire stays the same. However, if you use a converter that factors in FOV, the output will differ because the angular movement per pixel changes.
Apex uses per-optic multipliers on top of a global ADS multiplier. If your source game has a single ADS value, you need to map it to each optic tier individually or adjust the global ADS multiplier to approximate the feel.
The in-game slider snaps to one-decimal increments. For finer control, you can edit the settings config file in your profile folder, though Apex may round to the nearest supported step on next launch.