cm/360 & eDPI calculator

cm/360 & eDPI calculator

cm/360 is the one number you can fairly compare across mice, DPI settings and games: how many centimetres you move the mouse for a 360° turn. More centimetres means a slower sensitivity.

Pixels are calculated for CS2 only, because its field of view is fixed. In other games you set the FOV yourself, so the pixel step depends on your setting. The step in degrees is exact for every game in the list.

Changing DPI? Convert your sensitivity

Going from 400 to 800 DPI means halving your sensitivity, otherwise the mouse is twice as fast. The calculator gives you the sensitivity that keeps your cm/360 exactly the same.

Note: the conversion is only as accurate as the DPI you enter. A mouse’s real DPI can differ from the number on the box. If the mouse feels different after the change, measure its real DPI (see below).

Sensitivity converter between games

Moving from CS2 to Valorant or from Apex to Overwatch 2? The converter finds the sensitivity at which a full turn takes the same hand movement. Your DPI stays the same.

• This converts hip-fire aim. Every game handles ADS and scope multipliers its own way – set those separately.
• Battlefield 6 and games without a known formula. One honest number is not possible here. FPS Performance Lab measures the turn directly: start the measurement, Alt+Tab into the game, make one or more full turns, come back – and you have that game’s cm/360.

400 vs 800 DPI in CS2

At the same eDPI there is no difference in accuracy. 400 DPI × 2, 800 DPI × 1 and 1600 DPI × 0.5 are exactly the same turn in CS2: 51.95 cm per 360°. Only the size of one crosshair step changes. Higher DPI with lower sensitivity gives finer steps.

The feeling that you “aim better on 400” usually comes from something else: the sensitivity was not converted after the DPI change, the mouse’s real DPI differs from the declared one, an older sensor smooths movement at high DPI, or it is simply habit.

At 1080p and 1440p with a typical eDPI, 400 DPI works fine – the step is smaller than a pixel. The problem only appears at 4K or with a high sensitivity. Then one count moves the crosshair by more than a pixel, and switching to 800 or 1600 DPI with a converted sensitivity makes sense.

• What pros use: 47% play on 400 DPI, 46% on 800, 5% on 1600 (csdb.gg, 820 players, data from 19 Oct 2026).
• 4000–8000 Hz polling: at such high rates you want at least 1600 DPI, so the mouse has something to send in every report.
• Very high DPI: some older sensors (e.g. PMW3360 from 2100 CPI) smooth movement, and jitter grows from about 10,000 CPI. Newer sensors (PAW3395, PAW3950) do not smooth.

What cm/360 and eDPI mean

cm/360 tells you how many centimetres of mouse movement make a full turn. It does not depend on the game or the mouse, so it works for comparisons. eDPI (DPI × sensitivity) is handy, but only compare it within one game – 800 eDPI in CS2 and in Valorant are completely different speeds.

cm/360 = 360 ÷ (DPI × sensitivity × yaw) × 2.54 eDPI = DPI × sensitivity crosshair step [°] = sensitivity × yaw

Hence a simple rule: divide your CS2 sensitivity by 3.18 to get Valorant, multiply it by 3.33 to get Overwatch 2. Apex uses the same formula as CS2.

DPI and sensitivity myths

• “Windows pointer speed affects CS2” – no. CS2 always reads raw mouse input (the m_rawinput option is gone). Pointer speed and “Enhance pointer precision” only apply to the desktop and menus.
• “High DPI causes pixel skipping” – DPI alone does not. Skipping depends on the crosshair step, i.e. sensitivity, FOV and resolution. High DPI with low sensitivity actually gives a finer step.
• “The DPI on the box is your DPI” – not always. Sensor tests show deviations between real and declared DPI. Two mice “at 800” can have different cm/360.
• “There is one best sensitivity” – there isn’t. Half of CS2 pros play between 707 and 960 eDPI – and just as many play outside that range. What matters is whether your hand stops on the target.

Your mouse’s real DPI

The calculator is exact, but only with what you enter. If your mouse actually runs at 760 instead of 800 DPI, every result on this page is off by 5%.

FAQ

What is the best sensitivity for CS2?

There is no single best one. The median CS2 pro plays at 800 eDPI (e.g. 400 DPI × 2 or 800 DPI × 1), about 52 cm/360. Half of them sit between 707 and 960 eDPI. A good sensitivity is one where you hit with your first movement and do not overshoot. Change it in small steps (5–10%) and check the effect under the same conditions.

Is 400 DPI better than 800 DPI?

No, as long as the eDPI is the same. 400 × 2 and 800 × 1 turn you exactly the same. 800 DPI only gives a finer crosshair step, which matters at 4K or with a high sensitivity.

How do I convert CS2 sensitivity to Valorant?

Divide your CS2 sensitivity by 3.18 (exactly 0.07 ÷ 0.022). Sensitivity 1 in CS2 is about 0.314 in Valorant at the same DPI. The other way round, multiply by 3.18.

Does Windows pointer speed affect aim in CS2?

No. CS2 reads raw mouse input, so pointer speed and “Enhance pointer precision” do not change in-game aim. They only matter on the desktop.

What is a good cm/360?

Half of CS2 pros play at about 43–59 cm/360 (960–707 eDPI). That is a CS2 reference – between games, compare cm/360, not eDPI.

Sources

• csdb.gg – CS2 pro sensitivity and DPI (820 players, data from 19 Oct 2026)
• Liquipedia – Counter-Strike mouse settings
• Microsoft – raw mouse input
• TechPowerUp – PMW3360 smoothing, PAW3395, 8000 Hz polling
• mouse-sensitivity.com – DPI and pixel skipping

Pixel calculations: CS2 vertical FOV 73.74°, horizontal FOV derived from the aspect ratio, step at the screen centre. Page current as of 26 Oct 2026.