Free FPS sensitivity tool

Valorant Sensitivity Converter: Convert to CS2

Convert a Valorant sensitivity to a CS2 baseline, or work backward from CS2 to Valorant. The tool also checks both results with an estimated cm/360 distance so you can see whether the physical turn length stays close.

Two-way conversionValorant ↔ CS2 baselineRuns locally in your browser

Valorant sensitivity converter

Convert Sensitivity Between Valorant and CS2

Choose a direction, enter the sensitivity from the source game, and optionally add your active mouse DPI. The conversion ratio is a practical baseline, not a promise that every FOV, scope, or input setting will feel identical.

Conversion direction

The ratio is based on the common Valorant-to-CS2 baseline used by sensitivity-converter tools.

Source-game sensitivity

Enter the normal or hipfire value, not an ADS multiplier or a percentage unless the game stores it as a decimal.

Mouse DPI

DPI is optional for the conversion, but it is needed for the cm/360 check. Use the active DPI stage.

The calculation stays on this page. Your DPI and sensitivity values are not uploaded or saved.

Target sensitivity 1.113 CS2 CS2 = VALORANT × 3.18

Source distance (VALORANT)46.65cm/360

Target distance (CS2)46.68cm/360

How to use the Valorant sensitivity converter

Start with the value stored in the source game, then verify the result in the target game instead of treating the first number as a guaranteed perfect match.

Choose the direction

Select Valorant to CS2 when moving into Counter-Strike 2, or CS2 to Valorant when moving the other way.

Enter the source value

Use the normal or hipfire sensitivity from the game settings. Do not paste an ADS multiplier into the base field.

Add active DPI

DPI does not change the ratio, but it lets the page estimate cm/360 for both games and expose an obvious input mistake.

Test and adjust

Save the converted value, make a controlled turn in the target game, and adjust only after checking FOV, zoom, acceleration, and rounding.

The conversion ratio and cm/360 check

The common baseline for this page is CS2 sensitivity = Valorant sensitivity × 3.18. The reverse direction divides the CS2 value by 3.18. This is a numerical starting point for the two supported games, not an official Riot or Valve guarantee.

When DPI is provided, the page also estimates the physical distance for a full turn. Valorant uses a reference yaw of 0.07 and CS2 uses 0.022 in this check. Near-matching cm/360 is useful evidence that the basic turn distance is close, while it cannot make FOV, ADS, zoom, or input processing identical.

For a different game pair, use a converter that documents the supported scale or use the cm/360 calculator with a verified yaw. Do not copy the 3.18 ratio into Apex, Overwatch, Aim Lab, or another title.

CS2 sensitivity = Valorant sensitivity × 3.18

Valorant sensitivity = CS2 sensitivity ÷ 3.18

Valorant to CS2 conversion examples

These examples show how the calculation behaves. They are not a recommendation for a best sensitivity or a promise that the games will feel the same.

Direction	Source	Target	DPI	cm/360 check
Valorant → CS2	0.35	1.113	800	46.65 → 46.68 cm
CS2 → Valorant	1.113	0.350	800	46.68 → 46.65 cm
Valorant → CS2	0.5	1.590	1600	16.34 → 16.35 cm

Round only when the target game requires it. If the saved value is rounded, measure a full turn again and keep the game value that behaves consistently in your setup.

What this converter does—and does not do

The right tool depends on whether you want a cross-game number, a same-game comparison, or a physical desk-distance target.

Tool or value	Meaning	Best for	Main limitation
Valorant ↔ CS2 converter	Maps a base sensitivity through a documented baseline ratio	Starting a move between Valorant and Counter-Strike 2	FOV, zoom, input processing, and rounding can change the feel
eDPI	DPI × the numeric sensitivity inside one game	Comparing settings on the same sensitivity scale	It is not a universal cross-game conversion
cm/360	Physical mouse travel for a full turn	Checking a target distance when yaw values are verified	Equal distance does not guarantee equal perceived motion

Accuracy, edge cases, and limits

A converter can make the first setup faster, but the final check still belongs in the target game with your real settings.

Base sensitivity only

The result is for normal or hipfire sensitivity. Scoped, ADS, sniper, and per-zoom values may use separate rules.

FOV changes perception

Two settings can share a similar turn distance while looking faster or slower because the field of view is different.

Updates and rounding

Game updates, config limits, and decimal rounding can move the final value slightly. Recheck after saving it.

DPI and acceleration

Use the active DPI stage and keep acceleration behavior consistent. Windows pointer speed is not a replacement for mouse DPI.

Continue tuning your aim setup

Use a tool that matches the next question instead of forcing every sensitivity problem into one formula.

Method context: Aimlabs sensitivity converter · mouse sensitivity research

Valorant sensitivity converter FAQ

Multiply the Valorant base sensitivity by 3.18 as a starting baseline. For example, 0.35 in Valorant becomes 1.113 in CS2. Test the saved value in CS2 and adjust for your actual setup.

Divide the CS2 base sensitivity by 3.18. A CS2 value of 1.113 becomes about 0.350 in Valorant before rounding and in-game verification.

No. DPI is not needed for the numerical ratio. Add DPI when you want the page to estimate cm/360 and compare the physical distance for a full turn.

Not necessarily. FOV, zoom or ADS rules, input processing, acceleration, display setup, and rounding can change the feel even when the basic turn distance is close.

No. This page only implements the Valorant and CS2 baseline. Use a game-specific converter or the cm/360 calculator with verified values for another title.

Check the active DPI stage, base sensitivity, yaw reference, acceleration, and the value actually saved by the game. The example uses 800 DPI and the reference yaws shown on this page.