Mouse Sensitivity: eDPI & cm/360 Calculator

Understanding the mouse sensitivity (eDPI and cm/360) calculator — concept and principle

Players in shooters often say "my sens is 1.5" but that number means little without the mouse DPI and the game. This calculator turns DPI and in-game sensitivity into two comparable measures: eDPI (effective DPI) and the distance you must move the mouse to turn a full 360°. Use it to compare your settings with other players, keep the same feel on a new mouse, or tune your aim.

eDPI compares settings in one game; cm/360 is the real arm distance for a full turn, here 34.6 cm.

How it is calculated

eDPI = mouse DPI × in-game sensitivity.
Inches per 360° = 360 ÷ (sensitivity × yaw) ÷ DPI.
cm per 360° = inches per 360° × 2.54.

DPI (more correctly CPI, counts per inch) is how many counts the mouse sends per inch of movement. Yaw is the number of degrees the camera turns per count at sensitivity 1. Commonly used community values are 0.022° for CS2, Apex and other Source-based games, 0.07° for Valorant and 0.0066° for Overwatch 2.

The principle

Each count from the mouse rotates your view by sensitivity × yaw degrees. Dividing 360° by that angle gives the number of counts needed for one full turn. Dividing counts by DPI converts them into inches of physical movement. Unlike eDPI, cm/360 includes the game's yaw, so it is the true physical measure and can be compared across games. eDPI is only comparable between players of the same game.

Worked example

Defaults: 800 DPI, sensitivity 1.5, CS2 (yaw 0.022°).

eDPI = 800 × 1.5 = 1,200.
Degrees per count = 1.5 × 0.022 = 0.033°.
Counts per 360° = 360 ÷ 0.033 = 10,909.
Inches per 360° = 10,909 ÷ 800 = 13.64 in.
cm per 360° = 13.64 × 2.54 = 34.64 cm.

Each point is the calculator re-run with only “Mouse DPI” changed; the gold point is the default example. Change the inputs above and this chart follows your numbers.

Mouse DPI	eDPI
200	300
400	600
600	900
800	1,200
1,000	1,500
1,200	1,800
1,600	2,400

How to read the result

A larger cm/360 means a lower sensitivity: more arm movement, but finer control for small adjustments. A smaller cm/360 means faster turns with less precision. As a rough guide, many competitive tactical-shooter players use something like 30–60 cm/360, while fast-paced games often use lower values. There is no single correct number; what matters is that you can make your usual flicks and track targets comfortably on your mousepad.

Common mistakes

Comparing eDPI between different games; use cm/360 instead.
Forgetting Windows pointer settings or mouse acceleration, which can change results in some games.
Assuming the DPI printed on the mouse is exact; real DPI can differ slightly.
Expecting scoped or aim-down-sights sensitivity to match; those use separate multipliers.

Keep in mind: Yaw values are widely used community figures, and games can change them in updates. Treat results as close estimates, especially for Fortnite and Rainbow Six, whose settings work differently.

Frequently asked questions

Is higher DPI better?

Not by itself. With a fixed cm/360 you can lower in-game sensitivity as you raise DPI. Many players use 400–1,600 DPI.

How do I keep the same feel on a new mouse?

Keep cm/360 constant: new sensitivity = old sensitivity × old DPI ÷ new DPI.

What is a "normal" eDPI in CS2?

Many players fall somewhere around 600–1,200 eDPI, but personal preference varies widely.

Sources: Valve Developer Community – m_yaw console variable (default 0.022)

Checked 8 Nov 2026. Official league / federation formulas where they exist; widely used community formulas otherwise. For fun and analysis — not betting advice.

Your numbers