Sensitivity is one of the highest-leverage changes a Counter-Strike 2 player can make, and it isn't a magic number you copy from a stream and instantly improve with. It's a personal value that balances how fast you can turn against how precisely you can stop. This guide breaks down why pros tend to play low, how to read eDPI, what a sane DPI actually is, how to carry a setting over from CS:GO, and how to lock in a value that actually sticks long enough to build muscle memory around.
Why CS2 Pros Favor Low Sensitivity
Watch professional Counter-Strike and one pattern jumps out immediately: almost everyone plays on a relatively low sensitivity. This isn't fashion, it's mechanics. CS2 rewards stillness and precise stopping far more than fast 180-degree spins, so the entire competitive scene has converged on settings that maximize control. There are three concrete reasons this dominates at the top level.
Precision and micro-adjustment
At lower sensitivity, every centimeter of mouse movement maps to a smaller in-game angle, so tiny hand movements produce tiny, controllable crosshair corrections. Most CS2 duels are won by a small adjustment onto a head, not a wild flick across the screen. A lower setting gives you the resolution to make those micro-adjustments cleanly instead of overshooting them.
Counter-strafing accuracy
CS2 punishes shooting while moving. To fire accurately you counter-strafe, tapping the opposite key to cancel momentum so you're effectively standing still for the shot. Lower sensitivity makes that stop-and-shoot rhythm more repeatable because your aim doesn't jerk when your hand resets. The combination of a steady counter-strafe and controlled sensitivity is what produces the crisp first-bullet kills you see from pros.
Spray control
Pulling down and across to fight the AK-47 or M4 recoil pattern is a physical mouse motion. At very high sensitivity, the compensation movements become so small that they turn twitchy and inconsistent. A lower setting spreads the recoil pattern across more mouse travel, giving your hand room to learn the shape and reproduce it under pressure.
Understanding eDPI
You can't compare two players' sensitivities by looking at the in-game slider alone, because the slider interacts with mouse DPI. The number that actually matters is eDPI, effective DPI, a single value that captures your true sensitivity regardless of which mouse you use.
The formula: eDPI = mouse DPI × in-game sensitivity.
A player on 400 DPI with an in-game sens of 2.0 has an eDPI of 800. A player on 800 DPI with a sens of 1.0 also has an eDPI of 800, and the two will turn identically in game. eDPI is the only fair way to compare settings between players, which is why every serious settings discussion in CS2 revolves around it rather than the raw slider value.
Across the competitive scene, a common eDPI range sits roughly between 600 and 1000, most often built on 400 DPI. That's a general pattern in where high-level players cluster, not a rule. If you land inside that window you're firmly in competitive territory; for most players, starting around an eDPI of 800 is a sensible middle ground to tune from.
cm/360: The Most Intuitive Measure
eDPI is great for comparison, but cm per 360 is the most intuitive way to actually feel your sensitivity. It tells you how many centimeters you need to physically drag your mouse to turn a full 360 degrees in game. A lower eDPI means more centimeters per turn and more precision; a higher eDPI means fewer centimeters and a flickier, wristier feel.
Most strong CS2 players sit somewhere between roughly 35 and 55 cm per 360. That range favors arm aiming, anchoring your wrist and moving from the elbow and shoulder, which stays far more consistent over a long session than pure wrist aim.
| DPI | In-game sens | eDPI | Approx. cm/360 | Feel |
|---|---|---|---|---|
| 400 | 1.5 | 600 | ~53 cm | Low, arm-heavy precision |
| 400 | 2.0 | 800 | ~40 cm | Common balanced choice |
| 800 | 1.0 | 800 | ~40 cm | Identical to 400 × 2.0 |
| 400 | 2.5 | 1000 | ~32 cm | Upper end of pro range |
| 1600 | 1.0 | 1600 | ~20 cm | High, wrist-heavy, harder to control |
| 800 | 0.8 | 640 | ~50 cm | Low, modern hero-aim style |
These cm/360 figures are approximate, but they illustrate the relationship clearly: as eDPI climbs, the centimeters needed for a full turn shrink fast. If your mousepad is at least 35 to 40 cm wide, you have room to play comfortably at the lower, more precise end of this range.
What DPI Should You Actually Use?
The most popular and reliable choice is 400 or 800. Both are native, true DPI steps on the vast majority of gaming mice, meaning the sensor reports cleanly without interpolation. Higher DPI values don't make you better; they just require a lower in-game sens to reach the same eDPI. In practice, 400 and 800 are safe, proven choices the entire competitive scene relies on.
Pick one DPI and never touch it again, then do all your tuning with the in-game sensitivity slider. Changing DPI mid-journey resets your muscle memory just as much as changing sensitivity does, so treat DPI as a hardware setting you configure once. For a deeper look at how DPI behaves across different shooters, see our Best DPI Settings for FPS Games guide.
Converting From CS:GO to CS2
Good news for veterans: your sensitivity carries over directly. CS2 uses the same sensitivity scale as CS:GO, so if you played at 400 DPI and 2.0 sens in CS:GO, the exact same value feels identical in CS2. There's no conversion math required; your sensitivity and m_yaw values transfer one-to-one, and your eDPI and cm/360 stay unchanged.
The one thing worth re-checking is your config. If you migrated manually or started fresh, confirm raw input is enabled and mouse acceleration is off, since a clean config is what guarantees the CS:GO feel actually survives the move. If your old sensitivity served you well, keep it and spend your energy on placement and movement instead of second-guessing the number.
Raw Input and Mouse Settings That Matter
Sensitivity doesn't live in a vacuum. A few supporting settings determine whether your aim is consistent or subtly unpredictable. Get these right once and forget about them.
- Raw input on: set m_rawinput to 1 so CS2 reads your mouse directly and ignores Windows pointer settings. This is essential for one-to-one tracking.
- Mouse acceleration off: disable it in-game and in Windows so the same physical movement always produces the same turn. Acceleration destroys muscle memory.
- Windows pointer speed at 6/11: the default, unscaled setting. Raw input bypasses this, but keeping it neutral avoids surprises.
- Polling rate 1000 Hz: a standard, smooth report rate for modern gaming mice.
- Disable mouse smoothing and enhanced pointer precision: both add input lag or inconsistency and should stay off.
With these locked in, your in-game sensitivity is the only variable left, which is exactly what you want when dialing in feel.
Picking and Testing Your Own Sensitivity
There's no universal best value, only the best value for your hand, your mousepad, and your play style. Use this process instead of copying a number blindly.
- Start in the common range. Set 400 or 800 DPI and choose an in-game sens that lands near 800 eDPI. This is a proven starting point.
- Check your mousepad room. Do a full 180 swing and a precise micro-adjustment. Running out of pad on big turns means go a touch higher; jittery small corrections mean go lower.
- Bias toward the low end. When in doubt, drop sensitivity slightly. Precision and counter-strafing improve more from going lower than higher for most players.
- Commit for two weeks. Pick a value and stop touching it. Constant tweaking resets muscle memory and is the single biggest mistake players make.
- Adjust in small steps. If you must change, move by 0.1 to 0.2 in-game, not in big jumps, so your hand adapts gradually.
For a calculator-driven approach and a deeper breakdown of the effective DPI math, our Sensitivity Guide and eDPI Calculator walks through the numbers step by step.
Practicing Your Sensitivity in a Trainer
Once you've chosen a value, the fastest way to bond with it is repetition, and a browser aim trainer gives you far more reps per minute than live matches do. Set your trainer to the same eDPI you use in CS2 so the muscle memory transfers cleanly, then drill precision clicking and target switching to feel how your sensitivity stops on small targets. Consistently overshooting is real-time feedback that your setting may be a hair too high. Pair browser drills with practice-server work on counter-strafing and spray patterns, and see our Best Aim Training for CS2 guide for a complete practice plan.
Lock It In and Start Training
The best sensitivity for CS2 is the one you can stop precisely with, counter-strafe cleanly behind, and control spray with, sitting somewhere in that common 600 to 1000 eDPI window on 400 or 800 DPI. Pick a value, enable raw input, disable acceleration, and commit long enough to build real muscle memory. Match your eDPI in the free browser aim trainer and run a focused block now, then carry that steadier, more confident crosshair straight into your next match.