Skip to content
SPYLD.Gaming
PC PerformanceStep-by-step

Apex Legends Performance Guide — Frames, Stutter and Latency

Apex has three separate performance problems that look identical. Here's how to tell which one you have.

DODan OkaforCompetitive & Settings Editor· 3 min read·Published · Reviewed by Marcus Reyes

The short answer

Apex Legends performance problems split into frame rate limits, engine stutter from shader and streaming issues, and server-side latency that no local setting fixes. The most effective settings changes are an external frame cap below your refresh rate, texture streaming budget matched to available VRAM, and disabling all overlays, while rubber-banding and delayed hit registration are network problems requiring different diagnosis.

Verified and last updated August 12, 2026.

Time needed
18 min
Difficulty
Intermediate
Read time
3 min

Apex has a reputation for running badly, and part of that reputation comes from three different problems being described with the same words.

Which one do you have?

Low frame rate — consistently fewer frames than expected. Stutter — frame rate is fine but the game hitches. Rubber-banding — you move and snap back, shots do not register. The third is a network problem and no graphics setting touches it.

Step 1: Three problems that look the same

Apex problems by category

Step 2: Texture streaming budget

The most impactful Apex-specific setting and the one most commonly set wrongly.

Setting it higher than your available VRAM does not give you better textures — it forces streaming across the PCIe bus, which produces heavy hitching. People set it to maximum expecting quality and get stutter.

Check your VRAM in an overlay during a match 10 min

Not the card's rated capacity. What is actually free while the game runs.

Set the budget one step below what fits 2 min

Headroom prevents the edge case where a busy fight pushes past the limit.

Test in a close-quarters fight, not the lobby 10 min

Streaming pressure is highest when many players and effects are on screen.

Step 3: Cap frames outside the game

An external limiter produces steadier pacing than the engine's own cap.

Set it three to five below your refresh rate, and combine with correctly configured variable refresh rate — G-Sync or FreeSync on, driver V-Sync on, in-game V-Sync off.

This matters more in Apex than most games because the frame rate swings enormously between an empty ridge and a three-team fight in a building.

The rest of the settings

Competitive Apex configuration

On launch options

Most widely shared lists are outdated and some are harmful — flags that no longer exist, or that force settings you do not want.

The genuinely useful ones are limited to selecting the correct rendering API for your hardware and skipping the intro videos. Ignore the long copied lists.

If it is the network

Wired if at all possible. Apex is sensitive to latency variation rather than absolute latency, and Wi-Fi jitter shows up as exactly the rubber-banding people blame on settings. The mechanics are in Wi-Fi vs Ethernet for gaming.

Key takeaways

    Frequently asked questions

    What texture streaming budget should I use?

    Match it to your available VRAM with headroom, not to the highest option. Setting it above what your card has forces streaming from system memory across the PCIe bus, which produces exactly the hitching people are trying to fix. On an 8 GB card a mid setting is usually right; on 12 GB or more you can go higher. Watch VRAM usage rather than guessing.

    Why does Apex stutter even on strong hardware?

    Usually shader compilation after updates, texture streaming set too high for the available VRAM, or an overlay injecting into the render pipeline. The engine is also sensitive to background CPU load in a way some others are not. Work through those three before considering hardware, because a powerful machine with the streaming budget set wrongly stutters badly.

    Is rubber-banding a settings problem?

    No, and no graphics setting will fix it. Rubber-banding, delayed hit registration and players teleporting are network and server symptoms. The useful checks are a wired connection, avoiding Wi-Fi entirely if possible, and confirming whether the problem occurs across all servers or only one. Some of it is server-side and outside your control entirely.

    Should I use the in-game frame rate limiter?

    An external limiter is generally more consistent, producing steadier frame pacing than the engine's own cap. Set it three to five frames below your refresh rate and combine it with correctly configured variable refresh rate. The consistency matters more in Apex than in many games because the frame rate swings widely between open terrain and close-quarters fights.

    Do launch options still help?

    Some do and most of the widely shared lists are outdated or actively harmful. The genuinely useful ones are limited to setting the correct rendering API for your hardware and disabling the intro videos. Long copied lists of launch options frequently include flags that no longer exist or that force settings you do not want.

    About the author

    DO
    Dan Okafor

    Competitive & Settings Editor

    Dan played CS:GO semi-professionally in a regional ESEA Main roster between 2017 and 2020, and has hit Radiant in VALORANT in three separate acts. He now spends most of his competitive energy on the unglamorous side of the game: input latency, sensitivity consistency and warm-up routines that actually transfer.

    ESEA Main roster (CS:GO), 2017–2020VALORANT Radiant, 3 acts2,400+ hours of tracked aim-training data
    All articles by Dan

    Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.

    Keep reading