Tools
Apex to CS2 sensitivity
CS2 sensitivity = Apex hipfire sensitivity at the same DPI. Both games use 0.022° per count. Type 2.00 in Apex and you type 2.00 in CS2. The work left is ADS: Apex’s per-optic multipliers are not CS2’s zoom_sensitivity_ratio.
Slider 0.1–10. Yaw 0.022°/count.
CS2 sensitivity
1.050
Matched cm/360
32.99 cm
Same DPI on both sides. Hipfire only. CS2 yaw 0.022°/count.
How this pair converts
Hipfire new = old. Yaw 0.022 on both sides.
Apex Legends uses the same 0.022 Source-family yaw as CS2, so the hipfire number is 1:1 at the same DPI.
Both games turn the same amount per mouse count, so the number carries over 1:1.
Apex Legends movement and ADS FOV still make the fight feel different after a 1:1 paste. Do a 360 in the firing range, then look at the optic sliders separately.
cm/360 = (360 ÷ (yaw × sensitivity × DPI)) × 2.54. The converter keeps that distance equal.
If Apex hipfire is 1.050 at 1200 DPI, CS2 is 1.050. That is also my Overwatch 3.5 turn.
Common questions
Is Apex sensitivity the same as CS2?
Yes, for hipfire at the same DPI. Both games use 0.022 yaw, so you can use the same number, though ADS sensitivity works differently.
Why does ADS feel different in Apex after converting from CS2?
Apex has a separate ADS multiplier for each optic, while CS2 uses zoom_sensitivity_ratio for scoped weapons. Tune ADS separately in each game.
Does Apex FOV change my converted sensitivity?
Your hipfire cm/360 stays the same at any FOV. A higher FOV can make aiming feel slower on screen, though, so adjust slightly if needed.
Reverse this pair on CS2 to Apex sensitivity. All seven games, including titles not listed here, stay on the shared converter. Measure a 360 in how to find your sensitivity.