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.
Choose the correct backup boundary
For Dark Souls III, the researched PC save location is Windows: %APPDATA%DarkSoulsIII<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/374320/pfx/. The known save file or folder pattern is DS30000.sl2. Copy DS30000.sl2, preferably by archiving the full account-ID folder, before major progression, mods, or migration. 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 directory is part of the profile. The save location is separate from the game installation directory.
Account for cloud saves
Do not rely on Steam Cloud as the only backup for Dark Souls III; current community reports continue to emphasize local manual backups. 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 standard PC profile uses one DS30000.sl2 container under the account-ID folder. Multiple characters are stored inside that container rather than as separate files. Compatibility note: Replacing DS30000.sl2 replaces the profile container containing multiple character slots. Character-level import/export is a separate game-specific operation. 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 migrated file is ignored, restore the original and confirm the account folder and game version before attempting identity edits or third-party conversions. 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: 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.