FPS Mouse Sensitivity Converter β CS2, Valorant, Apex & More
Convert your mouse sensitivity between CS2, CS:GO, Valorant, Apex Legends, Overwatch 2, Call of Duty and more. Keeps the same cm/360 so your aim feels identical, with eDPI shown for both games.
π Runs entirely in your browser. Your input and output are never sent to a server or stored β fully private.
Same cm/360Β° = same aim feel: the converted sensitivity needs exactly the same physical mouse distance for a full turn. Always verify the value in-game β some titles round internally. Click any result to copy it.
About this tool
Switching from CS2 to Valorant and suddenly your aim feels alien? Each FPS engine converts mouse movement to camera rotation with its own yaw constant, so the same sensitivity number means completely different things in different games. This converter does the math for you: pick your source game and sensitivity, and it outputs the matching value for Valorant, Apex Legends, Overwatch 2, Call of Duty and more, alongside your cm/360 and eDPI so the physical feel of your aim carries over exactly. Everything is computed locally in your browser β no account, no upload, just instant numbers.
Frequently asked questions
What does cm/360 mean, and why is it the best way to keep my aim consistent?
cm/360 is the physical distance your mouse must travel across the pad to turn your character a full 360 degrees. Because it is measured in real-world centimetres, it describes what your arm and wrist actually do, independent of any game's internal numbers. If your cm/360 is identical in two games, a flick of the same length lands on the same spot in both β that is why matching cm/360, rather than copying the raw sensitivity value, is what transfers muscle memory between titles.
Why does my converted sensitivity look like such a strange number?
Because every engine uses a different yaw constant β the number of degrees the camera rotates per sensitivity unit per mouse count. CS2 uses 0.022, Valorant 0.07, Overwatch 2 0.0066, and so on. Converting means dividing one constant by another, which rarely produces a round figure: a tidy 2.0 in CS2 becomes roughly 0.629 in Valorant. The odd decimals are not an error; they are exactly what is needed so your physical cm/360 stays the same. Round them only if your game's settings menu forces you to.
Do I need an account, and is my sensitivity data uploaded anywhere?
No account, no upload. The conversion is a handful of multiplications and divisions using each game's published yaw constant, and your browser performs all of it locally the moment you type β nothing is sent to a server, stored or shared. That also means it works offline once the page has loaded. One practical tip: enter your real mouse DPI, because cm/360 depends on it; the game-to-game sensitivity conversion itself is correct at any DPI.