This converter keeps your aim consistent when you switch games. Enter your mouse DPI, your current game, and its in-game sensitivity, then choose the game you want to play. The tool returns the sensitivity that preserves your cm/360 - the physical distance you move the mouse to turn a full circle - so your muscle memory transfers intact. It also shows your eDPI and your exact 360 distance in centimeters and inches.
The calculation holds rotation distance constant. It uses a community yaw value: the degrees your view rotates per mouse count at sensitivity 1. Source-engine games like CS2 and Apex share a yaw of 0.022, so they convert one to one; Valorant uses 0.07; the Overwatch 2 and Call of Duty family uses 0.0066. To match your feel in a new game, the target sensitivity is your sensitivity times your game’s yaw divided by the target game’s yaw, which holds your cm/360 constant at the same DPI.
The caveat: a handful of games (Fortnite, some battle royales) use a percentage or per-scope slider rather than a clean linear scale, so their conversion is a close approximation marked with an asterisk. Halo Infinite, Deadlock and Rust retain disputed community values with the same asterisk. Confirm those approximations with an in-game 360 test. Marvel Rivals and Battlefield 2042 are labeled yaw unresolved, and their distance and conversion outputs are withheld. Field of view also changes how a given sensitivity feels, so if you are also moving between aspect ratios, set your view with the FOV Calculator, and see where a graphics card sits at your resolution in the CPU and GPU benchmark lookup.
DPI calculator: change DPI without changing your aim
Switching mouse DPI changes how far the crosshair moves for the same hand movement. The fix is one line of arithmetic. Multiply your in-game sensitivity by your old DPI divided by your new DPI. That holds your eDPI where it was, and your cm/360 with it.
The page computes cm/360 = 360 / (sensitivity x yaw) / DPI x 2.54. With the game unchanged the yaw is fixed, so the distance stays put as long as sensitivity x DPI does. Enter your new DPI in the Changing DPI panel. It prints the sensitivity for the game you selected. I’d still confirm it with one 360 on the mousepad.
Worked examples
These are this calculator’s own outputs, computed with the same formula the tool runs in your browser — so you can see a real answer without touching a single input.
A CS2 player moving to Valorant and wanting the same feel (the tool’s own default pairing, at a realistic CS2 sensitivity)
- Inputs: DPI = 800, Game = CS2 (yaw 0.022), In-game sensitivity = 0.80, Target game = Valorant (yaw 0.07)
- Result: eDPI 640; 64.9 cm / 25.6 inches per 360 degrees; Valorant sensitivity 0.251 at 800 DPI to match the 64.9 cm/360.
A Valorant player on a high-DPI mouse trying CS2, going the other direction through the same yaw pair
- Inputs: DPI = 1600, Game = Valorant (yaw 0.07), In-game sensitivity = 0.35, Target game = CS2 (yaw 0.022)
- Result: eDPI 560; 23.3 cm / 9.2 inches per 360 degrees; CS2 sensitivity 1.11 at 1600 DPI to match the 23.3 cm/360.
A CS2 player moving from 800 to 1600 DPI and keeping the same feel (the Changing DPI panel’s defaults)
- Inputs: DPI = 800, Game = CS2 (yaw 0.022), In-game sensitivity = 1.00, New DPI = 1600
- Result: eDPI 800; 52.0 cm / 20.5 inches per 360 degrees; CS2 sensitivity 0.500 at 1600 DPI for the same 52.0 cm/360 (eDPI stays 800).
Assumptions and sources
- The conversion itself is algebra, not data: holding cm/360 constant gives target sensitivity = your sensitivity x (your game’s yaw / target game’s yaw), with DPI canceling out because you keep the same mouse.
- The DPI calculator is the same algebra the other way round: in one game the yaw is fixed, so holding cm/360 constant means holding sensitivity x DPI constant, and new sensitivity = your sensitivity x old DPI / new DPI.
- The per-game yaw values (0.022 for Source-engine titles, 0.07 for Valorant, 0.0066 for the Overwatch 2 / Call of Duty family, 0.044 for Deadlock) are community-documented constants. The major converters do not all agree on them - the evidence ledger below records the cited evidence and its limits. Asterisks mark approximations; unresolved Marvel Rivals and Battlefield 2042 results are withheld. That disagreement is exactly why this page tells you to confirm the result with a physical 360 test on a marked mousepad.
- Marvel Rivals and Battlefield 2042 return no cm/360 or cross-game conversion until yaw is verified. Their eDPI and same-game DPI adjustments still calculate because yaw cancels.
- Other games flagged with an asterisk are approximations rather than settled engine constants, for one of two reasons: they use a percentage or per-scope slider rather than a clean linear scale (Fortnite, Rainbow Six Siege), or published values disagree between converters (Halo Infinite, Deadlock, Rust).