eDPI Differences Between Popular FPS Games Explained

Introduction

You finally found a CS2 sensitivity that feels right. Then you boot up Valorant for the first time, copy your CS2 eDPI into Valorant's settings menu, and the cursor either flies across the screen or feels glued to the desk. What happened?

The answer is yaw — a hidden game-specific multiplier that converts mouse counts into in-world rotation. Every FPS uses a different yaw, which is why the same eDPI produces very different feel across titles. Once you understand yaw and how it interacts with eDPI, switching between games becomes a clean conversion calculation instead of a frustrating guess-and-check loop.

This guide explains the math, gives you exact conversion formulas for the most popular FPS games, and shows how to maintain consistent muscle memory across titles. If you want to skip straight to the math, our eDPI Calculator computes cm/360° for each game using their actual yaw values.

Why Sensitivity Scales Differ

When you move your mouse one inch at 800 DPI, your computer reports 800 mouse counts to the game engine. The engine then needs to decide how to translate those counts into camera rotation. That conversion is the yaw multiplier — a constant that says "this many counts equals this many in-game degrees of horizontal turn."

Each game studio picked a yaw value somewhat arbitrarily during development. They were not coordinating with each other, and they did not always pick values that produce identical feel at the same eDPI. Here are the actual yaw values used by the most popular FPS games today:

Notice that CS2 and Apex share the same yaw (0.022), which is why CS2 and Apex sensitivities feel similar. OW2 and Warzone also share a yaw (0.0066), which is why their sensitivity values look so different from CS2 even when they produce comparable cm/360° at higher eDPI.

The cm/360° Standard

Because yaw varies across games, eDPI is not directly comparable between titles — only within the same game. The metric that *is* comparable across all games is cm/360°: the physical mouse distance required to rotate your camera a full 360 degrees in-world.

The formula is:

cm/360 = (2.54 × 360) / (DPI × Sensitivity × Yaw)

This simplifies to:

cm/360 = 914.4 / (eDPI × Yaw)

Two players with the same cm/360° experience the same physical motion for a full rotation, regardless of game. That makes cm/360° the gold standard when migrating between titles.

Some sample numbers using common pro setups:

Despite drastically different eDPI values, ZywOo, TenZ, and ImperialHal all hover in the 40–52 cm/360° range — close enough that their physical motion patterns are similar.

CS2 ↔ Valorant Conversion

This is by far the most common conversion request because so many players move between the two tactical shooters.

To convert CS2 sensitivity to Valorant at the same physical feel:

Valorant Sensitivity = (CS2 Sens × 0.022) / 0.07
                     = CS2 Sens × 0.3142857

So a CS2 sensitivity of 1.5 becomes a Valorant sensitivity of about 0.471.

To convert Valorant sensitivity to CS2:

CS2 Sensitivity = (Valorant Sens × 0.07) / 0.022
                = Valorant Sens × 3.18

A Valorant sensitivity of 0.4 becomes a CS2 sensitivity of about 1.273.

If you would rather not do the math, our eDPI Calculator shows the exact cm/360° for any DPI/sensitivity combination — match your cm/360° across games and you have a perfect conversion.

Apex ↔ CS2 Conversion

Because Apex and CS2 share the same yaw value (0.022), the conversion is trivial:

Apex Sensitivity = CS2 Sensitivity

That is the only direct one-to-one match between major FPS games. If you go from CS2 1.5 to Apex 1.5, your cm/360° is identical. The difference is only in feel — Apex involves more movement and tracking than CS2, so a sensitivity that works in one might not feel right in the other even though the physical motion is identical.

Overwatch 2 and Warzone

OW2 and Warzone use the same yaw (0.0066), making them the high-sensitivity outliers among popular FPS games. Their sensitivity values look enormous (4.0, 6.0, 8.0) but produce reasonable cm/360° because the yaw is so small.

Converting CS2 to OW2 or Warzone:

OW2/Warzone Sens = (CS2 Sens × 0.022) / 0.0066
                 = CS2 Sens × 3.333

A CS2 sensitivity of 1.5 becomes about 5.0 in Overwatch 2 or Warzone.

Converting OW2 to Valorant:

Valorant Sens = (OW2 Sens × 0.0066) / 0.07
              = OW2 Sens × 0.0943

An OW2 sensitivity of 6.0 becomes about 0.566 in Valorant.

Fortnite Is Special

Fortnite uses a yaw of 0.5555 — far higher than any other major FPS. That is why Fortnite sensitivity values look tiny (0.05, 0.10, 0.12) while still producing normal cm/360°.

Converting CS2 to Fortnite:

Fortnite Sens = (CS2 Sens × 0.022) / 0.5555
              = CS2 Sens × 0.0396

A CS2 sensitivity of 1.5 becomes about 0.0594 in Fortnite.

If your Fortnite sensitivity field rejects very small decimals, you may need to round up slightly and accept a tiny conversion error.

Maintaining Muscle Memory Across Games

If you regularly play multiple FPS games, the goal is identical cm/360° across all of them. That keeps the physical hand motion consistent so muscle memory transfers cleanly.

A simple workflow:

1. Pick your anchor game — the title where you have the most hours and best aim. For most players this is CS2 or Valorant.
2. Calculate your cm/360° in the anchor game using our eDPI Calculator.
3. For every other game you play, work backwards from that target cm/360° to find the in-game sensitivity that matches.
4. Lock those settings and resist the urge to "tweak per game" until you have at least 50 hours in each.

Some pros run slightly different cm/360° per game by choice — for example, a tracking-heavy player might run 35 cm/360° in Apex but 45 cm/360° in CS2. That is fine if it is intentional and committed. The mistake is running different sensitivities accidentally because the conversion was never done properly.

Why Some Pros Run Different eDPI Per Game

Even pros with identical cm/360° anchors choose to run game-specific tweaks for two reasons:

• TTK and target size differences. Apex enemies are larger and farther on average than CS2 enemies. A faster cm/360° helps with the constant tracking that defines Apex, while CS2's one-tap precision rewards a slower setup.
• Engine smoothing. Some games apply subtle mouse smoothing or input curves at certain sensitivities. Pros sometimes prefer a slightly different sensitivity in those games to avoid the affected zones.

For 95% of players these effects are invisible compared to the benefit of consistent cm/360°. Stick with one cm/360° across all games unless you have specific data showing a per-game adjustment helps.

Frequently Asked Questions

Why does my CS2 eDPI feel faster in Valorant?

Valorant's higher yaw (0.07 vs CS2's 0.022) means the same eDPI rotates the camera more per mouse count. Use cm/360° to compare instead, or use our eDPI Calculator to convert.

Are the yaw values the same on console?

Console games handle controller input separately and do not expose yaw values directly. This guide is specifically for mouse-and-keyboard PC players. Console sensitivity comparisons require different math.

Can I match my pro idol's settings across multiple games?

Sometimes. If your pro plays the same games you do, copy their cm/360° (calculate it from their published DPI/sens). If they play a different game, convert their cm/360° to your game using the formulas above.

Does field of view (FOV) affect eDPI conversion?

Indirectly. Higher FOV makes the same cm/360° feel slightly slower because targets are smaller on screen. Most pros run their game's max FOV and the conversion math is unaffected. If you change FOV, your perceived sensitivity will shift even with identical cm/360°.

What is the easiest way to convert sensitivities between games?

The easiest way is to match cm/360° across games using our eDPI Calculator. Calculate your cm/360° in your anchor game, then plug in different DPI/sensitivity combinations for the second game until the cm/360° matches.

Conclusion

The reason "the same" eDPI feels different across FPS games is simple math: yaw values are not standardized. Once you accept that and switch your anchor metric from eDPI to cm/360°, cross-game migration becomes a clean calculation instead of a multi-week adjustment period.

Use our eDPI Calculator to compute cm/360° for any of the six major FPS games, and pair this guide with our perfect eDPI guide for the full optimization picture.