Counter-Strike 2 has one of the simplest sensitivity systems in shooters, yet most players still copy a number from someone else without knowing what it means on their own desk. A setting of 1.0 can be a slow, wrist-friendly turn at 400 DPI or a very fast one at 1600 DPI, so the number alone tells you almost nothing.
This guide explains the maths behind the setting (the yaw value of 0.022), shows the eDPI and cm/360 ranges that most competitive players sit in, and gives you two ready-made tables so you can pick a sensitivity from a target distance. It also covers converting from Valorant or Apex Legends, how scoped sensitivity behaves, a calm way to test changes, and the mistakes that keep players stuck.
What the CS2 sensitivity number really does
Every time the mouse reports one count of movement, CS2 turns your view by yaw × sensitivity degrees. The yaw for CS2 (and CS:GO before it) is 0.022. So at sensitivity 1.0, one count rotates the view by 0.022 degrees, and a full 360° turn needs 360 / 0.022, roughly 16,364 counts.
Your DPI decides how many counts the mouse sends per inch of movement. That is why the physical distance for a full turn is:
cm/360 = 360 / (0.022 × sensitivity × DPI) × 2.54
Distance is the number that matters for muscle memory: how far your hand travels to turn around. Sensitivity and DPI are just two ingredients. Our sensitivity converter does this calculation for you and shows eDPI and cm/360 together, and the eDPI guide goes deeper into why the product of the two settings is useful.
eDPI and the ranges most players use
eDPI is simply DPI multiplied by in-game sensitivity. At 800 DPI and sensitivity 1.0 you have 800 eDPI; at 400 DPI and 2.0 you also have 800 eDPI, and both give the same turn distance. Inside CS2 it is a handy shorthand for comparing settings, but it is only comparable between games that share the same yaw.
Roughly speaking, many competitive CS2 players sit between about 700 and 1,200 eDPI, which works out to around 30 to 55 cm/360°. These are approximate ranges, not rules, and there is a wide spread on both sides. Beginners often play too fast, below about 25 cm/360°, which makes small corrections jittery.
- Lower eDPI / more cm per turn: easier to place the crosshair precisely and hold small adjustments, but you need more desk space to turn around quickly.
- Higher eDPI / fewer cm per turn: fast turns with little movement, but fine aim becomes shakier.
- Middle ground: most players settle somewhere in the 30 to 55 cm range and fine-tune a little as their grip and comfort change.
Pick a sensitivity from a target cm/360
If you already know the turn distance you like (for example from another game), work backwards. The table shows the CS2 sensitivity you need for each target at the three common DPI values. Pick your DPI column, then your cm/360 row.
| cm/360 | 400 DPI | 800 DPI | 1600 DPI |
|---|---|---|---|
| 20 | 5.2 | 2.6 | 1.3 |
| 25 | 4.16 | 2.08 | 1.04 |
| 30 | 3.46 | 1.73 | 0.866 |
| 35 | 2.97 | 1.48 | 0.742 |
| 40 | 2.6 | 1.3 | 0.649 |
| 45 | 2.31 | 1.15 | 0.577 |
| 50 | 2.08 | 1.04 | 0.52 |
| 60 | 1.73 | 0.866 | 0.433 |
For example, a 45 cm/360° target at 800 DPI: 360 × 2.54 = 914.4, and 0.022 × 800 × 45 = 792, so the sensitivity is 914.4 ÷ 792 = 1.15. Notice how the numbers halve when DPI doubles; the distance stays identical. If your calculation lands between two values, rounding to the nearest two decimals changes the distance by only a small amount that you will not feel.
What your current settings mean in centimetres
Now the other direction: you already have a sensitivity and want to know where you stand. The next table lists common CS2 values with the resulting cm/360° at each DPI, plus the eDPI at 800 DPI for reference (multiply or divide by two for 1600 or 400).
| Sensitivity | 400 DPI | 800 DPI | 1600 DPI | eDPI at 800 |
|---|---|---|---|---|
| 0.5 | 208.0 | 104.0 | 52.0 | 400 |
| 1.0 | 104.0 | 52.0 | 26.0 | 800 |
| 1.5 | 69.3 | 34.6 | 17.3 | 1200 |
| 2.0 | 52.0 | 26.0 | 13.0 | 1600 |
| 2.5 | 41.6 | 20.8 | 10.4 | 2000 |
| 3.0 | 34.6 | 17.3 | 8.66 | 2400 |
Read it like this: sensitivity 1.0 at 800 DPI is 52 cm/360°, which is on the slower, precise side of the common range. Sensitivity 1.5 at 800 DPI is 34.6 cm/360°, closer to the faster end. The same 1.0 at 1600 DPI drops to 26 cm/360°, a lot quicker than most players expect from such a harmless-looking number. If you are unsure what your eDPI and cm/360° are, our DPI and eDPI tool calculates both from your DPI and sensitivity.
Converting from Valorant or Apex Legends
Switching from Valorant is the most common case. Valorant uses a yaw of 0.07 and CS2 uses 0.022, so a Valorant sensitivity multiplied by about 3.18 gives the CS2 value that matches the same cm/360° at the same DPI. The reverse is a multiplication by roughly 0.314. For instance CS2 1.0 is about Valorant 0.314, and Valorant 0.35 becomes roughly 1.11 in CS2.
Apex Legends also uses a yaw of 0.022, so its sensitivity maps one-to-one: Apex 2.0 is CS2 2.0 at the same DPI. That makes moving between those two games very easy.
Because you keep the same DPI in both games, the converted number does not depend on DPI; DPI only changes the cm/360° you read afterwards. If you prefer a dedicated page, see Valorant to CS2, CS2 to Valorant and Apex to Valorant, or read the longer conversion guide and the Valorant sensitivity and DPI guide.
Scoped sensitivity and zoom settings
Matching cm/360° fixes your hip-fire turn, but scoped weapons are handled by a separate setting. In CS2 the zoom sensitivity ratio scales how fast the view moves while scoped. Players who want a scope to feel connected to their normal aim sometimes adjust it, though what feels right depends on the weapon and personal taste, so treat any single number you read online as a starting point only.
Also remember that a matched distance does not guarantee a matched feel. Field of view, viewmodel and movement speed differ between games, so the same 40 cm may feel a touch faster or slower after you switch. Give yourself a few days rather than judging after one match.
How to test a new sensitivity properly
The temptation is to change the number after every lost duel. A calmer routine gives you real information:
- Set the sensitivity from a table above, keeping your DPI fixed. Disable mouse acceleration and use raw input.
- Do a short warm-up on an aim map or deathmatch for a few days, always at the same time of day if possible.
- Use a repeatable drill. The sensitivity test can give you a rough starting estimate from quick flicks, and our aim routine guide shows how to structure the practice.
- Change the value in small steps, and give each step at least a few sessions before you judge it.
- Pick one setting and stay with it for a few weeks. Consistency builds muscle memory faster than any perfect number.
Common CS2 sensitivity mistakes
- Copying a settings screenshot without matching DPI. The same sensitivity with a different DPI is a completely different turn distance.
- Raising DPI for "more precision". Beyond roughly 1600 there is no real aiming advantage, so keep it at 400, 800 or 1600 and tune the in-game number.
- Leaving mouse acceleration on. Turn off "Enhance pointer precision" so the same hand movement always gives the same result.
- Judging after one session. Form varies from day to day, which makes short tests misleading.
- Changing mouse pad, grip and sensitivity at once. Change one thing at a time so you know what helped.
Frequently asked questions
What is a good CS2 sensitivity?
Many competitive players sit at roughly 700 to 1,200 eDPI, which is about 30 to 55 cm/360°. As a starting example, 800 DPI at 1.0 is eDPI 800 and 52 cm/360°; if that feels slow, try 1.3 (about 40 cm/360°) and adjust in small steps.
Is the CS2 sensitivity the same as CS:GO?
The yaw value of 0.022 is the same, so your old CS:GO sensitivity at the same DPI gives the same turn distance. For example, CS:GO 1.5 at 800 DPI is 34.6 cm/360° in CS2 as well.
How do I convert Valorant sensitivity to CS2?
Multiply the Valorant value by about 3.18 while keeping the same DPI. For example Valorant 0.35 becomes roughly 1.11 in CS2. The converter does the maths and also shows the cm/360°.
Does DPI change my CS2 sensitivity?
Only through the final turn distance. Doubling DPI while halving the in-game sensitivity keeps cm/360° identical, so choose a DPI you like (400, 800 or 1600) and tune the in-game value.
Should I use the same sensitivity for Apex and CS2?
Both games use a yaw of 0.022, so the same number gives the same cm/360° at the same DPI. For example, 1.5 at 800 DPI is 34.6 cm/360° (eDPI 1200) in both Apex and CS2.
CS2 sensitivity becomes simple once you think in centimetres per turn instead of a bare number. Choose a DPI, use the tables to land in a sensible range, and then change the value slowly while you practise consistently. To skip the calculations, open the sensitivity converter and check your result in seconds.