Publish to mod.io with the BG3 Toolkit

Requirements

• Windows only. The BG3 Toolkit does not run on Mac or Linux. If you are not on Windows, this path is not available to you.
• Baldur's Gate 3 installed, plus the free "Toolkit Data" DLC (added to your library from the BG3 store page).
• A mod.io account, free to create at mod.io.
• Script Extender mods cannot be published to mod.io. This is a Larian policy on mod.io itself, not a Karsus Codex limitation.

Steps

1. Download your pak from Karsus Codex, same as always.
2. Open the BG3 Toolkit and use Import on the pak. A "Multiple meta.lsx files found" warning during import is expected and harmless. If you see other warnings you do not recognize, stop and check them before continuing.
3. Close and reopen the Toolkit, then open the project from the project list. Do not Import again; open the project that Import already created.
4. In the Stats Editor, run File > Validate All.
5. Still in the Stats Editor, run File > Export Project Stats. This regenerates your item and treasure data from what Karsus Codex generated, so nothing gets silently dropped from the published pak.
6. In Project Settings, set a thumbnail and description if you want, then Publish.

Publishing goes through mod.io's own review, same as any other Toolkit mod.

Updating a published mod

Download a new version from Karsus Codex and repeat the steps above. The mod's identity (its internal UUIDs) is pinned across every version you generate, so republishing updates your existing mod.io listing instead of creating a new one.

If your mod is not eligible

Some mods cannot carry a BG3 Toolkit project: mods with progression/class content, because the Toolkit's own Import skips base-game overrides by design (documented in Larian's Toolkit docs), so that content cannot round-trip through a published project. Your mod page tells you if this applies. An ineligible mod's pak still installs and plays exactly as before — it just cannot also open as a Toolkit project for mod.io.