Open any professional CS2 config and you'll notice the same thing over and over: low DPI, low sensitivity, and a mouse that barely seems to move relative to how far the crosshair travels. That's not a coincidence or a superstition — it's the natural end point of a game that rewards millimetre-level precision. Here's why the standard looks the way it does, and how to arrive at a setting that's genuinely yours.
Under the hood, CS2 turns your view by a fixed amount for each unit of mouse movement. That constant is the game's yaw, and in CS2 it's 0.022 degrees per count at a sensitivity of 1. It sounds like trivia, but it's the reason two players with identical DPI and identical in-game sliders will always turn exactly the same distance. It's also the reason a "sensitivity of 2" in CS2 feels nothing like a "sensitivity of 2" in a game with a different yaw. The slider is meaningless in isolation; the yaw is what gives it physical meaning.
The pro-standard combination is a low DPI — almost always 400 or 800 — paired with an in-game sensitivity somewhere around 1.5 to 2.5. Put together, that produces a slow, deliberate feel where your whole forearm sweeps across the pad for a wide turn and your fingers handle the fine adjustments.
There are two practical reasons this works. First, lower DPI means the sensor reports fewer counts per inch, so the small tremors and imperfections in your hand movement translate into smaller on-screen wobble. Second, a slow overall setting gives you more physical room to correct. A tiny flinch at 400 DPI moves your crosshair a hair; the same flinch at 3200 DPI throws it off the target entirely. Precision comes from having distance to work within.
Worth saying plainly: 400 and 800 aren't sacred. They're round, universally supported values that happen to pair cleanly with a low sensitivity. If your mouse tracks flawlessly at 1600, that's fine too — what matters is the combined feel, not the headline DPI.
Because DPI and sensitivity only mean something together, players use two derived figures to compare setups honestly.
If you want to see exactly how these interact, plug your figures into the Sensitivity Converter — it'll show your eDPI and cm/360 the moment you type in your DPI and sensitivity. We break the concept down further in eDPI Explained.
This is where most people accidentally sabotage themselves. They memorise their sensitivity number in Valorant or Apex, type the same number into CS2, and wonder why their aim feels wrong. It feels wrong because every game has its own yaw, so an identical slider value turns a different amount.
The fix is to match your cm/360, not the slider. Take the DPI and sensitivity you already trust, and convert them to the CS2 sensitivity that reproduces the same physical distance per turn. Our Sensitivity Converter does this directly — pick your source game and CS2, and it hands you the exact number. For the reasoning behind it, see How to Convert Mouse Sensitivity Between Games. Do this once and your months of built-up muscle memory carry straight over.
None of the above holds up if the operating system is quietly editing your movement. Two settings guarantee a clean signal:
You can confirm your mouse is behaving with the DPI Analyser: measure a slow pass and a fast pass across the same distance. If both report the same DPI, your signal is clean and CS2 is receiving honest movement.
Set it, then leave it alone. The single biggest mistake in aim is constantly changing settings. Once acceleration is off and your DPI is verified, give any new sensitivity at least a week before you judge it.
Standards are a starting line, not a finish line. Here's a sane way to find your number: begin at 800 DPI with an in-game sensitivity of 1.0 (that's 800 eDPI, comfortably mainstream). Play for a few days without touching it. If you frequently overshoot when you flick, drop the sensitivity a little. If you can't turn to check your flank without lifting and repositioning the mouse repeatedly, raise it a little. Change one variable at a time, and only in small steps.
Pay attention to your mousepad size too — a slow cm/360 needs physical room, and if you're constantly running off the edge of a small pad, that's a hardware limit, not a skill issue. The right setting is the one that lets your calm, controlled aim and your rushed, mid-fight aim start to look like the same thing. When that happens, you've found it.