That boss kill you finally earned, the build you spent three evenings tuning, the map you cleared one cave at a time - all of it lives in one small save file. When it vanishes, gets corrupted, or Steam Cloud decides an older copy looks more fashionable, the question is not philosophical: how do you restore Elden Ring progress before panic turns into a full reinstall?
On PC, recovery can work. But the order matters. Every time you launch the game or let a sync conflict resolve blindly, you risk replacing the good copy with the bad one. Treat your save like a cracked flask: stop using it, make copies, then work backwards.
First: do not launch Elden Ring again
If your character has disappeared, your progress rolled back, or the game says the save cannot be loaded, close Elden Ring and Steam. Do not make a new character “just to check”. Do not accept a Steam Cloud prompt without reading which version is newer. And definitely do not repeatedly boot the game hoping it will remember 80 hours of decisions it has already forgotten.
The immediate goal is simple: preserve every version still on your PC. Steam Cloud can be useful, but it can also sync an empty, damaged, or older local save across your devices with the confidence of a player invading at level 300.
Before changing anything, copy the whole Elden Ring save folder somewhere safe, such as your desktop or an external drive. Give the copy a name with the date and time. That way, even a bad recovery attempt is reversible.
Where Elden Ring keeps its PC save
For the Steam version, the usual local save location is:
`C:\Users\YourName\AppData\Roaming\EldenRing\`
Inside, you should see a folder made up of numbers. That is tied to your Steam account. Open it and look for `ER0000.sl2`, which is the main save file. You may also see `ER0000.sl2.bak`, a backup file created by the game.
If you cannot see `AppData`, turn on hidden items in File Explorer, or paste `%appdata%\EldenRing` into the address bar. Do not confuse this with the game installation folder. Reinstalling Elden Ring usually does not repair a damaged save because the important file is sitting elsewhere, quietly having a terrible day.
Copy the numbered account folder, not just the `.sl2` file. Keeping the whole folder gives you more options if you need to undo a rename or compare dates later.
Restore Elden Ring progress from the local backup
The `.bak` file is your first sensible recovery shot. It may contain an earlier version of your progress, although it is not guaranteed to be current or healthy. It depends on when the game last wrote it and what caused the problem.
With Steam and Elden Ring fully closed, make another copy of the current `ER0000.sl2` and `ER0000.sl2.bak` files. Then rename the damaged or unwanted `ER0000.sl2` to something obvious, such as `ER0000.sl2.bad`. Next, make a copy of `ER0000.sl2.bak` and rename that copy to `ER0000.sl2`.
Launch Steam, but keep an eye out for a Cloud conflict. If Steam asks whether to use local or cloud files, choose carefully. You want the version containing the save you are testing to remain in place, not to be immediately overwritten by another machine's version.
Start Elden Ring and check the character select screen. If your Tarnished is back, do not celebrate by immediately playing for six more hours. Exit cleanly, then copy the working save folder somewhere separate. You have just proved a recovery point works. Make it a proper backup before the game gets another chance to surprise you.
If the backup is also missing progress or fails to load, restore the copies you made earlier before trying anything else. A `.bak` is not a time machine. It is simply the most likely local spare tyre.
What if the backup is older than your lost progress?
An older backup can still be worth keeping, especially if it contains a character you thought was gone for good. But do not overwrite every other candidate save with it. Store each version in clearly named folders, such as `before-recovery`, `bak-test`, and `working-older-save`.
This is boring for roughly two minutes and dramatically less boring than losing the only recoverable version because three files all became called `ER0000.sl2` again.
Check Steam Cloud without letting it make things worse
Steam Cloud may hold a newer save, an older save, or the exact same broken file. The useful clue is the modified date and file size. If the cloud copy comes from before the disaster and looks plausibly sized for your playthrough, it may be the version you need.
The catch is that cloud syncing is designed for convenience, not forensic save recovery. It aims to make your devices agree. It does not know that last night's co-op session ended with a crash, a power cut, or a mate clicking the wrong thing.
If you play across a desktop, laptop, or handheld PC, check each device before launching the game on it. One machine might still have a healthier local copy. Disconnect that device from the internet first, copy its Elden Ring save folder, then inspect it. Do not let it connect and sync before you have taken the copy.
Also check your Recycle Bin and any backup software you already use. Windows File History, a synced documents folder, or an old manual archive can occasionally save the day. Search for `ER0000.sl2`, then sort results by date. Be suspicious of files created after the problem began.
When save corruption needs a different plan
If Elden Ring reports that the save data is corrupted, replacing the main file with a known-good backup is usually safer than trying random save editors or downloading somebody else's save. Tools promising a one-click fix can be useful in expert hands, but they can also alter progression flags, trigger anti-cheat concerns, or leave you with a technically loading save that behaves like it has been cursed by Mohg.
A downloaded save is not a clean replacement for your own. It may have a different Steam ID association, missing items, altered quest states, or progress you did not earn. More importantly, it does nothing to retrieve your character. It only gives you a different one wearing someone else's trousers.
If you use mods, keep that context in mind. Mod loaders, overhaul mods, item randomisers, and interrupted updates make save problems more likely. Restore the save first, then return the game to the same mod setup it had when that save was made. Changing several variables at once is how a recovery attempt turns into a group project nobody asked for.
Prevent the next lost run with version history
Manual copies work, right up until the day you forget to make one. Steam Cloud works, right up until it syncs the wrong thing. The real protection is version history: multiple dated save states, kept separately, so you can pick the one from before a bad session rather than merely hoping the latest copy survived.
Checkpoint64 is built for exactly this sort of save-file nonsense. It watches supported game save folders, records changes, and keeps prior versions so a bad overwrite is not the end of a 120-hour run. The free plan is actually free, and upgrades are pay once, keep it forever - no subscription, no “powered by AI”, no pretending a cloud sync conflict is a feature.
For Elden Ring, the useful habit is to preserve milestones: before a major mod change, before lending your PC to someone, before a risky co-op experiment, and after a session you would hate to replay. Automatic versioning means you do not need the discipline of a speedrunner with a spreadsheet. You just need a restore point that existed before the disaster.
Your Tarnished can die as many times as they like. Your save file should not get the same privilege.