A CS2 eDPI calculator needs only one multiplication: your mouse DPI times your in-game sensitivity. eDPI lets you compare two CS2 setups, or keep the same feel after changing DPI, while cm/360 does that job across different games. Below are both formulas, the Valorant to CS2 sens ratio and the console settings behind them.
How to calculate eDPI in CS2
eDPI = DPI × sensitivity. DPI here is the number of counts your mouse sends per inch of movement, which Liquipedia notes is more accurately called CPI. Setups with the same eDPI turn the same distance in game:
| DPI | Sensitivity | eDPI |
|---|---|---|
| 400 | 2.5 | 1,000 |
| 800 | 1.25 | 1,000 |
| 1,600 | 0.625 | 1,000 |
To keep your feel after changing DPI, divide your eDPI by the new DPI: 1,000 eDPI at 1,600 DPI needs a sensitivity of 0.625.
A higher DPI isn't more accurate in itself, Liquipedia stresses; it is just a finer unit. A low DPI makes the sensitivity setting more forgiving, because each step changes your turn speed less, while at a high DPI you end up adjusting the second or third decimal.
Set it under Settings > Keyboard / Mouse > Mouse Sensitivity, a slider from 0.1 to 8 with two decimals, or type sensitivity 0.625 in the console, which accepts values down to 0.0001. CS2's default is 1.25.
eDPI only compares like with like. Liquipedia points out that it is meaningful between players with the same m_yaw, and not between different games.
cm/360 for CS2
cm/360 is how far you move the mouse for one full turn. Liquipedia's formula is 360 ÷ (DPI × sensitivity × m_yaw), which gives inches; multiply by 2.54 for centimetres. With CS2's default m_yaw of 0.022, that comes down to roughly 41,564 ÷ eDPI.
| eDPI | cm/360 |
|---|---|
| 400 | 103.9 |
| 600 | 69.3 |
| 800 | 52.0 |
| 1,000 | 41.6 |
| 1,200 | 34.6 |
| 1,600 | 26.0 |
Because cm/360 is a physical distance, it is the number to match when you move between games that scale sensitivity differently.

Valorant to CS2 sens
The same number turns you further in Valorant than in CS2, so the value has to grow when you switch. Dot Esports and ONE Esports multiply by 3.18, and esports.gg gives 3.182; the difference only shows in the third decimal. Keep the same DPI in both games.
| Valorant sens | CS2 sens (×3.18) |
|---|---|
| 0.3 | 0.95 |
| 0.4 | 1.27 |
| 0.5 | 1.59 |
Going the other way, divide your CS2 sensitivity by 3.18. If you change DPI at the same time, scale by the two DPI values as well: CS2 sensitivity = Valorant sensitivity × 3.18 × Valorant DPI ÷ CS2 DPI. A Valorant 0.4 at 800 DPI becomes about 2.54 in CS2 at 400 DPI.
From CS:GO there is nothing to convert. Both games use the same default m_yaw of 0.022, so the same sensitivity turns the same distance. Old configs need one rename, though: CS:GO's zoom_sensitivity_ratio_mouse doesn't exist in CS2, where the command is zoom_sensitivity_ratio.
ONE Esports warns that a converted value only feels the same if the rest of your setup stays the same, monitor and resolution included, and Dot Esports and esports.gg both treat it as a starting point to adjust. A stretched 4:3 image, for example, makes targets cross the screen faster, as our video settings guide explains, even though the formula above has no term for your display.
m_yaw, m_pitch and zoom sensitivity
m_yaw and m_pitch set how many degrees you turn per mouse count, sideways and up or down, at a sensitivity of 1. Both default to 0.022 and neither is cheat-protected. Changing m_yaw alone makes sideways movement faster or slower than vertical movement, and every eDPI and cm/360 figure in this guide, or on any list of pro settings, assumes the default.
Scoped aim has its own multiplier: zoom_sensitivity_ratio, called Zoom Sensitivity Multiplier in the menu, scales your sensitivity while the view is zoomed in. It runs from 0.01 to 3 and defaults to 1. Valve describes it as an additional scale factor, so a value below 1 makes scoped aim slower than the game's own zoomed sensitivity and a value above 1 makes it faster.
Two CS:GO staples are gone. m_rawinput and m_customaccel, the raw input and mouse acceleration commands, are not in CS2's current list of console variables, so config lines that set them do nothing.
CS2 sensitivity among professionals
Liquipedia's list of player mouse settings, counted on October 27, 2026, mixes active players with inactive, retired and banned ones. Of its 552 complete entries, 94% use 400 or 800 DPI, the median eDPI is 800, and most sit between 600 and 1,200, which is roughly 69 to 35 cm per 360.

Dexerto's settings page for donk, last updated in September 2025, lists 800 DPI and 1.25 sensitivity, so 1,000 eDPI or about 41.6 cm per 360; our donk article has the rest of his setup. Players change their settings, so match a pro's eDPI rather than the raw sensitivity if your DPI differs. To try a new value, an offline map with bots works well, set up as in our practice commands guide.
Sources
- Mouse Settings — Liquipedia Counter-Strike Wiki
- List of player mouse settings — Liquipedia Counter-Strike Wiki
- How to convert your VALORANT sensitivity to CS2 — Dot Esports
- How to convert Valorant sensitivity to CS2 — ONE Esports
- How to convert VALORANT sensitivity to CS2 — esports.gg
- Donk's CS2 settings: Config, resolution, crosshair and more — Dexerto
- CS2 convar dump (convars.txt) — GameTracking-CS2 on GitHub
- CS2 Keyboard / Mouse settings layout — GameTracking-CS2 on GitHub



