CS2 eDPI & Sensitivity Calculator

Read on 18 August 2026. cm/360 is computed from their DPI and sensitivity, not copied.

How eDPI is calculated

eDPI = mouse DPI × in-game sensitivity. Sensitivity on its own says nothing, because it is multiplied by the DPI of your mouse. Somebody on 400 DPI and 2.0 moves exactly as far as somebody on 800 DPI and 1.0 — same eDPI, same aim, two numbers that look nothing alike. That is why every comparison worth making uses eDPI, and why copying a pro's sensitivity without their DPI gives you something they have never played. Results are shown to one decimal; the calculation is not rounded before that.

eDPI vs. cm/360

eDPI compares two players; cm/360 tells you something physical — how much mousepad you need for one full turn. It is computed from CS2's own m_yaw of 0.022 degrees per mouse count, so it is arithmetic rather than opinion. If your number is under about 20 cm you are turning with your wrist; over about 45 cm you are turning with your shoulder and will want the desk space to do it.

How to compare CS2 sensitivities

All 13 players in the table sit between 620 and 1236 eDPI, with the median at 800. That is 13 players read from one public source on one date — a sample, not a survey of the scene, and not a recommendation. There is no professional in it playing at 3,000, and none at 200 either. If you are far outside that band it is the one setting worth changing deliberately — not because the pros are right about everything, but because a band that tight across different people and roles is not a coincidence. There is no cross-game converter here on purpose: the yaw constants of other games are community measurements, and a converter that is 3% off is worse than none.

While you are setting things up, the crosshair generator and the autoexec generator cover the rest of the config.

Questions people ask