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 Kingdom Come: Deliverance Saves to Another PC

Step-by-step Kingdom Come: Deliverance 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.

Kingdom Come: Deliverance uses Windows’ Saved Games folder, which is easier to back up than many AppData layouts, but its nearby profile/configuration directory can create confusion about what actually contains progress. SaveEditor separates the saves tree from profile XML and recommends copying them for different purposes. The page also emphasizes build, DLC, and mod context: a structurally intact save can still fail if the installation that loads it no longer matches the environment that created it.

Prepare the source PC

On the source system, identify the actual Kingdom Come: Deliverance save root: Windows: %USERPROFILE%Saved Gameskingdomcomesaves. The expected file/folder pattern is Profile/campaign save files below the saves tree; configuration profiles live separately under Saved Gameskingdomcomeprofilesdefault.. 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, GOG, Epic Games Launcher, EA app, Microsoft Store. Multiple storefronts are documented, but the normal Windows save root is shared. Cloud services can still restore a conflicting copy. 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

Back up the entire kingdomcomesaves directory. If preserving user configuration or mod-related profile settings too, copy profilesdefault separately so save data and settings remain distinguishable. 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

Steam Cloud, GOG Galaxy, Epic, EA, and Xbox cloud support are documented depending on storefront. 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 game keeps saves under the Windows Saved Games known folder rather than AppData. Configuration/profile XML is nearby but outside the saves directory, so backup scope can be chosen deliberately. Compatibility note: A save can depend on the game version, DLC, or mod state. Restoring the file alone does not reproduce every external dependency. If the destination does not see the transferred progress, If a restored save refuses to load, compare game build/DLC/mod state and check cloud synchronization before assuming the save bytes are damaged. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.

Verification context: Reviewed against current PCGamingWiki Kingdom Come: Deliverance save and profile paths.

Troubleshooting

If the expected result does not match.

Game-specific note: If a restored save refuses to load, compare game build/DLC/mod state and check cloud synchronization before assuming the save bytes are damaged. 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 Kingdom Come: Deliverance. 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