How to Install Mods in Baldur’s Gate 3: Complete Guide

Baldur’s Gate 3 mods can change your game in simple, powerful ways. I’ve spent years modding RPGs and, honestly, BG3’s mod scene is one of the friendliest. I write this as someone who’s tested dozens of setups; you’ll get practical steps, why they matter, and a few hard truths (yes, some mods will break save files).

🎮 What you need before you install mods

First: match your mod to your game version. As of April 10, 2025 I still see people trying mods for older builds and wondering why they crash. Make a full backup of your Baldur’s Gate 3 folder (that’s C:Users[YourUser]AppDataLocalLarian StudiosBaldur’s Gate 3 on Windows). Why? Because a misplaced file can corrupt saves and cost hours of play—been there.

Quick checklist (do these):

• BG3 updated to the version the mod supports (check mod page date)
• At least 10 GB free space
• Admin rights on your PC
• Game folder backed up
• Your antivirus set to ignore the BG3 folder (some scanners quarantine .pak files)

📁 Mod managers vs manual install — what I use

Two routes: a manager (Vortex or BG3 Mod Manager) or manual. I’ve noticed Vortex simplifies lots of steps. The BG3 Mod Manager on GitHub automates many BG3-specific quirks. Manual install gives you absolute control, and sometimes that’s the only way to fix weird conflicts. Controversial? Yes: I think Vortex sometimes hides problems and you should learn manual methods anyway.

Feature	Vortex / BG3 Mod Manager	Manual
Ease	Easy — good for most users	Harder — needs care
Control	Good	Complete
Auto-updates	Yes	No
Conflict handling	Automated assistance	You must resolve

⚙️ Manual install — concise steps and why they matter

Why do mods go into a Mods folder? The game reads that directory at startup. Put the wrong file in the wrong place and the loader won’t see it.

Steps (simple):

1. Download the .pak file from a trusted site (Nexus Mods, GitHub, or the mod author’s page).
2. Open your BG3 folder: C:Users[YourUser]AppDataLocalLarian StudiosBaldur’s Gate 3Mods
3. If Mods doesn’t exist, create it. Copy the .pak in there.
4. Edit modsettings.lsx to include the mod UUID (copy exactly—one missing character causes trouble).

Example (add this block for each mod):

Why edit modsettings.lsx? Because the game references that file to know which mods to load and in what order. If you skip it, the mod might sit in the folder and do nothing.

🔧 Using BG3-specific mod managers

BG3 Mod Manager (find it on GitHub) detects your install and strips much of the guesswork out. Drag-and-drop, activate, and it writes the modsettings file for you. That’s handy. But watch this: managers can apply default load orders that won’t suit some complex mod lists.

Features most managers offer (and why they matter):

• One-click installs — saves time and reduces copying errors.
• Load order hints — because order affects which files override others.
• Profiles for different playthroughs — useful if you want a pure run versus a modded chaos run.

“If a mod doesn’t load, check the UUID and the XML formatting in modsettings.lsx first.” — practical rule I’ve used many times.

🚨 Troubleshooting common errors

Mod not loading? UUID missing or formatted wrong. Crashes on load screens? Likely a conflict. Missing textures? Maybe a dependency is absent. Ask yourself: did I read the mod page? It usually lists dependencies and compatibility.

Simple checklist to try first:

• Verify game files (Steam/GOG verify integrity).
• Remove the last mod you added.
• Test with a clean profile or save.
• Check mod pages for compatibility notes (authors often list tested versions).

Tip: disable mods one by one to find a conflict. Yes, it’s tedious. Unfortunately, there’s no magic button that always fixes conflicts.

💾 Load order basics (and why it matters)

Load order decides which mod wins when two mods change the same thing. My rule: load frameworks and script extenders first, then large gameplay overhauls, then small tweaks and cosmetics last. This isn’t absolute (depends on your niche), but it works most of the time.

Example order I use:

• Script extenders / frameworks
• Core gameplay overhauls
• Class/race content
• Items and equipment
• Visual/UI enhancements
• Final small tweaks

Why frameworks first? They expose hooks other mods call. If those hooks aren’t loaded, dependent mods fail.

🧭 Extra notes, odd tips, and a counterintuitive insight

Here’s the funny part: sometimes a tiny mod fixes a crash caused by a large overhaul because it patches one XML node the big mod left untouched. Oddly enough, small changes can matter more than the headline mod. One counterintuitive insight I’ll share — keep an unchanged save file from before you add mods. You’ll thank yourself.

Two debatable points (between us):

• I think mod managers are overused; they hide education. You should learn manual fixes.
• Some compatibility patches are unnecessary; a clean load order often solves the issue.

Also, expect exceptions. Not every method works for every mod. If something feels wrong, step back and read documentation—authors usually include the fix (honestly).

🛠 Final practical reminders

Backup before you change anything. Keep a simple log of installed mods and dates. If you update BG3 (and you will), check each mod’s page for an update date and compatibility notes—don’t assume it will keep working after a patch on April 10, 2025 or later.

One last small code tip (copy-paste carefully):

-- quick check: look inside Mods folder for .pak files
dir "C:Users%USERNAME%AppDataLocalLarian StudiosBaldur's Gate 3Mods"

Happy modding. If you want, tell me what mods you’re considering and I’ll point out likely conflicts (I’ve done this a lot). And yes — may your dice roll well!