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.
Which storefront context matters
Documented Elden Ring PC launchers/storefronts: 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. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Steam Cloud is documented. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is Windows: %APPDATA%EldenRing<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/1245620/pfx/; the known file or folder pattern is ER0000.sl2
ER0000.sl2.bak. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
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. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
Save files can contain multiple characters and account-specific data. Do not treat an individual character as a standalone file. If progress disappears or rolls back, 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. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
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.