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.
For this PC reference, the documented storage is Windows: %USERPROFILE%AppDataLocalLowIronGateValheim. The known file or folder pattern is characters_local/worlds_local for explicit local saves; .fch character and .db/.fwl world pairs. 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.
Backup guidance: 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. Steam Cloud can hold cloud saves separately from *_local folders; move/copy only through a workflow that preserves the intended local-versus-cloud state. Launcher and cloud context matters because 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.
Compatibility and recovery should stay conservative. 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 expected progress is not visible, 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. SaveEditor.com only labels a game-specific editor as available when a separate linked Tool has a verified operational runtime; this reference page by itself is not an editor claim.