How does the sensitivity converter work?
Every shooter turns your view by a set number of degrees for each count your mouse sends. That number is called yaw. CS2 uses a yaw of 0.022 degrees per count at sensitivity 1, which is the default value of the m_yaw setting in the game files.
When two games have different yaw values, the same sensitivity number feels different. The converter fixes that by matching how far your view turns for the same hand movement. If the turn is the same, your muscle memory carries over.
You can type in either box. The other box, the table of all games and the cm/360 figure update as you type.
What is the formula for converting sensitivity?
The math is one line:
new sens = old sens × old game yaw ÷ new game yaw
To go from CS2 to Valorant, you multiply by 0.022 and divide by 0.07. That is the same as dividing your CS2 sens by about 3.18. To go the other way, you multiply by about 3.18.
DPI is not part of the formula. As long as you use the same mouse at the same DPI in both games, only the yaw values matter. DPI only comes in when you want cm/360.
Which yaw values does the tool use?
These are the values in our config file. Each one links to its source in the "Numbers used by this tool" box on this page.
| Game | Yaw (degrees per count) | Multiply by this to get CS2 sens | Notes |
|---|---|---|---|
| CS2 | 0.022 | 1 | Default m_yaw from the game files |
| Valorant | 0.07 | 3.1818 | Community measured, Riot has not published it |
| Apex Legends | 0.022 | 1 | Same as CS2 with a default config |
| Overwatch 2 | 0.0066 | 0.3 | Hipfire value |
| Fortnite | 0.005555 per 1% | 0.2525 | Use the percent shown in the game menu |
| Rainbow Six Siege | 0.00572958 | 0.2604 | Only with the default multiplier of 0.02 |
| Call of Duty (MW, Warzone, BO6) | 0.0066 | 0.3 | Hipfire, same as Overwatch 2 |
Valorant, Overwatch 2 and Call of Duty values come from community measurement and open-source tools, not from the game makers. They are the values most converters use.
What does cm/360 mean?
cm/360 is how many centimeters you move your mouse to spin a full circle in game. It is the cleanest way to compare aim speed, because it includes DPI, sensitivity and yaw in one number.
cm/360 = (2.54 × 360) ÷ (DPI × sens × yaw)
The 2.54 turns inches into centimeters, because DPI means counts per inch. If you match sensitivity with this tool, your cm/360 is the same in both games. That is why the tool shows only one cm/360 number.
Worked example 1: CS2 to Valorant
You play CS2 at 1.25 sensitivity and 800 DPI.
- Multiply by the CS2 yaw: 1.25 × 0.022 = 0.0275.
- Divide by the Valorant yaw: 0.0275 ÷ 0.07 = 0.3929.
- Your Valorant sens is 0.393.
Check it with cm/360. In CS2: 914.4 ÷ (800 × 1.25 × 0.022) = 41.6 cm. In Valorant: 914.4 ÷ (800 × 0.3929 × 0.07) = 41.6 cm. Both games turn the same amount for the same hand movement.
Worked example 2: Overwatch 2 to CS2
You play Overwatch 2 at 5.00 sensitivity.
- Multiply by the Overwatch 2 yaw: 5 × 0.0066 = 0.033.
- Divide by the CS2 yaw: 0.033 ÷ 0.022 = 1.5.
- Your CS2 sens is 1.50.
At 800 DPI that works out to about 34.6 cm for a full turn. You can plug that into the eDPI calculator to see your CS2 eDPI, which is 1,200.
Why does my converted sens still feel a bit off?
A few things can change how aim feels even when the math matches:
- Field of view. A wider FOV makes the same turn look slower on screen. The turn speed is the same, but your eyes judge it differently.
- Mouse acceleration. If one game or Windows adds acceleration, the turn depends on how fast you move. Turn it off and use raw input.
- Scoped and ADS aim. This tool only converts hipfire. Zoom scaling uses different rules in each game, so check scoped sensitivity separately.
- Changed config values. If you edited
m_yawin CS2 or the multiplier in Rainbow Six Siege, the default yaw no longer applies.
Give the new setting a few sessions before you change it. Most of the "feel" comes from habits, not numbers.
Which games are left out?
We only add a game when we can find its yaw value in a source we can link to. Deadlock is out for now because the game files and a popular sensitivity site disagree by a factor of two. Scoped and ADS conversion is also out, because it depends on FOV settings that change from game to game.
When should you use this tool?
Use it when you move to CS2 from another shooter, or when you play two games and want the same aim in both. It is also handy for checking a pro's settings from another game against your own.
After you convert, set up the rest of your game. Build a crosshair in the crosshair generator, adjust your gun position in the viewmodel generator, and save it all in a config with the autoexec builder.
Be careful with sites that offer "pro configs" behind a Steam login. Read how to spot fake Steam login pages before you sign in anywhere.
