Best PC Settings for Higher FPS in Warzone, Fortnite, and Apex in 2026
For Warzone, Fortnite, and Apex, the safest first pass is a capped, repeatable test run: lock the monitor refresh path, lower the few settings that hit frame time hardest, and record 1% lows before changing drivers, BIOS, or overclocking.
How this page was reviewed
Pages are reviewed around game version, driver version, 1 percent lows, shader behavior, and whether a tweak is reversible.
Reader problem
This page is kept narrow around best PC settings for higher FPS for readers who need a practical answer rather than a broad overview.
Decision boundary
The site does not promise universal FPS gains; it shows readers how to isolate likely bottlenecks and avoid risky changes.
Evidence checklist
The draft is checked for render scale discipline, shadow trimming, VRAM monitoring, and frame cap logic before it is treated as ready for readers.
Refresh trigger
Driver, DLSS/FSR, shader-cache, and Windows game-setting pages get priority after major GPU or game updates.
I use this order when a mid-range PC feels fine in the menu but gets rough once a real match starts: record one baseline, cap the frame rate, trim the GPU-heavy visual settings, then check whether the 1% low and frame-time graph actually improved. Average FPS alone is a poor judge here. A system can show 145 FPS on the counter and still feel bad if the graph keeps throwing 35 ms spikes during drops, builds, smoke, or late-circle fights.
For a practical reference point, think of a Ryzen 5 5600 or Core i5-12400F, RTX 3060 Ti or RX 6700 XT, 16 GB of dual-channel RAM, and a 144 Hz or 165 Hz display. That class of PC should not need risky BIOS changes to make Warzone, Fortnite, or Apex playable. If it does, something earlier in the chain is usually wrong: render scale drifted above native, VRAM is full, the frame cap is fighting V-Sync, or the game is rebuilding shaders after an update.
Build a baseline before touching settings
Pick one scene you can repeat. In Fortnite, use the same Creative island or a consistent early-match route. In Apex, use the Firing Range plus one actual match on the same server region. In Warzone, use a short drop route that includes a building interior, a vehicle pass, and an outdoor fight if you can repeat it safely. Run it once without changing anything and write down average FPS, 1% low, GPU usage, VRAM use, CPU usage, and the worst frame-time spike you see.
You do not need a lab bench. CapFrameX, MSI Afterburner with RivaTuner, NVIDIA FrameView, or AMD Adrenalin's metrics overlay are enough. The important part is using the same scene twice. If you change the route, server, graphics preset, and driver on the same night, the numbers stop meaning anything.
- Record the monitor refresh rate and whether G-Sync, FreeSync, or V-Sync is enabled.
- Note the GPU driver version before updating or rolling back.
- Track 1% low FPS and frame time, not only the average FPS counter.
- Keep one screenshot or exported log from the baseline run.
Use a frame cap that gives the PC breathing room
The first setting I would change is the frame cap, not texture quality. If your uncapped run swings between 118 and 176 FPS on a 165 Hz monitor, the system is already telling you it cannot hold that ceiling. Try a cap around 141 FPS for a 144 Hz display or around 158 FPS for a 165 Hz display when using adaptive sync. If the game still spikes, drop the cap another 10 frames and test again.
This is not about making the number look lower. A sane cap can keep the GPU out of constant 99% load, which often improves mouse feel and makes frame pacing less erratic. In shooters, a steadier 135 FPS can feel better than a noisy 165 FPS that collapses every time effects, buildings, or smoke hit the screen.
Try first
In-game FPS cap slightly below your stable range, NVIDIA Reflex or AMD Anti-Lag if the game supports it, adaptive sync matched to the monitor.
Be careful
Driver-level caps stacked on top of in-game caps. They can help in some games, but double capping makes troubleshooting harder.
Avoid for testing
Changing monitor refresh, V-Sync, Reflex, frame generation, and driver caps all at once. You will not know which change fixed or hurt the run.
Trim the settings that hurt frame time first
For these three games, I would lower settings in this order: render scale or 3D resolution, shadows, volumetric effects, screen-space reflections, post-processing, then texture quality if VRAM is close to full. Textures are not always the villain. On an 8 GB card, high textures may be fine in Fortnite but rough in Warzone after several matches if the VRAM graph sits at the ceiling.
Keep anti-aliasing and image reconstruction readable. A blurry competitive setup is not automatically better. If DLSS, FSR, XeSS, or TSR is available, start with Quality or Balanced, then judge motion clarity around fences, foliage, nameplates, and thin UI lines. If you cannot track targets cleanly, the FPS gain is not worth much.
| Setting area | First test | What to watch |
|---|---|---|
| Render scale | Native to 90%, or DLSS/FSR Quality | Immediate FPS gain, but watch blur and UI shimmer |
| Shadows | High to medium or low | Often helps 1% lows in outdoor fights |
| Effects and volumetrics | Medium or low | Smoke, explosions, and storm effects should spike less |
| Textures | Only lower if VRAM is near full | Stutter after several matches, not just lower average FPS |
Game-specific starting points
In Warzone, VRAM behavior matters more than the menu preset suggests. Set the VRAM target conservatively, avoid max texture streaming on 8 GB cards, and test a few matches before deciding the setting is stable. If the first match feels fine and the third match gets rough, that is a different problem from a bad graphics preset.
In Fortnite, check rendering mode before anything else. Performance Mode, DirectX 11, and DirectX 12 can behave very differently across updates. If you play builds or crowded Creative maps, test the mode you actually use, not a quiet corner of the lobby. Shader compilation after a driver update can also make the first run look worse than the second.
In Apex, stable frame pacing usually comes from a clean cap, Reflex, sensible shadows, and avoiding a GPU that is pinned flat at full load. If mouse input feels heavy while average FPS looks fine, check GPU usage and frame-time spikes before blaming the mouse, USB port, or polling rate.
When not to spend money yet
Do not buy a new GPU because one game stutters after a patch. Do not add RAM because a single overlay shows high memory use without checking whether you are actually paging to disk. Do not replace a monitor because tearing appears while V-Sync, adaptive sync, and the frame cap are fighting each other. Those are expensive guesses.
Upgrade only when the logs point in the same direction across more than one test. If GPU usage is high, VRAM is full, and lowering textures or render scale clearly improves the 1% low, a GPU upgrade may be reasonable. If RAM use is near the limit and the system is touching the page file during traversal stutter, 32 GB may help. If the game sits on a nearly full SATA SSD and asset streaming causes spikes, storage cleanup or an NVMe move may solve more than another graphics preset.
Rollback notes before you close the page
Save the original preset, driver version, and frame cap. Most bad tuning sessions go sideways because the player changes six things, plays one good match, then cannot get back to the old setup when the next session feels worse. A useful settings pass should leave you with a short record: what changed, what improved, what got worse, and what you restored.
If the new settings only improve the built-in benchmark but make real matches feel worse, keep the real match result. Benchmarks are useful for repeatability, but shooters are played in messy scenes with network load, background voice chat, overlays, and sudden effects. The setting that survives that environment is the one worth keeping.
Site policies and support
If you need a correction, policy clarification, or privacy answer, use the contact and policy pages linked below. They remain accessible from every page on the site.