There is no single correct configuration here, but there is a range that most good players land inside.
Short answer
Start from the middle of the sensible range, play a week without touching it, and only then adjust one value.
Changing sensitivity resets weeks of aim training, so change it deliberately or not at all. The difference between two similar values is smaller than the difference between changing it and leaving it alone. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts.
Re-checking after an update
Input lag comes from the whole chain, not just the in-game setting you are looking at. Visual clarity settings do more for performance in a fight than raw frame rate does. If your result differs from what is described here, note what is different first rather than starting over. Consistency beats optimality — a mediocre setting you have muscle memory for outperforms a perfect one you do not.
Every major patch has a chance of resetting a config file, so keep a copy. If you are coming to this after a long break, the terminology has probably moved on. Defaults are chosen for the median player, which makes them a reasonable starting point and a poor destination.
Finding your own number
Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. What follows assumes you are on a current install and have not modified it. Treat anything stated without a version number as provisional.
- Change one value at a time and give it several sessions.
- Write down the previous value before replacing it.
- Write down what you changed, so you can undo exactly one thing if it goes sideways.
- Re-check after a major update — patches quietly reset things.
Settings to leave alone
Everything below is framed around the current state of Counter-Strike 2 rather than a launch-week impression. Where something depends on your platform or region, that is called out rather than glossed over. Where two approaches both work, the one with fewer moving parts is the one to keep. There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing.
The developers have changed their mind about this at least once, which explains the older advice. The community wisdom on this is roughly half right, and the half that is wrong costs the most time. There is no hidden trick here that the game is keeping from you.
Where pro setups mislead
If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about. The short version is near the top on purpose; the reasoning is there if you want to know why. Most of the disagreement you will find online is two people describing different builds.
Nothing here assumes a particular playstyle beyond wanting the thing to work. A single check up front replaces a lot of guessing later. Do the cheap check before the expensive one — that ordering alone saves most of the frustration.
The values that actually matter
The awkward part is rarely the step itself, it is knowing which step comes first. Screenshots age faster than text, which is why this describes rather than shows. It helps to understand why a step exists, because then you can adapt it when your situation is slightly different.
Where people go wrong
- Changing five things at once and then not knowing which one helped.
- Skipping the prerequisite because it looked optional in someone else's summary.
- Copying a setup wholesale from a streamer without understanding what each part does.
CS2 FAQ
Does this work the same on console and PC?
The logic is identical. Menu paths and button prompts differ, and any real difference is flagged above.
Why do other guides describe this differently?
Most were written for an earlier version and never revisited. Compare the steps against what your build actually shows.
Do I need any mods or third-party tools for this?
No. Everything described here works with the base game on any supported platform.
How long before I know if a change helped?
Several sessions. Anything shorter measures novelty rather than improvement.
Come back to the caveats list if it does not work first time — the answer is almost always in there.