CS2 eDPI, DPI, Sensitivity and cm/360 Explained

Comparing two players’ sensitivity settings is difficult if you only compare the in-game slider. DPI changes the scale of physical mouse movement. eDPI and cm/360 are useful standard descriptions, provided you understand their assumptions.

Start with eDPI

eDPI is DPI multiplied by in-game sensitivity. A player using 800 DPI with sensitivity 1.0 has the same nominal eDPI as someone using 400 DPI with sensitivity 2.0.

That does not mean the two devices behave identically in every respect. Sensor performance, acceleration and other input features can still differ.

• Confirm your active DPI profile in mouse software.
• Avoid confusing CPI or marketing maximums with your current setting.

Translate to physical distance

For the usual Source yaw setting of 0.022, estimated centimeters per 360° is 360 × 2.54 ÷ (DPI × sensitivity × yaw). Lower total scale generally means more physical travel for a full turn.

If you modified m_yaw, provide the actual value. This conversion assumes linear input and a stable configuration; actual physical measurement is a useful check.

• Use the calculator to compare candidate values.
• Measure your real full turn on the same mousepad.

Choose consistency over mythology

There is no universal “pro sensitivity” that suits every grip, desk, mousepad and playstyle. Copying another player’s number without accounting for DPI can produce an unexpectedly fast or slow setup.

Change one variable at a time and allow yourself a consistent test period. Keep a record of what you started with so you can revert.

• Beware guides that promise a guaranteed aim improvement.
• An eDPI comparison is not a measure of skill.

Example: two different DPI settings

At 800 DPI and sensitivity 1.0, eDPI is 800. At 400 DPI and sensitivity 2.0, eDPI is also 800. With the same default yaw setting, the approximate centimeters-per-turn calculation is equal. That makes these two configurations useful reference points when you change mouse DPI.

If the physical turning distance is not close, verify which DPI profile is actually enabled and whether you use custom m_yaw or unusual input processing. Do not automatically assume the formula is wrong or that matching eDPI guarantees identical feel across different devices.

Put the numbers to work

Use the eDPI & cm/360 Calculator to turn these observations into a repeatable test or calculation. It works entirely in your browser.

Continue troubleshooting

Related questions often require a different measurement. These guides help narrow the next step:

• CS2 Input Lag vs Ping: Two Different Delays
• CS2 Monitor Refresh Rate: What 144 Hz, 240 Hz and 360 Hz Mean