Skip to content
Set up my rig

CS2 sensitivity guide: eDPI, cm/360 and zoom sensitivity

What eDPI and cm/360 mean in CS2, typical ranges, the zoom ratio and how to convert from another game.

DontLag · · updated Nov 12, 2026

CS2 sensitivity guide: eDPI, cm/360 and zoom sensitivity

In CS2, your effective sensitivity is DPI multiplied by in-game sensitivity. Most players use 400 or 800 DPI with an in-game value between about 1.0 and 3.0, which gives an eDPI of roughly 800 to 1,400. These are starting points.

eDPI and cm/360

eDPI = DPI x in-game sensitivity. cm/360 tells you how many centimetres you move the mouse for a full turn. For CS2 the formula is (2.54 x 360) divided by (DPI x sensitivity x 0.022). A typical range is about 25 to 45 cm/360.

Concrete yard inside a warehouse on a Counter-Strike 2 map

Test your sensitivity in a quiet offline map first.

Typical settings

DPIIn-game sensitivityeDPI
4002.0 to 3.0800 to 1,200
8001.0 to 1.5800 to 1,200

Raw input

The raw input option was removed. CS2 now reads your mouse directly, so there is no setting to turn on.

Zoom sensitivity

The zoom_sensitivity_ratio command controls how sensitive scoped weapons feel compared to normal aiming. The default is 1.0, and many players use between 0.8 and 1.0. Lower numbers feel slower when scoped.

Converting from VALORANT

CS2 uses a different yaw value from VALORANT. To keep the same feel, multiply your VALORANT sensitivity by about 3.18 at the same DPI. For example, 0.35 in VALORANT is about 1.1 in CS2. See our VALORANT sensitivity guide for the other direction.

Finding your value

  1. Pick a DPI and keep it.
  2. Start with an eDPI near 1,000.
  3. Play several matches and note whether you overshoot or undershoot.
  4. Change by about 0.1 at a time.
  5. Warm up the same way before each session.

Mouse and surface

A big mouse pad makes low sensitivity easy. Turn off mouse acceleration in Windows and keep your polling rate at what your mouse supports. A consistent set-up is more important than any single number.

Common mistakes

  • Raising the DPI to feel faster instead of changing the in-game value.
  • Changing the value after one bad session.
  • Different zoom ratios on different scopes, which leads to inconsistent aim.

Quick tips

  • Add the setting to your autoexec: see our config guide.
  • High, stable frames improve aim. See the CS2 FPS boost page.

Warm-up routine

Before queuing, spend five minutes on an aim training map or in deathmatch. Do the same drills each day: tracking a moving target, flicking between targets and holding an angle with a quick tap. A steady routine makes it easier to tell if a new setting is helping or whether you are just warming up differently.

Console commands

You can set sensitivity directly with the console command sensitivity, for example sensitivity 1.2. Add this to your autoexec file so it is always applied. The zoom_sensitivity_ratio command works the same way.

Frequently asked questions

Is there a right sensitivity? No. Choose one that allows both small adjustments and a quick turn.

Should I match my other shooters? If you play several games, using cm/360 to match them can help, but small differences are normal.

Does a higher DPI help? Not noticeably, once you are at 400 or 800.

Practice map ideas

Use an aim training map from the community workshop or a deathmatch server to test settings. Track a moving target for a minute, then flick to static targets. Compare your results before and after each change, and stop changing once the numbers stop improving. Treat the first week with a new setting as a trial, and go back only if the problem is clear.

When to change it

Change sensitivity only if something has clearly felt off for more than a week, such as constant overshooting or not being able to turn in time. If you change hardware, such as a new mouse or pad, re-check the values with the cm/360 formula to keep the same turning distance.

Related guides