Mouse sensitivity in CS 2: conversion and cm/360
Enter your DPI and sensitivity to see cm/360, in/360, eDPI and the sensitivity for the target game. Pairs involving PUBG and ARC Raiders are off: their coefficients are not established.
How we calculate
cm/360 is how many centimetres you have to move the mouse across the desk to turn your character a full circle. That number describes the movement of your hand rather than a figure in a menu, which is why it is the one worth carrying between games. Three steps: degrees per inch = m_yaw × sensitivity × DPI; inches per 360° = 360 ÷ degrees per inch; centimetres = inches × 2.54.
eDPI (DPI × sensitivity) is a handy way to compare two players inside one game, and nothing more. Across games it breaks down, because each title has its own conversion from a unit of sensitivity to a degree of rotation. The same eDPI in CS 2 and in another shooter produces a different full-turn distance, so use cm/360 instead.
The CS 2 multiplier is m_yaw = 0.022 degrees per mouse count. The primary Valve source (developer.valvesoftware.com) returns 403, so the value comes from community references and is flagged as unconfirmed. For PUBG only the slider bounds and the vertical ratio are published; for ARC Raiders not even that. Both games appear in the selects but stay disabled. A disabled conversion is more honest than an invented coefficient.
Sources
checked 18 August 2026
Questions and answers
What is cm/360, and why is it the number to carry over?
It is the distance your mouse travels across the desk for one full turn. It measures your motor habit rather than an in-game scale, so it stays the same in any title. Match cm/360 and your muscle memory moves with you.
Why can I not simply copy my eDPI from one game to another?
Because eDPI carries no game coefficient. One unit of sensitivity in CS 2 equals 0.022 degrees per count; in another game it equals something else, and nothing guarantees the two match. Identical eDPI in two games means two different turn angles.
Why are PUBG and ARC Raiders listed but disabled?
For PUBG the slider bounds (0–100, default 50) and the 70 % vertical ratio are known, but no open source publishes how a slider step converts into degrees per count. For ARC Raiders not even that much is established. We kept both in the list so the edge of what is known stays visible.
Where does 0.022 come from, and how much should I trust it?
From community console-command references: csdb.gg and totalcsgo.com. The official Valve page could not be retrieved: the server returns 403. The value agrees across both independent references and has been used by the community for years, but that is not official confirmation, and we say so.
What does the inverted-axis checkbox do?
Nothing to the numbers, and that is deliberate. A negative m_yaw flips the direction, but the distance for a 360° turn is unchanged because the formula uses the absolute value. The box exists so you can see that rather than spend time testing it.
Unofficial tool. Not affiliated with Valve.