Degrees per mouse count
Both games turn 0.022° per count, so the same sensitivity gives the same turn.
CS:GO sensitivity =
CS2 sensitivity × 1
Both games turn 0.022° per mouse count, so the same sensitivity at the same DPI gives the same turn.
Different value? Find it in the chart or let the Windows app read it from your game.
CS2 values from 0.40 to 3.20, the CS:GO value with the same 360° distance, and how far you move the mouse for one full turn at 400, 800 and 1600 DPI.
| CS2 | CS:GO | cm/360 · 400 DPI | cm/360 · 800 DPI | cm/360 · 1600 DPI |
|---|---|---|---|---|
| 0.40 | 0.400 | 259.77 | 129.89 | 64.94 |
| 0.60 | 0.600 | 173.18 | 86.59 | 43.30 |
| 0.80 | 0.800 | 129.89 | 64.94 | 32.47 |
| 1.00 | 1.000 | 103.91 | 51.95 | 25.98 |
| 1.11 | 1.114 | 93.28 | 46.64 | 23.32 |
| 1.20 | 1.200 | 86.59 | 43.30 | 21.65 |
| 1.40 | 1.400 | 74.22 | 37.11 | 18.56 |
| 1.60 | 1.600 | 64.94 | 32.47 | 16.24 |
| 1.80 | 1.800 | 57.73 | 28.86 | 14.43 |
| 2.00 | 2.000 | 51.95 | 25.98 | 12.99 |
| 2.20 | 2.200 | 47.23 | 23.62 | 11.81 |
| 2.40 | 2.400 | 43.30 | 21.65 | 10.82 |
| 2.60 | 2.600 | 39.97 | 19.98 | 9.99 |
| 2.80 | 2.800 | 37.11 | 18.56 | 9.28 |
| 3.00 | 3.000 | 34.64 | 17.32 | 8.66 |
| 3.20 | 3.200 | 32.47 | 16.24 | 8.12 |
CS2 turns 0.022° per mouse count at sensitivity 1. CS:GO turns 0.022°. The ratio of the two is the multiplier.
Both games turn 0.022° per count, so the same sensitivity gives the same turn.
360 ÷ (0.022 × 1.114) = 14,689 counts
14,689 ÷ 800 DPI = 18.36 in = 46.64 cm
Divide 360° by the angle per count to get counts per turn, then divide by DPI to get inches.
CS:GO shows 106.26° horizontally at 16:9 and CS2 106.26°, so matching a point on screen gives a different CS:GO value than matching a full turn. For CS2 1.114:
| Method | What feels the same | CS:GO for 1.114 | |
|---|---|---|---|
| 360° distancethis chart | Full turns, flicks to targets behind you, 180° checks | 1.114 | |
| Monitor distance 0% | Tracking right at the crosshair | 1.114 | |
| Monitor distance 56.25% | Flicks to targets about halfway to the screen edge | 1.114 | |
| Monitor distance 75% | Flicks to targets three quarters of the way out | 1.114 | |
| Monitor distance 100% | Flicks to the screen edge | 1.114 |
This page is a reference chart. The parts that need your PC are in the free Windows app:
"Open in TrueSens" starts the installed app with CS2 1.114 → CS:GO already filled in (truesens://convert?from=cs2&to=csgo&sens=1.114). If nothing opens, install the app first. Windows 10 and 11, x64, no ads, no account.
Use the same value. CS:GO 1.114 is CS2 1.114.
Use the same value. CS2 and CS:GO both turn 0.022° per mouse count, so CS2 1.114 is CS:GO 1.114 at the same DPI.
1.114 at any DPI. At 800 DPI both settings turn you 360° with 46.64 cm of mouse movement.
No. The multiplier is the same at 400, 800 or 1600 DPI as long as you use the same DPI in both games. DPI only changes your cm/360.
360 distance keeps full turns and flicks to off-screen angles identical, and the chart on this page uses it. Monitor distance 0% matches tracking near the crosshair and gives CS:GO 1.114 for CS2 1.114, because CS:GO's horizontal FOV (106.26°) equals CS2's (106.26°).
Open the CS:GO console and enter sensitivity 1.114, or set it in the game's mouse settings. The free TrueSens app for Windows can write the value into the CS:GO config for you and keeps a backup.
Use the same value: CS:GO 1.114 is CS2 1.114.