How to Install Baldur’s Gate 3 Mods Safely (Without Corrupting Your Save)

Wondering how to install Baldur’s Gate 3 mods safely? Use the free BG3 Mod Manager, install the Script Extender it prompts for, back up your save folder first, add mods one at a time, and fix the load order before you launch. The whole routine takes about 20 minutes — and it protects your 100-hour campaign from the corrupted-save nightmare that sends most players to Google.

Modding Baldur’s Gate 3 is tempting: new classes, better cameras, quality-of-life tweaks, whole new stories. It’s also the fastest way to watch a beloved Tav vanish into a “save file corrupted” error screen. The good news is that corrupted saves are almost never random. They follow patterns — and once you know the patterns, installing mods safely is a repeatable routine, not a gamble.

This guide does things in a different order than most modding tutorials. We fix load order and backups first, because that’s where 90% of mod disasters actually start.

What Do You Need Before You Install a Single BG3 Mod?

Two tools and one habit:

1. BG3 Mod Manager — the free, community-standard mod manager. It handles activation, load order, and exporting mods to the game.
2. BG3 Script Extender — many of the best mods need it. The Mod Manager offers to install it for you automatically; say yes.
3. The backup habit — your saves live in Documents\Larian Studios\Baldur's Gate 3\PlayerProfiles\Public\Savegames\Story. Copy that entire Savegames folder somewhere safe (or zip it) before you touch anything. This takes two minutes and has saved my campaigns more than once.

Also, download mods only from established sources — Nexus Mods with a free account is the standard home for BG3 mods. Random file mirrors and Discord uploads are how malware and broken .pak files reach your game.

How to Install Baldur’s Gate 3 Mods Safely: The 7-Step Routine

Follow these in order. Don’t skip step 5 — it’s the one everyone skips.

Step 1 — Install BG3 Mod Manager. Download it, extract it anywhere (it doesn’t need to live inside the game folder), and run it. Point it at your BG3 install when asked.

Step 2 — Let it install Script Extender. On first run, the manager prompts you to download the Script Extender. Accept. A surprising number of “my mods don’t work” problems are really “I never installed the Script Extender.”

Step 3 — Download your mods as .pak files. On Nexus Mods, grab the “Mod Manager Download” or the manual .pak file. Drop downloaded .paks into the manager’s Mods folder (it shows you where).

Step 4 — Activate mods on the right panel. Drag them from the left (inactive) list to the right (active) list. One mod at a time — activate one, and note what it changes.

Step 5 — Fix the load order. This is the critical step. BG3 loads mods top-to-bottom, and later mods overwrite earlier ones when they touch the same files. As a rule of thumb: frameworks and libraries first, small tweaks in the middle, big overhauls and anything that changes the UI or character creation last. The Mod Manager lets you drag entries up and down — take 60 seconds to get this right.

Step 6 — Export the load order to the game. In the manager’s menu, use “Export Order to Game.” Until you do this, BG3 won’t see your changes at all — another classic “my mods don’t work” cause.

Step 7 — Launch and test on a throwaway save. Start the game through the Mod Manager (so the Script Extender loads), then load a save you don’t care about — or start a quick new game. Walk around, open the menus your mods touch, and confirm nothing is broken before you load your real campaign.

Why Does Load Order Matter So Much in BG3?

Because BG3 mods rarely conflict loudly — they conflict quietly. Two mods that edit the same character-creation file won’t crash your game; the one loaded last simply wins, and you get a mysteriously missing race option or a UI panel that renders blank.

Here’s a concrete example from my own setup: I run 12 mods including a class pack, a camera tweak, and a UI overhaul. With the UI overhaul sitting above the class pack in the load order, the new subclasses simply didn’t appear at level-up — no error, no crash, just missing content. Moving the UI overhaul to the bottom of the list (so it loaded last) fixed it instantly. Sixty seconds of dragging, one “export order,” problem gone.

Learning how to install Baldur’s Gate 3 mods safely is mostly about learning this one step: when a mod “doesn’t work,” don’t reinstall it — reorder it first.

What Causes Corrupted Saves (and How Do You Prevent Each One)?

Corrupted BG3 saves almost always come from one of three mistakes:

1. Removing a mod mid-playthrough. This is the number-one save killer. If a save was created with a mod active, that mod’s data is baked into the save. Uninstall the mod and the save can’t resolve the missing references. Rule: never remove mods from an active campaign. If you must drop a mod, finish the campaign first — or start fresh.

2. Two mods fighting over the same files. This is the load-order problem from the section above. Prevention: keep your mod list short (under 15 is a good ceiling for stability), add mods one at a time, and test after each addition so you know exactly which one broke things.

3. Updating BG3 before your mods are ready. Big BG3 patches routinely break the Script Extender, and every mod that depends on it breaks with it. Prevention: after a patch drops, wait — usually a few days — for the Script Extender and your key mods to update before you launch the game. If Steam auto-updated on you, that’s what your save backup is for.

What Should You Do If a Mod Breaks Your Game?

Don’t panic, and don’t delete everything. Work the problem in order:

1. Disable half your mods and test. If the problem disappears, it’s in the disabled half — repeat until you’ve found the culprit (the classic binary search).
2. Restore your save backup from before the mod was added. This is why step zero was the backup.
3. Verify the game files in Steam (Properties → Installed Files → Verify integrity) to clean up anything a mod left behind in the game folder.
4. Check the mod’s page for a known conflict or a patch-day update before you reinstall it.

Once you know how to install Baldur’s Gate 3 mods safely, troubleshooting is just the same routine in reverse: nine out of ten “broken game” cases resolve at step 1 or 2 — the culprit is a single mod in the wrong load-order position or a mod that hasn’t been updated for the current patch.

Frequently Asked Questions

Are BG3 mods safe to use on an existing save?

Yes — as long as you follow the golden rule: back up the save folder first, and never remove a mod mid-playthrough. Adding mods to an existing campaign is fine; uninstalling them from one is where saves die.

Do Baldur’s Gate 3 mods disable achievements?

The Script Extender itself disables achievements, but the community has a tiny “achievements enabler” mod that restores them. Install it alongside everything else and your achievement hunting is unaffected.

Will my mods still work after a BG3 patch?

Probably not immediately. Major patches break the Script Extender, which breaks every mod that needs it. Wait for the Script Extender update (usually days, not weeks) before updating the game or launching your modded campaign.

Can you use mods on the Steam Deck?

Yes. BG3 runs great modded on the Deck — the Mod Manager works on Linux, though you’ll point it at the Proton-managed install path instead of the usual Windows one. The load-order and backup rules are identical.

That’s how to install Baldur’s Gate 3 mods safely — back up, add mods one at a time, fix the load order, and your campaign stays intact.