GAME TOOL / 03
FPS Sensitivity Converter
Switching games and want the same feel? We convert through cm/360, the physical distance your mouse travels for a full turn, so CS2 2.0 lands on exactly the right Valorant number.
Source
Target
CS2 to Valorant quick reference
| CS2 sens | Valorant sens | cm/360 @ 800 DPI |
|---|---|---|
| 0.5 | 0.157 | 103.9 |
| 1.0 | 0.314 | 52.0 |
| 1.5 | 0.471 | 34.6 |
| 2.0 | 0.629 | 26.0 |
| 2.5 | 0.786 | 20.8 |
| 3.0 | 0.943 | 17.3 |
How the conversion works
Every FPS engine has its own yaw: the degrees your view turns per mouse count at sensitivity 1.0. CS2/Source uses 0.022, Valorant (Unreal) uses 0.07, Apex keeps the Source 0.022, and Overwatch 2 uses 0.0066. The same number therefore means different real rotation in each game.
Conversion goes through the physical quantity: cm/360 = 914.4 ÷ (DPI × sens × yaw). We then solve the target sens from the same cm/360. At equal DPI this reduces to new sens = old sens × (old yaw ÷ new yaw), and the ratio never depends on DPI.
Why FOV and resolution are not inputs
cm/360 is a purely physical measure: how far the mouse travels for one full turn. FOV and stretched resolution change how fast it looks, not how far you move. If you want your scoped aim to feel consistent too, that is a monitor-distance problem handled by each game's own zoom or ADS multiplier, not by this hipfire factor.
Frequently asked questions
What is cm/360?
How many centimeters of mousepad travel it takes to turn a full 360 degrees. It is a physical measure, independent of each game's sensitivity scale: lower means faster.
What is CS2 sensitivity 2.0 in Valorant?
0.629. The ratio is 0.3143 (CS2 yaw 0.022 ÷ Valorant yaw 0.07), so 2.0 × 0.3143 ≈ 0.6286, which Valorant rounds to three decimals: 0.629. This assumes the same DPI in both games.
What if my DPI is different in the new game?
Fill in the target DPI field. Sensitivity and DPI are inverse: double the DPI, halve the sens, and cm/360 stays identical.
Why are Rainbow Six Siege and Fortnite not listed?
Both use non-linear, FOV-coupled sensitivity curves, so no fixed conversion factor exists and any single number would be an approximation. Only constant-yaw games are included.
Can I convert scoped or ADS sensitivity too?
Not with the hipfire factor. CS2 uses a separate zoom_sensitivity_ratio and Valorant has its own scoped multiplier, so set those inside each game.
Why does it still feel different after converting?
Disable mouse acceleration, Windows “Enhance pointer precision”, and check raw input settings on both sides. FOV and stretched resolution do not change cm/360, but they change how fast it looks, which is normal.