You decided to take a break from VALORANT and hopped into your first CS2 deathmatch; how bad will it be? You've had hundreds and thousands of hours in VALORANT, and you're so sure of yourself that this is a breeze. But then it hit you: you watch as your default crosshair goes past three heads in a row. But that's not on you, and no, you weren't humbled. It's just that VALORANT and CS2 read your mouse differently. The good news is that you can convert your VALORANT sensitivity to CS2 by multiplying your sensitivity by 3.18.
The 3.18 Multiplier Is the Only Math You Need
To get your VALORANT to CS2 sensitivity, take your in-game VALORANT sensitivity and multiply by 3.18.
- VALORANT to CS2: VALORANT sens * 3.18
- CS2 to VALORANT: CS2 sens / 3.18
Why 3.18? It Comes Down to Yaw
And before you say 3.18 is some folklore or the sister of pi, no, it comes from the fact that these different game engines handle rotation differently. Both games rotate your view by a fixed amount per mouse count at sensitivity 1.0, and this is where the yaw value comes in. This value is called yaw; CS2 uses 0.022, while VALORANT uses 0.07. Dividing 0.07 by 0.022 gives you 3.1818, which we round to 3.18.
What stays the same is your 360° distance (the physical mouse movement needed to complete one full 360 degree rotation). Converting your mouse sensitivity inherently preserves this distance between games, helping your aim feel consistent.
Why You Cannot Just Copy Your eDPI
Many players try to match eDPI, but that eventually leads to the wrong result. eDPI is just your DPI (dots per inch) multiplied by your sensitivity in-game.
Say your sensitivity in VALORANT is 0.35 at 800 DPI, then that would be equal to 280 eDPI. After converting to 1.11 sensitivity in CS2, your eDPI becomes 888 primarily because CS2 uses a different sensitivity scale.
Even though the eDPI changes, the distance you move your mouse stays the same, so whether you're doing the math yourself or using a sensitivity converter, convert your current in-game setting and not your eDPI to preserve muscle memory.
Keep Your DPI, Then Sort Out Zoom
One sensitivity setting that most people forget to check after converting is scoped sensitivity in CS2, which is controlled by zoom_sensitivity_ratio. The default value of 1.0 keeps your AWP aiming feel close to your normal (hipfire) sensitivity. VALORANT works a bit differently, using its own ADS exactly the same even if you convert your sensitivity.
Same goes for FOV in VALORANT, and since neither game really lets you tweak it, having set your base is something you'd want to get the groove with. And if you're still losing your gunfights, it may be because of your crosshair placement and something only a coach could point out in gameplay or two of yours.
Convert First, Then Decide If You Want to Change
If I were you, I'd stick with your converted sensitivity for a week before deciding to change your sensitivity at all. It's all about muscle memory and getting the hang of CS2's movement and mechanics.
Frequently Asked Questions
Does this work for other games? Carrying your sens into another game depends on the yaw value, but for Overwatch, Fortnite, and Apex it works fine. For any other supported game outside of these, just find the individual multiplier and do the math. There's also a sensitivity calculator per game you can use if you don't fancy the manual approach.
Does my aim trainer need the same number? Yes, match your equivalent sensitivity — the physical distance needed to complete a 360° rotation (cm/360)
