Convert Your Sensitivity to CS2 from Valorant, Apex or Overwatch

If you are coming to Counter-Strike 2 from another shooter, there is exactly one number you need, and it is not a matter of opinion.

Every first person shooter turns the camera a fixed number of degrees for each unit your mouse reports. CS2 turns 0.022 degrees per count. Valorant turns 0.07. Overwatch 2 turns 0.0066.

Divide one by the other and you have your conversion. That is the whole thing.

Every game, and what to multiply by

Take your in-game sensitivity from the game you are coming from and multiply it by the number in the right hand column. That is your CS2 sensitivity. Keep your DPI exactly the same.

Valorant 0.35 becomes CS2 1.114. Overwatch 2 at 5 becomes CS2 1.5.

Two rows are worth stopping on.

Apex Legends is 1. Apex is built on Source, same as Counter-Strike, and uses the identical 0.022. If you play Apex at 1.5, you already play CS2 at 1.5. There is nothing to convert, and almost nobody knows this.

Deadlock is exactly 2. Also a Valve game, also Source 2, and the value is precisely double. Halve your Deadlock sensitivity and you have CS2.

If you would rather not do arithmetic, the sensitivity converter handles every game on that list and gives you the CS2 console command to paste.

What you are actually converting

This is the part people miss, and it is why copying a number between games feels so wrong.

A Valorant player on 0.35 at 800 DPI and a CS2 player on 1.114 at 800 DPI are playing different numbers. But both of them move their hand 46.7 centimetres to turn a full circle.

That distance is the real setting. The in-game number is just how each game happens to label it.

So a correct conversion does not give you the same number. It gives you the same hand movement, which means every flick you have already learned still lands in the same place. That is the entire point.

This is also why eyeballing it fails so badly. A Valorant player who types 0.35 into CS2 ends up at roughly 148 centimetres per 360, which is three times slower than what they are used to, and it feels like dragging a brick.

What does not carry over

The maths is exact, but it only covers one thing. Four others it does not.

Scoped sensitivity is separate. Every game sets zoom sensitivity on its own scale. CS2 uses zoom_sensitivity_ratio_mouse, default 1. No converter touches it, and you have to feel that one out yourself, especially if you AWP.

Field of view changes the feel. CS2 has a fixed vertical FOV of 73.7 degrees. If you are coming from a game with a wider FOV, targets will appear to move differently across your screen even at an identical cm/360. That is covered properly in the resolution article.

Mouse acceleration voids all of it. If acceleration is on in Windows or in either game, your mouse does not move a fixed number of counts per centimetre, and none of these numbers describe anything.

Ability aiming has no equivalent. Nothing in CS2 corresponds to flicking onto an ability cast, so part of what you trained is simply not transferable.

After you convert

Check where you landed. Run the result through the eDPI calculator and see whether it sits inside the range the professional field actually uses. Coming from Overwatch or Valorant, a lot of people land much higher than any CS2 player plays.

If you landed above 1300 eDPI, think about it. Converting preserves what you are used to, not what is good. Valorant rewards a different kind of aim and plenty of Valorant players are on numbers no Counter-Strike player would choose. Here is where the professional field sits.

Then leave it alone. You have one correctly converted number. Changing it again in a week throws away the only advantage converting gave you.

Frequently asked

What is my Valorant sensitivity in CS2? Multiply by 3.1818. Keep the same DPI.

What is my CS2 sensitivity in Valorant? Divide by 3.1818, or multiply by 0.3143.

Do Apex and CS2 use the same sensitivity? Yes, exactly. Both use 0.022 degrees per count, so no conversion is needed.

What about Overwatch 2? Multiply your Overwatch sensitivity by 0.3 to get CS2.

Does converting change my DPI? No. Leave the DPI exactly where it is and only change the in-game number.

Why does the converted sensitivity still feel different? Most often the scoped sensitivity, the field of view, or mouse acceleration left on somewhere.

Will converting make me good at CS2? It means your hand starts where it left off instead of from zero. That is worth a lot and it is not the same as being good at the game.

The degrees-per-count values are the published constants each game uses, consistent across independent conversion tools. Every multiplier in the table is that game’s value divided by CS2’s 0.022, and you can check any row with a calculator. The cm/360 figure is 360 divided by DPI times sensitivity times degrees per count, multiplied by 2.54.