Competitive Fortnite settings
The Windows tweaks get the system out of the game’s way; these settings are what you set inside Fortnite itself. The goal is the lowest, most consistent input lag and a frame rate that does not lurch — not the prettiest scene. A few of these are genuinely debated, and this guide says so rather than pretending there is one true config.
FrameForge may have done part of this already
When FrameForge detects Fortnite, the fortnite tweak backs up your existing config, writes a competitive low-latency GameUserSettings.ini, and locks it read-only so a patch cannot quietly revert it. It also sets the Fortnite process priority to High. So some of the table below may already be in place. The in-game settings here are the ones you confirm or fine-tune by hand on top of that — and if you would rather set everything yourself, your backed-up original is right beside the locked file.
The settings
Video settings live in Settings → the monitor/Video tab. The first four are not really up for debate for competitive play; the last two are where reasonable players disagree, and the table is honest about it.
| Setting | Set to | Why |
|---|---|---|
| Rendering Mode | Performance | The Performance mode drops visual fidelity hard in exchange for the highest, most stable frame rate — the right call on an RX 580. If you dislike its flat look, DirectX 11 is the next-best for consistent frametimes; DX12 can stutter on older cards. |
| Vsync | Off | Vsync adds a frame or more of input lag. Off, always, for competitive. You handle tearing with the FPS cap below, not with Vsync. |
| Motion Blur | Off | Smears moving targets and adds nothing competitive. Off. (FrameForge’s config sets this already.) |
| Frame Rate Limit | a few FPS below your Hz | Counter-intuitive but real: capping a few frames under your monitor’s refresh rate gives the most consistent input lag — it keeps the GPU from running flat-out and stacking up latency. On a 144Hz panel, cap around 141–143. |
| View Distance | Medium / Far — debated | Honest take: it is debated. Lower can lift FPS, but too low pops in distant players late, which costs you info you want. Medium or Far is the common competitive compromise — not the lowest setting. Test it yourself. |
| Shadows / Effects / Post | Off / Low | Free frames with no competitive downside (Performance mode forces most of this anyway). Shadows off can even help you spot movement. |
| Anti-Aliasing | Off / Low | Cheap to leave low. Some players keep a light AA for cleaner edges on distant targets — a small, personal trade against frame rate. |
| 3D Resolution | 100% | Keep at 100%. Dropping it below 100 blurs the image and makes far targets harder to see — rarely worth the frames on this hardware. |
Why cap below your refresh rate
When the GPU renders as fast as it possibly can, frames queue up and the one you see is slightly stale — that is added input lag. A cap a hair under your monitor’s Hz keeps the pipeline shallow and the latency low and, crucially, consistent. Set the cap in-game; if you want belt-and-braces, you can also cap in the driver (Radeon Chill / Frame Rate Target) to the same number.
Set your monitor to its real Hz first
All of this assumes Windows is actually driving the monitor at its top refresh rate. If the diagnostics scan flagged you at 60Hz on a 144Hz panel, fix that in Display settings before you touch the in-game cap — otherwise you are capping against the wrong ceiling.
This is all above board
None of this is bannable. A GameUserSettings.ini is a normal config file every player edits through the menus — FrameForge just writes the same file you could write by hand, and never reads or writes game memory or touches Easy Anti-Cheat. Lower settings and an FPS cap are settings, not cheats.