This Valorant to Apex Legends sensitivity converter takes the sensitivity you use in Valorant and returns the Apex Legends value that produces the same physical turn — the same cm/360 — on the same mouse DPI. Valorant runs on a yaw of 0.07 degrees per count and Apex Legends on 0.022, so the number changes even though your arm movement does not. Example: Valorant 0.4 at 800 DPI is 40.82 cm per full turn; the matching Apex Legends value is 1.27.
0.4 × (0.07 / 0.022) = 1.27. Set Apex Legends to 1.27 and both games compute to about 40.82 cm per 360.Both games turn your view by a fixed number of degrees for every count the mouse sends, scaled by the sensitivity value you type in. That per-count constant is the yaw: Valorant uses 0.07, Apex Legends uses 0.022. Your DPI stays the same, so the only thing that has to change is the in-game number.
cm/360 = (2.54 × 360) / (DPI × sensitivity × yaw)Valorant sens × 0.07 = Apex Legends sens × 0.022Apex Legends sens = Valorant sens × (0.07 / 0.022) = Valorant sens × 3.182The multiplier is 3.182, so every Valorant value becomes a larger number in Apex Legends. That is not a faster sensitivity: Apex Legends moves fewer degrees per count, so it needs a bigger multiplier to produce the same turn.
Eight common Valorant values, the Apex Legends value that matches each one, and the shared cm/360 at three DPI settings. Every row is computed with the formula above; the cm/360 columns are the same for both games by construction, because that is the quantity the conversion preserves.
| Valorant sens | Apex Legends sens | cm/360 at 400 DPI | cm/360 at 800 DPI | cm/360 at 1600 DPI |
|---|---|---|---|---|
| 0.2 | 0.64 ✱ | 163.29 cm | 81.64 cm | 40.82 cm |
| 0.25 | 0.80 ✱ | 130.63 cm | 65.31 cm | 32.66 cm |
| 0.3 | 0.95 ✱ | 108.86 cm | 54.43 cm | 27.21 cm |
| 0.35 | 1.11 | 93.31 cm | 46.65 cm | 23.33 cm |
| 0.4 | 1.27 | 81.64 cm | 40.82 cm | 20.41 cm |
| 0.5 | 1.59 | 65.31 cm | 32.66 cm | 16.33 cm |
| 0.7 | 2.23 | 46.65 cm | 23.33 cm | 11.66 cm |
| 1.0 | 3.18 | 32.66 cm | 16.33 cm | 8.16 cm |
✱ Outside the Apex Legends menu range (1 to 8). Keep the same cm/360 by changing DPI instead: halving DPI doubles the required Apex Legends value, doubling DPI halves it.
In VALORANT, your aim sensitivity lives under Settings > General > Mouse. The slider labeled Sensitivity: Aim accepts values from 0.1 up to 100 with two-decimal precision, so you can dial in something like 0.35 without rounding issues. VALORANT uses a fixed 103-degree horizontal field of view with no FOV slider at all, which simplifies cross-game conversions because there is no FOV variable to match.
Scoped sensitivity is handled by a separate Scoped Sensitivity Multiplier that scales from 0 to 1. At 1.0 your scoped aim moves at the same speed as hip-fire; lower values slow the reticle while zoomed. When converting from another title, the most common mistake is ignoring this multiplier and only matching the base value. That leaves your Operator or Marshal scope feeling wildly off.
Apex Legends places mouse sensitivity under Settings > Mouse/Keyboard. The slider runs from 1.0 to 8.0 and accepts one-decimal increments. Unlike most tactical shooters, Apex has a horizontal FOV slider from 70 to 110, and changing it directly affects how your sensitivity feels — a wider FOV makes the same cm/360 appear visually slower because each degree of rotation covers less screen space.
ADS sensitivity uses a per-optic multiplier system. Each magnification tier has its own multiplier that scales off your hip-fire value, so swapping a 1x Holo for a 3x Ranger changes your scoped speed automatically. There is also a global ADS Mouse Sensitivity Multiplier that scales all optics together. The most common conversion error is matching only hip-fire and ignoring the per-optic layer, leaving high-zoom scopes feeling inconsistent.
| Game | Setting | Menu range |
|---|---|---|
| Valorant | Sensitivity: Aim 0.1 - 100 | 0.1 to 100 |
| Apex Legends | Mouse Sensitivity 1.0 - 8.0 | 1 to 8 |
Of the eight Valorant values in the table above, 5 convert to a Apex Legends value inside its menu range. If yours lands outside, keep the cm/360 and move DPI: half the DPI needs double the value, double the DPI needs half.
The reverse direction uses the inverted ratio 0.022 / 0.07 = 0.3143. Apex Legends 1.5 becomes Valorant 0.47, and both sit at 34.64 cm/360 at 800 DPI. The Apex Legends to Valorant converter has its own prefilled tool and table.
Keep your DPI the same and multiply your Valorant value by 0.07 / 0.022 = 3.182. Example: Valorant 0.4 becomes Apex Legends 1.27; at 800 DPI both give 40.82 cm per 360-degree turn. The tool above does this and prints both cm/360 values so you can check they match.
No. Valorant uses 0.07 and Apex Legends uses 0.022 degrees per count, so the same number turns your view slower in Apex Legends: Valorant 0.4 at 800 DPI is 40.82 cm/360, while Apex Legends 0.4 is 129.89 cm/360. The matching Apex Legends value is 1.27.
VALORANT locks FOV at 103 degrees. If your source game used a different FOV, the visual speed of camera rotation will feel different even at identical cm/360. Give yourself a few minutes of warm-up to adjust to the visual difference.
Yes. The scoped multiplier only affects zoomed weapons like the Operator and Marshal. If your source game has separate ADS values, convert the zoom sensitivity on its own rather than relying on the base conversion alone.
The in-game slider displays two decimal places, but you can edit the settings config file directly to get finer values. This is useful when a conversion produces a number like 0.3467 that the slider would round.
It changes how the sensitivity feels visually but the raw cm/360 for hip-fire stays the same. However, if you use a converter that factors in FOV, the output will differ because the angular movement per pixel changes.
Apex uses per-optic multipliers on top of a global ADS multiplier. If your source game has a single ADS value, you need to map it to each optic tier individually or adjust the global ADS multiplier to approximate the feel.
The in-game slider snaps to one-decimal increments. For finer control, you can edit the settings config file in your profile folder, though Apex may round to the nearest supported step on next launch.