CS2 Sensitivity Converter
Switching games? Keep the exact same aim. Here's how sensitivity converts between CS2 and other shooters.
The idea: match cm/360
Your real aim isn't the sens number — it's how far you move the mouse for a full 360° turn (cm/360). To carry your aim between games, you keep that distance the same and let each game's sens number change to suit it.
Quick conversions (same DPI)
To keep the same aim as CS2, multiply your CS2 sens by:
| To game | Multiply CS2 sens by | Example (CS2 = 2.0) |
|---|---|---|
| Valorant | × 0.314 | 0.63 |
| Apex Legends | × 1.0 | 2.0 |
| Overwatch 2 | × 3.33 | 6.67 |
Apex uses the same Source-engine yaw as CS2, so the number is identical at the same DPI. Valorant is "slower" per unit, Overwatch "faster".
Do it exactly
The eDPI calculator includes a live converter — enter your DPI and CS2 sens, pick a target game, and it gives the precise sensitivity (not just a rule of thumb).
Why DPI matters too
The multipliers above assume you keep the same DPI in both games. If you change DPI as well, convert on cm/360 rather than the raw sens — that's what actually fixes your aim distance. Not sure what your figure is? The eDPI guide explains how DPI and sens combine into your effective aim speed.
Why not just feel it out?
Muscle memory is built on cm/360. Guessing a new sens resets weeks of aim training. Converting keeps your flicks and tracking intact from day one. CS2 itself uses the same yaw as CS:GO, so if you're coming from the old game your existing sens already carries over with no conversion needed.