Elden Ring concentrates multiple characters in a single profile-level .sl2 container, so the practical backup unit is the whole account folder, not one character slot. The nearby .bak file is useful as a possible recovery point but should itself be backed up before experimentation. Because Steam Cloud can synchronize the same profile, restoration should be deliberate: close the game, preserve current local files, decide which copy is authoritative, then allow cloud sync to resume.
Choose the correct backup boundary
For Elden Ring, the researched PC save location is Windows: %APPDATA%EldenRing<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/1245620/pfx/. The known save file or folder pattern is ER0000.sl2
ER0000.sl2.bak. Copy ER0000.sl2 and its .bak companion with the game closed. For maximum safety, copy the entire account-ID folder to a dated backup outside AppData. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.
Make an offline copy before changing anything
Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher context: Steam. The account-ID subfolder is part of the save context. Avoid mixing files between Steam identities without a tool explicitly designed for that purpose.
Account for cloud saves
Steam Cloud is documented. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.
Restore without changing format assumptions
The Steam PC profile uses an account-ID folder and the main ER0000.sl2 container. The .bak companion can provide an additional recovery point, but it should be copied before trying to restore it. Compatibility note: Save files can contain multiple characters and account-specific data. Do not treat an individual character as a standalone file. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.
Recovery fallback
If a manual restore is immediately replaced, pause and inspect Steam Cloud synchronization instead of repeatedly overwriting the live folder. Preserve both local and cloud versions until you know which one is newer. If the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.
Verification context: Windows/Steam Play path and Steam Cloud support were reviewed against current PCGamingWiki coverage. Filename notes reflect the standard Steam PC profile layout.