Skip to main content
Home / Blog / Why Converters Disagree
Guides Published: November 18, 2026 • 9 min read

Why Sensitivity Converters Give Different Answers

You put the same settings into two converters and get two different numbers. Usually neither is broken: they are making different assumptions. Here is what those assumptions are, which ones matter, and how to check any conversion yourself in five minutes.

Yaw: The Number Every Converter Is Built On

Your mouse doesn't send the game an angle. It sends counts: at 800 DPI, one inch of movement produces 800 of them. Each game then decides how far to turn the camera per count. That figure, at in-game sensitivity 1, is called yaw, and it is different in almost every game.

That is why "0.4 sensitivity" means nothing on its own. In Valorant, 0.4 at 800 DPI turns 0.4 × 0.07 = 0.028° per count. In CS2, the same 0.4 turns 0.4 × 0.022 = 0.0088° per count, less than a third as far.

GameEngineYaw (degrees per count at sens 1)
ValorantCustom (Riot)0.07°
CS2Source 20.022°
Apex LegendsSource (modified)0.022°
Overwatch 2Custom (Blizzard)0.0066°
Call of DutyIW engine, Legacy sensitivity0.0066°
FortniteUnreal Engine0.5555° at 100%

Once you know two games' yaw values, conversion is one division:

The Conversion

New sens = Old sens × (Old yaw ÷ New yaw)

Changing DPI too? Multiply by Old DPI ÷ New DPI as well.

Worked example: Valorant to CS2

  • Valorant: 0.4 sensitivity at 800 DPI
  • Ratio: 0.07 ÷ 0.022 = 3.18
  • CS2 = 0.4 × 3.18 = 1.27 at 800 DPI

Both settings take 40.8 cm of mouse movement for a full 360° turn. Apex Legends uses the same yaw as CS2, so the Apex answer is also 1.27. Overwatch 2 and Call of Duty share 0.0066°, so a sensitivity copied straight between those two needs no conversion at all.

Yaw Values Are Measured, Not Published

Developers almost never document their yaw. The values every converter uses were worked out by the community: send a known number of counts, measure how far the camera turns, divide. Valve's 0.022 is visible in the game's own m_yaw console variable. Most others are measurements.

For most popular games the measurements agree. Fortnite is the main exception: published values range from about 0.5515° to 0.5715° per count at 100%. Converting Valorant 0.4 at 800 DPI gives:

  • Yaw 0.5515 → 5.08%
  • Yaw 0.5555 → 5.04% (what our calculators use)
  • Yaw 0.5715 → 4.90%

So two honest converters can disagree by about 3.5% for Fortnite. In practice that is the difference between a 39.7 cm and a 41.1 cm full turn. That's noticeable if you measure it, and small enough that most players won't feel it. If you want certainty, measure it (see the last section).

Mixed-Up Units: The Bug That Gives Nonsense Results

A small disagreement comes from measurement. A huge one usually comes from a bug, and the most common bug is mixing units in the yaw table. Some converters store yaw in degrees (0.07 for Valorant). Others store a ratio relative to a reference game (CS2 = 1.0, Valorant = 3.18). Both work, as long as every game in the table uses the same system.

Mix them, with Valorant stored as 0.07° and CS2 stored as 1.0, and Valorant 0.5 converts to a CS2 sensitivity of 0.035 instead of the correct 1.59. That's a result 45 times too slow.

We found this in our own tools

In November 2026 we found this exact mistake in several of our own calculators, along with cm/360 formulas that left yaw out entirely. We fixed them by moving every tool onto one shared table of yaw values, so the converter, the cm/360 calculator and the per-game eDPI pages can no longer disagree with each other. Each tool now shows the formula and values it uses.

A quick sanity check for any converter: convert Valorant 1.0 to CS2. The answer should be 3.18. If it isn't, don't trust the tool's other results either.

360° Distance vs Monitor Distance Matching

Even with identical yaw values, converters can choose to match different things.

360° distance

A full turn takes exactly the same mouse movement in both games. This is the default in most converters, including ours, and it's the only method that uses yaw alone.

Monitor distance

Flicking to a point at a set place on your screen takes the same movement in both games. This depends on each game's field of view, so converters that use it also ask for your FOV.

When two games have the same field of view, both methods give the same answer. When they don't, they can't both be matched at once. A wider FOV squeezes more of the world onto your screen, so a target the same distance from your crosshair on screen sits at a bigger angle. That is why a perfectly converted sensitivity can still feel "off" for small flicks: the full turn matches, but the screen doesn't.

Neither method is wrong. 360° distance is the better choice if you rely on muscle memory for big turns and checking corners. Monitor distance suits players who care most about flicking to targets already on screen. Just make sure you compare converters using the same method.

Games That Can't Be Converted With a Simple Ratio

The yaw formula assumes doubling your sensitivity doubles your turn speed. For some popular games that isn't true, or there are extra settings in play that a single number can't capture. A converter that offers these games through the same simple ratio is guessing.

PUBG: Battlegrounds

The sensitivity slider isn't linear. Moving it from 40 to 50 doesn't change your speed by the same amount as moving it from 50 to 60, so a straight ratio gives a different error at every point on the slider.

Rainbow Six Siege

On top of the visible sensitivity, Siege has a separate mouse sensitivity multiplier in its settings file, and each optic has its own aim sensitivity. The same displayed number can mean different speeds on two players' setups.

Battlefield

Uniform Soldier Aiming and its coefficient setting change how sensitivity scales with zoom, so hipfire and aimed sensitivity interact in ways a single ratio can't describe.

Call of Duty: Black Ops Cold War

Most Call of Duty titles since Modern Warfare (2019) share the 0.0066° yaw with the Legacy sensitivity type. Black Ops Cold War uses a different scale, so a "Call of Duty" setting in a converter may not apply to it.

We have taken these games out of our converter rather than show a number we can't stand behind. If you play one of them, measure your cm/360 directly using the method below.

Things No Converter Can See

Your mouse's real DPI

Sensors don't always deliver exactly the DPI printed on the box. If an "800 DPI" mouse actually reports 824 counts per inch, Valorant 0.4 gives a 39.6 cm turn instead of 40.8 cm. If it reports 776, the turn is 42.1 cm. The conversion stays correct between games on the same mouse. But if you copy a pro's settings, or switch mice, the real distance can change.

ADS and scoped sensitivity

Converters match hipfire, the sensitivity you use when not aiming down sights. Every game handles aiming down sights and scopes with its own multipliers, so set those separately after converting.

Acceleration and smoothing

Most modern shooters read raw mouse input, so Windows pointer speed doesn't matter. If a game doesn't use raw input, or your mouse software adds acceleration, your speed depends on how fast you move. No formula can convert that. Turn acceleration off in your mouse software, and turn off Windows' "Enhance pointer precision" for any game without raw input.

How to Check a Conversion Yourself

The final test of any conversion is a ruler. It takes about five minutes and settles the question for good.

1

Set up a reference

Lay a ruler or a strip of tape with centimetre marks along the bottom of your mousepad. Line the edge of your mouse up with zero.

2

Pick a fixed point in game

In a practice range or offline mode, put your crosshair exactly on a sharp edge or corner that won't move.

3

Turn slowly through 360°

Move the mouse slowly and steadily in one direction until the crosshair comes back to the same point. Slow movement avoids any acceleration. Read the distance on the ruler.

4

Repeat in the other game and compare

Do the same with your converted setting. If the two distances match within about a centimetre, the conversion is right. Compare your measurement with the cm/360 calculator too. A big gap points to a DPI or acceleration issue rather than the formula.

Related Reading

For step-by-step conversions between specific games, see How to Convert Sensitivity Between Games. For what the numbers mean within one game, see What is eDPI?

Frequently Asked Questions

What is yaw in mouse sensitivity?

Yaw is the number of degrees a game turns your camera for each count your mouse reports, at in-game sensitivity 1. Valorant uses 0.07°, CS2 and Apex Legends use 0.022°, and Overwatch 2 and modern Call of Duty use 0.0066°. Dividing one game's yaw by another's gives the conversion ratio between them.

Why does my converted sensitivity feel different even though the numbers match?

A 360° distance conversion makes a full turn take the same mouse movement. But games with different field of view put targets at different places on screen, so small flicks feel different. Scoped and ADS sensitivity are also set separately in every game, and the conversion only covers hipfire.

What is the Valorant to CS2 sensitivity ratio?

Multiply your Valorant sensitivity by 3.18 to get CS2 at the same DPI, because 0.07 ÷ 0.022 = 3.18. Valorant 0.4 at 800 DPI becomes CS2 1.27 at 800 DPI, and both take 40.8 cm of mouse movement for a full turn.

How can I check if a sensitivity conversion is correct?

Measure your cm/360 in both games. Put a ruler next to your mouse, line your crosshair up with a fixed point, move the mouse slowly until you turn exactly 360° back to that point, and read the distance. If both games give the same distance within about a centimetre, the conversion is correct.

Convert your sensitivity

Our converter shows the yaw values it uses, so you can check every result by hand.

Open the Sensitivity Converter