Sensitivity Converter for Valorant, CS2 & Apex
Mouse sensitivity converter: keep the same hipfire cm/360 when you switch between Valorant, CS2, and Apex—then check one full turn in-game.
Counter-Strike 2 Sensitivity
Use 1.591 at 800 DPI in Counter-Strike 2. That matches Valorant (800 DPI × 0.5) at about 32.7 cm/360—the mouse travel for one full turn.
Matched: hipfire turn distance only
ADS, scopes, FOV, and game feel can still differ. Treat this as a starting hipfire number.
Copy it, paste into the target game's hipfire setting, and test in the training range before ranked.
What this sensitivity converter does
This sensitivity converter finds the hipfire sensitivity that keeps your mouse travel for a 360° turn the same across Valorant, CS2, and Apex.
Each game uses a different sensitivity scale, so the same slider number is not the same feel.
Copy a raw number across games and your flicks land short or overshoot—then you blame aim instead of the mismatch.
When the conversion is right
- Same physical turn distance (cm/360) in the target game
- A concrete hipfire number you can paste and test
- A clear boundary: hipfire only—not ADS or scopes
What a sensitivity converter keeps the same—and what it does not
The math only protects turn distance. It does not promise identical aim feel in every situation.
How does the number get calculated?
target sens = (source DPI × source sens × source yaw) ÷ (target DPI × target yaw). If source and target cm/360 match on screen, the transfer worked.
Which games and numbers does this use?
Fixed hipfire yaw values: Valorant 0.07; CS2 0.022; Apex 0.022. Those are calculator inputs—not claims about ADS, FOV, or performance.
Checked 2026-07-28. Sources below. Game updates or custom settings still need an in-game check.
What do real conversions look like?
Plug these into the calculator above to verify the output and its limits.
Valorant to CS2 sens, same DPI
Valorant 800 DPI, 0.35 → CS2 800 DPI
Result: 1.114 CS2 · ~46.7 cm/360 on both sides
Valorant's yaw is larger, so CS2 needs a bigger slider number for the same turn.
Start at 1.114 in CS2, then check a marked 360 and tracking on a practice map.
Does not set zoom_sensitivity_ratio or make the games look identical.
CS2 to Apex sens, DPI doubles
CS2 400 DPI, 2.0 → Apex 800 DPI
Result: 1.000 Apex · ~52.0 cm/360 on both sides
Same yaw on both profiles; double DPI → half the sensitivity.
Enter the DPI you actually use in Apex—DPI and sens trade off inside this hipfire math.
ADS multipliers and FOV stay separate. Test them in the firing range.
How do I check the result in-game?
The number is a starting point. Confirm inputs, then confirm the same mouse travel before you tweak.
- 1
Lock the source
Note the DPI and base hipfire sens you play with now—not a scoped multiplier or an old profile. The source cm/360 is your reference.
- 2
Enter the real target DPI
Use the DPI your mouse will actually run in the target game. Change DPI later? Run the converter again.
- 3
Test one full turn
Paste the value, mark a spot on the pad, and match a 360 to the source distance. Then track a few targets. Only then make a small, repeatable tweak.
What usually goes wrong?
Weird results almost always mean a bad input—not a broken formula.
Wrong active DPI
Mouse software can hide several presets. Enter the preset you play on. Right sens + wrong DPI = wrong turn distance.
Reusing the source slider number
Sliders are not universal. Copy the calculated target value, not the number from the old game.
Changing DPI after converting
DPI is part of the math. Raise it and keep the old sens → turns get faster. Recalculate when DPI changes.
Expecting ADS or scopes to match
This tool only matches hipfire cm/360. Set ADS/zoom/FOV separately and test them.
Skipping the range check
Same mouse distance can still feel different across engines. Verify a 360 and basic tracking before ranked.
How to Use
- 1
Enter your current hipfire setting
Pick the source game, then enter the DPI and base sensitivity you use now.
- 2
Choose the target game and DPI
Set the DPI you will actually use in the target game. It can differ from the source—the math accounts for both.
- 3
Copy and verify
Paste the target sensitivity into that game's hipfire setting, then verify a full turn in the training range.