Valorant Sensitivity Converter: Match Your Aim Across Games

Convert your Valorant sensitivity without guessing

Switching from Valorant to CS2 or Apex on the same mouse? Keep your DPI, then multiply your Valorant sensitivity by 3.18. For Overwatch 2 or Warzone, use 10.6. Coming back to Valorant means dividing instead.

This valorant sensitivity converter guide is the manual version: grab your current setting, use the table, and enter the result in your next game. No need to copy a streamer’s entire setup just to stop your mouse feeling wildly different after switching games.

For the 800 DPI crew hopping between games at a Bangladeshi or SEA gaming cafe, the goal is matching physical mouse travel. That does not mean every fight will feel identical. Your base turning distance can match while zoom and the view on screen still feel different.

Valorant sensitivity conversion table

These multipliers assume you keep the same mouse DPI between games. Use the forward column when leaving Valorant and the reverse column when bringing another game’s sensitivity back.

The Recharge conversion guide lists these game scales. Marvel Rivals uses the same scale as Overwatch 2, making 10.6 a starting point there too. Fortnite needs more care: its conversion is FOV-dependent, so use a converter that accounts for your FOV rather than borrowing a multiplier from this table.

The manual formula behind the conversion

The underlying rule is targetSens = sourceSens × (sourceYaw / targetYaw). Yaw is the rotation applied per mouse count. Valorant’s fixed yaw is 0.07 degrees per count, while CS2 and Apex use 0.022. Overwatch 2 and Warzone use 0.0066.

Dividing Valorant’s yaw by the CS2 or Apex yaw produces the 3.1818 ratio, rounded to 3.18 for practical conversion. That is why entering your Valorant sensitivity unchanged in CS2 does not preserve your turning speed.

For a ready-made check, LagoFast’s worked conversion takes 0.35 in Valorant to 1.113 in CS2: 0.35 × 3.18. Reverse the operation when returning to Valorant. Keep the calculation separate from any scoped setting.

Worked example: TenZ’s settings

Our TenZ Valorant settings guide lists 800 DPI and 0.415 in-game sensitivity. His eDPI is 332, calculated as 800 × 0.415.

For CS2, the conversion is 0.415 × 3.18 = 1.3197, or 1.32 rounded. Apex uses the same multiplier. Keep the mouse at 800 DPI instead of changing both the hardware setting and the in-game value.

To move that Valorant setup to Overwatch 2 or Warzone, multiply 0.415 by 10.6. The important part is using the original Valorant sensitivity as your source, not the already-converted CS2 value.

eDPI explains your setup, not every game’s scale

eDPI = DPI × sensitivity. Within Valorant, it lets you compare setups using different mouse DPI settings. For example, 0.35 at 800 DPI and 0.7 at 400 DPI both produce 280 eDPI and identical turning speed.

Do not carry that eDPI number straight into another game. As BoostRoyal’s conversion explanation notes, sensitivity scales differ. Convert the in-game sensitivity and keep your DPI instead. A matching eDPI label across games is not the same thing as matching mouse movement.

At a cafe, check the mouse DPI before judging the converted setting. Otherwise, you are comparing a different setup from the one used in your calculation. Get the base setup consistent before deciding the multiplier feels wrong.

cm/360: the distance you are actually matching

cm/360 means the physical mouse distance needed for a full 360-degree turn. Sensitivity conversion preserves that turning distance, with the table’s rounded multipliers providing a practical match.

For Valorant, the distance formula is 360 ÷ (0.07 × DPI × sensitivity). Watch the unit: this expression returns inches, not centimetres. The TenZ example is 360 ÷ (0.07 × 800 × 0.415) = 15.5 inches, approximately 39 cm.

That physical distance is a better cross-game reference than the sensitivity number alone. Still, matching mouse travel is not a promise of identical visual feel. Valorant has a fixed horizontal base FOV of 103, and scoped views need separate attention.

Scoped sensitivity needs its own check

The table handles base sensitivity, not every zoomed view. Valorant’s Marshal and Outlaw use 3.5× zoom. The Operator has 2.5× and 5.0× zoom, so do not judge your entire conversion from scoped shots alone.

Recharge gives scoped cm/360 as base cm/360 divided by the scoped multiplier. It also lists 0.747 as a math-perfect 1:1 scoped multiplier and a pro average of 0.97. Treat these as scoped references, not extra multipliers to apply to your base conversion.

After moving to CS2, check zoom_sensitivity_ratio_mouse separately. Get your normal turning distance comfortable first, then assess scoped aim. Mixing both adjustments makes it harder to tell which setting you actually dislike.

Use pro benchmarks as context, not instructions

Recharge’s 2025 pro-settings analysis reports average eDPI of 267, average sensitivity around 0.35, and average cm/360 around 45 cm. The most common DPI is 800, used by 79% in that analysis.

Individual settings still vary: Asuna is listed at 224 eDPI, Hiko at 272, and TenZ at 332. Pro-turned-streamer tarik uses 360 eDPI. Those are reference points, not evidence that your converted setting needs replacing.

Apply it, then give your aim time

In Valorant, go to Settings → Mouse → Sensitivity: Aim. Enter the converted value, keep your DPI consistent, and refine through deathmatch or aim trainers. BoostRoyal recommends giving the converted sensitivity about a week before tweaking.

Valorant borrows CS-style movement inaccuracy and spray patterns, as its game overview explains, but matching sensitivity does not erase differences between games. Use our Valorant pro crosshair codes if you also want a familiar aiming reference. Keep that separate from sensitivity testing so you can judge each change clearly.

Frequently asked questions