Baldur’s Gate 3 makes the folder boundary important: each save folder contains the .lsv archive and related slot context. Backing up the whole folder avoids separating the main payload from supporting files. Campaigns can also be sensitive to mods, so SaveEditor.com treats mod compatibility as part of restoration rather than calling every failed load corruption. Larian cross-save is useful for recent saves, but a complete local archive is still the better long-term backup.
Start with the least destructive explanation
When Baldur's Gate 3 progress appears missing, first verify the active PC location: Windows: %LOCALAPPDATA%Larian StudiosBaldur's Gate 3PlayerProfilesPublicSavegamesStory | macOS: $HOME/Documents/Larian Studios/Baldur's Gate 3/PlayerProfiles/Public/Savegames/Story/ | Linux / Steam Play: $XDG_DATA_HOME/Larian Studios/Baldur's Gate 3/PlayerProfiles/Public/Savegames/Story/. Expected files/folders: <save-folder><save-name>.lsv. Many apparent save failures are actually profile, storefront, path-redirection, or cloud-selection problems rather than damaged game data.
Preserve every surviving copy
Copy the entire Story directory or selected complete save folders. For heavily modded campaigns, also keep the mod configuration required by that campaign. Before renaming, moving, replacing, or opening candidate backups, copy them outside the live directory. Do not use the only surviving file as the test specimen for repair or editing.
Check launcher and cloud state
Storefront context: Steam, GOG Galaxy. The same Larian profile hierarchy is used across desktop platforms, with OS-specific base directories. Steam also exposes a remote cloud area. Cloud notes: Steam Cloud is documented. Larian account cross-save can synchronize a limited set of recent saves across supported PC storefronts/platforms. A sync client can reintroduce an older or newer version after a manual restore, so recovery work should keep local and cloud copies conceptually separate until the wanted progress is confirmed.
Use format and compatibility clues
Each campaign save is stored in its own folder and includes an .lsv archive. Preserve the whole save folder rather than extracting only the archive when making a normal backup. An .lsv can be structurally valid but still depend on mods or game versions that are not present on the destination system. If the file exists but is ignored, compare the complete directory structure, slot/profile naming, game edition, mods/DLC, and any companion metadata. Do not assume an extension change or generic checksum tool can repair a game-specific container.
Game-specific troubleshooting
When a campaign save fails after migration, check the exact save folder, mods, and profile before assuming the archive is damaged. Cloud cross-save only covers supported recent saves, not every local backup. If a known-good backup works, preserve it and create a fresh in-game save before further experiments. If no copy works, prefer read-only inspection and source-backed game-specific tooling over repeated writes.
Verification context: Windows, macOS, Linux, Steam remote/cloud, and Larian cross-save notes were reviewed against current PCGamingWiki coverage.