Valorant to Apex sens: multiply your Valorant sens by 3.1818 at the same DPI, or your Apex sens by 0.3143 to go back. Includes a two-way converter, 800 and 1,600 DPI charts and tips on ADS, optics and FOV.
Last updated: October 10, 2026

Valorant to Apex sens: Valorant sens × 3.1818 = Apex sens at the same DPI. For Apex to Valorant sens, use Apex sens × 0.3143. Apex uses the same scale as Counter-Strike (yaw 0.022), so the factor is identical to CS2. Example: Valorant 0.4 at 800 DPI = Apex 1.273; Apex 1.5 = Valorant 0.471. Leave the ADS multiplier at 1.0 to start.
Apex Legends and Valorant could hardly play more differently: one is a fast battle royale with drawn-out fights, the other a tactical shooter where the first clean hit often decides the round. Your hand still shouldn’t have to relearn how far a turn goes every time you switch. That’s what a Valorant to Apex sens conversion is for. This page gives you a two-way converter, charts for 800 and 1,600 DPI, and everything Apex adds on top: the ADS multiplier, per-optic settings and the FOV slider that Valorant doesn’t have at all.
Choose a direction, enter your sens and DPI, done. When you switch direction, the result moves into the input field automatically – so you can see that Apex 1.273 turns straight back into Valorant 0.4. The converter uses hipfire sens, i.e. without aiming down sights or through an optic.
The conversion keeps your hipfire turn distance (cm/360) identical. ADS, scope and zoom values are set separately – see below.
Apex Legends descends from the Source engine and turns the camera exactly as far per mouse count as Counter-Strike: 0.022° at sens 1.0. Valorant sits at 0.07°. That gives you the whole formula:
Both yaw values are measured standard values, not official figures from Riot or EA. They do line up across senslab.pro, game-sens.jor.dev and a measurement on the mouse-sensitivity.com forum, where 10,000 counts at Apex sens 1.636364 produced exactly one 360° turn – a precise match for 0.022°.
To double-check, work out the turn distance: cm/360 = 360 ÷ (DPI × sens × yaw) × 2.54. Apex 2.0 at 800 DPI gives 360 ÷ (800 × 2.0 × 0.022) × 2.54 = 26.0 cm, and Valorant 0.629 at 800 DPI also gives 26.0 cm.
The first chart covers a wide range from very slow to fast Valorant values. The cm/360 applies to both games, because the conversion keeps exactly that hand distance constant.
| Valorant sens | eDPI | cm/360 | Apex Legends sens |
|---|---|---|---|
| 0.15 | 120 | 108.9 | 0.477 |
| 0.20 | 160 | 81.6 | 0.636 |
| 0.25 | 200 | 65.3 | 0.795 |
| 0.30 | 240 | 54.4 | 0.955 |
| 0.40 | 320 | 40.8 | 1.273 |
| 0.50 | 400 | 32.7 | 1.591 |
| 0.60 | 480 | 27.2 | 1.909 |
| 0.70 | 560 | 23.3 | 2.227 |
| 0.80 | 640 | 20.4 | 2.545 |
At 1,600 DPI you need half the in-game sens for the same distance. Valorant 0.25 at 1,600 DPI equals 0.5 at 800 DPI and lands at 0.795 in Apex.
| Valorant sens | eDPI | cm/360 | Apex Legends sens |
|---|---|---|---|
| 0.08 | 128 | 102.1 | 0.255 |
| 0.10 | 160 | 81.6 | 0.318 |
| 0.15 | 240 | 54.4 | 0.477 |
| 0.20 | 320 | 40.8 | 0.636 |
| 0.25 | 400 | 32.7 | 0.795 |
| 0.30 | 480 | 27.2 | 0.955 |
| 0.35 | 560 | 23.3 | 1.114 |
| 0.40 | 640 | 20.4 | 1.273 |
Looking across the columns, Valorant 0.15 to 0.8 at 800 DPI corresponds to roughly 0.48 to 2.55 in Apex. If you play Apex much faster than that, the Valorant value you get may feel twitchy for precise headshots – more on that in the switching section.
For the reverse direction, here are common Apex values. The Valorant sens applies at the same DPI; the two right-hand columns show your 360° distance at 800 and 1,600 DPI.
| Apex Legends sens | Valorant sens | cm/360 at 800 DPI | cm/360 at 1,600 DPI |
|---|---|---|---|
| 1.0 | 0.314 | 52.0 | 26.0 |
| 1.2 | 0.377 | 43.3 | 21.6 |
| 1.4 | 0.440 | 37.1 | 18.6 |
| 1.6 | 0.503 | 32.5 | 16.2 |
| 1.8 | 0.566 | 28.9 | 14.4 |
| 2.0 | 0.629 | 26.0 | 13.0 |
| 2.5 | 0.786 | 20.8 | 10.4 |
| 3.0 | 0.943 | 17.3 | 8.7 |
| 3.5 | 1.100 | 14.8 | 7.4 |
| 4.0 | 1.257 | 13.0 | 6.5 |
So Apex 1.5 at 800 DPI becomes Valorant 0.471 with 34.6 cm per turn. At 1,600 DPI the Valorant sens stays the same (0.471), but the turn is only half as long – always make sure you keep the DPI you used in Apex.
The 3.18 factor only carries over hipfire sens. As soon as you aim, each game uses its own settings that aren’t part of the conversion:
The global “ADS Mouse Sensitivity Multiplier” applies to all sights. EA recommends 1.0 in its settings guide. Apex adjusts the sensitivity to the zoom automatically while you aim.
Optionally you can enable “Per Optic ADS Sensitivity” and give every optic from 1× to 10× its own value. That’s only worth it if a particular optic keeps feeling too fast or too slow.
Valorant uses the “ADS Sensitivity Multiplier” for rifles and SMGs and the “Scoped Sensitivity Multiplier” for snipers. Both default to 1.0.
Community tools describe Apex’s per-optic zoom scaling in different ways, so we deliberately don’t list fixed 1:1 values per optic here. The safe route: start at 1.0 in Apex, start at 1.0 in Valorant, and only fine-tune after a few rounds.
Valorant has fewer zoom levels than Apex. The Vandal and Phantom zoom 1.25× when aiming, the Guardian 1.5×. At the default of 1.0, a movement to the edge of the screen feels the same zoomed and unzoomed. If you want to carry over the feel right at the crosshair instead, the math lands at about 0.870 for 1.25× and 0.815 for 1.5× zoom.



Not your turn distance. Apex lets you set the field of view freely: EA lists 70 as the default, and 90 to 110 is common in competitive play. The hipfire conversion is independent of it – a 360° turn in Apex depends only on sens, DPI and the 0.022 yaw. A higher FOV does make movement on screen look slower, because more of the world fits into view.
Valorant, on the other hand, has a fixed 103° horizontal field of view at 16:9 and no FOV slider. Community measurements indicate that Apex’s FOV value refers to a 4:3 image; mathematically, an Apex FOV of about 86 to 87 matches Valorant’s view (not officially confirmed). If you play Apex at 104 or 110, Valorant will look noticeably tighter. That’s normal, not a conversion error.
In Apex you often track targets for longer, while Valorant rewards short, precise corrections at head height. Your converted sens may therefore feel too fast in Valorant at first. Start with the exact value anyway and adjust afterwards:
To see how your sens compares with other players, try the Valorant eDPI calculator.
Every game pair has its own page with a converter, charts and the aiming quirks of that game.
Same factor as Apex, plus AWP vs Operator and whether your CS:GO sens still applies.
Factor 10.61 and zoom sensitivity for Widowmaker, Ana and Ashe.
Percent instead of decimals: factor 12.6 plus the X/Y, targeting and scope sliders.
Valorant to Apex sens is plain multiplication: × 3.1818 one way, × 0.3143 the other – the same factor as CS2, because Apex uses the Source yaw of 0.022. FOV doesn’t affect turn distance, only the feel. Set the ADS multiplier to 1.0 in both Apex and Valorant to start, and only tweak individual optics once you’ve tested them in game.
Valorant 1.0 equals an Apex sens of 3.18 (precisely 3.1818) at the same DPI. At 800 DPI that’s only 16.3 cm for a full 360° turn – a very high sens.
Yes. Apex Legends and CS2 both use the measured yaw value of 0.022, so your Apex sens carries over 1:1 to CS2 and vice versa.
No. DPI is set on your mouse, not in the game. The 3.1818 factor applies as long as your DPI stays the same in both games.
EA recommends 1.0 as the starting point for the ADS Mouse Sensitivity Multiplier. Per Optic ADS Sensitivity is optional and only worth using if a specific optic keeps feeling off.
No. The 360° turn distance in Apex depends only on sens, DPI and the 0.022 yaw. A higher FOV only changes how fast the image appears to move.
Apex 1.5 equals Valorant 0.471 at the same DPI. At 800 DPI that’s 34.6 cm for a 360° turn.
Multiply your Apex sens by 0.3143 (0.022 ÷ 0.07). Apex 2.0 becomes Valorant 0.629, as long as you use the same DPI in both games.
May I set a statistics cookie?
With your consent, Matomo (self-hosted in Germany, no sharing, IP shortened) uses a cookie to remember whether you come back – so I can see which pages really help. Without consent I keep measuring anonymously with no cookies at all. Change it any time via “Cookie settings” in the footer. Privacy policy