Convert your mouse sensitivity between Valorant, CS2, Apex Legends, Overwatch 2, Fortnite and more — matched by real 360° distance (cm/360), with eDPI included.
Yaw = degrees your view turns per mouse count at sensitivity 1. It is the constant that makes every game's sens scale different — and the number this converter is built on.
| Game | Yaw (° per count) | Notes |
|---|---|---|
| CS2 / CS:GO | 0.022 | 1:1 with Apex, Marvel Rivals, TF2 and Quake Champions |
| Valorant | 0.07 | CS2 sens ÷ 3.18 |
| Apex Legends | 0.022 | 1:1 with CS2 |
| Overwatch 2 | 0.0066 | CS2 sens × 3.33 |
| Call of Duty (MW / Warzone / BO6) | 0.0066 | 1:1 with Overwatch 2 |
| Marvel Rivals | 0.022 | 1:1 with CS2; Overwatch 2 sens ÷ 3.33 |
| The Finals | 0.0066 | 1:1 with Overwatch 2 and CoD |
| Destiny 2 | 0.0066 | 1:1 with Overwatch 2 and CoD |
| Fortnite | 0.005555 per 1% | enter the X-axis sensitivity %; CS2 sens = % × 0.2525 |
| Rainbow Six Siege | 0.00572958 | default multiplier 0.02; CS2 sens = R6 ÷ 3.84 |
| Halo Infinite | 0.0225 | almost 1:1 with CS2 (2.3% faster) |
| Team Fortress 2 | 0.022 | engine default m_yaw |
| Quake Champions | 0.022 | engine default m_yaw |
One rule: keep the physical distance of a 360° turn identical.
Choose the game you play now, the game you are switching to, and type your current sensitivity and mouse DPI. For Fortnite, use the X-axis sensitivity percentage. If you are also changing DPI — say moving from 400 to 800 — fill in the optional new DPI and the conversion accounts for it.
The result keeps your cm/360 — the mouse-pad distance of a full turn — exactly the same, so your flicks and tracking feel identical on day one. The eDPI and inches/360 are shown too (the Unit Converter can handle any other cm-to-inch math).
Enter the converted value in the target game's settings, then adjust in small steps only if the game's FOV or pacing calls for it. Starting from a matched cm/360 beats guessing — and the swap button converts back the other way in one click if you return to your old game.