CS2 Sensitivity Converter

Most players search for a CS2 sensitivity converter when they are changing resolution, copying a pro setup, or moving from another game. Those are three very different situations, and only one of them usually needs real conversion math.

The biggest mistake is converting sensitivity when nothing actually changed.

The First Rule: Resolution Does Not Need a New Sensitivity

Inside CS2, changing resolution or aspect ratio does not automatically require a new mouse sensitivity.

That surprises a lot of players, but the turning speed of your mouse is not tied to whether you play:

• 16:9
• 4:3 stretched
• 4:3 black bars

The game may feel different visually, but the base sensitivity does not need a conversion just because the resolution changed.

If you aim worse after changing resolution, it is usually because the image looks different, not because the sensitivity became mathematically wrong.

See Best CS2 Resolution.

What Actually Matters: eDPI

The easiest shared language for sensitivity is eDPI:

eDPI = DPI × in-game sensitivity

Examples:

These setups feel extremely similar in raw turn speed even though the DPI and sensitivity numbers look different.

Related: CS2 DPI Guide.

Converting Between Games

Sensitivity conversion matters more when moving between different games because different engines use different base look values.

One common example is VALORANT:

CS2 sensitivity ≈ VALORANT sensitivity × 3.18

And the reverse:

VALORANT sensitivity ≈ CS2 sensitivity ÷ 3.18

That is useful as a starting point, not a promise that both games will instantly feel identical. FOV, movement, model scale, and game pace still affect how aiming feels.

Another Useful Metric: cm/360

Some players prefer centimeters per 360 because it describes the physical mouse distance needed for one full turn.

That is useful because it answers a practical question:

How far do I move my mouse to spin around once?

If you want cross-game consistency, matching cm/360 is often more meaningful than copying a random pro's raw sensitivity number.

When You Should Not Convert at All

Do not convert sensitivity just because:

• a streamer uses another number
• you switched from black bars to stretched
• your aim felt bad for one session
• your new mouse has a different shape

Those are all real feel changes, but they do not automatically mean the math is wrong.

Best Way to Find Your Real Baseline

Use this order:

1. Pick a stable DPI, usually 400, 800, or 1600.
2. Pick a reasonable CS2 sensitivity.
3. Leave it alone long enough to test real habits.
4. Adjust only if your turning range is clearly too slow or too wild.

Most players improve more from consistency than from endless conversion experiments.

See Crosshair Placement Explained and How to Improve at CS2.

Takeaway

The most important CS2 sensitivity conversion rule is that resolutions inside CS2 do not need separate conversion. Use eDPI to compare setups, use cross-game conversion only when changing games, and stop "recalculating" your aim every time the screen looks a little different.