For most players, the safest Baldur’s Gate 3 mod workflow is the official in-game Mod Manager introduced with Patch 7 and expanded through Patch
8. Open Mod Manager, find a supported mod, subscribe/download, verify dependencies, enable it in Installed, then start a clearly labelled modded campaign. Use third-party PC tools or manual files only when the feature you need is not available in the supported pipeline and you accept responsibility for load order, updates and platform compatibility.
Quick answer: use the in-game Mod Manager first in 2026
The most important Patch 8 correction is old ImpUI advice. Patch 8 moved many common UI capabilities into the base game/Toolkit. The current official ImpUI listing is marked NOT MAINTAINED and says it should be kept only when another mod still depends on it. “Install ImprovedUI first for every mod” is no longer a safe universal instruction.
The official Mod Manager Browse tab is now the safest starting point for supported mods on PC, Mac and console.
Official supported mods vs third-party PC mods
Swipe horizontally to view all columns.
| Route | Best for | Advantages | Maintenance cost / limits |
|---|---|---|---|
In-game Mod Manager / mod.io | Most users; PC/Mac/console-supported mods | One UI for browse, subscribe, enable, platform tags and supported multiplayer verification. | Catalogue is curated/supported; does not include every possible PC script/native mod. |
Third-party PC manager / Nexus ecosystem | PC-only features absent from official catalogue | Broader ecosystem, script tools, advanced mods and old projects. | Manual compatibility/load-order work; cannot be assumed console/Mac compatible. |
Manual file install | Very specific author instructions | Useful when the author explicitly requires a manual path/tool. | Highest user-error risk; updates and clean removal are your responsibility. |
Install your first supported mod
1. From the main menu, open Mod Manager.
2. Browse/search the supported catalogue. Read the description, platform availability, Patch 8 tag and dependencies before subscribing.
3. Subscribe/download the mod.
4. Open Installed and make sure the mod is enabled.
5. If a dependency is listed, install and enable the dependency too.
6. Start a new campaign or load a save that already expects this exact supported mod set.
Use category/platform filters before subscribing to a large list; supported does not mean every mod belongs in every save.
A mod appearing in Browse does not mean the current save is using it. The Installed list is where you confirm what is present/enabled. Before changing a long campaign, take a screenshot or export a record of the working list. That simple record is often the difference between restoring a save in ten minutes and guessing for an hour.
The Installed list is the campaign configuration you should document before adding, removing or updating a batch of mods.
A supported mod such as FaerunColors can be managed directly through the official installed-mod flow.
Installed tab: this is your actual campaign mod list / Dependencies and load order: do not “clean up” a dependency because it looks boring
If a content mod lists a dependency, install/update the dependency first.
Do not disable a dependency just because one launch happened to work without an obvious error.
When updating a stack, update shared frameworks/dependencies before content mods that consume them.
Avoid removing classes, races, spells, items or overhauls from a long-running save unless the author explicitly documents safe removal.; Add mods in small batches so a conflict has a small suspect list.
Dependency information is part of the install, not optional fine print.
Patch 8 added Toolkit/base support for UI functions that previously required mod frameworks: extra action resources, racial spells at level-up, race passives, scrolling through large creator lists, feat passives and radial customization. The official ImpUI page now says NOT MAINTAINED and recommends using it only when another mod still depends on it. Better Topbar, for example, still declares ImpUI as a dependency, so “ImpUI is obsolete” would also be wrong. The current rule is dependency-driven: install it when the selected mod requires it, not as universal ritual.
Patch 8 and ImpUI / Multiplayer: Mod Verification is the diagnostic screen
For a supported modded lobby, the host list is the contract. Patch 8’s Mod Verification can surface missing, disabled and version-mismatched mods and guide the joiner toward install/enable/disable/upgrade/downgrade actions. If console/Mac players are joining, every required mod must also support those platforms. Do not replace a missing mod with a similarly named fork unless the save/mod author explicitly says it is compatible.
Mod Verification tells you whether the mismatch is missing, disabled or version-related; read it before deleting local mod files.
When a modded save will not load
1. Stop. Do not mass-delete Mods or PlayerProfiles. Screenshot the exact error/missing-mod list.
2. Re-enable or reinstall the version the save expects where possible.
3. Update required dependencies and restart the game.
4. If the failure started after a new batch, disable only that batch in small groups to isolate the conflict.
5. If UI/hotbar elements vanish, fully update/remove the relevant UI mod before declaring the save corrupted.
6. Once the save opens, create a new manual save with a clear name before continuing experiments.
Achievements are disabled while mods are active. Keep at least one clearly labelled unmodded/vanilla save profile or test campaign when troubleshooting. A clean baseline answers the most important question: is the game itself failing, or is the current mod stack failing?
Patch 8 is the final major content patch, but hotfixes and platform/mod catalogue updates still happen. Before updating a heavily modded campaign, record the working list, read the game hotfix, read the authors’ current pages, and avoid updating thirty mods at once. A mod author’s “Patch 8 Tested” tag is a useful compatibility signal, not a lifetime warranty against future dependencies or another mod in your stack.
Console rules that PC guides often forget / Achievements and a clean vanilla baseline
Console users can only install curated supported mods through the official pipeline.
Manual/Nexus-only PC mods are not available on console.
The official console limit is 100 mods; a PC host must respect that if a console player is joining.
Patch 8 guidance states playable-race mods cannot be curated for console, so a PC character-creation stack may not be portable.
Patch/hotfix hygiene / FAQ
Do I need Nexus Mods to mod BG3 now? No. The in-game Mod Manager is the safest default for supported mods; third-party PC mods still exist for unsupported features.
Do I always need ImpUI? No. Install it when a selected mod still lists it as a dependency.
Can modded players cross-play? Yes with supported compatible mods and matching required lists/platform availability.
Why will my save not load after removing a mod? The save can reference content/classes/items/dependencies that no longer exist. Restore the expected mod and follow the author’s safe-removal guidance.
How many console mods can I run? The current console limit is 100.