7 Days To Die V3.2.0 Is Out, But Only On Experimental (August 19, 2026)

Is V3.2.0 out?

Yes, but only as an experimental build. It went up on August 19, 2026 on the latest_experimental branch. The default branch, and therefore every player who has not deliberately opted in, is still on V3.1.0, which went stable on July 27, 2026.

This is consistent with what The Fun Pimps said they wanted after 3.0: smaller, more frequent updates instead of long alpha cycles. V3.2.0 is a couple of features plus a fix pass, not a headline release.

There is no announced stable date for 3.2. On the previous two cycles the experimental branch ran for roughly five days before the stable promotion, but that is a pattern, not a promise, and a longer experimental window is normal when something turns up in testing.

How to opt in on PC

Right-click 7 Days to Die in your Steam library, choose Properties, open Game Versions & Betas, and pick latest_experimental from the drop-down. Steam will download the build. To go back, select the default public version in the same drop-down.

Do this on a copy of your save, not your live one. Experimental builds are where save-breaking bugs get found, which is the entire point of them existing.

Console players cannot opt in. Xbox and PlayStation only ever receive stable builds, so 3.1 is the current build there and will be until 3.2 is promoted.

The two headline features

Honk to open trader doors

Your vehicle's horn now opens the outer doors at traders, so you can pull up to Rekt without dismounting. Not every door responds to every vehicle, and on-screen text tells you when you are close enough for it to work.

To stop this from opening doors you did not mean to open, a new door variant called oldWoodDoorNoHonk was added for trader interiors. It has replaced the interior oldWoodDoor in Rekt, Hugh and Joel, so inner doors stay shut when you sound the horn outside.

The Combine Station is readable now

The Combine Station UI was reworked so the result and its final stats are visible before you commit to the combine. A plus marker flags items that have already been combined, and combining is now an explicit button press instead of something that happens implicitly while you are arranging items.

This mostly matters because the old flow made it easy to destroy a good roll by accident.

What actually matters if you run a server

The feature list is short. The server-side changes are the reason to read the patch notes at all.

Four of those deserve a caveat rather than a celebration.

Do not skip the fix list, because one entry in it changes how you fight. "Demolition zombies not exploding from client damage" is filed as a bug fix, but what it means in practice is that demolishers now detonate from damage dealt by a client, where previously they did not. On a dedicated server, every player except the host is a client. If your group has been comfortably shooting demolishers because nothing ever went off, that habit is now expensive. This was the change the release thread singled out as the one buried in the wrong section.

The custom POI push is the biggest operational change in the release, and the patch note describing it is terse. Treat the exact scope as unconfirmed until it has been tested properly in the wild. That is not scepticism about the feature, it is the normal position on any experimental build: the note says a minimal metadata package is sent, and what "minimal" covers is exactly the kind of thing that gets refined between experimental and stable.

The screamer change is the one most likely to break a modlet. If any modlet on your server overrides entitygroups.xml, it will still apply its own version of the file and may put the chain-spawn behaviour straight back, or conflict in a messier way. Diff your modlet against the new file before you run this build.

The auto turret change is real and players noticed immediately. It is in the patch notes and it was confirmed by players on the release thread within hours, one of whom pointed out they had been putting a plank under wall turrets purely for looks and now have to do it for real. There is a secondary, unconfirmed report that placement still appears to be permitted and the turret then falls and breaks, with a pink outline as the "cannot place" indicator. If you build with wall turrets, test on a throwaway base first.

Other changes

• Cooking pot, cooking grill and anvil requirement logic fixed, so a held one no longer influences cook time

• Campfires can morph terrain like other blocks again

• Junk loot and general trader inventory can supply cotton when Crop Yield is set to none, which unblocks a progression dead end on low-yield rulesets

• Timid animals detect threats better

• New buff icons for the chicken stress events introduced in 3.1

• Some Chinese localization clarified

Fixes

• Being unable to craft lower-tier items after unlocking them

• Demolition zombies not exploding from client damage

• Rabbits running too slow

• Permadeath not granting Base Skill Points on death

• Loot Max Tier clamping user mods

• Entities causing blocks to collapse during chunk resets

• The "Failed to search EOS servers" popup

If you run mods, check these before updating

1. entitygroups.xml - the screamer scout groups changed. Any modlet overriding this file needs a diff.

2. Prefab properties - if you author or ship POIs, AllowTopSoilDecorations is gone and AllowDecorations replaces part of what it did.

3. Trader interior doors - oldWoodDoorNoHonk replaced oldWoodDoor inside Rekt, Hugh and Joel. A modlet that edits those trader prefabs may now be editing a door that is no longer there.

4. Turret-based base designs - wall mounting is gone, so any prefab or blueprint that mounts auto turrets on walls needs reworking.

Overhaul mods will not be on 3.2 for a while regardless. Darkness Falls, Undead Legacy, Ravenhearst and the rest pin a specific game build, and none of them chase an experimental branch. Our one-click modpacks stay on the stable line for that reason.

Reported but not confirmed

These came from players on release day. None of them are TFP statements and we have not reproduced any of them. They are here because if you are hitting one of them, it helps to know you are not alone, and because they are the sort of thing an experimental branch exists to surface.

• Quest progression settings on a dedicated server reported broken for at least two patches, and not addressed in 3.2

• Clothing disappearing from an existing character, icon and all, with no option to equip newly found clothing. The same player reported a fresh save behaved normally, which points at a save-migration issue rather than a general one

• Items lost through the world after a crash (a drone and a truck) with no way to recover or re-acquire them

• Crossplay still not working, reported several days before the 3.2 build

If you can reproduce any of these, the experimental branch is exactly where that report is worth filing.

A note on the honk feature

Opening trader gates from a vehicle has existed as a community mod for a long time, and the reaction on release day was a mix of "about time" and irritation that a modder's idea shipped as a vanilla feature. That is a community sentiment, not something we can adjudicate, but it does answer a practical question: if you were running a remote-gate modlet, you can probably drop it on 3.2, and you should check it for conflicts rather than leaving it stacked on top of the vanilla implementation.

Frequently asked questions

Is 7 Days to Die 3.2 out?

Only on the experimental branch, as of August 19, 2026. It is not the default build. V3.1.0 is still stable and still what you get if you do nothing.

What is the current stable version of 7 Days to Die?

V3.1.0 "Henpocalypse", stable since July 27, 2026 on PC, PlayStation and Xbox. See the full V3.1.0 notes.

When does V3.2.0 go stable?

No date has been announced. The last two cycles ran roughly five days on experimental before promotion, but that is an observed pattern rather than a commitment.

Should I put my server on 3.2?

Not if other people play on it. Clients on the default branch cannot join a server running an experimental build, so opting the server in cuts off everyone who has not also opted in. Test on a second server or a local copy instead.

Is 3.2 on Xbox or PlayStation?

No. Consoles only receive stable builds, so both are on V3.1.0 until 3.2 is promoted.

Do I need to start a new world for 3.2?

Nothing in the notes forces a new world. That said, this is an experimental build, so back up before you touch it and do not test on the save you care about.

Will my mods work on 3.2?

Assume not, for now. Overhaul mods pin a game build and none of them target an experimental branch this early. Small modlets may work, but any modlet touching entitygroups.xml is specifically at risk this patch.

Did demolishers change in 3.2?

Effectively yes, though it is filed as a fix rather than a change. Demolition zombies now explode from damage dealt by a client, which they previously did not. On a dedicated server everyone except the host is a client, so a group that had gotten used to shooting demolishers safely needs to unlearn that.

Does 3.2 fix the screamer horde problem?

It removes screamers calling more screamers, which is the runaway part. Screamers still spawn from heat as normal.

Related

• V3.1.0 Henpocalypse - the current stable build, and what your server should be on today

• V3.0 Dead Hot Summer - the major release the 3.x line is built on, including the 150-option sandbox layer

• V4.0 - the next major update, no date, and where bandits actually stand

• SandboxCode generator - build and encode your ruleset in the browser

• How to install modlets - and how to check one against a new build

• 7 Days to Die Roadmap 2026 - where 3.2 sits in the wider plan

• Official 7 Days to Die news on Steam - the studio's own release announcements