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.
Identify the exact save you intend to edit
The researched Dark Souls III PC save location is Windows: %APPDATA%DarkSoulsIII<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/374320/pfx/. Known file/folder pattern: DS30000.sl2. Storefront context: Steam. The account-ID directory is part of the profile. The save location is separate from the game installation directory. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Copy DS30000.sl2, preferably by archiving the full account-ID folder, before major progression, mods, or migration. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Do not rely on Steam Cloud as the only backup for Dark Souls III; current community reports continue to emphasize local manual backups. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
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. File-extension context: .sl2 Compatibility note: Replacing DS30000.sl2 replaces the profile container containing multiple character slots. Character-level import/export is a separate game-specific operation. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists Dark Souls III, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, 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. Return to the untouched backup before trying another change.
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.