Valorant to CS2 Sensitivity Converter: The Formula That Works

The conversion is one line of maths. Take your Valorant sensitivity and multiply it by 3.18, and the result is your CS2 sensitivity. That is the whole formula, and it is the same one every converter tool uses, whether it shows its working or not. If your Valorant sensitivity is 0.40, your CS2 sensitivity is 1.272, because 0.40 multiplied by 3.18 is 1.272. If your Valorant sensitivity is 0.60, your CS2 sensitivity is 1.908. The reverse works the same way in the other direction: take your CS2 sensitivity and divide it by 3.18, or multiply it by 0.314, and the result is your Valorant sensitivity. CS2 2.0 becomes Valorant 0.628, because 2.0 multiplied by 0.314 is 0.628. The one rule that sits underneath the formula is to keep the same DPI in both games. DPI is the mouse setting, sensitivity is the in-game setting, and the conversion only works when the DPI stays the same, because changing the DPI changes the whole calculation. Keep the DPI fixed, apply the formula, and you have a converted sensitivity that feels the same in both games.

The number 3.18 is not a guess, and it is not a round figure someone picked because it felt right. It comes from the yaw of each game, which is the amount the view turns for each unit of mouse movement. Valorant's yaw is 0.07 and CS2's yaw is 0.022, and 0.07 divided by 0.022 is 3.1818, which rounds to 3.18. That division is the entire reason the formula works: because Valorant turns your view further per unit of mouse movement than CS2 does, you need a higher sensitivity number in CS2 to cover the same turn. The ratio of the two yaw values tells you exactly how much higher, and that ratio is 3.18. This is why the formula is stable and why it does not change between updates unless one of the games changes its yaw, which neither game has done. You do not need to remember the yaw values to use the formula, but knowing where 3.18 comes from helps you trust it: it is a measured ratio between the two engines, not a community guess that might be wrong. If you ever see a converter using a different multiplier, that converter is either using a different method or it is simply wrong.

Here is the formula applied to the sensitivity values most players actually use, so you can find your number without doing the maths yourself. Each row is computed from the formula above, Valorant sensitivity multiplied by 3.18. Valorant 0.25 becomes CS2 0.795. Valorant 0.30 becomes CS2 0.954. Valorant 0.40 becomes CS2 1.272. Valorant 0.50 becomes CS2 1.59. Valorant 0.60 becomes CS2 1.908. Valorant 0.80 becomes CS2 2.544. Valorant 1.00 becomes CS2 3.18. If your Valorant sensitivity is not on the list, multiply it by 3.18 yourself and you will have the answer in seconds. The reverse direction works the same way, using CS2 sensitivity multiplied by 0.314. CS2 1.0 becomes Valorant 0.314. CS2 2.0 becomes Valorant 0.628. CS2 3.0 becomes Valorant 0.942. Use the table as a starting point, not a final answer, because the next sections explain what the formula cannot cover. But if you only need the number, the table has it, and every row in it comes from the same formula, so there are no surprises hiding in it.

The formula matches hipfire sensitivity only, and that limit matters more than most guides admit. Hipfire is aiming without scoping in, and it is the sensitivity you use for most of your movement and most of your fights. Scoped sensitivity and ADS sensitivity work differently in each game, because each game applies its own zoom multiplier when you scope in, and those multipliers do not match. A converted hipfire value will not give you a matching scoped feel, so do not expect your AWP or Operator scope to feel identical after converting. The second limit is field of view and engine feel. Valorant and CS2 render the world differently, with different fields of view and different movement, so the same turn speed can still feel different on screen. The third limit is that the formula gives you a starting point, not a finished setting. Your mouse, your mousepad, your grip, and your habits all change how a sensitivity feels, so two players with the same converted number can have very different experiences. The right move is to convert, play with the result, and fine-tune in small steps until it feels right in CS2 itself, rather than treating the converted number as untouchable.

eDPI is the number that makes sensitivity portable, and it is worth understanding before you convert anything. eDPI is DPI multiplied by sensitivity, so it combines your mouse setting and your in-game setting into one number. A player on 800 DPI with a Valorant sensitivity of 0.40 has an eDPI of 320, because 800 multiplied by 0.40 is 320. After converting to CS2, that same player uses 800 DPI with a sensitivity of 1.272, and the eDPI in CS2 terms is 800 multiplied by 1.272. The eDPI number itself changes between the games because the sensitivity scale changes, but the physical feel, the distance you move your mouse to turn a full circle, stays the same, and that is what matters. The practical lesson is simple: pick one DPI and keep it in both games. If you change your DPI between Valorant and CS2, the conversion breaks, because the formula assumes the DPI is identical. Most players settle on 400 or 800 DPI and leave it there forever, which keeps every conversion clean. If you are copying a pro setup, check their DPI first, because a sensitivity without its DPI is only half a setting. For a worked example of a pro setup, see our Keiko Valorant settings guide, which lists 800 DPI with 0.25 sensitivity for 200 eDPI.

Use this checklist every time you convert, and the switch between games will be smooth instead of frustrating. Step one is to write down your current Valorant sensitivity and your DPI before you change anything, so you can always go back. Step two is to keep the same DPI in both games, because the formula only works when the DPI stays fixed. Step three is to turn mouse acceleration off in both games and in your system settings, because acceleration makes the same mouse movement turn your view by different amounts depending on speed, which breaks any conversion. Step four is to apply the formula and set the CS2 sensitivity to the converted value. Step five is to test in a practice range, not in a live match, because the range lets you check flicks and tracking without pressure. Step six is to adjust in small steps if it feels off, changing the value a little at a time and testing again, rather than jumping to a new number. Step seven is to give it a few days, because a new sensitivity always feels strange at first and your muscle memory needs time to settle. Players who want a quicker route can also use the Valorant sensitivity converter tool on 217G, which applies the same formula for you. Once your setup is settled, you can browse the store for account options.