EN
TestYourSetup / Aim and sensitivity / Sens converter

Sens converter

Pick the game you play now, type your sensitivity and DPI, and get the sensitivity that turns exactly as far in the other game. You also get your cm/360 and eDPI, and every number shows where it comes from.

From
To
Your Counter-Strike 2 sensitivity Calculated1.1136CS2 = Valorant x 3.182
cm/36046.7same in both games
in/36018.4inches per full turn
eDPI before280Valorant, DPI x sens
eDPI after891CS2, DPI x sens

Train at this sens

Valorant

Horizontal FOV is fixed at 103 degrees. Scoped sensitivity multiplier is a separate setting and is not converted here.

Turn rate: 0.07 degrees per count at 1. Source: 0.07 degrees per count is the widely reproduced 360 measurement; it gives the well-known ratio CS2 = Valorant x 3.18 (0.07 / 0.022).

Counter-Strike 2

Horizontal FOV is fixed at about 106 degrees at 16:9 (90 at 4:3). Scoped weapons use zoom_sensitivity_ratio, which is not converted here.

Turn rate: 0.022 degrees per count at 1. Source: Source engine convar m_yaw, default 0.022 degrees per count, multiplied by the sensitivity convar (listed in the public CS2 convar dump).

Hip fire at the same cm/360 (360 degree distance). Scoped and ADS sensitivity are separate settings in most games and are not converted here.

No permissions needed. Everything runs in your browser and nothing is uploaded.

How the conversion works

A game turns your view by a set angle for every count your mouse sends. CS2 turns 0.022 degrees per count at sensitivity 1, Valorant 0.07, Overwatch 2 0.0066. Multiply by your sensitivity and you have your turn per count; multiply by your DPI and you have your turn per inch of mouse movement. The converter keeps that number the same, so a 30 cm swipe that spins you around once in one game spins you around once in the other.

That distance is your cm/360, and it is the one number that means the same thing in every game. eDPI (DPI x sens) is handy inside one game, but an eDPI of 280 in Valorant and 280 in CS2 are very different speeds. For the reverse question, which sensitivity gives a cm/360 you choose, use the cm/360 calculator.

Most games scale in a straight line, so a pair has one fixed multiplier: CS2 = Valorant x 3.18, Apex = CS2 x 1, Overwatch 2 = CS2 x 3.33. PUBG is the exception: its slider is a curve, so there is no single multiplier and the converter does the maths for you.

Popular conversions

These pages explain the quirks of a pair (field of view, scopes, why it feels different) with a table of common values:

Every other pair works in the converter above. Use the Swap button to go the other way.

After you convert

  1. Set the new sensitivity in game and play a few warm-up rounds before judging it. The first minutes always feel strange.
  2. If the game's slider only takes whole numbers (Siege, Destiny 2, PUBG), round to the nearest step, or change your DPI in the New DPI field to land on a step.
  3. Match ADS and scope settings separately in the game. They are not part of this conversion.
  4. Practise the new feel in the aim trainer: it can turn at your converted sens, so the hand movement is the same. The Train at this sens button above fills it in.

Not sure what DPI your mouse really sends? Sensors are often a few percent off the number on the box. The mouse DPI test measures it with a bank card, and the result goes straight into these maths.

Sources for every game

The turn rates below are the whole data set behind this page, the aim trainer and the cm/360 calculator. A game is marked approximate when no developer figure exists and the public measurements are few or disagree. Last checked 2026-10-15.

GameSettingDegrees per countStatusSource
Counter-Strike 2Sensitivity0.022 x sensSolidEngine config. Source engine convar m_yaw, default 0.022 degrees per count, multiplied by the sensitivity convar (listed in the public CS2 convar dump). Link
ValorantSensitivity0.07 x sensSolidCommunity 360 measurement. 0.07 degrees per count is the widely reproduced 360 measurement; it gives the well-known ratio CS2 = Valorant x 3.18 (0.07 / 0.022). Link
Apex LegendsMouse sensitivity0.022 x sensSolidEngine config. Apex runs on a modified Source engine with the same m_yaw of 0.022; public converters agree that CS2 and Apex sensitivities are 1:1 at the same DPI. Link
Overwatch 2Sensitivity0.0066 x sensSolidCommunity 360 measurement. 0.0066 degrees per count per sensitivity point; listed identically by independent open-source converters, giving CS2 = Overwatch / 3.33. Link
FortniteX-axis sensitivity (%)0.005555 x sensSolidCommunity 360 measurement. About 0.005555 degrees per count per percent (0.5555 at 100%), the value used by independent open-source converters. Link
Marvel RivalsMouse sensitivity0.0175 x sensApproximatePublished community ratio. A guide states Marvel Rivals = Valorant x 4 at the same DPI, which means 0.0175 degrees per count. Only one public source, so it is marked approximate. Link
Rainbow Six SiegeMouse sensitivity (horizontal)0.00572957795 x sensSolidConfig file. GameSettings.ini: the slider value is multiplied by MouseSensitivityMultiplierUnit (default 0.02); public converters use 0.00572957795 degrees per count per slider point at the default unit. Link
Call of Duty (Black Ops 7, Warzone)Mouse sensitivity0.0066 x sensSolidCommunity 360 measurement. 0.0066 degrees per count, the same as Overwatch; listed identically by independent open-source converters. Link
PUBG: BattlegroundsGeneral sensitivity (slider)0.042 x 10^((sens - 50) / 50)ApproximateCommunity measurement. Curve shape (double every 15 steps, also stated as 400 DPI at 50 = 800 DPI at 35 = 1600 DPI at 20) from Korean community converters; the anchor of 0.042 degrees per count at 50 comes from a single reported match, so it is approximate. Measure your own 360 to confirm. Link
RustMouse sensitivity (input.sensitivity)0.1125 x sensApproximateCommunity 360 measurement. About 0.1125 degrees per count (one source lists 0.11247); sources disagree on the FOV dependence. Link
DeadlockMouse sensitivity0.044 x sensApproximateCommunity measurement. Two public converters give 0.044 degrees per count (twice CS2, so Deadlock = CS2 / 2); another lists 0.022. Marked approximate until confirmed with a 360 test. Link
Destiny 2Look sensitivity0.0066 x sensApproximateCommunity measurement. 0.0066 degrees per count per step in public converters; no developer figure and no published measurement method, so approximate. Link
The FinalsMouse sensitivity0.001 x sensApproximateCommunity measurement. 0.001 degrees per count per slider point, as listed by public converters marked community measured. Link
Halo InfiniteMouse sensitivity (horizontal)0.022 x sensApproximateCommunity measurement. 0.022 degrees per count in two public converter tables, with no developer figure, so approximate. Link

Battlefield 6 is not listed yet: we could not find a turn rate with enough public agreement. Game names are used only to say which game a number is for; TestYourSetup is not affiliated with any of these publishers.

Questions

How does a sens converter work?

Every game turns the camera by a fixed angle for each count your mouse sends, multiplied by your sensitivity. The converter works out how many degrees per count your current game gives, then finds the sensitivity that gives the same degrees per count in the other game. Your mouse then travels the same distance for a full turn (the same cm/360) in both games.

Why does my converted sens still feel different?

The turn distance matches, but the view does not. Games use different fields of view, so the world seems to slide past faster or slower at the same cm/360, and targets look bigger or smaller. Frame rate, mouse acceleration and third-person cameras change the feel too. Give it a few sessions before you tweak it, and change it in small steps.

Does this convert scoped or ADS sensitivity?

No. This tool converts hip fire, the turn speed when you are not aiming down sights or scoped. Most games set ADS and scope sensitivity with a separate multiplier, and games handle zoom in different ways, so match hip fire first and then tune ADS in the game.

What does "approximate" mean next to a game?

For those games the developer has not published the turn rate and the public measurements are few or disagree, so the result may be off by a few percent. Check it with a 360 test: mark a spot on your mouse pad, turn a full circle in game, and compare the distance with the cm/360 shown here.

Should I change my DPI or my in-game sens?

Either works, as long as DPI x sens stays the same turn distance. Changing DPI also changes your desktop cursor and every game at once. If a converted value is outside a game's range or lands between two whole-number steps, put your new DPI in the New DPI field and the converter adjusts the sens to match.

Where do the numbers come from?

From a hand-maintained table that lists, for every game, the turn rate, where it comes from (an engine setting, a config file or a public community measurement) and whether it is approximate. The table is on this page under Sources, and it was last checked on 2026-10-15.

Is my sensitivity saved or uploaded?

Nothing is uploaded. The converter runs in your browser. The address bar keeps your last conversion in the part after the #, so you can bookmark or share it, but that part is never sent to a server.

More tests