Keep the same aim across games. Convert your sensitivity between CS2, Valorant, Apex and more - matched by cm/360. Free, no signup.
Matched by cm/360 turn distance. Aim can feel slightly different across engines - fine-tune in-game.
This converter keeps your aim the same when you move between games by matching cm/360: how far you move the mouse to turn a full circle. Pick the game you are coming from, enter your sensitivity, pick the game you are going to, and read the new value. Results update as you type, and nothing is saved.
Every game turns the camera a fixed number of degrees for each count the mouse sends at sensitivity 1. This number is often called the game's yaw. Your turn per count is sensitivity × yaw, so two settings feel the same when that product matches. The tool uses these yaw values:
| Game | Yaw (degrees per count) |
|---|---|
| CS2 / CS:GO, Apex Legends, Titanfall 2 | 0.022 |
| Valorant | 0.07 |
| Overwatch 2 | 0.0066 |
| Deadlock | 0.044 |
New sensitivity = your sensitivity × from-game yaw ÷ to-game yaw.
cm/360 = 360 ÷ (sensitivity × yaw) ÷ DPI × 2.54.
Valve has not published a yaw value for Deadlock. Most sensitivity converters use 0.044, twice the CS2 value, so a CS2 sensitivity of 2.0 becomes 1.0 in Deadlock. At least one source lists 0.022 instead. If a Deadlock conversion feels twice as fast or slow, measure your turn distance in the game as described below.
Games that share a yaw value convert one to one. CS2 1.5 is also 1.5 in Apex Legends and Titanfall 2.
DPI only feeds the cm/360 result. The new sensitivity assumes you keep the same DPI in both games. If you change DPI, scale the sensitivity the other way: doubling from 800 to 1,600 DPI means halving the sensitivity to keep the same cm/360. The eDPI calculator helps you compare settings across different DPI values, and the cm/360 calculator works out turn distance on its own.
Put a strip of tape or a ruler beside your mouse pad. Line your crosshair up with a clear point in the game, then move the mouse slowly to the right until you have turned exactly one full circle. Measure how far the mouse travelled. It should be close to the cm/360 shown here. If it is far off, check that your DPI is right and that mouse acceleration is off.
It matches your cm/360 (the distance you move the mouse for a full 360 turn) between games by adjusting for each game engine sensitivity scale, so your muscle memory carries over.
They are matched to standard sensitivity scales for each game. Aim can feel slightly different across engines, so fine-tune in-game if needed.
No. The conversion assumes the same DPI in both games, and DPI is only used to show your cm/360. If you change DPI, scale your sensitivity the opposite way, for example halve it when doubling DPI.
No, it converts hipfire sensitivity only. Aim-down-sights and scope settings are separate in most games, so adjust them in each game's own menu.