CS2 Sensitivity Tips for Finding Your Real cm/360
You change your sensitivity on Tuesday because two sprays went wide, you change it back on Thursday because a flick felt sluggish, and by the weekend you have no idea what number you are actually aiming with.

You change your sensitivity on Tuesday because two sprays went wide, you change it back on Thursday because a flick felt sluggish, and by the weekend you have no idea what number you are actually aiming with. I have watched this happen to maybe a third of the players who send me their config files, and almost none of them have a hardware problem. They have a measurement problem.
I test mice for a living, which means I spend more time with a tape measure next to a mousepad than most people would consider healthy. The thing that keeps surprising me is how many good players cannot answer a simple question: how far does your hand move to turn your character all the way around? If you cannot answer that, every sensitivity change you make is a guess, and guesses do not stack into muscle memory.
Why your aim feels different on the same setting
In-game sensitivity is only one of three numbers that decide how far your crosshair travels. The other two are your mouse DPI and your Windows pointer speed, and both of them drift without you noticing.
Mouse software is the usual culprit. Driverless mice remember DPI in onboard memory, but any mouse with a profile switch can land on profile two after a firmware update or a different USB port, and 800 DPI silently becomes 1600. Windows pointer speed is the other one. The sixth notch in the pointer slider is the only position that passes your mouse movement through untouched. Anything higher multiplies it, anything lower throws away counts, and a Windows reinstall or a new monitor can reset it.
Mouse acceleration adds a third layer. Modern sensors do not need it, and CS2 ships with it off, but some gaming mouse suites apply their own curve above the game. If your short corrections feel fine and your long swings overshoot, check the software before you touch the sensitivity slider.
Measure in centimeters, not in sensitivity
The only portable number is cm/360: how many centimeters of mouse travel it takes to spin a full circle. Two players with identical in-game sensitivity can have wildly different cm/360 if their DPI differs, which is why copying a number from a friend rarely works.
The formula is simple enough to do on your phone. Multiply DPI by in-game sensitivity to get eDPI, then divide 15240 by that number for a rough cm/360 in CS2. At 800 DPI and 1.0 sensitivity, eDPI is 800 and a full turn takes roughly 19 centimeters. Here is where common setups land.
| DPI | In-game sens | eDPI | Approx cm/360 | Who it suits |
|---|---|---|---|---|
| 400 | 1.4 | 560 | 27 cm | Arm aimers, large pads, AWP |
| 400 | 2.0 | 800 | 19 cm | The most common range in CS2 |
| 800 | 1.2 | 960 | 16 cm | Mixed wrist and arm, rifle play |
| 1600 | 0.8 | 1280 | 12 cm | Small desks, close range maps |
| 800 | 2.5 | 2000 | 8 cm | Fast rotators, hardest to keep consistent |
Measure yours rather than trusting the math. Stand in a casual server, put a pencil mark on your mousepad where the mouse sits, turn 360 degrees in one smooth motion with the crosshair ending on the same wall decal it started on, and mark where the mouse stopped. Do it three times and average. If your three marks are spread over four centimeters, your real problem is that your pad is too small for the swing you are trying to make, and no slider fixes that.
Copying a pro sensitivity is the wrong starting point
Everybody repeats this advice, and I think it is backwards. Pros do not share your desk depth, your pad surface, your chair height, or the angle your forearm rests at. A player who sits with the mouse near the keyboard and swings from the elbow needs a very different cm/360 from someone whose desk is 60 centimeters deep and who pivots at the wrist.
What actually transfers from pro configs is the range, not the value. Look at the published settings for a dozen tier-one riflers and you will see eDPI clustered roughly between 600 and 1100, with AWPers skewing lower. That range tells you something useful: almost nobody at the top plays at an eDPI of 2400, so if you are up there, you are fighting your own hand. Beyond that, the specific number belongs to the specific arm.
The reverse mistake is just as costly. Players drop to 400 DPI and 1.1 sensitivity because a favorite streamer plays there, then discover they cannot turn to check a flank without lifting the mouse twice. Lifting mid-fight is how you lose a position you had already won. Your sensitivity has to fit the space you actually have, which is also why I keep telling people to pick the mousepad before the number rather than the other way around.
A two week test that settles it
Pick one number and defend it. The point is not to find a perfect setting, it is to stop the weekly churn long enough for your hand to calibrate. Here is the routine I use when a reader asks me to help them lock this down.
- Days 1 and 2. Fix the hardware layer. Set Windows pointer speed to the sixth notch, turn off enhanced pointer precision, disable any in-software acceleration, and write your DPI on a sticky note under the mouse. Save a backup of your config so a game update cannot quietly change it.
- Day 3. Measure your current cm/360 three times and write it down. If it falls outside 12 to 28 centimeters, move it into that window in one step, not five.
- Days 4 to 10. No changes allowed. Open the game, spend eight minutes on a workshop aim map, then play. Keep a one line note after each session: did you overshoot targets, undershoot them, or neither?
- Days 11 and 12. Read your notes. Consistent overshooting means lower the sensitivity by about 10 percent of your eDPI, not more. Consistent undershooting with the mouse hitting the pad edge means raise it by the same step.
- Days 13 and 14. Replay two of your own demos and watch only your crosshair. A hand that is calibrated stops on the target and stays there. A hand that is not makes a small correction after every stop.
Two weeks is the shortest honest test I have found. Four days feels like enough and is not, because the first three days after any change are always worse while your hand adapts. That adaptation window is exactly what makes sensitivity tinkering so addictive and so useless: every change feels bad at first, so every change seems to prove the previous setting was right.
One caveat on my own advice. I have never seen this routine fail to reduce someone's shot correction count, but my sample is maybe 40 players who were already motivated enough to keep notes for a fortnight. Players who will not keep notes get nothing out of it, and I have stopped pretending otherwise.
What to change instead when aim feels off
If a bad night makes you want to touch the slider, touch something else first. Zoom sensitivity for the AWP is a separate value and most players leave it at the default of 1.0, which keeps scoped aim proportional to your hipfire. Crosshair size and gap do more for first bullet accuracy than any sensitivity tweak, and raw input should be on permanently.
Then check whether the real issue is movement rather than aim. If your first bullet lands wide while your tracking feels fine, the fault is almost always a stop that was not a full stop, and our walkthrough on counter-strafing that fixes your first bullet is the fix. Sensitivity gets blamed for a lot of problems that live in the keyboard hand.
FAQ
Does higher DPI make my aim more accurate?
Not above roughly 1600 on a current sensor. CS2 polls mouse input at your refresh and tick rate, so extra counts past that point are averaged away. Higher DPI mainly reduces the smoothness threshold on cheap sensors, and no mouse I have tested in the last three years struggles at 800.
Should my AWP sensitivity be lower than my rifle sensitivity?
Your zoom sensitivity multiplier handles that. Leaving it at 1.0 means the scoped view tracks at the same physical distance as unscoped, which keeps one muscle memory instead of two. Lowering it to 0.8 gives finer control on long shots but breaks the relationship between the two views.
How long before a new sensitivity stops feeling wrong?
Three to five days of regular play for most people, longer if you only play twice a week. Judging a change on the first evening is the single most common reason players never settle.
Is wireless input lag enough to affect this?
No. Current 2.4 GHz gaming receivers add under a millisecond, which is well below what a human hand can detect. If your aim changed when you switched to wireless, the likely cause is a different shape or weight, and that topic sits in why your aim feels worse after switching mice.
More in Tips
Tips
CS2 Molotov Tips for Clearing Angles and Delaying Pushes
Four hundred dollars buys the cheapest round winning utility in CS2, and most of the players I queue with waste it inside the...
Tips
CS2 Spray Control Tips for the AK-47 and M4 Rifles
You win the first duel with a clean tap, then a second enemy swings and your next eight bullets hit the wall above his head.
Tips
CS2 Deagle Tips for Landing Headshots on Eco Rounds
You bought a Desert Eagle on an eco round, peeked a rifler, fired four fast shots and hit nothing.