CS2 Mouse Settings: DPI, Sensitivity and eDPI

DPI vs in-game sensitivity - the difference

DPI (dots per inch) is a hardware property of the mouse itself: how many counts the sensor registers per inch of physical movement. DPI is set in the mouse driver or with a button on the body and does not depend on the game.

In-game sensitivity is a software multiplier inside CS2 that is applied to the signal coming from the mouse. The sensitivity console command sets this value, usually between 0.5 and 3.

The resulting in-game crosshair speed is the product of DPI and sensitivity. That is why the two settings cannot be considered separately: low DPI with high sensitivity can produce the same speed as high DPI with low sensitivity.

DPI changes sensor precision at the hardware level, while sensitivity is only a software multiplier. Change one at a time and keep the other stable.

What eDPI is and how to calculate it

eDPI (effective DPI) is the effective sensitivity, a single number that lets you compare the settings of different players regardless of their DPI. It is calculated with a simple formula.

It is eDPI, not DPI or sensitivity alone, that defines the real speed of crosshair movement. Two players with the same eDPI move the crosshair at the same speed, even if one uses 400 DPI with 2.0 sens and the other 800 DPI with 1.0 sens.

eDPI = DPI x sensitivity

# Examples:
400 DPI x 2.0 sens = 800 eDPI
800 DPI x 1.0 sens = 800 eDPI
1600 DPI x 0.5 sens = 800 eDPI
800 DPI x 1.5 sens = 1200 eDPI

Recommended ranges for CS2

Most professional CS2 players keep their eDPI roughly between 700 and 1100. This is a compromise between accuracy at long range and the ability to turn quickly.

If you are just starting out, use 800 DPI and 1.0 sensitivity - that gives 800 eDPI and is considered a universal starting point. Adjust from there.

Low sens needs more desk space but gives steadier micro-corrections. High sens saves space but makes precise long-range shooting harder.

• Low sensitivity: 400-700 eDPI - maximum accuracy, needs a large mousepad and arm movement
• Medium sensitivity: 700-1100 eDPI - the optimal balance for most players
• High sensitivity: 1100-1600 eDPI - fast turns, harder to control recoil

Polling rate

Polling rate is how often the mouse reports its position to the computer, measured in hertz. 1000 Hz means 1000 updates per second, that is about 1 ms of latency.

CS2 works well with high polling rates. For a stable result use 1000 Hz - that is the standard. If your mouse and system support 2000, 4000 or 8000 Hz you can try it, but the gain is mostly noticeable on powerful hardware and high FPS.

A very high polling rate (4000-8000 Hz) loads the CPU. If your FPS dropped after raising the rate, go back to 1000 Hz.

• 500 Hz - minimally acceptable, about 2 ms latency
• 1000 Hz - the recommended standard, about 1 ms latency
• 2000-8000 Hz - for high FPS and a powerful PC, demands CPU resources

Raw input and disabling acceleration

Raw input makes the game take the signal directly from the mouse, bypassing the operating system smoothing and acceleration. This is critical for predictable aim: the same hand movement always produces the same crosshair travel.

Mouse acceleration is when crosshair speed depends on how fast you move your hand, not only on the distance travelled. For a shooter it must be fully disabled so you can build muscle memory.

In CS2 raw input is enabled by default in the mouse settings. The commands above mirror this through the console and guarantee no acceleration.

m_rawinput "1"          // enable raw input
m_mouseaccel1 "0"        // disable acceleration (threshold 1)
m_mouseaccel2 "0"        // disable acceleration (threshold 2)
m_customaccel "0"        // disable custom acceleration

Mouse settings in Windows

Even with raw input enabled it is worth cleaning up the system settings - in case you alt-tab to a window or use other modes.

The key step is to disable Enhance pointer precision, which is the system acceleration. Keep the pointer speed slider exactly in the middle, at the 6th of 11 positions, so Windows does not scale the mouse signal.

The sixth slider position (the middle) is the only one where Windows passes the mouse signal through 1:1 without scaling.

1. 1Open Windows Settings - Bluetooth and devices - Mouse
2. 2Go to Additional mouse settings - Pointer Options tab
3. 3Uncheck Enhance pointer precision
4. 4Set the Select a pointer speed slider exactly in the middle (6/11)
5. 5Apply the changes and restart CS2

zoom_sensitivity_ratio for snipers

When aiming through a scope (AWP, SSG 08, auto-snipers) a separate multiplier zoom_sensitivity_ratio is applied. It defines how much the scoped sensitivity differs from the normal one.

A value of 1.0 does not mean identical on-screen speed - because the field of view shrinks in the scope, the crosshair behaves differently. Many players leave the default, but for a consistent feel a ratio around 1.0 is common.

If the crosshair feels too fast while scoped, lower the value; if too slow, raise it. Change in small steps of 0.1.

zoom_sensitivity_ratio "1.0"   // sensitivity multiplier while scoped
// usual range 0.8 - 1.2

How to find your sensitivity

There is no ideal sensitivity for everyone - it is tuned to your grip, mousepad size and playstyle. The main thing is consistency: once you find a value, do not change it for months so you can build muscle memory.

A practical method is training on maps like aim_botz or workshop training maps. Shoot at static and moving bots and watch whether you can settle the crosshair without overshooting.

Change only one parameter at a time - either DPI or sensitivity. That makes it easier to tell what actually affected the feel.

1. 1Start with 800 DPI and 1.0 sensitivity (800 eDPI)
2. 2Check a 180 degree turn: one swipe across the mousepad without lifting your hand should be enough
3. 3If you constantly overshoot the target - lower eDPI by 50-100
4. 4If you cannot turn in time or settle the crosshair - raise eDPI
5. 5Lock in the value you found and train on it for at least a week before any new changes