Free Apex Legends sensitivity tool
Apex Sensitivity Converter for VALORANT, CS2 and More
Convert a mouse sensitivity from a supported FPS into an Apex Legends starting value. Enter the active DPI on both sides, compare the modeled cm/360 distance, and then verify the result in the real game before changing your aim routine.
Apex Legends mouse and keyboard profile
Convert a sensitivity to Apex Legends
Choose the game your current setting comes from, enter its base or hipfire sensitivity and both DPI values, then read the Apex target value. The ratio is a transparent reference model, not a promise that every field of view or optic will feel identical.
The calculation runs in this page's JavaScript. Your sensitivity and DPI values are not uploaded or saved.
How to use the Apex sensitivity converter
The tool estimates a consistent horizontal turn distance. It cannot choose a comfortable setting for you, so keep the inputs stable and treat the output as a measured starting point.
Choose the source scale
Select VALORANT, CS2, Fortnite PC, Overwatch 2 or Apex Legends so the page uses the matching reference yaw.
Enter the base value
Use normal or hipfire sensitivity from the active profile. Do not mix an ADS multiplier, scoped value or controller response curve into this field.
Add both DPI stages
Enter the DPI used in the source game and the DPI you will use in Apex. If the hardware stage stays the same, enter the same number twice.
Test before tuning
Save the Apex value, make a controlled turn, and repeat a familiar tracking drill. Adjust one variable at a time after the baseline is repeatable.
How the Apex sensitivity conversion works
The converter models one horizontal 360-degree turn. It multiplies the source sensitivity by the source DPI and the source yaw, then divides by the Apex DPI and the Apex reference yaw. This keeps the estimated physical travel comparable when the two games use different numeric scales.
The page uses a reference yaw of 0.022 for Apex, 0.07 for VALORANT, 0.022 for CS2, 0.0055556 for Fortnite PC and 0.0066 for Overwatch 2. These values are calculation assumptions exposed for transparency; they are not a guarantee from the game developers or a recommendation for a competitive setting.
With 0.35 VALORANT at 800 DPI and 800 DPI in Apex, the model returns about 1.114 Apex sensitivity and roughly 46.65 cm/360 on both sides. Rounding can move the final distance slightly, so verify the value in game rather than treating three decimals as exact.
What the model does and does not measure
A yaw reference connects a game's numeric sensitivity to camera rotation. The tool applies one fixed reference per source option, so changing DPI changes the displayed target number while preserving the modeled physical distance.
This is a distance conversion, not an aim-quality test. The page does not inspect config files, change game settings, read your mouse, or send data to a conversion API. Field of view, optics, input processing and frame pacing can still make two profiles look or feel different.
Apex eDPI is calculated as Apex DPI multiplied by the converted Apex sensitivity. Compare that number inside Apex; do not use it as a universal scale across every game.
Apex sensitivity conversion examples
These examples use the displayed reference model and 800 DPI on both sides. They explain the arithmetic; they are not a recommendation for a best sensitivity or a professional player's profile.
| Source | Sensitivity | DPI | Apex result | Modeled distance |
|---|---|---|---|---|
| VALORANT | 0.35 | 800 → 800 | 1.114 | 46.65 cm/360 |
| CS2 | 1.50 | 800 → 800 | 1.500 | 46.65 cm/360 |
| Fortnite PC | 8 | 800 → 800 | 2.020 | 25.72 cm/360 |
| Overwatch 2 | 5 | 800 → 800 | 1.500 | 19.06 cm/360 |
Round only when Apex requires a particular precision. After saving a rounded number, measure one full turn again and keep the value that behaves consistently in your setup.
Prepare the right settings before converting
Start with the profile you actually use. Confirm whether the source game shows a decimal, percentage or multiplier before entering it, because a misplaced decimal creates a precise answer for the wrong scale. Keep your mouse, Windows pointer setting, polling rate and pad unchanged during the first comparison.
The formula includes DPI and base sensitivity, but it cannot remove acceleration, firmware smoothing or game-specific input behavior. If your source profile changes between matches, record the active value and use one stable baseline for the comparison.
Use the active DPI stage
Gaming mice often store several stages. Enter the stage used during the source session and the stage you will keep in Apex, not the maximum advertised DPI.
Separate hipfire from optics
The result represents base mouse movement. ADS, scope, sniper and per-optic multipliers may need separate Apex testing and should not replace the base value.
Keep units consistent
DPI means counts per inch. Do not enter centimeters, Windows pointer speed or a mouse's polling rate into either DPI field.
Read eDPI in context
Apex eDPI is useful for comparing Apex profiles. It does not prove that the same number in VALORANT, CS2 or Fortnite will feel the same.
Verify the converted value in Apex
Use the calculator for a repeatable first value, then let the game and your actual desk setup decide the final adjustment. Change one control at a time so you know what helped.
Enter the base value
Put the result into Apex's normal mouse sensitivity field. Keep ADS, optics and field of view at their current values for the first check.
Measure a full turn
Mark the starting point on the pad, complete one in-game 360, and compare the hand travel with the displayed cm/360 estimate.
Repeat a familiar drill
Run a short tracking or target-switching drill with the same frame rate, FOV and mouse grip. Look for repeatability, not a single lucky score.
Make a small adjustment
If the baseline is consistent but uncomfortable, change the sensitivity slightly and write down the direction. Do not change DPI, FOV and sensitivity together.
Accuracy, edge cases and limits
A converter removes arithmetic from the setup, but it cannot observe every game setting or make two cameras identical.
Yaw is an assumption
The calculation uses the reference yaw values shown on this page. A game update, platform difference or profile change can require a new check.
Hipfire is not ADS
The output covers base mouse movement. Scopes, optics, vertical sensitivity and controller response use different rules.
Equal cm/360 is not equal vision
FOV, aspect ratio, animation and target distance change perceived speed even when physical mouse travel is close.
Input limits are intentional
Empty, negative, non-finite and unusually large values are rejected. Check the decimal scale before trusting a surprising result.
Apex sensitivity converter FAQ
How do I convert VALORANT sensitivity to Apex Legends?
Choose VALORANT, enter the base sensitivity and both active DPI values, then read the Apex result. For example, 0.35 at 800 DPI maps to about 1.114 at 800 DPI in this reference model. Test it in Apex before fine-tuning.
How do I convert CS2 sensitivity to Apex?
Select Counter-Strike 2, enter the normal CS2 sensitivity, and keep the source and target DPI fields aligned with your real hardware stages. The reference yaw used here is the same for CS2 and Apex, so equal DPI values keep the numeric value close.
Do I need DPI to use an Apex sensitivity converter?
DPI is needed for the physical distance check and for a conversion when the source and target DPI differ. Enter the active stage, not the mouse's maximum setting or Windows pointer speed.
Will the converted Apex sensitivity feel exactly the same?
No. The model matches a reference turn distance. FOV, optics, input processing, frame pacing, display setup and personal control can still change the perceived speed.
Can I convert a controller sensitivity with this tool?
No. This page models mouse and keyboard base sensitivity with DPI. Stick response, aim assist and dead-zone settings need a separate controller method.
Why does changing Apex DPI change the result?
DPI is part of the physical-turn equation. If Apex DPI changes, the numeric sensitivity must change to preserve the modeled cm/360 distance.
Why does another converter show a different number?
Tools can use different yaw references, rounding, FOV assumptions or source scales. Compare the documented formula, then verify one full turn in Apex with your real settings.
Does this calculator upload my settings?
No. The calculation runs in local JavaScript and does not send the entered sensitivity or DPI to an API. Never enter account credentials into a settings calculator.