The gaming sensitivity converter translates your mouse sensitivity between CS2, Valorant, Overwatch 2, Apex Legends, Fortnite, Call of Duty, and Rainbow Six Siege. Enter your current game and sensitivity below – the tool calculates your equivalent setting in every other game, plus your cm/360 and eDPI so you know exactly how your aim translates. See our gaming tools hub for deeper context.
Most online converters give you a single number and hope you trust it. This one shows your cm/360 distance, includes a reverse calculator if you already know your target, and lets you load pro player presets from s1mple, TenZ, and others as a starting point. Pick your source game and start converting.
Disclosure: We may earn a commission when you buy through links on this page. This does not affect our recommendations. Learn more
Sensitivity Converter Tool
Select your source game, enter your DPI and sensitivity, then see the equivalent setting in every supported game. The converter preserves your cm/360 distance so your muscle memory stays consistent across titles.
Already know your ideal cm/360? Enter it below to find the exact sensitivity for every game.
Pro Player Sensitivity Presets
These are verified settings from top competitive players. Click any row to load that player’s settings into the converter above.
| Player | Game | DPI | Sens | eDPI | cm/360 | Role |
|---|
Understanding eDPI and cm/360
What is eDPI?
eDPI (effective DPI) is your DPI multiplied by your in-game sensitivity. It gives a single number that represents your true mouse speed regardless of DPI. A player using 400 DPI at 2.0 sensitivity (eDPI 800) has identical aim speed to someone using 1600 DPI at 0.5 sensitivity (eDPI 800).
eDPI is game-specific because different games use different sensitivity scales. An eDPI of 800 in CS2 is much slower than 800 in Overwatch 2 because CS2 uses a smaller yaw value (the internal rotation per count).
What is cm/360?
cm/360 measures how many centimeters you need to move your mouse to do a full 360-degree rotation in game. This is the universal metric – it stays the same across all games when you convert correctly. Most competitive FPS players use 25-50 cm/360. Lower numbers mean faster sensitivity, higher numbers mean slower.
Typical cm/360 Ranges
| cm/360 Range | Category | Best For |
|---|---|---|
| 15-25 cm | High sensitivity | Close-range tracking, Overwatch heroes like Tracer |
| 25-40 cm | Medium sensitivity | All-around aim, most Valorant and Apex players |
| 40-60 cm | Low sensitivity | Precision aiming, most CS2 riflers |
| 60-100 cm | Ultra-low sensitivity | AWP/sniper specialists, requires large mousepad |
How Sensitivity Conversion Works
Every FPS game uses an internal value called yaw – the number of degrees your view rotates per mouse count. Different engines use different yaw values, which is why the same “sensitivity 1.0” feels completely different in CS2 vs Valorant.
Yaw Values by Game
| Game | Yaw Value | Engine | Notes |
|---|---|---|---|
| CS2 | 0.022 | Source 2 | Same as CS:GO |
| Valorant | 0.07 | Unreal Engine 4 | Fixed, cannot change |
| Apex Legends | 0.022 | Source | Identical to CS2 |
| Overwatch 2 | 0.0066 | Proprietary | Higher sens scale |
| Fortnite | 0.5585 | Unreal Engine 4/5 | Uses percentage (0-100%) |
| Call of Duty: Warzone | 0.0066 | IW Engine | Same scale as OW2 |
| Rainbow Six Siege | 0.00572958 | AnvilNext 2.0 | Per-optic ADS sliders |
The Formula
To convert sensitivity between two games while keeping the same physical mouse movement:
This preserves your cm/360, meaning the same physical mouse movement produces the same in-game rotation in both games. The converter above handles this math automatically.
Common Sensitivity Mistakes
1. Using outdated conversion multipliers. Several popular tools still use CS:GO-era formulas that do not account for engine changes in CS2. Always verify your converted sensitivity matches your cm/360 in both games.
2. Ignoring mousepad size. Converting to a low sensitivity like 50+ cm/360 is pointless if your mousepad is 30cm wide. You physically cannot complete a 180-degree turn. Match your sensitivity to your available desk space. Our mousepad guide covers sizing.
3. Changing sensitivity too often. Muscle memory takes 2-4 weeks to develop at a new sensitivity. Switching every few days resets your progress. Pick a cm/360, convert it to all your games, and stick with it for at least two weeks before adjusting.
4. Copying pro settings without context. A pro using 25 cm/360 has thousands of hours of practice at that speed. If you are coming from 60 cm/360, jumping straight to 25 will destroy your aim. Adjust gradually – drop by 5 cm/360 increments over several weeks.
5. Forgetting DPI matters. Two players with the same in-game sensitivity but different DPI have completely different aim speeds. Always factor in DPI when comparing settings – use eDPI or cm/360 instead of raw sensitivity numbers.
Frequently Asked Questions
How do I convert CS2 sensitivity to Valorant?
Divide your CS2 sensitivity by 3.18. For example, CS2 sensitivity 1.0 equals Valorant 0.314. Both games will have the same cm/360, meaning your physical mouse movements produce identical rotations. The converter above does this math with your exact DPI for precision.
What DPI should I use for gaming?
800 DPI is the most common choice among competitive FPS players. It offers a good balance between in-game precision and desktop usability. 400 DPI is also popular but feels slow on the Windows desktop. Higher DPI like 1600 works fine – just lower your in-game sensitivity proportionally. The eDPI stays the same.
What is a good cm/360 for FPS games?
Most competitive FPS players use 25-50 cm/360. Lower values (25-35 cm) work for tracking-heavy games like Overwatch and Apex. Higher values (35-50 cm) suit precision games like CS2 and Valorant. Start around 35 cm/360 if you are unsure and adjust based on whether you overshoot or undershoot targets.
Does higher DPI give better accuracy?
Higher DPI gives finer mouse tracking resolution, which matters at very low in-game sensitivities. At 400 DPI with very low sens, you can get pixel skipping where the crosshair jumps over pixels. 800-1600 DPI eliminates this. Beyond 1600 DPI, the accuracy gains are negligible for most sensors and the higher DPI just makes your desktop cursor annoyingly fast.
Why does the same sensitivity feel different between games?
Each game engine uses a different yaw value – the internal degrees-per-count that converts mouse input to camera rotation. CS2 uses 0.022 yaw while Valorant uses 0.07, so “sensitivity 1.0” in CS2 is roughly three times slower than “sensitivity 1.0” in Valorant. FOV differences between games also affect perceived speed even when cm/360 matches.
Should I use the same sensitivity for all games?
Keeping the same cm/360 across games is generally recommended since it maintains your muscle memory. However, some players prefer slightly higher sensitivity in tracking-heavy games (Apex, Overwatch) and lower sensitivity in tap-heavy games (CS2, Valorant). A 10-15% difference between games is reasonable if it helps your playstyle.
Sources & References
- Mouse-Sensitivity.com – Game Engine Yaw Database (1,648 games verified)
- ProSettings.net – Professional Player Settings Database (CS2, Valorant verified Feb 2026)
- Kovaak Focal Length Scaling Research – Monitor Distance and FOV Conversion Mathematics
- Valve Developer Community – Source Engine Mouse Input and Yaw Documentation
