This CS2 to Fortnite sensitivity converter takes the sensitivity you use in CS2 and returns the Fortnite value that produces the same physical turn — the same cm/360 — on the same mouse DPI. CS2 runs on a yaw of 0.022 degrees per count and Fortnite on 0.005555, so the number changes even though your arm movement does not. Example: CS2 1.0 at 800 DPI is 51.95 cm per full turn; the matching Fortnite value is 3.96%.
1.0 × (0.022 / 0.005555) = 3.96. Set Fortnite to 3.96% and both games compute to about 51.95 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: CS2 uses 0.022, Fortnite uses 0.005555. 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)CS2 sens × 0.022 = Fortnite sens × 0.005555Fortnite sens = CS2 sens × (0.022 / 0.005555) = CS2 sens × 3.96The multiplier is 3.96, so every CS2 value becomes a larger number in Fortnite. That is not a faster sensitivity: Fortnite moves fewer degrees per count, so it needs a bigger multiplier to produce the same turn.
Eight common CS2 values, the Fortnite 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.
| CS2 sens | Fortnite sens | cm/360 at 400 DPI | cm/360 at 800 DPI | cm/360 at 1600 DPI |
|---|---|---|---|---|
| 0.5 | 1.98% | 207.82 cm | 103.91 cm | 51.95 cm |
| 0.8 | 3.17% | 129.89 cm | 64.94 cm | 32.47 cm |
| 1.0 | 3.96% | 103.91 cm | 51.95 cm | 25.98 cm |
| 1.2 | 4.75% | 86.59 cm | 43.30 cm | 21.65 cm |
| 1.5 | 5.94% | 69.27 cm | 34.64 cm | 17.32 cm |
| 1.8 | 7.13% | 57.73 cm | 28.86 cm | 14.43 cm |
| 2.0 | 7.92% | 51.95 cm | 25.98 cm | 12.99 cm |
| 3.0 | 11.88% | 34.64 cm | 17.32 cm | 8.66 cm |
Counter-Strike 2 exposes mouse sensitivity through Settings > Game > Mouse Sensitivity, where the in-game slider spans 0.10 to 8.00. You can bypass that cap with the console command sensitivity followed by any decimal value, giving you virtually unlimited precision. CS2 uses a fixed horizontal FOV of roughly 106 degrees with no way to change it, so conversions only need to account for the sensitivity coefficient and DPI.
Zoom sensitivity is controlled by zoom_sensitivity_ratio_mouse, which ranges from 0.1 to 3.0 in the menu. A value of 1.0 does not mean scoped and hip-fire feel identical — the zoom FOV reduction already slows the view, so 1.0 simply preserves the underlying ratio. Many players moving from VALORANT set this to 1.0 and wonder why scoping feels slower than expected.
Fortnite separates horizontal and vertical aim into X-Axis Sensitivity and Y-Axis Sensitivity, each expressed as a percentage from 1% to 100%. You will find these under Settings > Mouse and Keyboard. Most players keep X and Y identical, but Fortnite does allow independent tuning if you prefer slower vertical movement for recoil control.
Targeting and scoped aim each have their own percentage slider. Mouse Targeting Sensitivity scales your sensitivity while holding ADS on non-scoped weapons, and Mouse Scope Sensitivity applies to zoomed optics. These multiply against your base X/Y value. Fortnite also uses a fixed 80-degree vertical FOV in standard playlists. Because the sensitivity scale is percentage-based rather than a raw multiplier, converters need to translate from the source game's unit system into Fortnite's percentage — a step that often trips up new players who paste a raw decimal.
| Game | Setting | Menu range |
|---|---|---|
| CS2 | Mouse Sensitivity 0.10 - 8.00 (menu); unlimited via console | 0.1 to 8 |
| Fortnite | X-Axis Sensitivity / Y-Axis Sensitivity 1% - 100% | 1 to 100 |
Of the eight CS2 values in the table above, 8 convert to a Fortnite 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.005555 / 0.022 = 0.2525. Fortnite 7.5% becomes CS2 1.89, and both sit at 27.43 cm/360 at 800 DPI. The Fortnite to CS2 converter has its own prefilled tool and table.
Keep your DPI the same and multiply your CS2 value by 0.022 / 0.005555 = 3.96. Example: CS2 1.0 becomes Fortnite 3.96%; at 800 DPI both give 51.95 cm per 360-degree turn. The tool above does this and prints both cm/360 values so you can check they match.
No. CS2 uses 0.022 and Fortnite uses 0.005555 degrees per count, so the same number turns your view slower in Fortnite: CS2 1.0 at 800 DPI is 51.95 cm/360, while Fortnite 1.0% is 205.76 cm/360. The matching Fortnite value is 3.96%.
Yes. CS2 uses the same yaw value as CS:GO, so any sensitivity you used in CS:GO will produce the exact same cm/360 in CS2 without conversion.
The UI slider has a fixed range of 0.10 to 8.00 for most players. You can set any value above or below that range by typing the sensitivity command directly into the developer console.
It multiplies your base sensitivity while scoped. At 1.0, the underlying sensitivity value stays the same, but the narrowed FOV of the scope still makes your view turn more slowly per centimeter of hand movement.
Fortnite expresses sensitivity as a percentage of its internal maximum turn rate. When converting from a game that uses raw multipliers, you need to translate through cm/360 rather than pasting the number directly.
Building and editing sensitivity sliders are unique to Fortnite and have no equivalent in other shooters. Only your X/Y aim, targeting, and scope sensitivities carry over from a conversion.
Standard playlists use a fixed FOV. Some limited-time modes or creative maps may adjust FOV, but for conversion purposes you should use the default value.