- eDPI = DPI Γ sensitivity
- Pro median β 800 eDPI
- Valorant Γ 3.18 = CS2
- Raw input always on
Your sensitivity decides how far your crosshair moves for every centimetre of mouse β and it's the one setting that changes every duel you take. Too high and you overshoot heads; too low and you can't turn in time. This guide explains how CS2's sensitivity actually works, the two numbers that let you compare any setup (eDPI and centimetres per 360Β°), what professional players use, how to convert from Valorant, Overwatch, Apex, Fortnite or Siege, and the old CS:GO mouse commands you can delete. Checked 2026-10-25.
- eDPI = DPI Γ sensitivity β compare setups with it, not with the sensitivity number alone.
- cm/360 = 41,563.6 Γ· eDPI, because CS2's yaw is 0.022Β° per mouse count.
- Pros cluster around 800 eDPI (middle half 707β960) β community data.
- No raw-input or acceleration settings: CS2 reads the mouse directly.
- Zoom sensitivity 1 is the default and what 80% of tracked pros use.
How CS2 sensitivity works
CS2 has one main control: Settings β Keyboard / Mouse β Mouse Sensitivity, which sets the console variable sensitivity
(the slider runs from 0.1 to 8). Every mouse count turns your view by m_yaw degrees β
0.022 by default in Valve's variable list β multiplied by that sensitivity. Your mouse's DPI decides how many counts it sends per inch,
which is why the same sensitivity feels completely different on a 400 and a 1,600 DPI mouse.
- Raw input: CS2 always reads raw mouse input β there's no raw-input or acceleration setting to change. Your Windows pointer speed and "enhance pointer precision" don't affect the game.
- Invert: Reverse Mouse flips the vertical axis (!pitch) rather than using a negative m_pitch.
- Leave
m_yawandm_pitchat 0.022. Changing them stretches horizontal and vertical aim differently and breaks every conversion below.
eDPI and centimetres per 360Β°
eDPI ("effective DPI") puts every setup on one scale: 400 DPI at 2.0 and 800 DPI at 1.0 are both 800 eDPI and turn exactly the same. Centimetres per 360Β° turns that into something you can feel β how far you slide the mouse to spin all the way round.
| eDPI | cm per 360Β° | Sensitivity at 400 DPI | at 800 DPI | at 1,600 DPI |
|---|---|---|---|---|
| 400 | 103.9 cm | 1 | 0.5 | 0.25 |
| 600 | 69.3 cm | 1.5 | 0.75 | 0.375 |
| 800 β pro median | 52 cm | 2 | 1 | 0.5 |
| 1,000 | 41.6 cm | 2.5 | 1.25 | 0.625 |
| 1,200 | 34.6 cm | 3 | 1.5 | 0.75 |
| 1,600 | 26 cm | 4 | 2 | 1 |
cm/360 = 360 Γ 2.54 Γ· (DPI Γ sensitivity Γ 0.022) = 41,563.6 Γ· eDPI. Our arithmetic from Valve's default yaw.
What sensitivity do pros use?
Two community databases track professional settings. Neither is Valve data, and they count slightly different player lists, but they agree on the shape: low sensitivity, big arm movements.
- 800median eDPI, 820 active pros (csdb.gg, 19 October 2026)
- 707β960the middle half of pros (same data); mean 856
- 830median eDPI, 948 pros (prosettings.net, 25 September 2026)
- 52 cma full turn at 800 eDPI
| Mouse DPI | Share of pros (csdb.gg) | Share of pros (prosettings.net) |
|---|---|---|
| 400 | 47% | 66% |
| 800 | 46% | 28% |
| 1,600 | 5% | 5% |
DPI itself doesn't make anyone better β 400 at 2.0 and 800 at 1.0 aim identically. What matters is the eDPI, and pros settle low because long, smooth arm movements are easier to repeat under pressure than tiny wrist flicks.
Convert your sensitivity from another game
Each game turns a different number of degrees per mouse count (its "yaw"). Multiply your old sensitivity by the factor below to turn exactly as far in CS2 at the same DPI. The yaw values are community-measured β no studio publishes them.
| From | Multiply by | Example | Note |
|---|---|---|---|
| Valorant | Γ 3.182 | 0.4 β 1.273 | |
| Overwatch 2 | Γ 0.3 | 5 β 1.5 | Also Call of Duty and Destiny 2 |
| Apex Legends | Γ 1 | 1.6 β 1.6 | The same yaw as CS2 |
| Fortnite | Γ 0.2525 | 8 β 2.02 | The percent slider |
| Rainbow Six Siege | Γ 0.2604 | 10 β 2.604 | Default multipliers, hip-fire only |
Yaw values: csdb.gg's converter (community-derived). The Siege figure only holds with default multipliers and hip-fire.
Zoom sensitivity for the AWP and scoped rifles
zoom_sensitivity_ratio scales your sensitivity while scoped (slider 0.01β3,
default 1). According to csdb.gg, 80% of 1,008 tracked pros keep it at 1 β change it only if
your AWP flicks consistently over- or undershoot after a few hundred shots.
How to find your sensitivity
- Start from what you have.
Work out your eDPI and cm/360 with the table above. If you came from another game, convert first.
- Check the full turn.
Can you turn 180Β° with one comfortable arm movement on your mousepad? If not, you're too low for your space.
- Test on bots.
Twenty minutes of flicks and tracking on an aim map. Over-flicking means too high; stopping short means too low.
- Change it in small steps.
Move 5β10% at a time and play a few days before judging.
- Then stop changing it.
Muscle memory needs a fixed target. Most "aim slumps" fixed by a new sensitivity are really a new habit forming.
The aim guide has a 20-minute routine to test it with, and a practice server gives you bots and infinite ammo.
CS:GO mouse commands you can delete
These still sit in old configs, launch lines and guides, but CS2 has no such variables or options:
m_rawinputm_customaccelm_mouseaccel1 / m_mouseaccel2-noforcemaccel, -noforcemparms, -noforcemspd
Keep your config lean β your launch options and binds have the same CS:GO leftovers to clear out.
Help with aim and settings
- Settings and aim: 1-on-1 coaching β from $18.00 an hour with a high-level player watching your duels.
- See where your shots miss: demo analysis of a real match.
- Read next: the crosshair guide and the best video settings.
- Valve's CS2 variable list β
m_yaw/m_pitch0.022 (Valve Developer wiki dump) Β· menu sliders: the game's settings file (SteamDB GameTracking-CS2, read 2026-10-25) - Community data: csdb.gg β pro sensitivity (19 October 2026), yaw converter, raw input Β· prosettings.net (25 September 2026)
All free tools: calculators, percentiles & season countdowns β
