How to Install Baldur's Gate 3 Mods: A Complete Guide

Modding Baldur's Gate 3 can dramatically expand what's already one of the most content-rich RPGs ever made — adding new classes, visual overhauls, quality-of-life fixes, and mechanics that Larian Studios never shipped. But installing mods isn't always a single-click process, and the right approach depends on how you're playing, where you bought the game, and how comfortable you are tinkering under the hood.

What BG3 Modding Actually Involves

At its core, modding means adding or replacing game files — either loose files dropped into specific folders, or packaged .pak files that the game engine reads at launch. Baldur's Gate 3 uses the Divinity Engine, and most mods are distributed as .pak files designed to sit in a specific directory.

Larian introduced official mod support through the in-game Mod Manager with Patch 7 (released in late 2024). This changed the landscape significantly. Before that, virtually all modding happened through third-party tools. Now there are two main installation paths, and which one works best for you depends on your situation.

The Two Main Installation Methods

1. The In-Game Mod Manager (Official)

Larian's built-in manager integrates directly with the game's main menu. You can browse, download, and activate mods without ever leaving BG3. This system pulls from a curated mod portal and handles load order automatically for supported mods.

How it works:

  • Launch BG3 and navigate to the Mods tab in the main menu
  • Browse or search for mods from the official portal
  • Click to install — the game handles file placement
  • Enable or disable mods from the same menu before starting a session

This method is the most accessible entry point, especially for players who've never modded a game before. The tradeoff is that the library is smaller than what's available on community platforms.

2. Manual Installation via BG3 Mod Manager (Community Tool) 🛠️

The BG3 Mod Manager is a standalone third-party application widely used by the modding community. It gives you direct control over load order — which matters because conflicting mods can crash the game or produce weird behavior when loaded in the wrong sequence.

Basic process:

  1. Download the BG3 Mod Manager from its repository (typically GitHub or Nexus Mods)
  2. Download your chosen mods — usually as .pak or .zip files — from Nexus Mods or community sites
  3. Open the Mod Manager and point it to your BG3 installation directory
  4. Drag mods from the right (inactive) panel to the left (active) panel
  5. Adjust load order manually — mods lower in the list generally load last and take priority
  6. Click Export Load Order to Game to apply your setup
  7. Launch BG3 normally

The mods themselves are stored in: %LocalAppData%Larian StudiosBaldur's Gate 3Mods

This folder is where .pak files need to live, whether you place them manually or let the Mod Manager do it.

Key Variables That Affect Your Setup

Not every mod works the same way on every system or with every other mod. A few factors shape the experience significantly:

VariableWhy It Matters
Game versionMods built for pre-Patch 7 may need updates to work correctly with current builds
PlatformPC (Steam or GOG) is fully moddable; console mod support is available but limited to official portal mods only
Other active modsLoad order conflicts are the most common source of crashes
Technical comfort levelManual .pak installation requires some file system navigation
Mod typeScript extender mods need an additional dependency (BG3 Script Extender) installed separately

Script Extender Mods: An Extra Layer

A subset of mods — particularly those that add complex mechanics, new spells, or expanded UI features — require the BG3 Script Extender (often abbreviated SE or BGSE). This is a separate tool that expands what mods can access in the game engine.

Installing it means:

  1. Downloading the Script Extender and placing its files in the BG3 game directory (where bg3.exe lives)
  2. Launching the game through the extender's launcher, or configuring Steam to run it automatically

If a mod page lists Script Extender as a dependency, skipping this step will either cause the mod to fail silently or break your session.

Common Issues and What Causes Them

  • Mods not appearing in-game: The .pak file may be in the wrong folder, or the mod isn't enabled in your load order
  • Game crashing on launch: Usually a load order conflict or an outdated mod that hasn't been updated for the current patch
  • Missing textures or broken visuals: Often signals a mod dependency that wasn't installed
  • Achievements disabled: 🎮 Using mods — even through the official manager — disables Steam/GOG achievements in your current save

Multiplayer and Mod Compatibility

If you're playing co-op, all players in a session generally need the same mods installed and active. Mismatched mod setups are a common reason multiplayer sessions fail to connect or desync during play. The host's load order typically takes precedence, but requirements vary by mod.


How smooth the whole process feels depends heavily on the combination of mods you're working with, whether you're on PC or console, and how many mods you're stacking on top of each other. A single cosmetic mod via the official manager is a completely different experience from managing a 40-mod build with Script Extender dependencies — and both are valid approaches depending on what you're actually trying to get out of the game.