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.

Download for Windows Linux (.tar.gz) macOS (.dmg) All releases

Latest release 5.5.0.10, 25 August 2026. Maintained by SphereII. Official site 7d2dlauncher.org · Discord support.

Status, 10 September 2026: the current release is 5.5.0.10 (25 August 2026), and the 5.5 line has shipped steadily through the whole V3.x window. The launcher itself runs fine against current 7 Days to Die. The catch is not the launcher: the big overhauls most people install through it, Darkness Falls, Undead Legacy, War3zuk, Ravenhearst and The Wasteland, still target older game branches, so overhaul play means pinning the branch that pack requires. Check each pack before you launch, and see the 2026 Mod Status Tracker for the per-mod mapping. Always trust the GitHub releases page over any cached download label.

Mod Launcher Compatibility Tool

Pick an overhaul to see which Mod Launcher version installs it, the recommended hosting plan, and exact install steps. Each of these overhauls runs on the branch shown under "Pinned 7DTD Version" (pin it via Steam > Properties > Betas) rather than on current 7 Days to Die. 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.

7 Days to Die Mod Launcher V5 dashboard

Latest verified release

GitHub currently lists 5.5.0.10 (25 August 2026) as the latest release. Run the newest 5.5 build: the releases after 5.5.0.2 fixed the download problems people most often report. 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.10	25 August 2026	Current release. Corrects the release and update descriptions shown in the launcher.
5.5.0.9	25 August 2026	Performance, lag and hitch fixes; several backup and restore fixes; better default-folder handling per platform; adds a button that opens the current profile's modlet folder, which is how you drop a Nexus modlet into an overhaul profile.
5.5.0.7	6 August 2026	The download-reliability release: Azure download fixes, multi-ZIP cancellation fixes, prevention of duplicate downloads, and better download state reporting and troubleshooting logs.
5.5.0.2	July 1, 2026	Fixes expired API keys that broke mod-list loading - the fix for mod lists failing to load.
5.5.0.0	June 15, 2026	Multi-zip download and extraction fixes; the first release of the 5.5 line.

7 Days to Die V3.2 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 current 7DTD: run the latest V5 launcher 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: run the game version the overhaul requires on both the server and every client, and keep the mod files at matching versions. A current-branch server cannot serve a client pinned to an older overhaul branch - 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 GeneratedWorlds and Saves even 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

Most of the download complaints people still post were fixed in the 5.5 releases after 5.5.0.2. If you are hitting any of these, update the launcher first and retry before changing anything else:

Downloads stall, cancel themselves, or a multi-part mod never finishes. Older 5.5 builds had multi-ZIP queue and cancellation bugs. 5.5.0.7 fixed several of them and also stopped the launcher starting duplicate downloads of the same file.
An Azure-hosted mod refuses to download. Also fixed in 5.5.0.7, along with better download state reporting so a failure now tells you something.
The launcher stutters or hangs while managing downloads. 5.5.0.9 is a performance and hitch pass.
Backup or restore does the wrong thing. 5.5.0.9 carried several backup and restore fixes.
You want to add a Nexus or third-party modlet to an overhaul profile. 5.5.0.9 added a button that opens the current profile's modlet folder, which is where that file goes. You no longer need to hunt for the path.
The launcher puts files somewhere unexpected. 5.5.0.9 improved the default folder handling per platform, which matters most on Linux and macOS.

Beyond version-specific bugs:

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.

Hosting note: the launcher solves the client side of overhaul management. Your server still needs the matching world, modpack, and branch. To host a modded 7 Days to Die server with that handled, pick from our hosting plans for Darkness Falls, Undead Legacy and other overhauls. Weighing providers? Our best 7DTD hosts guide ranks them on overhaul mod headroom.