CS2 sensitivity converter
Pick two games, type your sensitivity and DPI, and get the number that turns your view the same distance in the other game.
Matches the distance your mouse travels for a full turn, not the on-screen distance at a different FOV.
How to convert sensitivity between games
Sensitivity numbers only mean something inside one game. A Valorant 0.4 and a CS2 0.4 are very different speeds, because each game multiplies your mouse movement by its own fixed constant before it turns the camera. The converter removes that constant and matches the thing that is the same in every game: how far your hand moves for a full 360 degree turn.
A worked example
Say you play Valorant at 800 DPI with a sensitivity of 0.4. A full turn takes 16.07 inches, or 40.8 cm, of mouse travel. To get the same turn in CS2 at 800 DPI you need a sensitivity of 1.273. If you would rather run CS2 at 400 DPI, the number doubles to 2.545 and the 40.8 cm stays put. That is the whole trick: DPI and sensitivity trade off against each other, so only their product matters. We call that product eDPI.
Why the numbers differ so much
The constant is called yaw: the degrees the view turns for each count the mouse reports at sensitivity 1. CS2, CS:GO, Apex and Team Fortress 2 use 0.022, Valorant uses 0.07, and Overwatch 2 and Call of Duty use 0.0066. Divide one by the other and you have the conversion ratio. Valorant to CS2 is 0.07 ÷ 0.022 = 3.18; Overwatch 2 to CS2 is 0.0066 ÷ 0.022 = 0.3, so Overwatch 2 sensitivity 5 is CS2 1.5 at the same DPI.
| Game | Yaw (deg per count) | Basis | Note |
|---|---|---|---|
| Counter-Strike 2 | 0.022 | Documented | m_yaw 0.022, the Source engine default. |
| CS:GO | 0.022 | Documented | Same yaw as CS2, so sensitivity carries over 1:1. |
| Team Fortress 2 | 0.022 | Documented | Source engine, m_yaw 0.022. |
| Apex Legends | 0.022 | Documented | Modified Source engine, m_yaw 0.022. |
| Valorant | 0.07 | Documented | Riot's yaw of 0.07 degrees per count. |
| Overwatch 2 | 0.0066 | Documented | 0.0066 degrees per count. |
| Call of Duty (Warzone, MW, BO6) | 0.0066 | Documented | Same 0.0066 yaw as Overwatch; assumes the default ADS multiplier of 1.00. |
| Fortnite | 0.005555 | Community-measured | Community-measured 0.005555 degrees per count per 1% of X-axis sensitivity. |
| Rainbow Six Siege | 0.00572957795 | Community-measured | Community-measured 0.00573 yaw (1/10,000 of a radian); assumes the default multiplier unit. |
Popular conversions
Valorant to CS2 and CS2 to Valorant have their own pages with longer tables. The rows below assume 800 DPI in both games.
Valorant to CS2
| Valorant sens | Counter-Strike 2 sens | Valorant eDPI at 800 DPI | cm per 360 |
|---|---|---|---|
| 0.2 | 0.636 | 160 | 81.6 |
| 0.25 | 0.795 | 200 | 65.3 |
| 0.3 | 0.955 | 240 | 54.4 |
| 0.35 | 1.114 | 280 | 46.7 |
| 0.4 | 1.273 | 320 | 40.8 |
| 0.45 | 1.432 | 360 | 36.3 |
| 0.5 | 1.591 | 400 | 32.7 |
| 0.6 | 1.909 | 480 | 27.2 |
| 0.8 | 2.545 | 640 | 20.4 |
| 1 | 3.182 | 800 | 16.3 |
CS2 to other games
| CS2 sens | Valorant | Overwatch 2 | Call of Duty | Fortnite | R6 Siege | cm per 360 |
|---|---|---|---|---|---|---|
| 0.5 | 0.157 | 1.67 | 1.67 | 1.98 | 1.92 | 103.9 |
| 0.75 | 0.236 | 2.5 | 2.5 | 2.97 | 2.88 | 69.3 |
| 1 | 0.314 | 3.33 | 3.33 | 3.96 | 3.84 | 52 |
| 1.25 | 0.393 | 4.17 | 4.17 | 4.95 | 4.8 | 41.6 |
| 1.5 | 0.471 | 5 | 5 | 5.94 | 5.76 | 34.6 |
| 2 | 0.629 | 6.67 | 6.67 | 7.92 | 7.68 | 26 |
| 2.5 | 0.786 | 8.33 | 8.33 | 9.9 | 9.6 | 20.8 |
| 3 | 0.943 | 10 | 10 | 11.88 | 11.52 | 17.3 |
| 4 | 1.257 | 13.33 | 13.33 | 15.84 | 15.36 | 13 |
CS:GO, Team Fortress 2 and Apex Legends use the same number as CS2 at the same DPI.
After you convert
Treat the converted number as a starting point. Fields of view differ between games, so a flick to a target on screen can feel a touch faster or slower even when the full turn matches. Play a few deathmatches and nudge the value by 1 to 2% until it feels right, then stop changing it. Chopping and changing is the quickest way to never build muscle memory.
To see whether your new setup is in the normal range, drop your numbers into the eDPI calculator: across 858 active pros the median CS2 eDPI is 800, about 52 cm per 360, which is a Valorant sensitivity of 0.314 at 800 DPI. If you would rather work backwards from a distance you like, the cm/360 calculator turns a target into a sensitivity for any DPI.
CS2 accepts sensitivity from 0.0001 to 8, so at 800 DPI the ceiling is 6,400 eDPI and you will not run into it. Put the final value in your config with the autoexec generator so it survives a reinstall, and while you are setting up a new game, rebuild your crosshair and tune the viewmodel too.
How the maths works
Every game turns the camera by yaw × sensitivity × counts, where a count is the smallest movement your mouse reports and yaw is a fixed number for each game. A mouse set to DPI reports that many counts per inch, so one full turn takes 360 ÷ (yaw × sens × DPI) inches.
- cm per 360 = 360 ÷ (yaw × sens × DPI) × 2.54
- Converted sens = (yawfrom × sens × DPIfrom) ÷ (yawto × DPIto)
Both games then turn the same distance for the same hand movement. The Source-engine games (CS2, CS:GO, TF2, Apex) share a yaw of 0.022, so their sensitivity is the same number at the same DPI. Valorant's yaw is 0.07, which is why its numbers are about a third of CS2's.
Yaw sources: 0.022 is Valve's own m_yaw default. 0.07 (Valorant) and 0.0066 (Overwatch 2 and Call of Duty) are the values every public converter agrees on, and we cross-checked them against three separate open-source converter tables. Fortnite (0.005555 per 1% of X-axis sensitivity) and Rainbow Six Siege (0.00572957795) are community-measured and are marked as such. Deadlock and The Finals are left out because no yaw we could cross-check exists.
How to use it
- Choose the game you play now under From, then enter its sensitivity and your mouse DPI.
- Choose the game you are moving to under To. Change its DPI only if you use a different mouse setting there.
- Copy the big number into the new game. Check the cm per 360 matches, then adjust by 1 to 2% by feel if you like.
- Press the arrows between the two boxes to run the conversion the other way.
FAQ
How do I convert my Valorant sensitivity to CS2?
Multiply your Valorant sensitivity by 3.18 (0.07 ÷ 0.022) when both games use the same mouse DPI. Valorant 0.4 becomes CS2 1.273. If you change DPI, scale the result by the old DPI ÷ the new DPI: the same Valorant 0.4 at 800 DPI is CS2 2.545 at 400 DPI.
How do I convert CS2 sensitivity to Valorant?
Divide your CS2 sensitivity by 3.18, or multiply by 0.3143. CS2 1.0 becomes Valorant 0.314 at the same DPI. Both numbers then give the same cm per 360, so your arm travels the same distance for a full turn.
Does the converter match my crosshair movement exactly?
It matches rotation per inch of mouse travel, the figure players call cm/360. Because games use different field of view settings, a flick to a target on screen can still feel slightly different, but a full turn will be identical.
Why is the CS:GO number the same as CS2?
Both use Valve's Source engine yaw of 0.022 degrees per count, so a CS:GO sensitivity carries straight over to CS2 at the same DPI. Apex Legends and Team Fortress 2 use the same value.
Does my scoped or zoomed sensitivity convert too?
Not by this tool, which converts normal unzoomed sensitivity. CS2 applies an extra zoom_sensitivity_ratio (default 1) when you are zoomed in, and Valorant has its own scoped sensitivity multipliers. Convert your unzoomed number first, then adjust the scoped settings in the new game by feel.
How accurate are the Fortnite and Rainbow Six Siege conversions?
Less than the rest. Valve, Riot and Blizzard values are fixed constants. The Fortnite and R6 Siege yaws are community-measured, so treat them as accurate to about 1% and fine-tune by feel.
Which games are missing?
Deadlock and The Finals are not included, because the community values for them disagree and we could not confirm one. They will be added once a figure can be verified.
