Kingdom Come: Deliverance II preserves the useful Windows Saved Games convention but moves into its own kingdomcome2 tree. That separation should be respected during backups: a similarly named save from the first game is not evidence of compatibility. The cloud situation also differs by storefront, with current PCGamingWiki coverage noting a GOG Galaxy cloud limitation. SaveEditor therefore recommends a local dated copy even for players who normally rely on cloud synchronization.
Which storefront context matters
Documented Kingdom Come: Deliverance II PC launchers/storefronts: Steam, Epic Games Launcher, GOG, Microsoft Store. Do not restore first-game files into kingdomcome2 because the directory naming reflects a separate generation. GOG users should not assume Galaxy will provide a cloud backup for this title. 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, Epic cloud, and Xbox Cloud are documented. PCGamingWiki notes GOG Galaxy cloud is unavailable due to its cloud-save limit. 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 Gameskingdomcome2saves; the known file or folder pattern is Save files beneath the kingdomcome2 saves tree; profile XML remains under Saved Gameskingdomcome2profilesdefault.. 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 kingdomcome2saves locally even if cloud synchronization is enabled. Keep profilesdefault separately if configuration preservation is also important. 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
The sequel’s saves are version-sensitive and should be kept with notes about patches/DLC/mods. First-game save compatibility is not implied by the similar folder structure. If progress disappears or rolls back, If a save disappears after switching storefront or machine, inspect the local Saved Games path first and confirm whether the cloud service actually supports this edition/storefront. 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 II save paths and cloud-support notes.