VOLOVerified Order and Load Optimisation Load order sorting for Baldur's Gate 3

    Mods in the wrong order override each other or never load, and the usual fix is moving them one at a time. VOLO sorts yours the way orders that actually work are sorted, with the reasoning shown for every mod. Runs in your browser, needs no account, and costs nothing.

    Played on an order already? Submit it and teach the sorter.

    Named after the Realms' most confident chronicler. Unlike Volo... we verify.

    What it does

    Export your order from BG3 Mod Manager, or use the game's own modsettings.lsx, and drop it in. VOLO reads the full export, the short one, CSV, or a plain list of names. Export the result and import it straight back.

    A sorted load order in VOLO. ImpUI sits first on its ImprovedUI slot, having moved up 84 places, and each row below shows how far that mod travelled, the slot it landed on such as Caites' UI Mods, and a note such as curated wherever the placement came from something other than a played order.
    Every row says where the mod landed and why. Mods placed from anything other than a played order are labelled, so a guess never looks like evidence.

    Where the order comes from

    A working BG3 load order is already divided into sections, and the community has settled on a set of divider mods that name them: a hundred-odd labelled positions running from interface mods at the top to compatibility patches at the bottom. VOLO treats those as the frame of the order, whether or not you install the dividers themselves.

    Which position a mod belongs at comes from the best evidence there is, in that order: where players filed it in orders they submitted, then what its name plainly says, then the category on its Nexus or mod.io page. Every row tells you which of the three you are looking at, so a guess never passes for evidence.

    Top of Load Order
    Resources
    Utilities
    Visuals
    Animations
    User Interface
    The first six sections of the frame, in the order VOLO files them. A hundred-odd more follow, down to compatibility patches at the bottom.

    What it will not do

    Dependencies are absolute: a mod that declares it needs another is never placed before it, whatever the sections say. Where VOLO has nothing to go on it leaves your order alone, so what you see moved is what it had a reason to move. Mods it knows nothing about wait at the end instead of being filed somewhere flattering, and you can move anything by hand.

    How much to trust it

    The masterlist knows 11,273 mods, calibrated against BG3 Patch 8, and you can browse every one of them. How well it sorts is measured against orders it has never seen, and the failures are published alongside the wins. Who makes VOLO, and where it is weak, is written down as well.

    Played on an order, working or not? Submitting it makes the sorter better for everyone. All of it, code and data, is on GitHub.

    Masterlist

    In numbers

    Mods in the masterlist
    11,273
    10,376 with a placement
    Orders submitted
    187
    153 reported working
    Agreement with players
    67.7%
    against 50.8% by chance
    Catalogue listings read
    26,326
    Nexus Mods and mod.io
    Corpus growth

    Orders landed by week

    Orders in the corpus, by the week they landed

    01020304050Week of 3 August 2026: 30 orders3 AugWeek of 10 August 2026: 50 orders5010 AugWeek of 17 August 2026: 24 orders17 AugWeek of 24 August 2026: 9 orders24 AugWeek of 31 August 2026: 14 orders31 AugWeek of 7 September 2026: 24 orders7 SepWeek of 14 September 2026: 12 orders14 SepWeek of 21 September 2026: 10 orders21 SepWeek of 28 September 2026: 1 order128 Sep

    Weeks start on a Monday. 13 orders in the corpus carry no date and are left out. The newest landed on 29 September 2026.

    Evidence

    Where placements come from

    Mods in the masterlist, by the evidence behind the placement

    02,0004,0006,0008,000Played orders: 7,171 modsPlayed orders7,171The mod's name: 1,989 modsThe mod's name1,989Nexus or mod.io listing: 1,165 modsNexus or mod.io listing1,165Unplaced: 886 modsUnplaced886Curated by hand: 45 modsCurated by hand45The author's other mods: 17 modsThe author's other mods17

    The same groups label every row of a sorted order, so a guess never passes for evidence.

    Questions

    No, although two moments make it look that way: picking your file, and saving the sorted one. Neither touches the network.

    When the page loads, your browser downloads VOLO's code and runs it on your computer, the same way a downloaded program runs. Picking a file hands it to that code through the browser's file picker, which reads it straight from your disk into the page's memory. The sorting happens in that memory. Saving the result uses the browser's download dialog, so it feels like a download, but the file is built inside the page and written from there to your disk.

    Check it in the browser's network panel. Everything you see comes from this site: VOLO's own code, styles, images and typeface, and the masterlist it sorts against, which is one file of public data served the same way to everybody. Your mod list is in none of them. The Submit page adds Cloudflare's anti-spam widget, and sends your order only once you press the button. That button is the only thing on the site that sends your list anywhere.

    The privacy page names every third party involved, including the ones this answer glosses over.

    No, for either. Sorting needs nothing, and submitting an order goes through this site with no sign-up.

    No. VOLO sorts the load order file, and a pak is a pak whether it came from Nexus Mods, the official in-game mod manager at baldursgate3.game (which runs on mod.io), or anywhere else. VOLO also keeps reference catalogues of both platforms, so a mod the community has not placed yet can still be categorised from its own listing.

    They say how much the placement is worth, because a guess and a verified position should not look alike. No label means players filed that mod there themselves, which is the strongest evidence VOLO has. A curated placement is a maintainer's hand-written rule. An inferred one was voted on by the mods either side of it in submitted orders, and the percentage is how much they agreed. A listing placement came from the mod's own Nexus or mod.io page, which describes the mod but says nothing about where people load it. An author placement means the mod itself is listed nowhere, but its author's other catalogued mods overwhelmingly sit in one section, so the mod is filed with them. A guess means VOLO read the title and had nothing else to go on, and unplaced means it had not even that, so the mod waits at the end.

    Expanding a row gives the reasoning in full, including any dependency that forced it. If a placement looks wrong, move it, and if the moved order works, submitting it is what corrects VOLO for the next person.

    It will, sometimes. The masterlist is only as good as the orders behind it, and plenty of mods have not been categorised yet. Every placement shows its reasoning, so you can see why a mod landed where it did and judge it for yourself. If you know better, put it right in your mod manager and submit that order; correcting VOLO is the whole idea.

    Usually not. Override-style mods do their work without joining the load order, so the in-game manager lists them as inactive; that is normal and safe to ignore. If every single mod is disabled after launch, that is different: one broken pak can take the whole list down with it, and the fix is finding and removing the broken one.

    Not today. This has been checked, so it is a confirmed answer.

    I asked Larian directly in August 2026, and a Community Manager checked with the team. There is a modsettings.lsx on consoles, the same file VOLO reads on PC, but there is no way to get it off the console or put a modified one back, and external software is not compatible with mods on consoles at all.

    It cannot be done with a mod either, which I looked into next. Load order is decided before any mod runs, so a mod cannot reorder the mods it was loaded alongside. Mod files are data with no access to the file system, and Script Extender, the only thing on PC that has such access, is a Windows library that cannot exist on a console.

    What already works in your favour is that the masterlist is built from mod.io as well as Nexus Mods, and mod.io is the platform behind the in-game mod manager. Your mods are in the data and sorted like anyone else's.

    So there is one workflow left, and it ends with you doing the last part by hand. VOLO shows you the order on a phone or a PC, and you drag your mods into that order in the in-game manager yourself. I could make that much less tedious by letting you connect your mod.io account, so VOLO reads what you are subscribed to and builds the list without you typing two hundred names in. However, it would still be incredibly manual (and tedious) to reorder them on a console.

    I have not built it, because it is only worth building if people would actually use it, and dragging a long list around with a controller may cost more than it saves. If you would use it, say so on the Nexus page or open an issue on GitHub. If enough people want it, I will build it.

    Same spirit, different method. LOOT sorts Bethesda games with a hand-written masterlist. VOLO is only for Baldur's Gate 3, and its rules are learned from orders the community has actually played on.

    Support VOLO

    VOLO is free and stays free. There is nothing to pay for and no server bill to cover. If it saved you an evening of load order wrangling and you feel like putting something in the tip jar, these work: