cm/360 Calculator
Work out how many centimetres of mouse movement turn your character a full 360° in any listed game.
Loading calculator…
What this tool does
Work out how many centimetres of mouse movement turn your character a full 360° in any listed game. Hip-fire yaw with raw input and no mouse acceleration. Scoped/ADS sensitivity multipliers are not applied.
How to use the cm/360 Calculator
- Enter or select game.
- Enter or select mouse dpi.
- Enter or select in-game sensitivity.
- Read the calculated result; change any measurement to compare alternatives.
Formula
cm/360 = 360 × 2.54 ÷ (DPI × in-game sensitivity × game yaw), using the same published per-game yaw constants as the sensitivity converter
- game
- Game
- dpi
- Mouse DPI
- sens
- In-game sensitivity
Hip-fire yaw with raw input and no mouse acceleration. Scoped/ADS sensitivity multipliers are not applied.
Worked example
For cm/360 calculator, the following measurements illustrate the exact method: Game: valorant; Mouse DPI: 800; In-game sensitivity: 0.4.
Inputs
- GameValorant
- Mouse DPI800
- In-game sensitivity0.4
Result
- Distance per 360° (cm)40.82
- Distance per 360° (inches)16.07
- Effective DPI320
Results explained
- Distance per 360° (cm)
- Distance per 360° (cm) from the formula above. Hip-fire yaw with raw input and no mouse acceleration. Scoped/ADS sensitivity multipliers are not applied.
- Distance per 360° (inches)
- Distance per 360° (inches) from the formula above. Hip-fire yaw with raw input and no mouse acceleration. Scoped/ADS sensitivity multipliers are not applied.
- Effective DPI
- Effective DPI from the formula above. Hip-fire yaw with raw input and no mouse acceleration. Scoped/ADS sensitivity multipliers are not applied.
Frequently asked questions
Most Valorant and Counter-Strike players fall between roughly 25 and 55 cm/360: lower values favour precise crosshair placement, higher values favour fast turns. There is no single best value — consistency matters more.
Each game multiplies mouse counts by its own yaw constant. Valorant's 0.07 yaw makes the same DPI and sensitivity value turn far less than Counter-Strike's 0.022, so cm/360 is the portable way to compare.
Mark your mouse position, turn exactly one full rotation in game until the crosshair returns to the same landmark, then measure the distance travelled on the pad. It should match this calculator if raw input is on.
Only their product matters for cm/360. 800 DPI × 0.4 and 400 DPI × 0.8 give the identical cm/360; pick the combination your game and sensor handle cleanly.
No. This is hip-fire only. Scopes apply their own multipliers (and often FOV scaling), so scoped cm/360 is different unless the game matches it deliberately.