Understanding the game sensitivity converter — concept and principle
When you switch from one shooter to another, the same sensitivity number does not give the same turn speed, because each game multiplies your mouse movement by a different angle. This converter finds the sensitivity in the new game that turns your view by the same number of degrees for the same hand movement, so your muscle memory carries over. It covers CS2 and Apex, Valorant and Overwatch 2.
How it is calculated
New sensitivity = old sensitivity × yaw of the old game ÷ yaw of the new game
Yaw is the number of degrees the camera turns per mouse count at sensitivity 1. The converter uses commonly cited values: 0.022° for CS2 and Apex, 0.07° for Valorant and 0.0066° for Overwatch 2. Your mouse DPI is assumed to stay the same, so it cancels out.
The principle
In each game, degrees turned per mouse count = sensitivity × yaw. To feel the same, that product must be equal in both games: sens₁ × yaw₁ = sens₂ × yaw₂. Solving for sens₂ gives the formula above. Equal degrees per count means equal cm/360, the physical distance for a full turn, which is what your arm actually learns. The conversion ratios that players quote come straight from the yaw values: CS2 to Valorant divides by 0.07 ÷ 0.022 ≈ 3.18, and CS2 to Overwatch 2 multiplies by 0.022 ÷ 0.0066 ≈ 3.33.
Worked example
Defaults: sensitivity 1.5 in CS2, converting to Valorant.
- Degrees per count in CS2 = 1.5 × 0.022 = 0.033°.
- Valorant sensitivity = 0.033 ÷ 0.07 = 0.4714.
- Check: 0.4714 × 0.07 = 0.033°, the same turn per count.
At 800 DPI both settings give about 34.6 cm per 360°.
| Your sensitivity | Equivalent sensitivity |
|---|---|
| 0.375 | 0.1178571429 |
| 0.75 | 0.2357142857 |
| 1.12 | 0.3535714286 |
| 1.5 | 0.4714285714 |
| 1.88 | 0.5892857143 |
| 2.25 | 0.7071428571 |
| 3 | 0.9428571429 |
How to read the result
Enter the result as closely as the game allows; Valorant accepts several decimals. The conversion matches full-turn distance, which is the standard method. Small aim feels the same only when field of view is also similar, because a wider FOV makes the same angle look smaller on screen. Expect a short adjustment period even with a perfect conversion.
Common mistakes
- Changing DPI at the same time as converting, which breaks the result.
- Converting scoped or ADS sensitivity with the same formula; those use separate multipliers.
- Using outdated yaw values after a game update.
- Leaving mouse acceleration on in one game but not the other.
Frequently asked questions
How do I convert Valorant to CS2?
Multiply the Valorant sensitivity by about 3.18. For example, 0.4714 becomes 1.5.
Why does my converted sens still feel different?
Field of view, frame rate, mouse acceleration and different movement speeds all affect feel, even when cm/360 is identical.
Do I need my DPI for this?
No, as long as you keep the same DPI in both games. If DPI changes, use the eDPI and cm/360 calculator instead.
Sources: Valve Developer Community – m_yaw console variable (default 0.022)