cm/360 calculator
Find how far your mouse travels for a full turn, or the sensitivity that gives you a target distance, in CS2, Valorant and more.
What cm/360 tells you
Sensitivity numbers are not comparable between games and DPI settings, but distance is. cm/360, sometimes written cm per 360 or 360 distance, is how far your mouse has to travel across the pad for the view to spin one full circle. A short distance means a fast turn and a long one means a slow turn, whichever game, mouse or DPI you use to get there.
That is why it is the number to keep when you change something. Swap to a new mouse with a different DPI, or move from Valorant to CS2, and aim to keep the same distance. The sensitivity converter does exactly that between games. The eDPI calculator shows the same idea as one number and compares it with the pros.
The formula
cm/360 = 360 ÷ (yaw × sensitivity × DPI) × 2.54. Yaw is the fixed number of degrees a game turns per mouse count at sensitivity 1: 0.022 in CS2, 0.07 in Valorant, 0.0066 in Overwatch 2. At 800 DPI and CS2 sensitivity 1.0 that gives 51.95 cm, or 20.45 inches. Reverse the formula and you have the sensitivity for any distance: sens = 360 ÷ (yaw × DPI × inches).
What cm/360 do CS2 pros use?
The median active pro in our settings data sits at 800 eDPI, a 52 cm turn. The middle half of players land between 43 and 59 cm. In practice that means a full circle is a long sweep of the arm, and nobody does it in a duel: most turns are a quarter or an eighth of the way round. If your 360 is longer than your mouse pad is wide, you will lift the mouse during big turns, which is fine for small corrections but costs time on a flick to a flank. Measure your pad before you copy anyone.
CS2 cm/360 by eDPI
| eDPI | cm per 360 | Inches per 360 |
|---|---|---|
| 300 | 138.5 | 54.5 |
| 400 | 103.9 | 40.9 |
| 500 | 83.1 | 32.7 |
| 600 | 69.3 | 27.3 |
| 700 | 59.4 | 23.4 |
| 800 | 52 | 20.5 |
| 900 | 46.2 | 18.2 |
| 1,000 | 41.6 | 16.4 |
| 1,100 | 37.8 | 14.9 |
| 1,200 | 34.6 | 13.6 |
| 1,400 | 29.7 | 11.7 |
| 1,600 | 26 | 10.2 |
CS2 sensitivity for a target cm/360
| Target cm per 360 | At 400 DPI | At 800 DPI | At 1600 DPI |
|---|---|---|---|
| 25 cm | 4.156 | 2.078 | 1.039 |
| 30 cm | 3.464 | 1.732 | 0.866 |
| 35 cm | 2.969 | 1.484 | 0.742 |
| 40 cm | 2.598 | 1.299 | 0.649 |
| 45 cm | 2.309 | 1.155 | 0.577 |
| 50 cm | 2.078 | 1.039 | 0.52 |
| 55 cm | 1.889 | 0.945 | 0.472 |
| 60 cm | 1.732 | 0.866 | 0.433 |
The same 40 cm in other games
A 40 cm turn at 800 DPI needs a different sensitivity number in each game. Type these in and your hand will travel the same distance in all of them.
| Game | Sensitivity for 40 cm at 800 DPI |
|---|---|
| CS2, CS:GO, TF2 and Apex | 1.2989 |
| Valorant | 0.4082 |
| Overwatch 2 | 4.33 |
| Call of Duty (Warzone, MW, BO6) | 4.33 |
| Fortnite | 5.144 |
| Rainbow Six Siege | 4.987 |
Measure your real cm/360
The maths assumes your mouse really reports the DPI you set. To check, load a practice map, face a landmark and lay a tape measure beside your mouse. Slide the mouse in a straight line until the view comes back to the same landmark, and read off the distance. If it matches the calculator you are set. If it is off by more than a few per cent, switch off Windows pointer acceleration, confirm the DPI in your mouse software and try again.
Once you have a distance you like, write the sensitivity into an autoexec so a reinstall does not undo it, and sort the rest of your setup with the crosshair generator and the viewmodel generator.
Changing mouse or DPI without losing your aim
A new mouse often comes with a different default DPI, and it is easy to end up with a turn that feels wrong for no obvious reason. The fix is to hold your cm/360 steady. Work out your current distance above, switch to the distance mode, enter the DPI of the new mouse and type in the sensitivity it gives you. At 400 DPI a 40 cm turn in CS2 needs 2.598; at 1600 DPI it needs 0.649. The turn is the same, so the muscle memory you already have still applies.
How to use it
- Choose your game and enter your mouse DPI.
- Type your sensitivity to read your cm per 360, or press the arrows and type a distance to get the sensitivity.
- Use the units switch to work in inches instead of centimetres.
- Press Copy to put the result on your clipboard, then paste it into the game or your config.
FAQ
What is cm/360?
It is the distance you move your mouse, in centimetres, to turn your view a full 360 degrees. Because it ignores DPI and each game's own sensitivity scale, it is the fair way to compare setups and to carry your aim between games.
How is cm/360 calculated?
cm/360 = 360 ÷ (yaw × sensitivity × DPI) × 2.54. CS2's yaw is 0.022, so 800 DPI at sensitivity 1.0 gives 51.95 cm.
What cm/360 do CS2 pros use?
The median active pro runs 800 eDPI, which is 52 cm per 360. The middle half range from 43 to 59 cm.
How do I set a target cm/360?
Switch the calculator to 'My distance', enter your DPI and the distance you want. It returns the in-game sensitivity to type in. The table on this page gives CS2 values at 400, 800 and 1600 DPI.
Is a higher or lower cm/360 better?
Neither wins on its own. A longer distance (low sensitivity) gives finer control for small adjustments but needs more arm and mouse pad. A shorter distance turns faster and needs less room but is harder to keep steady. Pick the one you can hit shots with consistently and keep it.
Why is my measured cm/360 different from the calculator?
The usual cause is a DPI that is not what the mouse software says, or mouse acceleration being on. Turn off Windows pointer acceleration (Enhance pointer precision), check the DPI in your mouse software and measure again over a long ruler or tape measure.
