🏆
🏆 Sports & games

Game Sensitivity Converter (CS2 ⇄ Valorant ⇄ Overwatch ⇄ Apex)

Results update as you type.

Your numbers

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.

Converting sensitivity between gamesCS2 sensitivity 1.5 at 0.022° per count turns 0.033°, the same as Valorant 0.4714 at 0.07°.Match the turn per mouse countCS2sens × yaw1.5 × 0.022°= 0.033° / countValorantsens × yaw0.4714 × 0.07°= 0.033° / count=1.5 × 0.022 ÷ 0.07 = 0.4714Same 34.6 cm per 360°at 800 DPI in both games
Sensitivity × yaw must be equal in both games, so CS2 1.5 becomes Valorant 0.4714 with the same hand distance.

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.

  1. Degrees per count in CS2 = 1.5 × 0.022 = 0.033°.
  2. Valorant sensitivity = 0.033 ÷ 0.07 = 0.4714.
  3. Check: 0.4714 × 0.07 = 0.033°, the same turn per count.

At 800 DPI both settings give about 34.6 cm per 360°.

How Equivalent sensitivity changes with Your sensitivityHow Equivalent sensitivity changes with…00.20.40.60.810.3750.751.121.51.882.253Example: 0.4714285714Your sensitivity
Each point is the calculator re-run with only “Your sensitivity” changed; the gold point is the default example. Change the inputs above and this chart follows your numbers.
Your sensitivityEquivalent sensitivity
0.3750.1178571429
0.750.2357142857
1.120.3535714286
1.50.4714285714
1.880.5892857143
2.250.7071428571
30.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

Keep in mind: Yaw values here are widely used community figures, not official specifications in every case. Verify with a 360° test in game if exact matching matters.

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)

Checked 8 Nov 2026. Official league / federation formulas where they exist; widely used community formulas otherwise. For fun and analysis — not betting advice.

🏆 All sports & games tools →🌍 Calculators by country →