How much FPS optimization adds in Fortnite
See the gain for your hardware. How to get there yourself is in the guide below.
- Source: average across measurements on our clients' PCs over 7 years, not a guarantee
- Depends on: your hardware and how cluttered the system is, weaker PC means a bigger gain
- Network: we cut jitter and extra traffic; physical ping to the server depends on your ISP
- Exact numbers: after a free diagnostic of your PC
Quick: best Fortnite settings for 2026. Turn on Performance Mode (DX12), set shadows, Nanite and Ray Tracing to OFF, effects and post-processing to Low, NVIDIA Reflex ON + Boost, and 3D Resolution to 100% at 1920x1080. Add
-USEALLAVAILABLECORES -NOSPLASH -PREFERREDPROCESSOR 0to your launch options, and in GameUserSettings.ini set FrameRateLimit=0 and bDisableMouseAcceleration=True. With VBS disabled and XMP enabled in the BIOS, this delivers up to +56% to average FPS and +115% to 1% low.
Why Fortnite eats FPS
Fortnite moved to Unreal Engine 5, and that changed everything. In the older chapters (Chapter 1-3) the game ran on UE4 and was light on hardware. Now the engine drags along Nanite (dynamic geometry) and Lumen (global illumination). Even if you play on the lowest settings, these systems still load your GPU in the background.
The second problem: building. Every wall you place, every floor, every ramp creates new geometry and rebuilds the scene. In an endgame scramble, when 10 players are building at once, the CPU gets sharp load spikes. These aren’t smooth dips, they’re micro-stutters.
Third: updates. Epic adds visual upgrades every season, and after a patch your FPS can drop 15-20% for no obvious reason. Graphics settings sometimes reset to default.
It’s a separate story if Fortnite doesn’t just lag but won’t launch at all with the LS-0016 (Launch Failed, Fortnite is currently unavailable) error. That’s not about FPS, it’s about a broken update or permissions on the game folder, and it takes a couple of minutes to fix: Fortnite LS-0016: how to fix it.
Performance Mode, DX11, DX12: which to choose
Performance Mode hasn’t gone anywhere. There was a rumor in the community that it was removed in Chapter 5 Season 1, but that’s not true. Epic updated it: the old Legacy version on DX11 was dropped, and the mode itself was moved to DX12. It’s still available in the settings and remains the standard for competitive play.
Performance Mode (DX12) is the main pick. It runs on DirectX 12 and is optimized for multi-threaded CPUs. Stable 1% low, minimal input lag. Turn it on: Settings -> Graphics -> Rendering Mode -> Performance. If the option is missing, update your GPU drivers and restart the game.
For Intel and NVIDIA GPUs, Performance Mode on DX12 gives the best balance of FPS and stability. For AMD GPUs the result is also good; the DX12 version fixed the old stutter problems on Radeon.
One more thing: in the Epic Games Launcher you can remove the high-resolution textures (the three dots next to Fortnite -> Options -> uncheck High Resolution Textures). It frees up ~15 GB and removes pop-in.
Regular DX12 (not Performance) makes sense if you want nice visuals and your hardware can handle it. RTX 4070 and up. For competitive play, go with Performance.
DX11 stays as a fallback for really old cards (GTX 1060, RX 580). If you get freezes or artifacts on Performance Mode, try DX11 with the lowest settings.
Graphics settings
| Setting | Value | Why |
|---|---|---|
| Display mode | Fullscreen | Exclusive access to the GPU, lower input lag |
| View Distance | Far | You see builds and enemies at range. Setting it to Epic is pointless, Far is enough |
| 3D Resolution | 100% | Lowering it blurs your aim. If you need FPS, it's better to drop the whole screen resolution instead |
| Shadows | OFF | Standard for competitive play. Removes visual noise, +15-25% FPS |
| Anti-Aliasing | OFF / Low | At 1080p the difference is minimal, and you save FPS |
| Textures | Low / Medium | Barely affects FPS but eats VRAM. 8 GB of video memory, set Medium. 6 GB or less, Low |
| Effects | Low | Explosions, smoke, particles. On Low there's less visual clutter in a fight |
| Post Processing | Low | Bloom, motion blur, and other cosmetics. Turn it down |
| TSR (Temporal Super Resolution) | OFF / Performance | TSR upscales the image like DLSS. Off gives clarity, Performance gives +20-30% FPS at the cost of sharpness |
| Hardware Ray Tracing | OFF | Not needed for competitive play. That's a 40-50% FPS hit |
| Nanite | OFF | Dynamic geometry looks nice but is expensive. Turn it off |
| NVIDIA Reflex | ON + Boost | Fortnite supports Reflex natively. Cuts input latency by 15-30 ms |
About NVIDIA Reflex
Fortnite was one of the first games with native Reflex support. It works on both DX11 and DX12. The “On + Boost” mode slightly raises GPU power draw but keeps latency minimal even under heavy load. There’s no reason to turn it off.
Resolution and display
1920x1080 at 240 Hz. That’s the sweet spot for Fortnite in 2026.
If your PC can’t hold a stable 240 frames, try 1600x900. Enemy models will be a bit blurrier, but the FPS gain is noticeable, around 30-40%. Some pro players (Bugha, Mongraal) ran a lower resolution in tournaments.
A 144 Hz monitor is the minimum for Fortnite. At 60 Hz you lose build fights before they even start. The difference between 144 and 240 is less obvious, but if you’re already on a stable 240+ frames, a monitor upgrade gives you an edge on flick shots.
A note on Windowed Fullscreen. In Fortnite it runs through DWM, which adds 5-10 ms of latency compared to true fullscreen. The only reason to use it: if you frequently Alt+Tab between the game and other apps. For competitive play, always Fullscreen.
Epic Games Launcher launch options
In the Epic Games Launcher: Library, the three dots next to Fortnite, “Manage”, “Additional Command Line Arguments”, tick the box and enter:
-USEALLAVAILABLECORES -NOSPLASH -PREFERREDPROCESSOR 0| Argument | What it does |
|---|---|
-USEALLAVAILABLECORES | Use all cores. By default UE5 doesn’t always engage all of them |
-NOSPLASH | Removes the splash screen on launch. Saves a couple of seconds |
-PREFERREDPROCESSOR 0 | Pins the main thread to the first core. Helps on Intel, minimal difference on AMD |
-NOTEXTURESTREAMING | Loads all textures at once. Removes pop-in during play but needs more VRAM. Only if you have 8+ GB |
-LIMITCLIENTTICKS | Limits client ticks, lowers CPU load in the lobby |
Don’t add -dx11 or -dx12 through the launch options. It’s better to pick the rendering mode in the game’s own settings.
NVIDIA settings for Fortnite
NVIDIA Control Panel, “Manage 3D settings”, the “Program Settings” tab. Add a profile for FortniteClient-Win64-Shipping.exe.
| Setting | Value | Why |
|---|---|---|
| Low Latency Mode | ON | Works alongside Reflex. Don't set "Ultra", Reflex already does that job |
| Power management mode | Max performance | The GPU won't drop clocks in lighter scenes |
| Shader cache | 10 GB | UE5 generates a lot of shaders. A large cache removes stutters after updates |
| Texture filtering quality | High performance | Processes textures faster |
| Threaded optimization | ON | Fortnite makes good use of multi-threading |
| Vertical sync | OFF | Extra input lag |
| FXAA | OFF | Blurs your aim |
| Triple buffering | OFF | Useless without V-Sync |
| Image scaling (NVIDIA Image Scaling) | OFF | Better to use in-game TSR if you need upscaling |
AMD Radeon settings for Fortnite
AMD Software: Adrenalin Edition, the “Gaming” tab, Fortnite profile.
| Setting | Value | Why |
|---|---|---|
| Radeon Anti-Lag | On | Lowers input latency. Safe with EAC |
| Radeon Anti-Lag+ (Anti-Lag 2) | Don’t enable | Modifies process code. EAC may react, there have been cases of bans |
| Radeon Chill | Off | Dynamically cuts FPS when idle |
| Radeon Boost | Off | Lowers resolution when the mouse moves. Unacceptable for a shooter |
| Wait for vertical refresh | Always off | |
| Texture filtering quality | Performance |
Anti-Lag+ deserves a separate note. Fortnite uses Easy Anti-Cheat, and EAC is less aggressive than FACEIT AC or Vanguard. But Anti-Lag+ injects code into the game process at the driver level. Even if it works now, after the next EAC update you risk a ban. Regular Anti-Lag works at the driver level without injection and is completely safe.
Windows optimization
Fortnite is heavier on the GPU than CS2 or Valorant. But Windows still eats about 15% of your performance out of the box.
| Setting | Where to find it | State | Gain |
|---|---|---|---|
| VBS / Memory Integrity | Windows Security → Core Isolation → Memory Integrity | OFF | +5-15% FPS |
| XMP / EXPO in BIOS | Del/F2 on boot, enable Profile 1 | ON | +10-20% FPS and 1% low. Critical for Fortnite |
| "Maximum performance" power plan | PowerShell: powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61 | ON | +3-8% FPS |
| HAGS (hardware-accelerated GPU scheduling) | Settings → Display → Graphics | ON | For RTX 30+ / RX 6000+. Off on older cards |
| Discord / Steam / Game Bar overlays | Discord Overlay, Steam Overlay, Xbox Game Bar | OFF | Removes micro-stutters |
| Startup apps | Task Manager → Startup | Clean up | Frees up RAM |
About VBS and Fortnite
VBS hits Fortnite harder than CPU-bound games like CS2. Fortnite leans heavily on the GPU, and core virtualization adds extra overhead on every graphics API call. On a GTX 1660/RTX 3060, turning VBS off gives a consistent +10% to average FPS.
Check it: Win+R, msinfo32, the “Virtualization-based security” line. If it says “Running”, turn it off.
About XMP
Fortnite depends on memory bandwidth more than it seems. UE5 constantly streams assets into memory, and DDR4 at 2400 MHz versus 3600 MHz CL16 makes a 20-30% difference in 1% low. Those are exactly the freezes you get on landing and in the endgame. XMP turns on in the BIOS in 30 seconds, and it’s the easiest gain you can get.
GameUserSettings.ini tweaks
The file is here:
%LOCALAPPDATA%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini
Open it in Notepad, find and change:
; Remove the FPS limit (0 = no cap)
FrameRateLimit=0.000000
; Render resolution (100 = native)
sg.ResolutionQuality=100.000000
; Disable mouse acceleration
bDisableMouseAcceleration=TrueAfter editing, save the file and set the “Read-only” attribute (right-click, Properties, tick the box). Otherwise Fortnite will overwrite your changes on the next launch.
FrameRateLimit
In-game the FPS limit is capped at 240 (or 360 on 360 Hz monitors). Through the config you can remove the cap entirely. If you have a 240 Hz monitor, set FrameRateLimit=0.000000 and don’t think twice.
bDisableMouseAcceleration
Mouse acceleration is on by default. For a shooter that’s harmful: the mouse moves non-linearly, and you can’t build muscle memory. Turn it off through the config; there’s no such setting in the game itself.
Extra parameters
In the same file you can tweak a few more things:
; Disable automatic quality scaling
sg.ViewDistanceQuality=2
sg.ShadowQuality=0
sg.PostProcessQuality=0
sg.EffectsQuality=0
; Disable motion blur through the config
bMotionBlur=FalseQuality numeric values: 0 = Low, 1 = Medium, 2 = High, 3 = Epic. If you set things through the in-game menu, the config is already updated. Manual editing is only needed for parameters that aren’t in the UI (like mouse acceleration).
Frequently asked questions
”FPS is fine, but building causes stutters”
CPU bottleneck. Building spawns dozens of new objects per second, and the CPU can’t keep up. It’s especially noticeable on quad-core CPUs. Fixes: close background apps (Chrome with 20 tabs, that’s you), enable XMP, make sure the CPU isn’t throttling. If you have an i5-10400 or Ryzen 3 3300X, that’s a hardware ceiling, and a CPU upgrade will fix the problem for good.
”Should I use Performance Mode?”
Yes, for competitive play it’s the go-to mode. It wasn’t removed, despite the rumors. Epic only dropped the old Legacy version (DX11), and updated Performance Mode itself to DX12. Turn it on in Settings -> Graphics -> Rendering Mode -> Performance. If the option isn’t in the menu, update your GPU drivers to the latest version.
”FPS dropped after an update”
Epic adds visual upgrades every season and sometimes resets your settings. Go into the graphics settings and check that everything is in place. Especially Nanite, TSR, and Ray Tracing: they can switch on after a patch. Also delete the shader cache: %LOCALAPPDATA%\FortniteGame\Saved\PipelineCaches\ and let the game recompile on the next launch.
”Fortnite uses 100% GPU, is that normal?”
Yes, that’s normal on DX12. Unlike CS2, Fortnite is a GPU-heavy game. If the card is at 95-100% load, it means it’s running at full tilt instead of sitting idle. The problem starts when the GPU is at 100% and FPS is still low. That means the card can’t keep up, and you need to lower your settings.
”Textures look blurry or load in with a delay”
Two options. First: low VRAM. Fortnite on DX12 with Medium textures takes 5-6 GB of video memory. If you have 4 GB, textures will stream in and look blurry. Drop them to Low. Second: a slow drive. Fortnite is better installed on an SSD. On an HDD the texture pop-in on landing is visible to the naked eye. NVMe and SATA SSDs give roughly the same result; the difference between them in games is minimal.
What to do yourself, and what to hand off
Graphics settings, the config, NVIDIA/AMD parameters: you can do these yourself in an hour. The gain will be 20-40%.
After that come the things that need experience with specific hardware. Tuning RAM timings can add another 15-25% to your 1% low, but wrong timings will cause crashes 20 minutes into a match. Custom Windows strips out telemetry and components, but you need to know which drivers to keep. GPU overclocking raises the FPS ceiling but requires stress testing.
Our packages:
- Classic 11 ($25): clean Windows 11 + drivers + BIOS setup
- CustomX ($30): custom Windows build, 10,000+ unnecessary files removed
- GamePro ($60): the full package, including CPU/GPU/RAM overclocking and stress tests
- Standalone: DDR4 overclocking, DDR5, GPU
CustomX works with Fortnite without issues. EAC is less strict than FACEIT AC or Vanguard, and doesn’t conflict with custom Windows builds.
Results on real hardware
The numbers below were measured on our test benches: the same build and scene before and after, with no hardware swapped. Treat them as a reference point; your result depends on your specific configuration, cooling, and room temperature.
i5-12400F + RTX 3060 after GamePro:
| Metric | Before | After | Difference |
|---|---|---|---|
| Average FPS | 140 | 220 | +57% |
| 1% low | 65 | 140 | +115% |
| CPU temperature | 82°C | 73°C | -9°C |
R5 5600X + RTX 4060:
| Metric | Before | After | Difference |
|---|---|---|---|
| Average FPS | 180 | 280 | +56% |
| 1% low | 90 | 195 | +117% |
| CPU temperature | 79°C | 70°C | -9°C |
The bulk of the gain came from RAM overclocking (DDR4 3200 -> 3600 CL14 with tightened secondary timings) and disabling VBS. In-game graphics settings added about 20%, the rest from the system and hardware.
If you want us to do everything described above for you, pick a package in the service catalog.
Want us to do it for you?
We optimize your PC remotely. Pick a package that fits or message us and we will help you choose.
