BG3 Mods / mod.io
mod.io · The in-game routeBG3 mods on mod.io: how the in-game manager actually works
mod.io is the catalogue behind the Mods button in Baldur's Gate 3. It installs a lot, refuses a specific set of things, and explains none of it. Here is where players actually get stuck.
What mod.io is inside Baldur's Gate 3
BG3 mods on mod.io are the in-game kind. You open Mods from the main menu, browse the catalogue, subscribe to a mod, and the game downloads, installs and orders it for you. There is no file to unzip, no folder to find and no load order to arrange.
That is the whole difference between the two routes. mod.io is a catalogue the game reads directly. Nexus Mods is a file host you read yourself on PC. The first one is a shop front built into the game; the second one is a warehouse you do your own delivery from.
For a console player, the catalogue is the only route. For a PC player, it is the low-effort route that still covers a surprising amount of what people actually want to install.
What the in-game catalogue can install
The catalogue is curated, which shapes what you will find there. The bulk of it falls into a few groups:
- Interface and quality-of-life mods. Better tooltips, clearer inventory sorting, camera and party-management changes. These are the safest installs on the list because they touch presentation rather than game rules.
- Cosmetic and armour sets. New outfits, hair, faces, dyes. Cosmetic mods are the ones you can add and remove most freely, because a save does not depend on them loading.
- Class, subclass and item packs. New build options and new equipment. These change what the save tracks, so removing them from a campaign in progress is where trouble starts.
- Difficulty and encounter tweaks. Adjusting enemy scaling, rest rules or combat pacing.
- Small content additions. Extra encounters, extra vendors, extra dialogue options within the shipped game.
What the catalogue is not built for is anything that changes how the game runs under the hood, or anything that replaces the campaign. Those live on the other side of the line.
Why your Nexus mods never show up
The most common confusion is expecting the two catalogues to be one thing. They are not.
A mod appears in the in-game list only when its author uploads it to mod.io through Larian's mod tools. A mod on Nexus is a zip file whose contents go into a folder on your drive, with an entry written into the game's mod configuration so the game knows it exists. Neither system can see the other's installs. Subscribing to a mod in-game will not download the Nexus version, and dropping an archive into your mod folder will not make it appear in the Mods menu.
So when a guide tells you to install a mod the Nexus way and then it does not show up in the in-game manager, nothing is broken. You installed it, the game loaded it, and the catalogue simply never knew about it. Check the mod configuration and your load order, not the Mods button.
The version lag after every patch
This is the part nobody warns you about until it happens. The game updates, and a chunk of the catalogue goes quiet.
When Baldur's Gate 3 patches, mods compiled against the previous build stop matching it. The catalogue will either flag them as incompatible or hide them until their authors re-upload. For a few days after a big patch, the in-game list can look half empty, and saves that depend on those mods may refuse to load.
Three things follow from that:
- Do not uninstall a mod that a save needs during patch week. The mod is usually coming back; the save will not.
- Wait rather than hunt for a workaround. A mod going quiet in the catalogue is an author-side gap, not something you can fix from the menu.
- On PC you have one lever the console does not: you can roll the game back to the previous build and keep playing while the catalogue catches up. If you do, stop there — do not add new mods on a rolled-back build.
Console players only have this route
On PS5 and Xbox, mod.io is not one option among several; it is the option. Consoles have no mod folder, no file browser and no script host, so anything distributed as an archive is out of reach. The upside is that the console install is the most reliable version of a mod you can get: it updates itself, it is ordered for you, and it keeps achievements enabled because the in-game route is the supported one.
For the console-specific detail — which categories make it across and which never will — see BG3 console mods on PS5 and Xbox.
When a mod will not enable
A mod that is in the catalogue but will not turn on is almost always one of four things. Work down this list in order; it catches the large majority of cases.
A missing dependency. Many mods are built on top of another mod — a framework, a library or a compatibility patch. The catalogue entry will usually name the dependency, and the game will not let you build a working list without it. Install the dependency first, then the mod that needs it.
A version mismatch. The mod was built for a different game build and has not been re-uploaded. There is no client-side fix. Check whether the author has posted an update; if not, this mod is simply unavailable to you right now.
A save that remembers a mod you no longer have. The save file records the active mod list. If a mod was removed or pulled, the manager can refuse to build a consistent list around that save. The usual outcome is starting a fresh campaign, or loading the save without the ability to add new mods around it.
Two installers fighting over one configuration. If you have been installing archives by hand on PC and also subscribing through the catalogue, both write to the same mod setup and the order one tool believes in may not be the order the game follows. Pick one route. If you need the archive route, do it properly through a BG3 mod manager rather than by hand.
Load order: handled for you, until it is not
The in-game manager decides the order for you. That is fine while everything you have installed came from the catalogue, because the catalogue entries know what they depend on.
The moment a hand-installed mod is in the mix, the automatic order stops being trustworthy. Two mods that change the same thing — the same class, the same item table, the same UI panel — will load in some order, and the wrong one wins silently. Nothing errors. The mod you wanted just does not take effect.
If you are at that point, the fix is not in the Mods menu. It is ordering by hand, which is a separate guide: BG3 mods not working walks through it by symptom, and how to install BG3 mods covers both routes from the start.
The mods that live outside mod.io
Some categories will never appear in the in-game catalogue, and knowing which ones saves a lot of time searching:
- Custom campaigns. Full replacement campaigns are distributed as archives and need a PC install with a campaign loader. Console players cannot run them at all.
- Script-driven mods. Mods that need a script extender depend on files the game does not load on its own, and consoles cannot load them in any form.
- Large overhauls. Projects that add classes with new animations, new spell systems or new races are usually too deep for the catalogue's scope.
- Unported PC favourites. Popularity on Nexus does not mean a mod.io build exists. Many authors never upload a second copy.
A short decision rule
The in-game catalogue is the right answer when you want to play now, on any platform, with the smallest chance of breaking a save. Use it whenever the mod you want is actually in there.
Go the archive route only when a mod you specifically need is not available in-game, and accept the cost that comes with it: manual load order, patch breakage you have to manage yourself, and no console support. Whatever you choose, choose it per save, and do not mix the two mid-campaign.
Common questions
Is mod.io the same as Nexus for BG3 mods?
No. mod.io is the catalogue the game itself reads, reachable from the Mods button on the main menu. Nexus Mods is a separate site that distributes archives you install yourself on PC. A mod can exist on both, but the two catalogues do not share files: installing something on Nexus does not put it in the in-game list.
Do I need a mod manager to use mod.io mods?
No. The game installs and orders mod.io mods for you. A mod manager is for Nexus-style archives on PC, where you control the load order yourself. Running both routes on the same save is where most broken installs come from, so decide which one you are using before you start.
Why did my mods disappear from the in-game list?
Usually a game patch. When Baldur's Gate 3 updates, mods built against the previous version get pulled or flagged until their authors re-upload against the new one. The mod is not deleted; it is pending an update. Wait for the author, or roll back the game version on PC if you cannot continue without it.
Can I install Nexus mods on PS5?
No. A PlayStation or Xbox has no mod folder, no file browser and no script support, so it can only read the in-game catalogue. Any guide that tells you to drop a file into a folder is a PC guide.
Do mod.io mods break saves?
Only in the way every mod does: the save remembers which mods were active. Removing a mod the save depends on can leave it unable to load. Adding mods is usually the safer direction; removing class, spell or companion mods from a campaign in progress is the risky one.
Can I use mod.io and Nexus mods together?
On PC, technically yes, and it is the most common source of crashes. Two installers write to the same mod configuration, so the load order one of them sees may not be the order the game loads. Pick one route per save.
Are mod.io mods free?
Yes, browsing and subscribing through the in-game catalogue costs nothing. There is no store, no purchase and no paid tier inside the Mods menu.