Converting sensitivity between games keeps your muscle memory working. If the same hand movement turns you the same distance in both games, your flicks and tracking carry over and you don’t start from scratch.
The maths is simple once you know each game’s yaw value. This guide explains the formula, gives the values for popular shooters, and lists the settings that quietly break a conversion. To skip the maths, use our free mouse sensitivity converter.
The formula
Every game turns the camera a fixed number of degrees for each count your mouse reports, multiplied by your in-game sensitivity. That fixed number is the yaw value.
To keep the same turn speed in a new game:
New sensitivity = old sensitivity × old game’s yaw ÷ new game’s yaw
Your mouse DPI must stay the same. If you change DPI as well, scale the sensitivity by the ratio of the old DPI to the new one: halve the sensitivity when you double the DPI.
Yaw values for popular games
| Game | Yaw (degrees per count at sensitivity 1) | Convert from CS2 |
|---|---|---|
| Counter-Strike 2 | 0.022 | Same |
| Apex Legends | 0.022 | Same |
| Valorant | 0.07 | Divide by 3.18 |
| Overwatch 2 | 0.0066 | Multiply by 3.33 |
| Call of Duty (Legacy sensitivity) | 0.0066 | Multiply by 3.33 |
These are the default values each game ships with. They assume default config values: changing m_yaw in CS2, for example, changes the result. Call of Duty’s figure applies to its Legacy sensitivity mode.
Worked examples
CS2 to Valorant. 1.5 × 0.022 ÷ 0.07 = 0.471. So 1.5 in CS2 at 800 DPI matches about 0.47 in Valorant at 800 DPI.
Valorant to Overwatch 2. 0.4 × 0.07 ÷ 0.0066 = 4.24.
Apex Legends to CS2. Both use 0.022, so 2.0 in Apex is 2.0 in CS2.
eDPI and cm/360
eDPI is your mouse DPI multiplied by your in-game sensitivity. It is handy for comparing players in the same game: 800 DPI at 1.5 and 400 DPI at 3.0 are both 1,200 eDPI in CS2. It can’t be compared across games with different yaw values.
cm/360 is how far you move the mouse for a full turn, and it works across every game:
cm/360 = 360 ÷ (yaw × sensitivity) ÷ DPI × 2.54
For 1.5 in CS2 at 800 DPI: 360 ÷ 0.033 ÷ 800 × 2.54 ≈ 34.6cm. Our mouse DPI and sensitivity explained guide covers how to choose a starting point.
Settings that break a conversion
Windows pointer acceleration. “Enhance pointer precision” in Windows mouse settings makes the cursor move further when you move the mouse faster, so the same distance no longer gives the same turn. Turn it off in Settings > Bluetooth & devices > Mouse > Additional mouse settings > Pointer Options.
Raw input off. Most shooters read the mouse directly (raw input), which Microsoft recommends for games because it skips Windows’ pointer processing. If a game has a raw input option, turn it on; otherwise leave the Windows pointer speed at the default, the sixth notch of eleven.
Different DPI. Check your mouse software or the DPI button. Many mice change DPI with a button that’s easy to press by accident.
Scoped and ADS multipliers. The formula converts your hip-fire sensitivity. Each game handles scopes and aim-down-sights differently, so set those separately after the main conversion.
Field of view. A wider FOV makes motion on screen look faster, even when the turn distance is identical. Give yourself a few sessions before adjusting by feel.
Fine-tune after converting
A conversion gets you close, not perfect. Play a few matches, then adjust in small steps of 5–10% at a time. If you overshoot targets, lower it; if you have to lift the mouse mid-flick, raise it or get a larger pad.
A consistent setup helps too: the same mouse pad, the same DPI, and a stable frame rate. If your game stutters, start with how to reduce input lag on PC and how to fix stuttering in PC games.
