There is no single best sensitivity for CS2. What most competitive players share is a fairly low eDPI — the product of DPI multiplied by in-game sensitivity — and a hardware DPI of either 400 or 800. If your eDPI lands somewhere between 600 and 1,100, you are in the range where the majority of serious players operate. This guide explains why that range works, how to find your own number, and how to make sure every other setting in your input chain is clean.
DPI, in-game sensitivity, and eDPI explained
These three numbers are distinct, and confusing them leads to bad comparisons and worse setups. DPI (dots per inch) is a hardware setting that controls how many pixels your cursor moves per inch of physical mouse movement. It is set at the driver or hardware level, not inside CS2. In-game sensitivity is the multiplier CS2 applies on top of your DPI. It is set via Settings → Mouse → Sensitivity, or with the console command sensitivity [value]. The CS2 default sensitivity is 1.0 [VERIFY: confirm this has not changed in a recent patch].
eDPI (effective DPI) is the number that actually matters for comparison. The formula is simple: eDPI = DPI × in-game sensitivity. A player running 400 DPI at 2.0 in-game sensitivity has an eDPI of 800. Another player running 800 DPI at 1.0 has the same eDPI of 800. The crosshair behavior is identical. eDPI is the standardized way to compare CS2 sensitivity across setups regardless of how the individual numbers are split.
Lower eDPI (roughly 400–700) requires more physical mouse movement but allows finer micro-adjustments. Higher eDPI (1,200 and above) enables faster flicks but makes small corrections harder. The range in between is where most competitive play happens.
CS2 eDPI quick-reference table
Use this table as a starting point. Find your DPI in the left column, pick a sensitivity value, and read off the resulting eDPI. The formula is always eDPI = DPI × sensitivity. For example: 800 DPI × 1.1 sensitivity = 880 eDPI.
| DPI | Sensitivity | eDPI |
|---|---|---|
| 400 | 1.5 | 600 |
| 400 | 2.0 | 800 |
| 400 | 2.5 | 1,000 |
| 800 | 0.8 | 640 |
| 800 | 1.1 | 880 |
| 800 | 1.5 | 1,200 |
| 1600 | 0.5 | 800 |
| 1600 | 0.6 | 960 |
| 1600 | 0.8 | 1,280 |
400 and 800 DPI are the most common hardware choices among competitive players. 1600 DPI is less common at the top level but produces the same eDPI if you pair it with a lower in-game sensitivity. The split between DPI and in-game sensitivity does not affect feel — only the combined eDPI does.
What pro CS2 players actually use
Professional players cluster heavily in the 400–900 eDPI range [ADD SOURCE: link to a current pro settings database such as prosettings.net or liquipedia before publishing]. The most common hardware setup is 400 DPI paired with an in-game sensitivity between 1.5 and 2.5, producing eDPI values in the 600–1,000 range. That range gives enough precision for tight crosshair placement while still allowing fast enough flicks to cover common CS2 angles.
AWPers tend to sit at the lower end of that spectrum. Precise, deliberate crosshair movement matters more than reaction-speed flicks when you are holding a single angle with a one-shot weapon. Riflers vary more, but few elite players run above 1,200 eDPI. High sensitivity introduces inconsistency at the micro-adjustment level, which shows up most in spray control and counter-strafing precision.
The takeaway is not to copy a pro’s exact numbers. Their eDPI was shaped by years of muscle memory built at that setting. The takeaway is that if your CS2 aim settings and full setup are above 1,500 eDPI, there is a real mechanical reason most competitive players avoid that range.
How to find your best CS2 sensitivity in 5 steps
Rather than guessing, work through this process once and commit to the result. If you want to aim faster in CS2, a stable sensitivity is the foundation everything else builds on.
- Set a starting eDPI. Pick 400 or 800 DPI in your mouse software. Set your in-game sensitivity so your eDPI lands between 800 and 1,000. This is a neutral starting point, not a final answer.
- Run the 180-degree turn test. On a blank wall in a practice map, place your crosshair on a reference point, then swipe your mouse as far as it comfortably travels in one direction. You should rotate close to 180 degrees. If you overshoot badly, your eDPI is too high. If you barely move, it is too low. Adjust by no more than 10% at a time.
- Test on a practice map. Load into a CS2 practice server or a Workshop map such as Aim Botz. If you consistently overshoot targets, sensitivity is too high. If you run out of mousepad before completing a flick, it is too low.
- Check your 360-degree distance. At your chosen sensitivity, measure how far your mouse needs to travel to complete a full 360-degree rotation. Competitive players generally land between 25 and 40 centimeters. Below 20 cm, micro-corrections become unreliable. Above 50 cm, fast flicks become physically awkward.
- Commit and give it time. Once a sensitivity feels workable, lock it in for at least two weeks of consistent play before deciding whether to adjust further. Muscle memory needs time to build, and sensitivity changes reset that process.
Pairing a stable sensitivity with good crosshair placement is what actually moves your aim forward. One without the other leaves improvement on the table.
Polling rate, raw input, and Windows sensitivity for CS2
Sensitivity and DPI are only part of the picture. Several other settings directly influence how accurately your physical mouse movement translates into in-game cursor movement. Getting these right also affects input latency, which is tied to your video settings and overall performance.
Raw input
Raw input should always be enabled. In CS2, this is set via Settings → Mouse → Raw Input: On, or with the console command m_rawinput 1. Raw input bypasses Windows pointer acceleration entirely, meaning your in-game sensitivity is the only variable affecting crosshair movement. Without it, Windows can modify the input signal and introduce inconsistency that changes behavior depending on how fast you move the mouse.
Separately, Windows Enhance Pointer Precision should be disabled in Windows mouse settings. Raw input in CS2 does not automatically override this at the OS level. Both need to be correct. The console command m_customaccel 0 confirms that no custom acceleration curve is being applied on top.
Polling rate
Polling rate is how often your mouse reports its position to your PC, measured in Hz. A 1,000 Hz polling rate means 1,000 reports per second. Higher polling rates reduce the gap between physical movement and what the game registers. Most modern gaming mice support at least 1,000 Hz. For CS2 specifically, 1,000 Hz is the standard competitive baseline. Rates above that offer diminishing returns for most players.
Windows sensitivity for CS2
Windows pointer speed should be set to the default sixth notch out of eleven. This is the only position where Windows applies a true 1:1 multiplier with no scaling. Any other setting introduces a modifier that interacts unpredictably with your in-game sensitivity, even with raw input enabled. If you are troubleshooting inconsistent aim across sessions, this is one of the first things to check. The correct Windows sensitivity for CS2 is the center notch — leave it there and do not touch it.
Converting sensitivity from Valorant, CS:GO, or other games
If you are moving to CS2 from another game, you do not have to start from scratch. The general approach is to find the conversion factor between the two games’ sensitivity scales and apply it to your existing setting.
For CS:GO to CS2, the sensitivity scale is the same [VERIFY: confirm no engine-level sensitivity change has been introduced]. Your CS:GO sensitivity number carries over directly.
For Valorant to CS2, the two games use different sensitivity scales. The general formula is: CS2 sensitivity = Valorant sensitivity × conversion factor [VERIFY: confirm the current multiplier from a reliable source such as mouse-sensitivity.com before publishing, as this can change with game updates]. Tools like mouse-sensitivity.com let you enter your exact settings and output the equivalent for CS2, which is more reliable than applying a static number manually.
For any other game, the same principle applies: use a sensitivity converter tool, enter your source game’s DPI and sensitivity, select CS2 as the target, and use the output as your starting point. Then run through the five-step method above to fine-tune from there. Once you have your numbers dialed in, working on hitting more headshots becomes a much more productive use of your practice time.
Common sensitivity mistakes CS2 players make
The most common mistake is changing sensitivity too often. After a rough session, the instinct is to adjust something, and sensitivity is the easiest dial to turn. But bad games are usually caused by positioning, decision-making, or tilt — not sensitivity. Chasing a perfect number through constant changes prevents muscle memory from developing at any setting.
Running mismatched settings is another frequent issue. Players set raw input to On inside CS2 but leave Enhance Pointer Precision active in Windows, or they set a non-default Windows pointer speed and wonder why their aim feels inconsistent across sessions. The entire input chain needs to be clean, from the OS level down to the in-game console commands.
A third mistake is choosing sensitivity based on what a specific pro player uses without accounting for eDPI. Copying a pro’s in-game sensitivity number without matching their DPI produces a completely different eDPI and a completely different feel. Always convert to eDPI before making comparisons.
Finally, practicing at a different sensitivity than you play at is a slow way to build bad habits. If you run custom practice servers or Workshop maps, make sure every session uses your actual competitive settings. Consistency across all play time is what builds reliable aim, not isolated drills at an arbitrary number.
FAQ
What is a good eDPI for CS2?
Most competitive players use an eDPI between 600 and 1,100. That range balances precision for micro-adjustments with enough speed for flicks across common angles. If you are above 1,500 eDPI, you will likely struggle with spray control and fine corrections. Below 400 eDPI, fast flicks become physically difficult. Start in the 800–1,000 range and adjust from there.
Is 400 or 800 DPI better for CS2?
Neither is objectively better. Both are equally common among professional players. What matters is the eDPI you produce, not the DPI alone. 400 DPI requires a higher in-game sensitivity to reach the same eDPI as 800 DPI at a lower in-game sensitivity. The crosshair behavior is identical if the eDPI matches. Pick whichever DPI your mouse handles most cleanly at its sensor’s optimal tracking speed.
What is the default CS2 sensitivity?
The default in-game sensitivity in CS2 is 1.0 [VERIFY: confirm this in the current build]. This is not a recommended competitive setting — it is simply the out-of-the-box value. Your effective eDPI at default sensitivity depends entirely on your mouse’s DPI setting. Most players will want to adjust this as part of the setup process described above.
Should I turn off mouse acceleration in CS2?
Yes. Enable raw input in CS2 (m_rawinput 1), disable Windows Enhance Pointer Precision, and confirm m_customaccel 0 is set. Mouse acceleration makes your crosshair move a different distance depending on how fast you physically move the mouse, which makes consistent aim impossible to develop. There is no competitive scenario where leaving it on is beneficial.
How often should I change my sensitivity?
As rarely as possible once you have settled on a range. Give any new sensitivity at least two full weeks of consistent play before evaluating it. Changing after a single bad session is the most common way players stall their aim development. If you feel the need to change, move by no more than 10% at a time and run the five-step method again rather than guessing.
Once your settings are locked in, make your loadout yours. Browse budget loadouts in CS2 for ideas at every price point, or trade for a new skin instantly using Skinvault’s trade bots.
