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.
Prepare the source PC
On the source system, identify the actual Baldur's Gate 3 save root: 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 expected file/folder pattern is <save-folder><save-name>.lsv. 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, GOG Galaxy. The same Larian profile hierarchy is used across desktop platforms, with OS-specific base directories. Steam also exposes a remote cloud area. 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
Copy the entire Story directory or selected complete save folders. For heavily modded campaigns, also keep the mod configuration required by that campaign. 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 is documented. Larian account cross-save can synchronize a limited set of recent saves across supported PC storefronts/platforms. 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
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. Compatibility note: An .lsv can be structurally valid but still depend on mods or game versions that are not present on the destination system. If the destination does not see the transferred progress, 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. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Windows, macOS, Linux, Steam remote/cloud, and Larian cross-save notes were reviewed against current PCGamingWiki coverage.