BETREF$

Sens Converter

Convert your mouse sensitivity between CS2, Valorant, Apex Legends, Fortnite, Overwatch 2, Call of Duty, Rainbow Six Siege, Rust and CS:GO. You turn exactly as far for the same mouse movement, and you see your cm/360, inches/360 and eDPI. Changing mouse? Add your new DPI.
Valorant sensitivity
0.3929
cm per 360°
41.6
inches per 360°
16.4
Valorant eDPI
314.3
at 800 DPI

In Valorant: Settings, General, Mouse, Sensitivity: Aim.

CS2 1.25 in every game

All of these turn 41.6 cm for a full 360°.

GameSensitivityeDPIYaw
1.2510000.022
1.2510000.022
0.39293140.07 *
1.2510000.022 *
4.95%39600.005555 *
4.16733330.0066 *
4.16733330.0066 *
4.838400.00572958 *
0.24441960.1125 *

* Measured by players: the publisher doesn't publish the value. eDPI uses each game's own number, so it only compares within one game.

How to use it

  1. Pick the game you play now and the game you are moving to.
  2. Type your current sensitivity (Fortnite: the percentage) and your mouse DPI.
  3. Optional: type a new DPI if you'll use a different one; the sensitivity is scaled to keep the same cm/360.
  4. Read the converted sensitivity, or use the table for every game at once. Copy the link to share the result.

How the conversion works

Every game on this page turns the camera a fixed angle for each count your mouse sends, multiplied by your sensitivity. That angle at sensitivity 1 is the game's yaw. Two settings aim the same when they turn the same angle per count:

new sens = old sens x old yaw x old DPI / (new yaw x new DPI)
cm/360 = 360 / (yaw x sens x DPI) x 2.54

CS2's yaw is the only one a game prints itself: m_yaw 0.022 is in its command list. The other publishers don't publish theirs, so the values below are what players have measured by turning a full circle a known number of mouse counts. They are marked as measured.

A wider field of view can make the same turn look faster on screen. The conversion keeps the distance your mouse travels for a full 360° the same, which is what your muscle memory follows. Zoom and aim-down-sights sensitivity are separate settings in each game, so convert hip-fire first and set those after.

Fortnite, Siege and Overwatch use different scales

Common CS2 sensitivities in other games

At the same DPI. The cm/360 column is for 800 DPI.

CS2ValorantFortniteOW2 / CoDR6Rustcm/360
0.80.2513.2%2.673.10.15664.9
10.3144%3.333.80.19652
1.250.3935%4.174.80.24441.6
1.50.4715.9%55.80.29334.6
20.6297.9%6.677.70.39126
2.50.7869.9%8.339.60.48920.8
30.94311.9%1011.50.58717.3

Yaw values we use

GameYaw (degrees per count)SettingSource
Counter-Strike 20.022Multiplier, 0.0001 to 8Game files. m_yaw 0.022 in CS2's own command list
CS:GO0.022MultiplierGame files. m_yaw 0.022, Valve Developer Community list of CS:GO console variables
Valorant0.07MultiplierMeasured by players. 0.07, measured by players (Riot doesn't publish it)
Apex Legends0.022MultiplierMeasured by players. 0.022, the Source engine value Apex is built on, confirmed by player measurements
Fortnite0.005555 per 1%Percent slider (X and Y)Measured by players. 0.005555 per 1%, measured by players (Epic doesn't publish it)
Overwatch 20.0066Slider, 0 to 100Measured by players. 0.0066, measured by players (Blizzard doesn't publish it)
Call of Duty (MW 2019 and later, Warzone)0.0066SliderMeasured by players. 0.0066, measured by players (Activision doesn't publish it)
Rainbow Six Siege0.00572957795Slider, 1 to 100, times MouseSensitivityMultiplierUnitMeasured by players. 0.00572957795 at the default multiplier 0.02, measured by players (Ubisoft doesn't publish it)
Rust0.1125MultiplierMeasured by players. 0.1125, measured by players (Facepunch doesn't publish it)

Not included yet: Deadlock, because published values disagree (some tables use CS2's 0.022, others twice that) and Valve doesn't list it; and PUBG, whose slider isn't linear and whose turn speed depends on field of view, so one fixed number would give wrong results. We'd rather leave a game out than show a number we can't back up.

What other converters often get wrong

Moving to CS2? See what the best players use on our CS2 pro settings page, compare your eDPI with theirs in the eDPI calculator, and build a full config with the CS2 config generator. New to the game? Open a free CS2 case or compare CS2 skin trading sites.

Sources: CS2 m_yaw from the game's command list (our console commands page); CS:GO m_yaw from the Valve Developer Community; the other games: player measurements, as marked. Checked 16 October 2026.

FAQ

How do I convert my sensitivity between games?
Multiply your sensitivity by your old game's yaw and divide by the new game's yaw, with the same DPI. The yaw is how many degrees the game turns per mouse count at sensitivity 1: 0.022 in CS2, 0.07 in Valorant. Your cm/360 then stays the same, so your aim carries over.
What is my CS2 sens in Valorant?
Divide it by 3.182 (0.07 / 0.022). CS2's default 1.25 becomes 0.393 in Valorant, and a Valorant 0.4 is 1.273 in CS2. Keep the same DPI in both games.
Is Apex sens the same as CS2?
Yes for hip-fire. Apex is built on a Source-based engine and turns 0.022 degrees per count at sensitivity 1, like CS2, so the same number gives the same cm/360. ADS uses its own multipliers in Apex's settings.
How do I convert Fortnite sens to CS2 or Valorant?
Fortnite's sensitivity is a percentage. Multiply it by 0.2525 for CS2 or by 0.0794 for Valorant: 10% in Fortnite is 2.525 in CS2 and 0.794 in Valorant. Going the other way, CS2 2.0 is 7.9% in Fortnite.
What is cm/360?
How far you move the mouse on your desk to turn a full circle in game. It is the one number that means the same in every game, which is why converters keep it fixed. At 800 DPI, CS2 1.25 is 41.6 cm/360.
Does changing DPI change my sensitivity?
Yes. Double the DPI and you turn twice as far for the same movement. To change DPI without changing your aim, enter the new DPI in the converter: it scales the sensitivity so your cm/360 stays the same.

More free tools

All tools →