Reduce Fortnite latency: what to check to play without lag
High ping, micro-freezes during a build fight, or input lag when you shoot: the cause is rarely where you think. Here's where each millisecond actually comes from, and which settings have a measurable effect.
Latence measures your network latency, frametime and PC state so you can compare before and after each change.
Download Latence- 01 Where latency comes from, and why ping shows only part of it
- 02 Which renderer to pick
- 03 Should you cap your FPS? The real criterion
- 04 V-Sync and Nvidia Reflex
- 05 Servers, ping and bufferbloat
- 06 The Windows settings that matter
Where Fortnite latency comes from
When you say "I'm lagging," you're describing a symptom, not a cause. Between your click and the moment the server validates your shot, the signal crosses a full chain. The ping the game displays measures only one of its links.
| Symptom | What you see | Where to look |
|---|---|---|
| Network lag | Enemies teleport, your shots don't register. | Ping, jitter and packet loss. Server, Wi-Fi, router. |
| Rendering lag | Stutters and freezes, even on an excellent ping. | Frametime and 1% lows. CPU, GPU, renderer. |
| Input lag | Aim feels like it drags, edits come out late. | GPU render queue, V-Sync, frame rate. |
Which Fortnite renderer should you pick?
Watch out for a common confusion: Performance Mode is not "DirectX 11." It's a separate renderer that strips down textures, shadows and lighting to free up CPU and GPU.
| Renderer | Who it's for | Trade-off |
|---|---|---|
| DirectX 11 | Older systems, or if DX12 causes stutters on your machine. | Leans mostly on one CPU core: wastes a modern multi-core processor. |
| DirectX 12 | Recent systems: spreads load across cores, better 1% lows. | Stutters while compiling shaders, especially in the first matches after an update. |
| Performance Mode | Chasing maximum FPS, or running Fortnite on modest hardware. | Heavily reduced visual quality, close to mobile rendering. |
With patch 37.00 (August 2025), Epic introduced a DirectX 12-based Performance Mode meant to replace the older one built on DirectX 11. The legacy version remains available as an option. If you use Performance Mode, check which of the two is active: rendering and stability differ between them.
No renderer wins everywhere. Run the same sequence on each one and compare frametime, not average FPS.
It's the 1% lows that create the feeling of lag. A higher average with deeper dips plays worse than a lower but steady one.
Should you cap your FPS in Fortnite?
This is the most poorly explained setting in the game. You'll read everywhere that you should "cap your FPS 3 frames below your refresh rate." That rule is real, but it answers one specific case: staying inside the working range of a G-Sync or FreeSync display. Outside that case, it can increase your latency.
The real criterion is GPU saturation. When it runs at 99%, frames pile up before being displayed: the one you see was computed several frames before your input. Capping the frame rate drains that queue. When the GPU has headroom, there is no queue to drain.
-
noyou hold several hundred FPS, the CPU is the limit
- G-Sync / FreeSync displayCap a few frames below your refresh rate.Here the "-3" rule makes sense: it stops V-Sync from engaging and adding a frame of delay. The goal is staying inside the display's range, not draining a queue.
- standard displayLeave the frame rate uncapped.Latency is at its lowest, tearing is the trade-off. This is the case for most systems that push past 500 FPS.
-
yesthe GPU is saturating, the render queue fills up
- Nvidia Reflex availableTurn Reflex on, no manual cap.Reflex adjusts the frame rate on its own when the GPU saturates. A fixed cap on top of it adds nothing and can cost you useful frames.
- no Reflex (AMD card, unsupported game)Cap below your stable frame rate.Come down until you leave saturation, then check that GPU usage falls back below 95%.
A stable cap still beats a frame rate that swings wildly.
Uneven frametime is felt more than a slightly lower average. If your FPS jump from 300 to 700 depending on the zone, a high but sustainable cap can feel cleaner. That's a trade-off to measure, not a rule to apply blindly.
V-Sync and Nvidia Reflex
Classic V-Sync syncs the display to the refresh rate and can add up to a full frame of delay. The cost therefore depends directly on your display. In exchange, it removes tearing: the split that appears when the screen shows two different frames on the same scan.
In competitive play without an adaptive display, turning V-Sync off is the common choice. With a G-Sync or FreeSync monitor the recommended combination is different: adaptive sync on, V-Sync enabled in the driver, and an FPS cap below the refresh rate so V-Sync never engages.
Nvidia Reflex works elsewhere: it shortens the GPU-side render queue. The "On + Boost" mode additionally keeps GPU clocks high, useful if your card downclocks for lack of load. On an AMD card Fortnite offers no built-in equivalent: the lever is still to avoid saturating the GPU.
Network: servers, ping and bufferbloat
The ping shown in Fortnite depends on the matchmaking server. You don't fully control it, but you can reduce the variables on your side.
- Matchmaking region: manually pick the closest region rather than auto mode, which can place you on a farther server if its queue is shorter.
- Ethernet: Wi-Fi adds jitter and micro packet loss that Fortnite handles poorly, especially in build fights where every action sends a packet. See Wi-Fi jitter in games.
- Bufferbloat: if your ping doubles when someone downloads on the same network, your router is saturating. Upload does the most damage. Diagnosis in testing bufferbloat for gaming.
- Background downloads: the Epic Games Launcher keeps updating while you play. Cut them before a competitive session.
Windows settings that actually matter
These act at the system level. Their effect depends heavily on the machine, so measure rather than applying a ready-made list.
- Power plan: a profile that avoids CPU frequency drops between frames limits hitching. On a laptop the effect is usually more visible than on a well-fed desktop.
- Hardware-accelerated GPU scheduling (HAGS): test it both ways. Depending on card and driver, the effect ranges from a small gain to a regression.
- Background apps: overlays (Discord, launchers, capture tools) insert themselves into the render path. This is one of the few points where the effect is visible without instruments.
- GPU drivers: a recent driver often fixes frametime regressions, but avoid release day. See GPU driver management.
For the full list, see best Windows gaming settings.
Common mistakes to avoid
Don't apply registry "tweaks" or network settings from a forum without measuring before and after. Most have no measurable effect, and some hurt stability. If you can't observe the difference through a measurement, the change is worthless.
Don't confuse network lag with rendering lag. A 20 ms ping with a stuttering game is not a connection problem. Check your FPS, frametime and CPU/GPU usage before blaming the network.
Don't change everything at once. One setting, two or three matches, then compare. Otherwise you'll never know which one worked, and you'll keep useless settings for months.
What Latence can help you check
Latence separates the network problem from the PC problem: ping, jitter, frametime and background activity, measured before and after each change. The goal is knowing which of your changes actually did something.
To go further: diagnosing high ping, understanding PC input lag, unstable frametime and FPS drops on Windows.
Why do I lag in Fortnite even though my connection is good?
Good bandwidth doesn't guarantee good ping, and lag doesn't necessarily come from the network. It can come from the matchmaking server, your ISP's routing, Wi-Fi, or your own PC when frametime is uneven. First check whether the displayed ping is high or whether your FPS are dropping: the two causes have nothing in common.
Should you cap your FPS in Fortnite?
Only in some cases. A cap reduces latency when your GPU is saturated at 99%, because it drains the render queue. If your GPU has headroom — for example when you push several hundred FPS and are CPU-limited — capping gains you nothing and displays older frames. With a G-Sync or FreeSync monitor, the cap exists to stay inside the display's range, not to shorten the render queue.
Is Fortnite's Performance Mode just DirectX 11?
No. Performance Mode is a separate renderer that strips down textures, shadows and lighting. Since patch 37.00 in August 2025, a DirectX 12-based Performance Mode replaces the older one built on DirectX 11, which remains available as a legacy option.
Does Nvidia Reflex lower latency in Fortnite?
Yes, by shortening the GPU render queue. The effect is clear when the GPU is loaded past 90%, and close to nil when the CPU is the limit. With Reflex on, a manual FPS cap is usually unnecessary.
What's a good ping for Fortnite?
As orders of magnitude: below 30 ms network latency is rarely noticeable, between 30 and 60 ms the game stays comfortable, and past 80 ms close-range fights become a disadvantage. Stability often matters more than the value: a steady 50 ms plays better than a ping swinging between 20 and 100 ms.
Does Wi-Fi cause lag in Fortnite?
Wi-Fi doesn't necessarily raise average ping, but it adds jitter and micro packet loss. In Fortnite, where every action sends a packet, those variations turn into teleporting and unregistered shots.
Measure before you change
Change one setting, play a few matches, compare. It's the only method that tells a real gain from an impression.
Try Latence on Windows