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.
Which storefront context matters
Documented Baldur's Gate 3 PC launchers/storefronts: 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. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Steam Cloud is documented. Larian account cross-save can synchronize a limited set of recent saves across supported PC storefronts/platforms. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is 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/; the known file or folder pattern is <save-folder><save-name>.lsv. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
Copy the entire Story directory or selected complete save folders. For heavily modded campaigns, also keep the mod configuration required by that campaign. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
An .lsv can be structurally valid but still depend on mods or game versions that are not present on the destination system. If progress disappears or rolls back, 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. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
Verification context: Windows, macOS, Linux, Steam remote/cloud, and Larian cross-save notes were reviewed against current PCGamingWiki coverage.