mouse sensitivity cm/360 conversion
Mouse sensitivity does not compare directly across games because every engine uses its own rotation-per-count constant, called yaw. The universal metric is cm/360: how many centimeters of physical mouse travel it takes to spin the view a full 360 degrees. This tool computes that number and converts the same physical turn between games with a known, constant yaw.
This is the physical reference value: any game set to the same cm/360 requires the exact same arm movement to complete the same turn, no matter what sensitivity unit that game uses natively.
DPI drops out of the math because it multiplies both sides of the equation equally; only the ratio between the two yaw values decides the conversion factor between the games.
Overwatch 2 has the smallest yaw on the list, 0.0066, almost a third of CS2's; that is why matching the same turning feel needs a much higher sensitivity number inside the game.
It is the physical distance, in centimeters, you need to move the mouse to turn your character 360°. It is the most reliable way to compare sensitivity across games, because it is independent of each game's internal scale. A higher cm/360 means a lower sensitivity.
Because each engine defines its own constant for degrees turned per mouse count at sensitivity 1, the yaw; CS2 uses 0.022 and Valorant uses 0.07, more than three times larger, so the same sensitivity number produces very different turns from one game to the other.
It is the physical distance, in centimeters, the mouse travels across the desk to spin the view exactly 360 degrees; since it only depends on DPI, sensitivity and yaw, not on each game's native sensitivity unit, it is the one number that compares equally across CS2, Valorant, and any other constant-yaw game.
Because both apply a sensitivity curve that changes with field of view instead of a simple fixed-yaw multiplication; without one single constant, any conversion would turn into a guess, and this tool would rather leave a game out than publish a number that is not exact.
Yes: since cm/360 is inversely proportional to DPI in the formula, doubling the DPI without adjusting the in-game sensitivity cuts cm/360 in half, meaning the same physical mouse distance now turns the view twice as far; that is why switching mice requires recalculating both together.
The conversion keeps the same cm/360 (the physical distance to turn 360°) and, when switching games at the same DPI, is DPI-independent. Games with non-linear or FOV-dependent models (like Rainbow Six Siege and Fortnite) are intentionally left out so the result stays exact.
Conversion is computed locally in the browser; nothing is sent to servers.