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.
Start with the least destructive explanation
When Dark Souls III progress appears missing, first verify the active PC location: Windows: %APPDATA%DarkSoulsIII<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/374320/pfx/. Expected files/folders: DS30000.sl2. Many apparent save failures are actually profile, storefront, path-redirection, or cloud-selection problems rather than damaged game data.
Preserve every surviving copy
Copy DS30000.sl2, preferably by archiving the full account-ID folder, before major progression, mods, or migration. Before renaming, moving, replacing, or opening candidate backups, copy them outside the live directory. Do not use the only surviving file as the test specimen for repair or editing.
Check launcher and cloud state
Storefront context: Steam. The account-ID directory is part of the profile. The save location is separate from the game installation directory. Cloud notes: Do not rely on Steam Cloud as the only backup for Dark Souls III; current community reports continue to emphasize local manual backups. A sync client can reintroduce an older or newer version after a manual restore, so recovery work should keep local and cloud copies conceptually separate until the wanted progress is confirmed.
Use format and compatibility clues
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. Replacing DS30000.sl2 replaces the profile container containing multiple character slots. Character-level import/export is a separate game-specific operation. If the file exists but is ignored, compare the complete directory structure, slot/profile naming, game edition, mods/DLC, and any companion metadata. Do not assume an extension change or generic checksum tool can repair a game-specific container.
Game-specific troubleshooting
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 a known-good backup works, preserve it and create a fresh in-game save before further experiments. If no copy works, prefer read-only inspection and source-backed game-specific tooling over repeated writes.
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.