Getting your sensitivity wrong costs you more duels than bad aim ever will. CS2 sensitivity settings determine how much your crosshair moves per inch of mouse movement, and if that number is off, no amount of practice will fix the inconsistency. This guide covers everything from eDPI to polling rate so you can dial in the right CS2 mouse settings and stop second-guessing your setup.
There is no universally correct sensitivity. What exists is a framework for finding yours, and that is exactly what this covers.
DPI, in-game sens, 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].
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 cursor 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 200–600) requires more physical mouse movement but allows finer micro-adjustments. Higher eDPI (1,000 and above) enables faster flicks but makes small corrections harder. The range in between is where most competitive play happens.
What pro CS2 players actually use
Professional players cluster heavily in the 400–900 eDPI range. 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. This is not a coincidence. 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 personal CS2 sensitivity
Start with a benchmark rather than a guess. Most players find a useful starting point somewhere between 800 and 1,200 eDPI. Set your DPI to 400 or 800 in your mouse software, then set your in-game sensitivity to land in that eDPI range. From there, the adjustment process is diagnostic.
The self-diagnosis method is straightforward. Load into a practice server or a Workshop map like Aim Botz. If you are consistently overshooting targets, your sensitivity is too high. If you are consistently undershooting or running out of mousepad before completing a turn, it is too low. Adjust in small increments, no more than 10% at a time, and give each change at least two or three full practice sessions before judging it. Changing sensitivity after a single bad game is how players end up stuck in an endless loop of adjustments.
A useful physical reference point is the 360-degree turn distance. At your chosen sensitivity, how far does your mouse need to travel to complete a full 360-degree rotation? Competitive players generally land somewhere between 25 and 40 centimeters for a full rotation. Below 20cm, micro-corrections become unreliable. Above 50cm, fast flicks across the map become physically awkward. This is not a hard rule, but it is a practical sanity check.
Once a sensitivity feels right, commit to it 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.
Polling rate, raw input, and other settings that affect aim
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.
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,000Hz polling rate means 1,000 reports per second. Higher polling rates (1,000Hz and above) reduce the gap between physical movement and what the game registers. Most modern gaming mice support at least 1,000Hz. For CS2 specifically, 1,000Hz is the standard competitive baseline. Rates above that offer diminishing returns for most players.
Windows sensitivity
Windows pointer speed should be set to the default sixth notch out of eleven. This is the only setting where Windows applies a 1:1 multiplier. Any other setting introduces scaling that interacts unpredictably with in-game sensitivity, even with raw input enabled.
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.
If you are upgrading your loadout once your aim settings are locked in, Skinvault’s inventory updates regularly and lists skins across all float ranges so you can find exactly the condition you are after without overpaying on the Steam Community Market.
