Fortnite does not use a decimal sensitivity like Valorant or CS2. It uses a percentage, set separately for the X axis and the Y axis, and that is why numbers copied from other games often look wrong. The good news: the maths behind it is simple, and once you know it you can land on a precise turning distance instead of guessing.
This guide covers the formula, tables for the three common DPI values, a full conversion example, the extra sliders (ADS, scope, build, edit), and a two-week plan to settle on a value. To calculate instantly, use the sensitivity converter.
How Fortnite sensitivity works
In Fortnite, sensitivity is a percentage. The yaw, meaning the degrees the view turns per mouse count, is 0.005555 per 1% of X-axis sensitivity. For comparison, Valorant uses 0.07 and CS2 uses 0.022 per 1.0 of sensitivity. Because the unit is a percentage, typical values look small: a single-digit number is normal.
The distance you move the mouse for a full turn (cm/360) comes from this formula:
cm/360 = 360 / (0.005555 × % × DPI) × 2.54
Solving for the percentage gives % = 360 × 2.54 / (0.005555 × DPI × cm/360). Two things follow. First, doubling the percentage halves the distance. Second, doubling your DPI also halves it, so the percentage and the DPI always travel as a pair. If you change one without the other, your aim changes.
Why cm/360 beats copying numbers
A percentage on its own tells you nothing. 5% at 400 DPI and 5% at 1600 DPI feel completely different, because the mouse sends four times as many counts per centimetre in the second case. The reliable way to describe a setup is cm/360, the physical distance for one full turn, because it already includes both DPI and sensitivity. The same logic applies to eDPI, with one limit: eDPI is only comparable between games that share the same yaw.
Fortnite's yaw differs from CS2 and Valorant, so you cannot compare a Fortnite eDPI with a Valorant eDPI. Compare cm/360 instead. If you are unsure about the relationship between the two settings, read DPI or in-game sensitivity: which one to raise first.
Fortnite percentage per DPI and cm/360
The table shows the X-axis percentage needed for a target cm/360. Pick the row for the distance you want and the column for your DPI.
| cm/360 | 400 DPI | 800 DPI | 1600 DPI |
|---|---|---|---|
| 20 | 20.58 | 10.29 | 5.144 |
| 25 | 16.46 | 8.23 | 4.115 |
| 30 | 13.72 | 6.859 | 3.429 |
| 35 | 11.76 | 5.879 | 2.939 |
| 40 | 10.29 | 5.144 | 2.572 |
| 45 | 9.145 | 4.572 | 2.286 |
| 50 | 8.23 | 4.115 | 2.058 |
| 60 | 6.859 | 3.429 | 1.715 |
To go the other way, here is the cm/360 you get from common X percentages:
| X % | 400 DPI | 800 DPI | 1600 DPI |
|---|---|---|---|
| 4% | 102.9 | 51.44 | 25.72 |
| 5% | 82.3 | 41.15 | 20.58 |
| 6% | 68.59 | 34.29 | 17.15 |
| 8% | 51.44 | 25.72 | 12.86 |
| 10% | 41.15 | 20.58 | 10.29 |
| 12% | 34.29 | 17.15 | 8.573 |
Notice how the same 5% gives 82.3 cm at 400 DPI but only 20.58 cm at 1600 DPI. Many competitive players across shooters sit roughly in the 30 to 55 cm/360 range for tactical games, and Fortnite players vary widely and often go a bit faster because of building and editing. That is common but not a rule, so treat the table as a starting menu, not a prescription.
Worked example: converting from Valorant
Suppose you play Valorant at 800 DPI with 0.35 sensitivity. That is an eDPI of 280 and about 46.7 cm/360. You want the same turning distance in Fortnite at 800 DPI.
- Use the conversion factor Valorant → Fortnite: 0.07 ÷ 0.005555 = about 12.60.
- Multiply: 0.35 × 12.60 = 4.41%.
- Check: 360 × 2.54 ÷ (0.005555 × 4.41 × 800) is about 46.7 cm/360. Same distance.
Because the same DPI is used in both games, the converted value does not depend on DPI. If you changed DPI, you would adjust the percentage inversely instead. You can also open the ready-made pages for Valorant to Fortnite and Fortnite to Valorant.
From CS2 the shortcut is simple: CS2 1.0 equals 3.96% in Fortnite at the same DPI. Going back, Fortnite 6% equals CS2 1.515. The full process for every pair of games is in how to convert sensitivity between games.
Keep X and Y equal, and know the extra sliders
Fortnite lets you set the X and Y axis separately. Unless you have a specific reason, keep both equal. Different values make a diagonal flick travel at an odd angle and make it harder to build muscle memory. Equal X and Y also keeps the table above valid for vertical movement.
Fortnite also has separate Targeting (ADS) and Scope sensitivity percentages, and separate build and edit sensitivities. These are multipliers or independent values, and their exact defaults can change with updates, so check the numbers on your own settings screen and do not copy someone else's. A practical way to handle them: set the main hipfire value first, keep the others at their defaults for a few days, and only then change one slider at a time.
How to test a new value
Use a consistent test instead of judging by one game. A simple method is to load a practice or creative island and run the same short drill each day, then compare how it feels over several sessions.
- Check the 90-degree and 180-degree turns: can you do a 180 on the mouse pad without lifting it more than once?
- Test a small flick to a stationary target, then tracking a moving one. Note whether you overshoot or undershoot.
- Keep the setting for at least two weeks before changing it again. Muscle memory needs repetition.
You can also run the sensitivity test, which plays short rounds of flicks at different cm/360 values and suggests a range. It is a quick estimate, not a verdict, so confirm it in real play.
A two-week plan to settle on a value
Own example: you pick 35 cm/360 at 800 DPI. From the table, that is 5.879%. At 400 DPI you would need 11.76%, and at 1600 DPI 2.939%, which shows why you should keep your DPI fixed while testing.
- Days 1 to 3: play with the chosen value and do not touch the slider, even if it feels odd.
- Days 4 to 10: if you consistently overshoot, move to a slower row (for example 40 cm/360 = 5.144% at 800 DPI). If you cannot turn enough, try a faster row (for example 30 cm/360 = 6.859%).
- Days 11 to 14: lock the value, then judge it. Only change it again if the problem is still clear.
Before you start, check your DPI and write it down, so that a later change in the mouse software does not secretly alter your setup.
Common mistakes
- Copying a percentage without the DPI. The number is meaningless without it.
- Changing the value every game. You never give your hand time to adapt.
- Mismatched X and Y by accident after a settings reset.
- Judging by a bad session. Fatigue, ping and warm-up all affect feel.
- Ignoring mouse settings. Turn off pointer acceleration ("Enhance pointer precision") in the operating system and keep the polling rate at the usual 1000 Hz.
Frequently asked questions
Is Fortnite sensitivity the same as CS2 sensitivity?
No. Fortnite uses a percentage with a yaw of 0.005555 per 1%, while CS2 uses a decimal with a yaw of 0.022. At the same DPI, CS2 1.0 equals Fortnite 3.96%, so a CS2 value of 2.0 corresponds to about 7.92%.
What percentage should I use at 800 DPI?
For a 40 cm/360 turn, use 5.144% at 800 DPI. For 30 cm/360, use 6.859%, and for 50 cm/360, use 4.115%. Start in that range and test for two weeks.
If I raise my DPI from 800 to 1600, what happens to the percentage?
Halve it to keep the same distance. For example, 40 cm/360 is 5.144% at 800 DPI and 2.572% at 1600 DPI. The cm/360 stays identical.
Should the X and Y sensitivity be different?
Keep them equal as a default, for example both at 6%. At 800 DPI, 6% is 34.29 cm/360 on both axes. Different values are only worth trying if you have a clear reason and test them for a full two weeks.
How do I move my Valorant sensitivity to Fortnite?
Multiply the Valorant value by about 12.60 and keep the same DPI. For example, Valorant 0.35 becomes 4.41%, which is about 46.7 cm/360 at 800 DPI. The result does not change with DPI as long as it is the same in both games.
Fortnite sensitivity becomes easy when you think in cm/360: choose the distance, pick the row in the table for your DPI, keep X and Y equal and give the value two weeks. If you are coming from another shooter, the sensitivity converter does the multiplication for you and shows the cm/360 so you can double-check the result.