ModLauncher
7D2D Mod Launcher
The fastest way to install, isolate, update, and swap overhaul mods for 7 Days to Die. This page tracks the current V5 state, links the right downloads, and explains what matters for players and server admins in 2026.
Mod Launcher Compatibility Tool
Pick an overhaul to see which Mod Launcher version installs it, the recommended hosting plan, and exact install steps. As of July 2026 none of these overhauls has a V3.0 build - each runs on the branch shown under "Pinned 7DTD Version" (pin it via Steam > Properties > Betas). Deciding what to install first? The wiki's best 7 Days to Die mods ranks Darkness Falls, Undead Legacy, and the rest, and the 2026 Mod Status Tracker shows who is closest to a V3.0 port.
What It Does Well
- Keeps overhaul installs isolated from your vanilla game.
- Lets you keep multiple versions of the same mod profile.
- Handles large modpacks faster than manual ZIP juggling.
- Creates backups for saves and generated worlds before play sessions.
Current V5 Notes
- Built with Unity UI Toolkit.
- Uses Git/API-driven metadata for overhauls and modlets.
- Defaults to offline mode on startup.
- Windows installer is InnoSetup-based.
Best For
- Darkness Falls, Ravenhearst, War3zuk, and similar overhauls.
- Players who switch between solo modded saves often.
- Admins who need clean client instructions for communities.
- Anyone tired of breaking a vanilla install by hand.
Latest verified release
GitHub currently lists 5.5.0.2 (July 1, 2026) as the latest release. The 5.5 line is the one to run in the V3.0 era: 5.5.0.0 fixed multi-zip downloads and extraction, and 5.5.0.2 fixed expired API keys that silently emptied the mod list.
| Release | Date | Why It Matters |
|---|---|---|
| 5.5.0.2 | July 1, 2026 | Fixes expired API keys that broke mod-list loading - the release to be on for V3.0-era play. |
| 5.5.0.0 | June 15, 2026 | Multi-zip download and extraction fixes; shipped the day V3.0 EXP went live. |
| 5.4.0.6 | February 8, 2026 | Allows GitHub-release split zip files (Windows-only update). |
| 5.4.0.5 | July 27, 2025 | Fixes missing scrollbar behavior and additional mod download problems. |
| 5.4.0.3 | July 6, 2025 | Repairs GitLab URL generation for overhaul downloads. |
| 5.4.0.2 | July 3, 2025 | Fixes malformed URLs that blocked some downloads. |
| 5.4.0.1 | June 25, 2025 | Adds the 7dlauncher button and fixes several UI/update issues. |
V3.0 "Dead Hot Summer" and the Mod Launcher
7 Days to Die V3.0 went stable on June 29, 2026, and the first experimental fix batch (V3.0.1 EXP) followed on July 9. The launcher handles this fine - the friction is on the mod side: V3.0 reworked the mod infrastructure (XUi overhaul, XML format changes, the SandboxCode consolidation), so overhauls built for V2.6 and earlier do not load on V3.0 unmodified.
- Playing vanilla or modlets on V3.0: update the launcher to 5.5.0.2 and check each modlet against the wiki's V3.0 mod compatibility guide.
- Playing an overhaul (DF, UL, Ravenhearst, War3zuk...): stay on the overhaul's pinned branch - Steam > Properties > Betas (for example "v2.6") - and let the launcher manage the profile as usual. No major overhaul has shipped a V3.0 build as of mid-July 2026; the 2026 Mod Status Tracker is the page to watch.
- Running a server: the server must match the client branch exactly. A V3.0 server cannot serve a V2.6 overhaul client - pin the server to the same branch as the mod.
How to install it cleanly
- Install the launcher from the GitHub releases page, not from random mirrors.
- Launch it once and let it create its own working folders outside your main Steam install.
- Create a mod profile for each overhaul you care about instead of reusing one folder for everything.
- Keep vanilla saves separate from overhaul saves. This is the easiest way to avoid silent corruption and mismatched XML.
- Before large game updates, back up both
GeneratedWorldsandSaveseven if the launcher already snapshots them.
What changed in V5
- The project moved away from the older Git implementation because it was unstable with larger mods.
- V5 uses API-driven version discovery for overhauls and modlets.
- The UI was rebuilt around Unity 2021 UI Toolkit.
- HTTP downloads replaced the older UnityWebRequest approach for better progress reporting and fewer failures.
- The launcher is intentionally better at managing separate copies of the same overhaul than a manual ZIP workflow.
When the launcher is worth using
Use it if...
You regularly swap overhauls, test old alphas, or help other players install the exact same mod stack.
Skip it if...
You only use a couple of simple modlets in the vanilla Mods folder and never hop between overhauls.
Best practice
Match the launcher-managed client profile to the server's overhaul version. Let the launcher simplify the client side, but still read the server's own install notes.
Troubleshooting that actually helps
- If a mod vanishes from the list, check GitHub releases and the project's Discord before assuming your local install is broken.
- If an overhaul update fails, create a fresh profile instead of trying to salvage a heavily modified one.
- If your game launches but a server rejects you, compare both the overhaul version and the 7 Days to Die branch.
- If saves act strangely after an overhaul update, restore the pre-play snapshot and regenerate your mod profile.
Useful links
Skip the setup - host your 7DTD server with us
Plan M ($9.99/mo) covers 16-player groups with mods one-click and 5 datacenter regions. 2-day money-back, no contract.
Stay in the journey
Mods & overhauls hub
Explore the most popular 7D2D modpacks, install guides, and tooling — all tied back to hosting that supports one-click installs.
More ways to get answers