Skip to content
Game save workbench
Local-first tools No installation Support status shown
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Backups & Safety

How to Transfer Dark Souls III Saves to Another PC

Step-by-step Dark Souls III PC save-transfer guidance using the researched save root, complete backup boundary, storefront context, cloud-sync precautions, and compatibility checks before replacing destination data.

Editorial state
Reviewed
Reading time
3 min
Difficulty
Beginner
Last reviewed

Before you start

Close the game before copying or replacing saves. Keep one untouched backup outside the live save directory. Identify the storefront/launcher and active player/profile before changing files.

Key takeaways

What this guide establishes.

  • Use the documented save directory for the PC storefront/profile you actually play.
  • Back up the complete save boundary before restore, migration, repair, or editing.
  • Treat cloud synchronization as a separate copy that can overwrite a manual restore.
  • If progress is missing, verify storefront, account/profile, path redirection, and cloud state before assuming corruption.

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.

Prepare the source PC

On the source system, identify the actual Dark Souls III save root: Windows: %APPDATA%DarkSoulsIII<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/374320/pfx/. The expected file/folder pattern is DS30000.sl2. Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.

Preserve storefront and profile identity

Documented storefronts: Steam. The account-ID directory is part of the profile. The save location is separate from the game installation directory. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.

Move the complete save boundary

Copy DS30000.sl2, preferably by archiving the full account-ID folder, before major progression, mods, or migration. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.

Handle cloud sync deliberately

Do not rely on Steam Cloud as the only backup for Dark Souls III; current community reports continue to emphasize local manual backups. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.

Check compatibility before blaming the transfer

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. If the destination does not see the transferred progress, 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. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.

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.

Troubleshooting

If the expected result does not match.

Game-specific note: 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 destination PC does not see the save, re-check the receiving storefront/profile and whether cloud sync replaced the copied data.

Verification and sources

How this guide was checked.

Phase 27 generated this Guide from the reviewed Phase 23/24 Game Hub evidence for Dark Souls III. The save path, backup boundary, storefront context, and transfer risks were cross-checked against the same public references recorded on the Game Hub. No unsupported game-specific editor, checksum, encryption, or cross-platform conversion capability is implied.

  1. www.pcgamingwiki.com
  2. www.reddit.com