
Sensitivity converter and eDPI calculator
Move your mouse sensitivity from one shooter to another so the same hand movement turns you just as far, and work out your eDPI and cm/360.
Sensitivity converter
Convert your sensitivity
Converted sensitivity
× 0.3143Valorant sensitivity
0.6286
at 800 DPI, 25.98 cm/360
Exact value
0.628571428571The big number is rounded to 4 decimals. Use more decimals if the game accepts them.
| Setting | Now | Converted |
|---|---|---|
| Game | Counter-Strike 2CS2 | Valorant |
| Sensitivity | 2 | 0.6286 |
| DPI | 800 | 800 |
| eDPI | 1,600 | 502.88 |
| cm/360 | 25.98 cm | 25.98 cm |
| in/360 | 10.23 in | 10.23 in |
Type your sensitivity to see the converted value.
The same aim in every supported game
At 800 DPI, each of these turns 360° in 25.98 cm of mouse movement.
| Game | Sensitivity | eDPI |
|---|
eDPI calculator
- eDPI
- 1,600
- cm/360
- 25.98
- in/360
- 10.23
eDPI is DPI × in-game sensitivity. It only compares settings within the same game, because each game turns a different angle per mouse count: 1,600 eDPI in CS2 turns as far as about 503 eDPI in Valorant. To compare across games, use cm/360.
Everything is calculated in this browser. Your last games and values are saved only here, and nothing is uploaded.
How to convert your sensitivity
- Choose the game you play now and type its in-game sensitivity. Add your mouse DPI to see eDPI and cm/360.
- Choose the game you want to convert to. If you will also change your mouse DPI, type the new DPI.
- Enter the converted sensitivity in the new game's normal (hipfire) mouse sensitivity setting. Open Exact value for more decimals.
- Select Swap to convert the other way. The value goes back to exactly what you started with.
Advertisement
What cm/360 is
cm/360 is how far you move your mouse on the mousepad to turn a full 360° in the game. Every game turns your view by a fixed angle for each count your mouse sends at sensitivity 1, called its yaw. The view turns yaw × sensitivity degrees per count, and your mouse sends DPI counts per inch of movement, so:
cm/360 = 360 ÷ (DPI × sensitivity × yaw) × 2.54
For example, CS2 at 800 DPI and sensitivity 2: 360 ÷ (800 × 2 × 0.022) = 10.23 inches, or 25.98 cm for a full turn.
Why converting by cm/360 keeps your aim the same
Muscle memory is a distance: how far your hand moves to turn your view by a certain angle. When two games have the same cm/360, the same flick turns you the same amount in both. So the converter keeps cm/360 fixed: new sensitivity = old sensitivity × old yaw × old DPI ÷ (new yaw × new DPI). From CS2 2 to Valorant at the same DPI, that is 2 × 0.022 ÷ 0.07 = 0.6286.
This matches hipfire, your normal aim without zooming. It does not convert scoped or ADS (aim down sights) sensitivity, which every game scales in its own way. Field of view isn't converted either: a wider view makes the same turn look faster on screen, even though your hand moves the same distance. Mouse acceleration, in a game, mouse software or Windows, makes the turn depend on how fast you move, so no fixed number can match it.
Windows Enhance pointer precision
Microsoft describes Enhance pointer precision as a setting that makes the pointer more accurate when you move the mouse slowly; in Windows 11 it is under Settings, Bluetooth & devices, Mouse. Because it changes pointer movement with speed, the same distance on your mousepad doesn't always give the same result. If a game follows the Windows pointer instead of reading raw mouse input, turn it off while you play, or a cm/360 value won't hold.
Supported games and their yaw
| Game | Yaw | Sources |
|---|---|---|
| Counter-Strike 2 | 0.022 | TotalCSGO (default m_yaw), CSDB.gg, MetaBot.gg |
| CS:GO | 0.022 | TotalCSGO (default m_yaw), Valve Source SDK, CSDB.gg |
| Valorant | 0.07 | CSDB.gg, MetaBot.gg, Hotspawn (CS2 ÷ 3.18) |
| Apex Legends | 0.022 | CSDB.gg, MetaBot.gg (same as CS2) |
| Overwatch 2 | 0.0066 | CSDB.gg, MetaBot.gg, GamerTweak (CS:GO × 3.3333) |
| Team Fortress 2 | 0.022 | Valve Source SDK (in_mouse.cpp), CSDB.gg |
CS2, CS:GO and Team Fortress 2 assume the default m_yaw of 0.022; if you changed m_yaw in the console, the result won't match. Left out on purpose: Deadlock, because the sources disagree (0.022 or 0.044), and Fortnite and Rainbow Six Siege, because we could not verify how their settings map to one number.
Sources, checked 20 November 2026: Valve, Source SDK 2013, in_mouse.cpp (m_yaw default 0.022; the view turns m_yaw × mouse movement scaled by sensitivity); TotalCSGO, CS2 & CS:GO m_yaw command (default 0.022); CSDB.gg, CS2 Sensitivity Converter (yaw table); MetaBot.gg, CS2 Sensitivity Converter (yaw table); Hotspawn, Counter-Strike to VALORANT sensitivity; GamerTweak, How to carry over your CSGO sensitivity to Overwatch 2; Aim Lab, A quick explainer on cm/360 (ranges credited to Voltaic); Microsoft Support, Change mouse settings.
Your settings stay in your browser
The converter does its maths on your device. Only your last games and values are saved, in this browser, and Reset to defaults removes them. Nothing is uploaded.
Frequently asked questions
How do I convert Valorant sensitivity to CS2?
At the same DPI, multiply your Valorant sensitivity by 3.1818 (0.07 ÷ 0.022), so 0.4 in Valorant is 1.2727 in CS2. To go from CS2 to Valorant, divide by 3.1818: 2 in CS2 is 0.6286 in Valorant.
Can I compare eDPI between games?
Only within the same game. eDPI is DPI × in-game sensitivity, but every game turns a different angle per mouse count, so 1,600 eDPI in CS2 and about 503 eDPI in Valorant are the same 25.98 cm/360. To compare across games, use cm/360.
Does this convert scoped or ADS sensitivity?
No. It converts hipfire, your normal unzoomed aim. Scopes, ADS multipliers and field of view work differently in every game, so set those in each game after you enter your converted hipfire sensitivity.
What is a good cm/360?
There is no single right value: pick one you can control and keep it. As a rough guide, Aim Lab lists common ranges from Voltaic of 35 to 75 cm for Valorant and CS2, and 20 to 60 cm for Overwatch 2 and Apex Legends.
Why are Fortnite, Rainbow Six Siege and Deadlock missing?
A game is only listed when at least two sources agree on its yaw. For Deadlock the sources disagree (0.022 or 0.044), and we could not verify how the Fortnite and Rainbow Six Siege settings map to one number, so they are left out rather than guessed.
More free tools
Advertisement