For Valheim, label backups as character or world and local or cloud. A world backup must keep the matching .db and .fwl together; copying one half is not a complete restore point.
Prepare the source PC
On the source system, identify the actual Valheim save root: Windows: %USERPROFILE%AppDataLocalLowIronGateValheim. The expected file/folder pattern is characters_local/worlds_local for explicit local saves; .fch character and .db/.fwl world pairs. Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.
Preserve storefront and profile identity
Documented storefronts: Steam, Microsoft Store. The active Steam, Microsoft Store installation determines which local profile and cloud copy can overwrite the save. Identify the storefront and account before restoring files. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.
Move the complete save boundary
Close Valheim, let the launcher finish any synchronization, then copy the complete documented save directory to a dated folder outside the live path. Preserve companion files rather than selecting only the newest-looking record. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.
Handle cloud sync deliberately
Steam Cloud can hold cloud saves separately from *_local folders; move/copy only through a workflow that preserves the intended local-versus-cloud state. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.
Check compatibility before blaming the transfer
Valheim distinguishes local files from cloud-managed characters/worlds. Local worlds use paired .db and .fwl files; both parts are required for a coherent world backup. Compatibility note: Treat saves as version-, storefront-, account-, and mod-sensitive unless the game or a separately verified migration workflow proves otherwise. A similar filename or extension is not evidence that two releases are interchangeable. If the destination does not see the transferred progress, If progress is missing after a restore, confirm the active Windows account, storefront/profile, cloud state, and exact directory first. Restore the untouched backup before experimenting with individual files or older autosaves. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Windows save location, file-boundary, launcher/cloud, and backup notes were reviewed against the linked game-specific references for Valheim. This Game Hub is documentation only and does not claim a new game-specific Save Editor.
Recorded Phase 40 evidence boundary
This Phase 40 entry is grounded in the researched PC save boundary for Valheim: Windows: %USERPROFILE%AppDataLocalLowIronGateValheim The recorded file or folder pattern is characters_local/worlds_local for explicit local saves; .fch character and .db/.fwl world pairs. These concrete identifiers are retained so backup, transfer, recovery, and editing preparation remain tied to the documented game/storefront context instead of a generic extension guess.