CS2 to Valorant Sensitivity Converter — Exact Math, Conversion Table & cm/360° Method

Introduction

If you have moved from CS2 (or CSGO) to Valorant — or you switch between the two — you have probably done what every player does: typed your CS2 sensitivity straight into Valorant's settings menu and watched the cursor fly across the screen the moment you entered a match. That feeling of "this is way too fast" is not bad luck. It is mathematically guaranteed by how each game scales mouse input internally.

This guide explains exactly why CS2 and Valorant cannot share a sensitivity value, gives you the precise conversion formula in both directions, and shows you the cm/360° method that pro players use to keep their physical motion identical across both games. By the end you will be able to convert any CS2 setting to a Valorant equivalent (and back) in seconds.

Skip ahead and our eDPI Calculator computes cm/360° for both games using their real yaw values — match the number and your conversion is done.

Why "Same eDPI" Does Not Mean "Same Feel"

eDPI is the most popular sensitivity comparison tool because it produces a single number: DPI × in-game sensitivity. The problem is that eDPI is only comparable within the same game. Across games, the in-game sensitivity scale changes, which means the same eDPI produces different physical motion in different titles.

The technical reason is the yaw multiplier — the internal constant each game uses to convert mouse counts into in-game camera rotation. Yaw is what the engine actually cares about. eDPI is just our convenient shorthand.

Valorant's yaw is roughly 3.18× higher than CS2's. That means at the same eDPI, your camera rotates 3.18× farther in Valorant per inch of mouse movement. This is why your CS2 eDPI of 800 feels like a CS2 eDPI of ~2,500 the first time you load Valorant.

For a deeper look at how yaw distorts cross-game comparisons (Apex, OW2, Fortnite, Warzone too), see our full guide on eDPI differences between popular FPS games.

The Actual CS2 to Valorant Conversion Formula

To convert a CS2 sensitivity into a Valorant sensitivity that produces the same physical mouse motion, the formula is:

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

Going the other direction:

CS2 Sens = Valorant Sens × (0.07 / 0.022)
        = Valorant Sens × 3.1818

Both formulas assume the same DPI in both games (almost always 800). If your DPI changes between games, multiply or divide by the DPI ratio as well — but the cleanest workflow is to keep DPI identical and only adjust in-game sensitivity.

CS2 to Valorant Conversion Table

Here are the most common CS2 sensitivities converted to Valorant at the same physical motion (assuming 800 DPI in both):

So if you ran ZywOo's CS2 setup (400 DPI × 2.0 sens = 800 eDPI), the matched-motion Valorant setting at 800 DPI is 0.629 sensitivity = 504 eDPI. Despite the eDPI numbers looking different, both produce exactly ~26 cm/360° — identical physical motion.

The cm/360° Method — What Pros Actually Use

eDPI conversion alone is not the gold standard for cross-game switching. The metric that *is* comparable across all games is cm/360° — the physical mouse distance required to complete a full 360° rotation in-game. It bakes in DPI, sensitivity, and yaw, producing a single hardware-independent number.

The formula is:

cm/360 = 914.4 / (DPI × Sens × Yaw)

Two players (or two games) with the same cm/360° experience the same physical motion for a full rotation, even if their eDPI, DPI, and in-game sensitivity values differ wildly.

The practical workflow for switching from CS2 to Valorant:

1. Calculate your CS2 cm/360° using the formula above (or our eDPI Calculator — set the game to CS2).
2. Solve for Valorant sensitivity that gives the same cm/360°. The formula becomes:

Valorant Sens = 914.4 / (DPI × Yaw × Target cm/360)

1. Round to three decimals — Valorant accepts that precision.
2. Lock it in and resist the urge to tweak for at least two weeks.

A worked example: ZywOo's CS2 setup gives a cm/360° of about 26.0. Plugging that into the Valorant formula at 800 DPI:

Valorant Sens = 914.4 / (800 × 0.07 × 26.0)
             = 914.4 / 1456
             = 0.628

Which matches the conversion table above. Same physical motion, different sensitivity values, identical muscle memory.

Why eDPI Conversion Alone Is Misleading

A common shortcut online is "just keep the same eDPI when switching games." Do not do this for CS2 → Valorant. If you run 800 eDPI in CS2 (Mid) and copy that as 800 eDPI in Valorant (1.0 sens × 800 DPI), you have created an extreme-high eDPI Valorant setup — roughly 3× the speed of the average Valorant pro. You will overshoot every duel for weeks.

The eDPI shortcut works in one specific case: when the two games share a yaw. CS2 and Apex Legends both use 0.022, so the same CS2 sensitivity copied directly to Apex produces the same physical motion. CS2 and Valorant do not share a yaw, so the shortcut fails badly.

If you only remember one thing from this guide: convert by cm/360°, not by eDPI, whenever you change FPS title.

Special Cases and Edge Considerations

A few details that occasionally trip up players doing the math correctly but still feeling off:

Raw Input Buffer

Valorant has a Raw Input Buffer toggle in the settings menu. It is on by default and should stay on. With it off, Valorant smooths input between polls, which can subtly affect feel at very low sensitivities. Leave it on for clean linear input.

Mouse Acceleration

Both CS2 and Valorant respect Windows mouse acceleration when "Enhance pointer precision" is enabled at the OS level. Every pro disables this — it adds curvature to your motion and makes the conversion math meaningless. Disable it once in Windows Mouse Properties → Pointer Options and forget about it.

Scoped / ADS Sensitivity

Valorant's ADS sensitivity is a multiplier of your hipfire sensitivity, defaulting to 1.0. Most CS2 players who scope or AWP use the zoom_sensitivity_ratio_mouse setting (default 1.0). If both are at 1.0 in their respective games, scoped motion converts cleanly using the same formula. If you have customized either, convert the scoped sensitivities separately.

FOV

Valorant's FOV is fixed at 103. CS2 defaults to roughly 90 FOV. A higher FOV makes the same cm/360° feel marginally slower because targets are smaller on screen. The motion math is unchanged, but expect Valorant to feel "smoother" than the same cm/360° in CS2 simply because more of the world is visible.

Polling Rate

Polling rate (Hz) affects responsiveness, not eDPI. Both games behave correctly at 1000 Hz; very high polling rates (4000 Hz, 8000 Hz) can introduce sensor noise on cheaper mice but do not change conversion math.

Switching Your Anchor Game

If you split time between CS2 and Valorant, do not try to play both with mismatched cm/360° — your hand will never settle. Pick one anchor game (the title where you have the most hours and best aim) and convert the second game's sensitivity to match the anchor's cm/360°.

For most ex-CSGO players moving to Valorant, the anchor game is whichever you currently play more competitively. If you compete in Valorant tournaments, anchor on Valorant and convert your CS2 sensitivity to match. If you stream CS2 ranked and only play Valorant casually, anchor on CS2.

For the full process — including the two-week commitment cycle, aim trainer benchmarking, and how to evaluate whether the new setting is actually working — read our ultimate guide to finding your perfect eDPI. And if you want a deeper look at how pros maintain consistent feel across titles, see our breakdown on how pro players choose their mouse settings.

When Slight Per-Game Drift Is OK

Some pros deliberately run slightly different cm/360° in CS2 and Valorant despite knowing the math. The most common reasons:

• Engagement distance. CS2 maps push longer ranges on average; some pros prefer marginally slower cm/360° in CS2 for precision and faster in Valorant for utility-driven rotates.
• Movement style. Valorant rewards counter-strafing and quick angle peeks; CS2 rewards held angles and pre-aim discipline. A small sensitivity gap (under 10%) can subtly serve these different demands.
• Pad size compromise. If your pad is borderline-small for your CS2 sensitivity, you may run a marginally faster Valorant sensitivity to avoid running out of pad on rotations.

These are exceptions, not defaults. For 95% of players, identical cm/360° in both games is the right call, and any drift should be a conscious adjustment made after weeks of data — not a "feels slightly off, let me tweak" decision.

Frequently Asked Questions

What is the CS2 to Valorant sensitivity conversion formula?

Multiply your CS2 sensitivity by 0.3142857 to get the equivalent Valorant sensitivity at the same DPI. So 1.5 in CS2 becomes roughly 0.471 in Valorant.

How do I convert Valorant sensitivity to CS2?

Multiply your Valorant sensitivity by 3.1818. A Valorant sensitivity of 0.4 becomes about 1.273 in CS2.

Should I keep the same eDPI between CS2 and Valorant?

No. CS2 and Valorant use different yaw values (0.022 vs 0.07), so the same eDPI produces about 3× more rotation in Valorant. Convert by cm/360° instead.

What sensitivity should I use in Valorant if my CS2 sens is 2.0?

At 800 DPI in both games, a CS2 sensitivity of 2.0 converts to approximately 0.629 in Valorant, giving you about 26 cm/360° in both games.

Do TenZ and ZywOo have the same cm/360°?

Close, but not identical. TenZ runs roughly 40 cm/360° in Valorant; ZywOo runs roughly 52 cm/360° in CS2. Both are in the precision-FPS range but ZywOo's is meaningfully slower.

Why does my Valorant cursor feel sluggish even after converting?

Two common causes: (1) Valorant's higher FOV makes the same cm/360° feel slower because targets occupy fewer pixels on screen, and (2) Valorant rewards smaller, more precise micro-adjustments than CS2's hold-angle play. Give it two weeks of focused practice before judging — the conversion is mathematically correct.

Is the CS2 to Valorant conversion the same for CSGO?

Yes. CSGO and CS2 share the same yaw value of 0.022, so any conversion formula that works for CS2 → Valorant works identically for CSGO → Valorant.

Can I use the same DPI for both games?

Yes, and you should. Almost every Valorant and CS2 pro runs 800 DPI in both games. Changing DPI per game just complicates the math and breaks cross-game muscle memory.

Conclusion

CS2 and Valorant cannot share a sensitivity value because their internal yaw multipliers are wildly different — Valorant rotates the camera 3.18× more per mouse count than CS2 does. The correct way to convert is by cm/360°, the physical distance your mouse travels for a full in-game rotation. Match that number across both games and your muscle memory stays intact.

Use our free eDPI Calculator to compute your CS2 cm/360°, then dial in the Valorant in-game sensitivity that hits the same number. Lock it for two weeks, gather data, and only adjust based on real evidence. That is how the pros switch between the two games without ever rebuilding their aim.

For the broader cross-game picture (Apex, OW2, Fortnite, Warzone), read our companion guide on eDPI differences between popular FPS games.