Find the save before you repair it
Apex Legends stores progress and settings in different places. Confusing the two is how people delete a working profile while trying to fix a graphics problem. Locate both, copy both, then work on a copy.
Save and configuration locations
SAVE PROFILE: Server-side progression
CONFIGURATION: %USERPROFILE%\Saved Games\Respawn\Apex\local\
BACKUP ORDER:
1. Copy the save folder while the game is fully closed.
2. Copy the configuration folder separately.
3. Zip both with a dated name before any repair. Steam Cloud conflicts
A cloud conflict appears when two machines both wrote a profile and Steam cannot decide which is newer. The safe sequence is: close the game, let Steam finish syncing, note the local file timestamp, then choose the local file deliberately rather than accepting the default prompt. Never launch a second machine while a sync is in progress.
Recover a corrupted Apex Legends profile
Verified recoveryWork from the backup, not the original.
- Copy the current profile folder to a dated backup.
- Restore the most recent known-good backup into a clean folder.
- Launch with Steam Cloud disabled for this title so the restore is not overwritten.
- Load the save, save once manually, close the game, then re-enable Cloud.
Launch options and the developer console
Most Modified Source builds accept a small, documented set of launch arguments. Keep the list short: a windowed or borderless flag when the display mode is stuck, a language override, and a safe-mode flag if the build provides one. Arguments that inject DLLs or disable integrity checks are not troubleshooting steps; they are a separate risk category.
If the build ships a developer console, bind it in the input settings rather than editing files. A console toggle written into the wrong configuration file can be overwritten on the next patch.
Verify the restore
Save integrity for Apex Legends
0 / 5 completeThe line to keep
A backup you have restored once is real. A backup you have only created is a hope. Test the restore before the patch that makes it necessary.
Did this fix work on Patch Season 28.1 — netcode and stability?
One click. No account. Your vote is stored in this browser and de-duplicated per file.
Verified against Season 28.1 — netcode and stability. Votes are local-only telemetry.
Apex Legends: bench questions
2 answersIs this Apex Legends fix safe for my current save?
How do I know the save files & console fix worked?
Save Files & Console
This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.
Apex Legends: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Apex Legends on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on Modified Source.
Apex Legends: Fixing Mouse Input, Packet Loss, and Frame-Time Jitter
A clean input and network troubleshooting path for Apex Legends, with a minimal Source-engine configuration.
Apex Legends: Shader Stutter, Frame Pacing & Modified Source Config Tuning
A measured stutter-hunting routine for Apex Legends: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Modified Source settings file to edit.