CS2 eDPI calculator
Enter your mouse DPI and in-game sensitivity — the tool computes eDPI, cm/360 and inches/360 separately for hip-fire aiming and for zoom (sniper rifles/AWP), and links to a real table of pro player settings for comparison.
How we calculate
eDPI = DPI × sensitivity. cm/360 and inches/360 are computed from the turn angle per mouse "count" (`m_yaw = 0.022` in CS2, the same constant used in `lib/sensitivity.ts`) — so the numbers here stay consistent with the site's other sensitivity tools instead of using a separate formula.
Zoom mode uses `zoom_sensitivity_ratio_mouse` — a multiplier applied to sensitivity while scoped in. As of 2026-09-28 we have NO available source confirming this command: prosettings.net/cs2-settings/ returns 404, and the direct command page on totalcsgo.com returns 404 as well. So enter your own value from your config; the pre-filled 1 is not an "official default" but a neutral number at which zoom eDPI equals hip-fire eDPI.
Sources
checked 17 September 2026
Questions and answers
What is eDPI and why does it matter?
eDPI (effective DPI) = mouse DPI × in-game sensitivity. This single number lets you compare aiming "physical speed" between players with different DPI and sensitivity — even if one player uses DPI 400 with sens 4 and another DPI 1600 with sens 1, at the same eDPI=1600 the physical mouse movement for the same turn is identical.
Why is zoom eDPI (AWP/sniper rifles) calculated separately?
Because CS2 has a dedicated command, `zoom_sensitivity_ratio_mouse`, that multiplies sensitivity while scoped in. At a value of 1, zoom eDPI equals hip-fire eDPI, but many players set it below 1 to lower sensitivity while zoomed — at which point the two numbers diverge. The 1 is not an «official default»: as of 2026-09-28 we have no working source for this command (both returned 404), so take the value from your own config.
Where does m_yaw = 0.022 for CS2 come from?
It is the same turn-rate constant already used by the site's sensitivity calculator (`lib/sensitivity.ts`, the `cs-2` entry in `data/sens-games.json`) — it is not duplicated with a separate formula here, it is the same computation.
Why is there no "average pro eDPI"?
Because we don't invent a number that isn't in the source. The CS2 settings list page on prosettings.net has no section with aggregate statistics (median/average) — confirmed by a direct fetch of the page on 2026-09-17. Instead of a fabricated number, the tool links to the real table with each player's individual settings.
How reliable is the zoom_sensitivity_ratio_mouse command?
The honest answer: we currently have no available source for it. This used to link to prosettings.net/cs2-settings/ — as of 2026-09-28 that page returns 404, and the direct command page on totalcsgo.com returns 404 too. No live prosettings.net page containing the command could be found. So it is flagged as unconfirmed in `data/SOURCES.md`, and the 1 in the field is merely a neutral value at which zoom eDPI matches hip-fire eDPI — not a verified in-game default.
Unofficial tool. Not affiliated with Valve.