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.
Identify the exact save you intend to edit
The researched Kingdom Come: Deliverance II PC save location is Windows: %USERPROFILE%Saved Gameskingdomcome2saves. Known file/folder pattern: Save files beneath the kingdomcome2 saves tree; profile XML remains under Saved Gameskingdomcome2profilesdefault.. Storefront context: 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. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Back up kingdomcome2saves locally even if cloud synchronization is enabled. Keep profilesdefault separately if configuration preservation is also important. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud, Epic cloud, and Xbox Cloud are documented. PCGamingWiki notes GOG Galaxy cloud is unavailable due to its cloud-save limit. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
The sequel intentionally uses a kingdomcome2 root, keeping it separate from the first game. Storefront cloud support differs; GOG Galaxy cloud is documented as unavailable because of its cloud save limit. File-extension context: No single extension is sufficient to identify every relevant save record. Compatibility note: 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. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists Kingdom Come: Deliverance II, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, 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. Return to the untouched backup before trying another change.
Verification context: Reviewed against current PCGamingWiki Kingdom Come: Deliverance II save paths and cloud-support notes.