DeviceTest

CS2 eDPI Calculator — Effective DPI and cm/360

CS2 players compare setups with eDPI and cm/360 rather than raw sensitivity, because the same number means different things at different DPI. This page does that math, and converts your CS2 sensitivity to other shooters.

Part of the eDPI Calculator.

Quick answer: Enter your mouse DPI and your CS2 sensitivity: eDPI = DPI × sensitivity, and cm/360 = 360 ÷ (sensitivity × DPI × 0.022). A typical competitive CS2 setup lands between 25 cm and 45 cm per 360° turn, which corresponds to roughly 800 eDPI at 800 DPI with sensitivity 1.0.

Typical: 0.110

eDPI
1,600
DPI × sensitivity
cm / 360°
10.23 cm
very fast — flick-oriented
inches / 360°
4.03 in
for imperial mousepads
Resolution
0.0284 cm/°
mouse travel per degree
Same turn distance in other games (sensitivity to enter there)
Valorant (yaw 0.07)0.6286
Apex Legends (yaw 0.022)2.0000
Overwatch 2 (yaw 0.0066)6.6667
Team Fortress 2 (yaw 0.022)2.0000
Quake Live (yaw 0.022)2.0000
Fortnite (yaw 0.005555)7.9208
Rainbow Six Siege (yaw 0.00572957795130823)7.6794
Call of Duty: Warzone (yaw 0.0066)6.6667

Scope sensitivity has its own multiplier (zoom_sensitivity_ratio); conversions here apply to hip-fire.

GameYaw (deg/count)Sensitivity for the same cm/360Confidence
Counter-Strike 20.0222.0000high
Valorant0.070.6286high
Apex Legends0.0222.0000high
Overwatch 20.00666.6667high
Team Fortress 20.0222.0000high
Quake Live0.0222.0000high
Fortnite0.0055557.9208medium
Rainbow Six Siege0.005729577951308237.6794medium
Call of Duty: Warzone0.00666.6667medium
Only games with a publicly documented yaw constant are listed — a conversion that is slightly wrong is worse than no conversion. If you are not sure of your real DPI, measure it first with the mouse DPI test. Scoped and ADS sensitivities have their own multipliers and are not covered here.
Core facts
Yaw constant used0.022 degrees per count (high confidence — documented, not estimated)
In-game controlSensitivity (sensitivity console value)
Typical rangeMost CS2 players sit between 600 and 1200 eDPI, with 800 eDPI (800 DPI × 1.0, or 400 DPI × 2.0) the classic baseline.
CaveatScope sensitivity has its own multiplier (zoom_sensitivity_ratio); conversions here apply to hip-fire.

How the Counter-Strike 2 numbers are calculated

CS2 inherited the Source sensitivity scale, so a sensitivity of 1.0 with 800 DPI is the long-standing reference point. Scope sensitivity is separate.

Keeping the same feel when you change DPI

Your cm/360 only changes if DPI × sensitivity changes. If you raise DPI from 400 to 800, halve the in-game sensitivity and your turning distance stays identical — the calculator will show the same cm/360 for both setups, which is the quickest way to confirm you have compensated correctly.

When to use this test

  • Copying a Counter-Strike 2 sensitivity from a video or a friend's setup into your own mouse settings
  • Comparing your Counter-Strike 2 setup with players who report DPI only, or eDPI only
  • Moving to Counter-Strike 2 from another shooter without losing your turn distance
  • Checking whether your sensitivity sits inside the range most Counter-Strike 2 players use

Frequently asked questions

Frequently Asked Questions

What is a normal Counter-Strike 2 sensitivity?
Most CS2 players sit between 600 and 1200 eDPI, with 800 eDPI (800 DPI × 1.0, or 400 DPI × 2.0) the classic baseline. Converted to cm/360 that is the range most players find comfortable, though preference and mousepad size matter as much as the number.
Can I use my Counter-Strike 2 sensitivity in another game?
Yes — use the sensitivity converter on this site, which matches the physical turn distance (cm/360) between games rather than the slider value.
Why does the calculator not include scope or ADS sensitivity?
Because scoped aiming uses an additional multiplier in Counter-Strike 2 that is separate from the hip-fire value. Convert the hip-fire sensitivity here, then adjust the scope setting in game.

More gaming sensitivity tools