Load order guide
Skyrim Mod Load Order, Explained Properly
Load order is the thing that quietly breaks more Skyrim installs than any single "bad" mod ever does. It's also one of the most misunderstood parts of modding — most new players have never had it explained without a wall of jargon. This guide covers what load order actually is, the mistakes that trip up almost everyone the first time, how to manage conflicts between mods, and a real beginner-friendly setup you can copy.
Why Load Order Causes More Problems Than Any Individual Mod
Here's the thing nobody tells new modders clearly enough: Skyrim doesn't really "merge" your mods together in any smart way. When two mods edit the same NPC, the same leveled list, or the same cell, the game mostly just uses whichever version loaded last and throws away the other one. Load order is the rule that decides which mod "wins" every single one of those overlaps, across your entire install. Get it wrong and you don't get an error message most of the time — you just quietly lose changes you paid attention to install in the first place.
This is also why two players can install the exact same 40 mods and have completely different experiences. One has a stable, working game. The other has floating NPCs, missing perks, or a crash on the loading screen. Same mods, different load order, wildly different results. If you've ever installed something from our best Skyrim mods list and had it "not seem to work," there's a good chance load order — not the mod itself — was the actual problem.
The good news is that load order isn't actually complicated once someone walks you through it without the jargon. This guide is written for players who are past the very first install (if you haven't installed your first mod yet, start with our how to install Skyrim mods guide instead) and want to understand why their load order matters, not just which button to click.
We'll cover the actual mechanics of load order, the mistakes that trip up almost every new modder at least once, how to handle conflicts between mods that touch the same things, and a real beginner setup order you can use as a template for your own install.
Think of your load order like stacked books — whichever one's on top is what you actually see.
Load Order Basics: What's Actually Happening
Every mod you install adds at least one plugin file — a .esp, .esl, or .esm file. These are the files Skyrim actually reads when it starts up, and the order they're read in is your load order. Your mod manager's plugin list — the panel with checkboxes in Mod Organizer 2 or Vortex — is showing you that order directly. Top of the list loads first, bottom loads last.
.esm files (masters) are mods that other mods can depend on, like Skyrim.esm itself, the official DLCs, or large frameworks. .esp files are standard plugins — most mods you install. .esl files are "light" plugins that don't use up a full slot in your load order's record limit, which matters once you're running 150+ mods but isn't something a beginner needs to worry about yet.
The rule that matters most: when two plugins edit the exact same record — the same NPC's stats, the same item, the same leveled list entry — whichever plugin loads later wins that specific edit. This is sometimes called "last loaded wins," and it's true at the individual record level, not the whole-file level. A mod loaded near the bottom of your list doesn't override everything from every mod above it — it only overrides the specific things it actually touches that those other mods also touch.
This is also why masters have to load before anything that depends on them. If a mod requires the Unofficial Skyrim Special Edition Patch, USSEP has to be higher in your load order than that mod, or the game won't be able to find what it's looking for and may crash or fail to load the dependent mod's changes at all.
You almost never need to figure this out by hand. LOOT (Load Order Optimisation Tool) reads metadata for thousands of known mods and automatically sorts your plugin list into a sensible order, flags missing masters, and warns you about known conflicts. It's built into Mod Organizer 2 and available as a standalone tool for Vortex users. Run it after every single change to your mod list — not just once at the end.
6 Load Order Mistakes Almost Everyone Makes Once
None of these are embarrassing — they're the standard mistakes that show up the first (and sometimes second) time anyone builds a real load order. Recognizing them early saves hours of confused troubleshooting.
Confusing install order with load order
Installing mods in a particular sequence doesn't sort anything by itself. The order you downloaded mods in has almost no bearing on the order they load in. Sort with LOOT after installing — install order on its own does nothing.
Ignoring LOOT's warning messages
LOOT doesn't just sort plugins — it surfaces real warnings in yellow and red about missing masters, known incompatibilities, and mods that need a patch. Skimming past these and hitting "Apply" anyway is the single most common cause of a "why won't my game launch" post.
Placing a patch above the mods it patches
A compatibility patch needs to load after both mods it's patching, or its fixes get overwritten by the very mods it was supposed to reconcile. If a patch isn't working, this is the first thing to check — drag it to the bottom of your relevant section.
Never building a bashed or merged patch
Running several mods that add items to the same leveled lists (loot tables, enemy spawn pools) without a bashed patch means only the last-loaded mod's additions actually show up. The others silently lose their entries. This is a very common reason a mod "doesn't seem to do anything" even though it installed fine.
Manually dragging plugins without understanding masters
It's tempting to drag a plugin to the very bottom because "that mod is important to me." If that plugin depends on a master that now loads after it, you can break the dependency entirely. Let LOOT handle ordering and only manually adjust when you understand exactly why.
Stacking conflicting overhauls and hoping for the best
Running two full combat overhauls, or two full weather overhauls, at the same time isn't a load order problem you can sort your way out of — it's a design conflict. No amount of reordering fixes two mods trying to own the same system. Pick one per category.
Mistakes avoided. Now let's talk about conflicts you can't just sort away.
Managing Conflicts Between Mods
A "conflict" just means two or more mods are editing the same record. That's not automatically a problem — it's extremely common and usually harmless. The question that actually matters is whether the result is what you want. Sometimes you want the later mod to win completely. Sometimes you want both mods' changes to combine. Those need different solutions.
For simple overwrite conflicts — where you genuinely just want one mod's version of something to win — load order alone handles it. Put the mod whose version you want last in the relevant section of your load order.
For additive conflicts — where multiple mods are each adding their own entries to the same leveled list, like loot tables or enemy spawns — load order picks a winner and discards the rest, which usually isn't what you want. This is what a bashed patch (built with Wrye Bash) or a smashed patch (built with zMerge) is for. These tools scan your whole load order, find every mod's additions to shared lists, and combine them into one patch that goes at the very bottom of your load order. It's the single highest-impact step most beginners skip.
For deeper conflicts — two mods editing the same NPC's appearance, or two big system overhauls both touching the same gameplay mechanic — you need an actual compatibility patch, not just reordering. Many popular mod pairs already have a community-made patch on Nexus Mods; check the patches/compatibility section of each mod's page before assuming you need to build one yourself. Tools like SSEEdit (xEdit) let you see exactly which records two mods both touch, which is how patch authors find these conflicts in the first place — useful to know exists, not something a beginner needs to learn on day one.
The practical workflow: install a few mods, run LOOT, read its warnings, fix anything flagged, and only then move on to the next batch. Building a bashed patch once near the end of a modding session (and rebuilding it any time your leveled-list mods change) closes the gap LOOT alone can't cover. This is also exactly why we recommend installing 2-3 mods at a time rather than 40 at once — it's far easier to spot which addition caused a new conflict warning when you've only just added one thing.
A Real Beginner Load Order Example
LOOT will fine-tune the exact plugin order for you, but it helps to understand the broad categories your load order should flow through, top to bottom. Here's a realistic example using mods covered across our best mods for beginners list — this is the shape of a sensible load order, not a strict file-by-file ruleset.
Skyrim.esm + official DLCs
Always at the very top. Everything else depends on these.
Unofficial Skyrim Special Edition Patch (USSEP)
Loads right after the base game and DLCs, before almost everything else.
Frameworks: SKSE64, Address Library, SkyUI
These don't change game content directly but plenty of other mods depend on them, so they load early.
Gameplay overhauls (combat, magic, perks)
Pick one combat overhaul, not several stacked together — see the mistakes section above.
NPC, world, and weather mods
Mods like Interesting NPCs, Immersive Citizens, or a weather overhaul typically slot in after gameplay systems.
Compatibility patches
Any patch you've downloaded for two of the mods above goes after both of them — never above.
Bashed patch / merged patch
Built last, after everything else is sorted, and always sits at the very bottom of your load order.
Run LOOT after building this skeleton and let it fine-tune the order within each category — it will catch things this rough outline can't, like a specific plugin that needs to load before another one in the same category. If you haven't installed your foundational mods yet, our installation guide walks through getting SKSE, a mod manager, and your first mods set up correctly.
Frequently Asked Questions
What is "load order" in Skyrim modding and why does it matter?
Load order is the sequence your plugins (.esm, .esp, and .esl files) are read in when Skyrim starts. When two mods edit the same thing — an NPC, a leveled list, a cell — the mod that loads later generally wins that specific edit. Get the order wrong and you can lose the changes you actually wanted, end up with floating objects, broken NPCs, or a crash to desktop. Load order is the single biggest cause of a broken Skyrim install, more than any individual mod being "bad."
What's the difference between load order and install order?
Install order is simply the order you downloaded or installed mods in through your mod manager — it has almost no effect on the game by itself. Load order is the actual sequence your mod manager or the game itself reads your plugin files in, which is what your mod manager's plugin list (sorted by LOOT) controls. You can install mods in any order you like; what matters is sorting the resulting plugin list correctly afterward.
Do I need to manually sort my load order or can a tool do it for me?
Use LOOT (Load Order Optimisation Tool) as your starting point every time — it's free, it's built into Mod Organizer 2 and available standalone for Vortex, and it reads masterlist data covering thousands of mods to suggest a sensible order automatically. LOOT gets you roughly 90% of the way there. The remaining 10% is reading LOOT's own warning messages and manually placing compatibility patches, which LOOT can't always infer on its own.
What's a bashed patch or merged patch, and do I really need one?
A bashed patch (built with Wrye Bash) or a smashed patch (built with zMerge or Smash) combines leveled lists, perks, and other additive records from multiple mods into one file, instead of letting the last-loaded mod simply overwrite everyone else's additions. If you're running more than two or three mods that touch leveled lists or perk trees — which includes almost any combat or loot overhaul — you need one. Without it, you'll often find that only one mod's added items or enemies actually show up in-game, even though you installed several.
My game crashes on launch — is that always a load order problem?
Not always, but it's the first thing to check. A missing master (a mod that depends on another mod you don't have enabled), two mods both editing the same record in an incompatible way, or a plugin loaded before its required master are all load order issues that show up as instant crashes. Run LOOT first and read every red and orange message it gives you — most of those are exactly this kind of problem. If LOOT is clean and you're still crashing, the next suspect is usually a missing requirement like SKSE or a mismatched Address Library version, not load order itself.
Should I sort load order before or after installing all my mods?
Run LOOT every time you add, remove, or update a mod — not just once at the end. It only takes a few seconds, and sorting after every change means you catch a new conflict warning right when it appears, while you still remember what you just installed. Waiting until you've installed 40 mods and sorting once at the end makes it far harder to figure out which specific addition caused a new warning to show up.
Building a setup and not sure where to start?
Let our AI Mod Builder put together a starting setup based on your style and focus, then come back here once you're ready to sort the load order and keep it stable.