Getting Started with Skyrim Special Edition Modding
MO2, SKSE64, Address Library, USSEP, SkyUI, and LOOT — the modern Skyrim modding stack
This guide is the modern equivalent of "How do I mod Skyrim" — the path almost every Skyrim modder follows in 2026, on Special Edition. If you're on the 2011 Legendary Edition, see the Skyrim guide instead; the two paths share concepts but differ in tools and version pinning.
The non-negotiable: use a mod manager from day one. No exceptions.
Step 1 — Decide on a game version
Skyrim Special Edition has two relevant executable branches:
- 1.5.97 — the pre–Anniversary Edition build. Most older mods target this.
- 1.6.x — the Anniversary Edition build. Most mods updated since 2022 target this.
Bethesda's launcher and Steam auto-update push you to 1.6.x by default. If you're starting fresh, 1.6.x is fine — it's where the modern modding scene lives. If you specifically want a legacy mod list (e.g. a wabbajack pre-built list from 2021), you may need to downgrade to 1.5.97 using the community SSE Downgrader tool.
Decide before installing anything else, because SKSE and most mods are version-specific.
Step 2 — Install Mod Organizer 2
Mod Organizer 2 is the community-standard mod manager.
After install, create a new instance pointed at Skyrim Special Edition (not Skyrim). MO2 detects the game folder via Steam's installation.
The principle: never install mods directly into the Skyrim Special Edition folder. MO2 keeps them in its own directory and projects them at runtime via a virtual file system.
Step 3 — Install SKSE64
Download the SKSE build matching your game version:
- For 1.5.97 → SKSE64 build labelled "current SE build" historically
- For 1.6.x → SKSE64 build labelled "current AE build" historically
Extract the .7z to your Skyrim Special Edition install directory (the one with SkyrimSE.exe). Required files include skse64_loader.exe, the matching DLL pair, and the Data/Scripts/ folder.
In MO2: Settings → Plugins → ensure SKSE is detected, then create the run-shortcut → SKSE in MO2's executables dropdown.
Launch Skyrim through MO2's SKSE shortcut. The main menu's bottom-left corner should show the SKSE version.
Step 4 — Install the essentials
Four mods nearly every modded SSE install runs:
- Address Library for SKSE Plugins — compatibility shim. Install the version matching your game (1.5.97 or 1.6.x).
- Unofficial Skyrim Special Edition Patch (USSEP) — community bug fixes.
- SkyUI — UI overhaul + MCM framework.
- A Quality World Map — quality-of-life map replacement, near-universal.
Install each through MO2's drag-and-drop install flow.
Step 5 — Run LOOT
LOOT (Load Order Optimisation Tool) sorts your plugin load order. Run it from MO2's toolbar, click Sort, click Apply. The plugin list in MO2's right pane reorders.
For new installs LOOT's defaults are excellent. Manual tweaks are usually only needed when running large mod lists (200+ plugins) or specific content combinations that LOOT doesn't know about.
Step 6 — Start a new save
Don't add or remove SKSE-dependent mods mid-playthrough. The save file embeds script state from every script-injecting mod, and removing one mid-run leaves orphaned references that grow over time and eventually corrupt the save.
The discipline: pick your mods, start fresh, finish that playthrough on that list. Save Game cleaning tools exist (FallrimTools Resaver, ReSaver) but they're surgical instruments, not casual fixes.
Common gotchas
- SKSE version mismatch. If SKSE complains about an unrecognised game version, you have the wrong SKSE build for your Skyrim patch. Match them exactly: 1.5.97 with SE-branch SKSE, 1.6.x with AE-branch SKSE.
- Address Library version mismatch. Same problem at a different layer. The Address Library download page has separate files for SE and AE; install the right one.
- Game auto-updated and broke everything. Bethesda's launcher periodically pushes updates that break SKSE. Disable Steam auto-updates for Skyrim Special Edition once you have a working mod list, and only opt-in to updates after SKSE has caught up to the new version (usually a few weeks).
- Plugin limit (still 255). Same hard limit as Legacy Edition. Past 255, plugins are ignored silently. ESL plugins don't count against the 255 limit, so converting non-master plugins to ESL is the standard scaling answer.
- Mod organiser confusion: install order vs load order. Left pane is install order (which mod's files win conflicts). Right pane is load order (which
.esploads first). They're independent settings that both matter. LOOT sorts only the right pane.
If you want a pre-built mod list rather than assembling your own, Wabbajack (a separate community project) automates installing curated mod packs. It's the path of least resistance for ENB-heavy "graphical overhaul" setups.
When you're ready to publish your own SKSE plugin or content mod, the OpenMods publishing guide explains the GitHub-connected workflow.