Mouse Sensitivity & cm/360 Converter

Why cm/360 Is the Only Universal Sensitivity Metric

In-game sensitivity numbers are meaningless across engines: 1.5 in CS2 and 1.5 in Valorant produce entirely different rotations. The conversion here passes through each game's yaw constant — the degrees turned per mouse count — so what is preserved is the physical distance your hand travels for a full 360° turn.

That physical distance is the only thing your muscle memory actually learns. Keeping cm/360 constant is what makes a switch between games seamless; keeping the raw number constant is what makes every aim duel feel wrong for a week.

Engine Yaw Constants Used

• CS2 and Apex Legends (Source): 0.022° per count.
• Valorant: 0.07° per count — which is why Valorant sens numbers are roughly 3.18× smaller than CS2 at equal DPI.
• Overwatch 2: 0.0066° per count — the smallest of the three, hence the largest raw sens values.
• The converter also reports cm/360 so you can sanity-check the result on your mousepad before committing to it in-game.

Why the Same DPI Feels Different in Every Game

Each game turns mouse counts into rotation with its own multiplier, called the yaw value. Source-engine titles use 0.022 degrees per count, while others use different constants, so identical DPI and in-game sensitivity can give a very different turn speed. Converting by the yaw ratio keeps the physical distance you swipe for a full turn the same.

The cm/360 figure is the most useful number for comparing setups: it is how far the mouse travels on the pad to complete a full rotation. Most competitive players settle somewhere between roughly 20 and 50 cm/360, but the right value depends on pad size and aim style. Convert once, then make small adjustments over a few sessions instead of changing the value repeatedly.