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 Back Up Kingdom Come: Deliverance Saves

A game-specific Kingdom Come: Deliverance backup and restore workflow based on the researched save boundary, launcher/cloud behavior, compatibility notes, and recovery risks for the PC release.

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.

Choose the correct backup boundary

For Kingdom Come: Deliverance, the researched PC save location is Windows: %USERPROFILE%Saved Gameskingdomcomesaves. The known save file or folder pattern is Profile/campaign save files below the saves tree; configuration profiles live separately under Saved Gameskingdomcomeprofilesdefault.. 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. 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, 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.

Account for cloud saves

Steam Cloud, GOG Galaxy, Epic, EA, and Xbox cloud support are documented depending on storefront. 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 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. 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 restored save refuses to load, compare game build/DLC/mod state and check cloud synchronization before assuming the save bytes are damaged. 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: 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.

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 backup boundary, cloud context, and restore 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