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.
Identify the exact save you intend to edit
The researched Kingdom Come: Deliverance PC save location is Windows: %USERPROFILE%Saved Gameskingdomcomesaves. Known file/folder pattern: Profile/campaign save files below the saves tree; configuration profiles live separately under Saved Gameskingdomcomeprofilesdefault.. Storefront 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. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
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. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud, GOG Galaxy, Epic, EA, and Xbox cloud support are documented depending on storefront. 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 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. File-extension context: No single extension is sufficient to identify every relevant save record. Compatibility note: A save can depend on the game version, DLC, or mod state. Restoring the file alone does not reproduce every external dependency. 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, 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 restored save refuses to load, compare game build/DLC/mod state and check cloud synchronization before assuming the save bytes are damaged. Return to the untouched backup before trying another change.
Verification context: Reviewed against current PCGamingWiki Kingdom Come: Deliverance save and profile paths.