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.
Which storefront context matters
Documented Kingdom Come: Deliverance PC launchers/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. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Steam Cloud, GOG Galaxy, Epic, EA, and Xbox cloud support are documented depending on storefront. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is Windows: %USERPROFILE%Saved Gameskingdomcomesaves; the known file or folder pattern is Profile/campaign save files below the saves tree; configuration profiles live separately under Saved Gameskingdomcomeprofilesdefault.. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
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. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
A save can depend on the game version, DLC, or mod state. Restoring the file alone does not reproduce every external dependency. If progress disappears or rolls back, If a restored save refuses to load, compare game build/DLC/mod state and check cloud synchronization before assuming the save bytes are damaged. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
Verification context: Reviewed against current PCGamingWiki Kingdom Come: Deliverance save and profile paths.