Baldur’s Gate 3 Save Location: Transfer an LSV Campaign

A campaign transfer should preserve both your adventure and your ability to return to the original files. Before importing a Baldur’s Gate 3 save, identify the campaign, main character and story stage. Someone else’s checkpoint may reveal choices or events you have not reached. The procedure here concerns local Windows PC saves.

Community save download

Honour mode Save Files — hosted on Nexus Mods. This is an Honour-mode save collection, not a spoiler-free new campaign. File variants have specific patch requirements; compare the selected variant with your installation.

View download on Nexus Mods

This opens the original download page, not an instant download from SaveGamesDL. Follow the host’s sign-in and download prompts. Completion labels belong to the uploader; we have not independently verified completion, compatibility or file safety. Preserve your own saves before importing anything.

Open the Story save directory

Larian’s support documentation points to the Public profile’s Story directory. Enter this reference path directly into File Explorer to reach the folder without manually browsing hidden AppData directories. 1

%LOCALAPPDATA%\Larian Studios\Baldur's Gate 3\PlayerProfiles\Public\Savegames\Story

If the directory appears empty, verify the Windows account and active installation. Compare a newly created save with the files that change after you exit the game. Folder names alone are not a reliable description of every campaign, particularly when you have several backups or machines.

Treat each save folder as a unit

Larian requests the .lsv save file when investigating issues, and its loading-troubleshooting guide describes saves inside individual directories. Preserve the full directory for the checkpoint you are archiving, rather than separating companion files from the main save. 1 2

A backup should have a readable note identifying the campaign, game build and mod environment. Keep personal account information out of a publicly shared archive. A file sent privately to support is not automatically appropriate for public distribution.

Transfer a campaign with a rollback path

1. Note the campaign name, character and last known-good checkpoint, then close the game.
2. Make an independent copy of the active Story folder. Do not use the only backup as your working copy.
3. Extract the incoming archive somewhere temporary and identify the folder containing the intended save.
4. Compare the game version and any listed mod dependencies with your installation. Unknown requirements should remain marked as unknown.
5. Add the relevant save folder without deleting your previous campaign directories. Preserve any existing directory before resolving a duplicate name.
6. Load the campaign, inspect the party, inventory and quest state, then save to a separate test slot and reload it.

A successful load provides evidence about that checkpoint in that environment. It does not establish compatibility with every mod, patch or multiplayer arrangement.

Separate missing saves from loading failures

If the file never appears in the menu, check the active path, directory nesting and extracted contents first. If it appears but produces an error or crash, record the exact message, game build and recent mod changes. Larian’s loading guide is the primary reference for that second situation. 2

Avoid applying several troubleshooting changes at once. A useful report answers three questions: does an older save load, does a fresh save load, and what changed before the failure? Preserve the original problem file before trying a repair so that support can still investigate it.

Frequently asked questions