How to Convert Valorant, Apex and Overwatch 2 Sensitivity to CS2

Valorant 0.4 at 800 DPI is 1.273 in CS2. Type your 0.4 into CS2 and you turn more than three times slower than you are used to. Type 4 and you turn three times faster, while your hand still remembers the old distance. The two games turn the view by a different angle for the same mouse step, so you cannot copy the number from one menu to the other. Below is the whole method, with multipliers for Valorant, Apex Legends, Overwatch 2, Fortnite, Rainbow Six Siege and Call of Duty, plus data on where the converted number lands among CS2 pros.

You can do the maths in our sensitivity converter, which went live together with this guide. Here we explain where the numbers come from and what else you have to check for a converted sensitivity to hold up.

Why 0.4 in one game is not 0.4 in another

Every game turns the view by a fixed number of degrees per mouse count at sensitivity 1. That value is called yaw. CS2 uses 0.022, Valorant 0.07, Overwatch 2 and Call of Duty 0.0066. The sensitivity in your menu is a multiplier on top of it, so 0.4 in Valorant turns the view 0.028° per count and 0.4 in CS2 only 0.0088°.

Your hand remembers distance: how many centimetres you drag the mouse to spin a full 360°. That is cm/360, and you get it from 360 ÷ (yaw × sensitivity × DPI) × 2.54. Converting between games means finding the number in the new game that keeps cm/360 the same. Valorant 0.4 at 800 DPI is 40.8 cm per turn, and the same 40.8 cm in CS2 comes from a sensitivity of 1.273.

Multipliers between games

The multiplier is the ratio of the two yaw values. With the same DPI in both games you multiply the sensitivity from the game you play now and get the one for the game you are moving to. Here are the multipliers to CS2 and back.

Apex is the odd one out because it runs a modified Source engine with the same yaw as CS2. Your Apex sensitivity goes into CS2 unchanged as long as the DPI matches. Fortnite counts sensitivity in percent and has separate X and Y sliders, so we convert the X slider and you set Y to the same value. Siege takes whole numbers in its menu, so the result has to be rounded, and at low values rounding can shift your cm/360 by a few percent.

Worked example: Valorant to CS2 in five steps

If you run a different DPI in CS2 than in Valorant, switch on "I use a different DPI in this game" in the converter and enter the second value. Without it the result is twice too slow or twice too fast whenever one game runs at 400 and the other at 800. At 1600 DPI in CS2 and the same distance you need half the sensitivity, which is 0.636.

Common Valorant sensitivities in CS2

If you would rather skip the converter, here are ready conversions for the Valorant sensitivities that show up most often. All at 800 DPI in both games.

From other games: four examples

Overwatch 2 at sensitivity 5 and 800 DPI is 34.6 cm per turn, which is 1.5 in CS2. Call of Duty shares the yaw, so 7 in Warzone is 2.1 in CS2. Fortnite 7.92% on the X slider gives 2.0, and Rainbow Six Siege 10 gives 2.604. Apex Legends 1.6 stays 1.6. In every case the number on screen goes up or down while the distance your hand travels for a full turn stays the same.

Entering it in CS2 and checking it with a ruler

In CS2 you set sensitivity in the keyboard and mouse tab of the settings, or in the console with sensitivity 1.273. The game stores the value in your config. It is worth checking once that what you typed really gives the cm per turn you calculated: load a practice map, pick a clear point on a wall and drag the mouse along a ruler by the calculated distance. If one smooth sweep brings you back to the same point after a full turn, the sensitivity is right. The test takes a minute and catches most problems, including a wrong DPI profile in your mouse software.

That leaves the DPI question: you do not need to change it when you switch games. In our database 96 of 185 pros play at 800 DPI and 81 at 400, so both are ordinary. Changing DPI at the same eDPI leaves cm per turn untouched and only changes how densely the sensor samples your movement. If you play at 800, stay at 800.

Where you land among CS2 pros

The median of the 185 pros in our database with a recorded DPI and sensitivity is 800 eDPI, or 51.95 cm per turn. The middle half of the field plays between 720 and 960 eDPI, which is 43.3 to 57.7 cm per turn. The full breakdown is in our report on pro settings, and every profile in the crosshair database shows one player's sensitivity.

Valorant 0.4 at 800 DPI works out to 1018 eDPI in CS2, between the third quartile and the ninth decile of the field: you turn faster than more than three quarters of the pros. That is no problem, but it is worth knowing that in CS2 the elite plays slower than you do. The eDPI calculator shows exactly what share of pros has a lower eDPI than yours.

What spoils a converted sensitivity

Mouse acceleration. In Windows pointer options, check that "Enhance pointer precision" is off and pointer speed sits at 6 of 11. In games, turn on raw input when it is offered. With acceleration on, your cm/360 changes with how fast you move, and no converter can fix that.

Mismatched DPI. The most common slip is entering the DPI from one game and forgetting that the mouse behaves differently in the other because of a profile in its software. Check which DPI is actually active while you play.

Field of view. Valorant shows a different picture than CS2, and weapon models and movement differ too. A converted sensitivity gives the same hand distance, but the image moves across the screen at another speed. Give yourself a few sessions before adjusting, then change the sensitivity by about 5% at a time.

Scopes and ADS. The converter handles normal sensitivity. In CS2 scopes multiply the turn by zoom_sensitivity_ratio_mouse times the scope FOV divided by 90, and the ratio that gives 1:1 at the centre of the screen is 0.818933 for the first AWP zoom. You can work out every value for the AWP, SSG 08 and AUG in the CS2 scope sensitivity calculator. Other games have no published formulas, so set ADS there by hand.

What is missing and why

The converter covers seven games, because only for those is the yaw confirmed by at least three independent sources or by the game itself. We left out PUBG, Marvel Rivals and Deadlock. Three different values circulate for PUBG, and some sources say its slider is not linear. Marvel Rivals has four values in circulation whose extremes differ by 25%. For Deadlock one source gives twice the CS2 yaw while another gives the same. Picking one blindly would hand some players a sensitivity off by a quarter or by half, so we are waiting for an in-game measurement.

On 16 October 2026 we checked the arithmetic against the three largest public converters: for all seven games their results match ours down to rounding. The table of yaw values and how each was confirmed sits at the bottom of the converter page, and if you spot a mismatch, tell us through the contact form.