Sensitivity Converter
A sensitivity converter translates your in-game sensitivity from one shooter into the number that feels identical in another. SensLib converts using each game's exact yaw value and proves the result by showing an identical cm/360 on both sides.
Physical aim match: 40.8 cm/360 in the from-game = 40.8 cm/360 in the to-game, at 800 DPI. If the two numbers differ, the conversion is wrong — ours always match.
Supported games and their yaw values
The yaw (degrees turned per mouse count) is the constant every conversion runs on. Games appear here only after their yaw passes a two-source check:
| Game | Yaw (°/count) | Typical pro sens |
|---|---|---|
| Valorant | 0.07 | 0.3–0.5 |
| Counter-Strike 2 | 0.022 | 1–2 |
| Apex Legends | 0.022 | 1.2–2.2 |
| Overwatch 2 | 0.0066 | 4–8 |
| Team Fortress 2 | 0.022 | 1–3 |
Popular conversions
Dedicated pages for the most-searched pairs, each with the exact ratio, worked examples and a pair-specific FAQ:
How conversion works
Every shooter turns your view by a fixed number of degrees per mouse count — its yaw. Valorant uses 0.07 degrees per count, CS2 and Apex use 0.022, Overwatch 2 uses 0.0066. To keep your aim identical, the product of yaw × sensitivity must match across games, which gives a fixed ratio per pair. Distance for a full 360° turn (cm/360) is the physical check: converted correctly, it stays exactly the same. All ratios on SensLib are validated against community-measured physical turns on every build.
FAQ
How does a sensitivity converter work?
Every shooter turns your view by a fixed number of degrees per mouse count (its yaw). A converter applies the ratio between the two games' yaw values to your sensitivity, so the same hand movement produces the same turn. Verified with cm/360: both setups must travel the same physical distance for a full 360.
Is the Valorant to CS2 conversion exact?
Yes, for hipfire. Valorant's 0.07 yaw divided by CS2's 0.022 gives a fixed ratio of 3.18182, so converted setups are physically identical. Scoped weapons and ADS use separate multipliers that need in-game tuning.
Why doesn't the converter support Fortnite or Roblox?
Those games handle sensitivity through their own scales and multipliers rather than a documented yaw, so a conversion cannot be guaranteed. SensLib only supports games whose constants pass a two-source verification — a wrong conversion is worse than no conversion.
Should I change my DPI when switching games?
No — keep the same DPI and convert only the in-game sensitivity. The converter assumes identical DPI on both sides.