Sensitivity

How to Convert Sensitivity Between Valorant, CS2, and Apex

By the AnalyzeMouseDPI team · Updated June 2026 · 7 min read

Switching games shouldn't mean relearning your aim. The trick is to keep your real-world muscle memory identical — and that means thinking in cm/360, not raw sensitivity numbers.

Why Raw Sens Numbers Don't Transfer

Drop your Valorant sensitivity straight into CS2 and your aim will feel completely wrong. That's not a bug — each game applies its own internal multiplier (often called the yaw, or turn rate per unit) to the number you type in. A sensitivity of 1.0 turns your view a different amount in each title.

Roughly speaking, the same numeric value spins you furthest in CS2, less in Apex Legends, and least in Valorant. So copying "0.5" or "1.6" between games gives you three different turn speeds — and three different feels. The number is just a label; what matters is how much the world rotates when you move your hand.

Key idea: sensitivity values are game-specific. To keep your aim consistent, match the physical motion, not the on-screen number.

Why cm/360 Is the Universal Unit

The one measurement that means the same thing in every game is cm/360: the number of centimetres you slide the mouse to turn a complete 360-degree circle. It folds your DPI and in-game sensitivity into a single real-world distance.

Because cm/360 is grounded in actual hand movement, it ignores each game's internal multiplier entirely. If your cm/360 is the same in Valorant, CS2 and Apex, the same flick covers the same angle in all three — your muscle memory carries over untouched. A lower cm/360 means a faster, twitchier setup; a higher one means slower, more deliberate aim.

Some players prefer to think in eDPI instead, which is simply your DPI multiplied by your in-game sensitivity. eDPI is a great shorthand for comparing two players within the same game — it strips out the fact that one might run 400 DPI and another 1600. But eDPI still can't be copied across titles, because it doesn't account for each game's yaw. cm/360 is the more portable measure; eDPI is the more convenient one for same-game comparisons. If that distinction is new to you, our explainer on what eDPI is breaks it down properly.

The Manual Method, Step by Step

  1. Work out your cm/360 in game A. Keep your DPI fixed, then find the sensitivity that gives the turn distance you like.
  2. Note that target distance — say a full 360 takes about 30 cm of mouse movement.
  3. Open game B and adjust its sensitivity until a full 360 also takes 30 cm at the same DPI.
  4. That new value is your converted sensitivity. Different number, identical feel.

A worked example in words: imagine you main Valorant at 800 DPI and 0.4 sensitivity, which works out to roughly 40 cm per 360. You want to play CS2 with that exact feel. Because CS2 turns faster for the same number, you'd need a noticeably lower CS2 sensitivity to stretch that turn back out to 40 cm. Jump to Apex and you'd land on yet another number — but all three share the same 40 cm/360, so every flick lands the same. Measuring this by hand with a mouse pad and ruler is doable, just slow and fiddly.

Which cm/360 Should You Aim For?

There's no single correct figure, but there are useful bands. Tactical shooters like Valorant and CS2 reward a lower sensitivity — most competitive players sit somewhere between roughly 30 and 50 cm/360, because slow, deliberate movement makes precise micro-adjustments and one-taps far more repeatable. Faster arena and battle-royale games such as Apex often pull players toward the quicker end, 25–40 cm/360, so you can whip around to track opponents who move erratically.

If you're unsure where to start, err on the slower side. A common beginner mistake is running a high sensitivity because it feels responsive on the desktop, then wondering why long-range aim is shaky — small hand tremors get amplified into big crosshair wobbles. Dialling the sensitivity down forces cleaner arm movement and usually pays off within a week or two of adjustment. Whatever you pick, the golden rule is to lock it in and keep it identical everywhere, which is exactly what converting protects. For game-specific starting points, see our best settings for Valorant and best settings for CS2 guides.

Convert Instantly With the Tool

Rather than crawl around your desk with a tape measure, let the math happen for you. Our Sensitivity Calculator stores each game's yaw, so you enter your DPI and source sensitivity, pick the target game, and it returns the matching value — and your cm/360 — in a click. Convert Valorant to CS2, CS2 to Apex, or any pair, with your aim preserved exactly. One tip: before you trust the output, confirm your mouse's real DPI with the DPI Analyser, because a mouse that under- or over-reports its DPI will quietly shift every converted number off target.

Ready to keep your aim across every game? Open the Sensitivity Calculator → Enter your DPI and sens, pick a target game, and copy the result straight in — then verify your real DPI so the numbers hold up.

Frequently Asked Questions

Why is the same sensitivity number different in each game?
Each game applies its own internal multiplier (yaw) to your setting, so the same number turns your view a different amount in Valorant, CS2 and Apex. The raw value can't simply be copied across.
What is cm/360 and why does it matter?
It's the distance you move the mouse to spin a full 360 degrees in game. Because it measures real hand movement, it's identical across every title — the universal unit for matching sensitivity.
How do I convert sensitivity between games quickly?
Use the Sensitivity Calculator: enter your DPI and source sensitivity, pick the target game, and it outputs the matching value so your cm/360 stays identical.
Should I change my DPI or my in-game sensitivity when converting?
Keep your DPI fixed and change the in-game sensitivity. DPI is a hardware setting shared by your whole system, so altering it affects your desktop and every other game; adjusting the in-game value keeps the change contained to that title.

← Back to all guides   Convert my sensitivity