Patch 7 turned modding in Baldur’s Gate 3 from a PC-only experiment into a supported, cross-platform feature. Larian Studios introduced an in-game Mod Manager, a free Baldur’s Gate 3 Toolkit for creators, and a curated path to consoles and Mac. This primer explains how to install mods safely, how the verification system works, and where the console boundaries sit.

What changed

Before Patch 7, Baldur’s Gate 3 players relied on third-party tools. Patch 7, released on PC in September 2024 and on console and Mac in October 2024, added official modding support through mod.io. By the time the patch had been live for roughly a month, players had uploaded more than 1,000 mods and generated over 15 million downloads through the official pipeline.

The official system has two halves:

  • The in-game Mod Manager lets players browse, download, install, enable, and update mods without leaving the game.
  • The Baldur’s Gate 3 Toolkit is a separate, free download on Steam for PC players who want to create or edit mods. It is not available on console or Mac.

Larian’s stated goal is to improve compatibility and make supported mods work wherever the game is played, while still allowing unsupported mods to exist outside the pipeline. The studio has been clear that it will not prevent third-party modding, but it can only offer direct support for mods that move through its official channel. Hotfix #26 and Hotfix #27, released alongside Patch 7, refined the manager’s filters, login flow, and download behavior across platforms. By the time console support went live, around 69 mods had already passed internal testing for console and Mac.

How it works

Installing mods on any platform

  1. Open the Mod Manager from the main menu and accept the terms.
  2. On the Browse tab, filter or search for a mod.
  3. Read the description carefully. Some mods require a separate dependency, such as ImpUI, to function.
  4. Download the mod. If dependencies are listed, the manager should enable them automatically.
  5. Go to the Installed tab, confirm the mod is checked, and start playing.

Mods downloaded through the official manager are tied to your mod.io account. They can be updated directly from the Installed tab when a new version appears. The manager also supports reporting a mod from its details page if it violates guidelines.

Curated versus unsupported mods

Mods uploaded through the Toolkit go through Larian’s checks before appearing in the in-game browser. On console and Mac, an additional internal curation round decides which PC mods can be made available: the community team reviews a mod against the modding guidelines, then sends batches through internal testing of basic functionality, usability, and stability. Mod authors can request console release during upload, and Larian has noted that technical limitations on certain platforms mean some PC mods will not be eligible for Mac or console at all.

As a result, mods that rely on level editing, story or dialogue changes, cinematic edits, or heavy local gameplay adjustments tend to stay on PC, where the Toolkit offers the most flexibility. Cosmetic mods, dice skins, equipment, UI helpers, and quality-of-life tweaks are the most common approved types on console. NSFW content and heavy scripting generally stay on PC or outside the official pipeline entirely.

Multiplayer, saves, and the Verification Window

When you load a save that uses mods, or join a multiplayer session, the game opens a Verification Window. It checks whether your installed mods match the save or the host’s setup and offers actions such as:

  • Download a mod you are missing.
  • Enable a mod that is installed but turned off.
  • Update or Downgrade a mod to match the session version.
  • New Mods lists mods you have enabled that the session does not use.
  • Third-Party lists mods that did not come from the official browser.

If you use cross-saves between PC and console, only curated mods—the ones approved for console and Mac—will load on the console side. A PC save with non-curated mods cannot be loaded on console until those mods are removed or disabled.

Creating mods on PC

The Toolkit is downloaded from Steam as a separate tool. It requires the BG3 Toolkit Data DLC to be enabled on the base game, and Larian recommends roughly 160 GB of free space. Inside the Toolkit, mod authors can create new items, classes, subclasses, spells, dice skins, and other assets, then publish directly to mod.io. Published mods go through moderation and stability checks before appearing in the in-game browser.

Patch 8 expanded Toolkit functionality by adding partial level editing for certain template types—items, characters, and triggers—while still blocking changes to static terrain, buildings, and core dialogue. New playable races were also flagged as unsupported on console due to technical constraints. Mod authors should read the updated modding guidelines before publishing, because each platform carries its own approval rules.

Console limits

Consoles have hard file-handling limits compared with PCs. In November 2024, Larian introduced a 100-mod cap on PlayStation and Xbox through Hotfix #29. Saves with more than 100 active mods cannot be loaded on console until the count is reduced. This limit also matters for PC players who use cross-saves: if you intend to move a save to console, keep the mod list under 100 and ensure every mod is tagged as available on console and Mac.

Larian also warned that general instability rises with mod count, particularly on console. Players who install more than they actively use are more likely to see slow loading or crashes. The recommendation is to keep only the mods you actually want in your load order.

Build path

For players new to modding, the safest way to start is a small, curated list rather than a large stack.

  1. Begin on a new or backed-up save. Mods can change save behavior, so keep an unmodded copy of any campaign you care about.
  2. Read descriptions and check dependencies. Look for the “Available on PC, Mac, and Console” tag if you play across platforms. Download dependency mods first.
  3. Prefer recently updated mods. Patch 8 in April 2025 added new subclasses, cross-play, and further Toolkit changes, so older mods may need an update from the author.
  4. Use the Installed tab to isolate problems. If the game crashes or a save fails to load, disable mods one by one to find the culprit.
  5. Report guideline violations through the mod listing. Larian cannot fix individual community mods, but it can remove listings that break platform rules.
  6. Keep achievements in mind. Achievements are automatically disabled while mods are active, so finish trophy or achievement goals on an unmodded save if that matters to you.

If you want to create mods, start with the Toolkit’s official documentation and test your work locally before publishing. Script-heavy or NSFW mods may be allowed outside the official pipeline, but they will not pass moderation for console and will not receive official support. Local-only mods can still be managed in the manager’s load order, but they will not benefit from automatic updates or multiplayer synchronization.

A useful vetting habit is to check the mod’s upload date, version number, and comment section before downloading. Mods that have not been updated since a major patch are more likely to cause load failures or missing content. If a mod adds a new class, subclass, or weapon, verify that it works in your current patch by loading it on a throwaway save first. Pay attention to load order only when a mod’s description mentions it; otherwise the manager handles ordering automatically.

What it means

Official mod support gives Baldur’s Gate 3 a more stable modding ecosystem than the third-party-only era, but it comes with trade-offs. PC players keep the most freedom: they can use the Toolkit, run third-party mods alongside supported ones, and manage load order through the manager. Console players gain access to a curated subset of PC mods and an easier installation flow, but they must accept the 100-mod cap, slower approval of new mods, and the inability to use unapproved content.

Cross-play, added in Patch 8, also affects mod use. Everyone in a cross-play lobby must run the same mod versions, and hosts can filter the browser to show only console-compatible mods. The pipeline therefore rewards players who build compact, curated mod lists and who check platform tags before committing to a long campaign.

For most players, the practical summary is simple: use the in-game Mod Manager for supported content, keep console lists under 100 mods, and treat third-party or script-heavy mods as PC-only experiments that may need to be disabled before cross-save or multiplayer sessions.