Sensitivity converter

The same aim in another game. Matched on the distance your hand actually moves, not on a ratio someone posted once.

I play

atsensitivity, withDPI.

cm / 360°

28.86cm

inches / 360°

11.4in

eDPI

1440

only comparable inside one game

The same aim, everywhere else

atDPI

Counter-Strike 2The m_yaw convar. Changing it is possible and almost always a mistake.1.8
CS:GOIdentical to CS2 - the sensitivity carried over untouched.1.8
ValorantRoughly a CS sensitivity divided by 3.18.0.5657
Apex LegendsSource underneath, so it matches Counter-Strike one to one.1.8
Overwatch 2Roughly a CS sensitivity multiplied by 3.33.6
Call of DutySame scale as Overwatch. Assumes the default 'Relative' aiming.6
Team Fortress 21.8
DeadlockSource 2, same m_yaw as Counter-Strike.1.8

Withzoom_sensitivity_ratioa scoped turn takes28.86 cminstead.

Centimetres per 360 is the only thing that compares.: A sensitivity number is a multiplier on a constant only its own game knows, so “1.8” means nothing across two games. What carries over is how far your hand travels to turn all the way around. Every number on this page is that distance, converted back into whatever each game wants to be told.
eDPI is a shorthand, not a conversion.: Sensitivity times DPI compares two players in the same game, because it drops the constant that makes games differ. The same eDPI in CS2 and Valorant is a 3.18× difference in how far you move. It is shown because everyone quotes it, with that caveat attached.
Some games are missing on purpose.: Rainbow Six Siege ties sensitivity to field of view, and Fortnite uses a percentage scale rather than a plain multiplier. Both need their own formula, and a guessed conversion produces a number that looks right and is wrong — which you would only find out in a match. Games are added here when the constant is settled, not before.
It reads your config too.: If you changed m_yaw away from 0.022, the standard conversions do not apply to you — the .vcfg converter reports what yours is set to.