Dark Souls III is a profile-container game: DS30000.sl2 can hold multiple characters, so copying it is not the same as exporting one slot. Manual backups remain especially important because players should not treat launcher sync as a guaranteed recovery system. Archive the full account-ID directory at important milestones. If you later experiment with a character manager or editor, keep the untouched original separate from every generated copy.
Which storefront context matters
Documented Dark Souls III PC launchers/storefronts: Steam. The account-ID directory is part of the profile. The save location is separate from the game installation directory. 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
Do not rely on Steam Cloud as the only backup for Dark Souls III; current community reports continue to emphasize local manual backups. 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%DarkSoulsIII<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/374320/pfx/; the known file or folder pattern is DS30000.sl2. 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 DS30000.sl2, preferably by archiving the full account-ID folder, before major progression, mods, or migration. 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
Replacing DS30000.sl2 replaces the profile container containing multiple character slots. Character-level import/export is a separate game-specific operation. If progress disappears or rolls back, If a migrated file is ignored, restore the original and confirm the account folder and game version before attempting identity edits or third-party conversions. 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: The AppData account-folder location was reviewed against current PCGamingWiki coverage. DS30000.sl2 naming and the practical lack of dependable Steam Cloud backup are corroborated by long-running PC community documentation.