How to Update a 7 Days to Die Server to a New Version

To update a 7 Days to Die server, stop it with saveworld then shutdown, back up Saves/ and GeneratedWorlds/ from the user data folder, run SteamCMD with app 294420 (add -beta latest_experimental only for experimental), and start it. Keep GameWorld and GameName the same so the old save loads. After a major version, check serverconfig.xml: since V3.0, most game rules live in one SandboxCode, and old properties are ignored.

What you can change on an existing world vs what needs a new world

When V3.1 went out, The Fun Pimps put it this way: "Although new games will always be recommended, game saves should be compatible and a new game is not required." Read each release's notes before updating, because that line is the one that tells you.

What is the current 7 Days to Die version?

As of October 2026, the stable branch is V3.2, released on 26 August 2026 (Steam). V3.3 with backpacks and an 8x6 inventory is on latest_experimental. PS5 and Xbox share the V3 line with PC for crossplay. See our 7 Days to Die 3.2 update guide.

What goes where

Step 1: Back up first

Run saveworld in the console, then stop the server. Copy the whole Saves folder and your world's folder in GeneratedWorlds, plus serverconfig.xml and Mods. Experimental builds and major versions are where saves most often misbehave.

Step 2: Read the release notes

Look for three things: whether the save is compatible, any serverconfig.xml properties added or removed, and anything about mods. V3.0's notes, for example, listed every legacy property moved into the SandboxCode.

Step 3: Update the server files

With the server stopped:

steamcmd +force_install_dir /path/to/7dtd-server +login anonymous +app_update 294420 validate +quit

For experimental, add -beta latest_experimental after 294420. A SteamCMD run without -beta always installs stable, which is how servers end up back on stable by accident.

Step 4: Merge serverconfig.xml

validate can restore the default serverconfig.xml, and new versions add properties. Compare your backup with the new file and copy your values across. Never paste an old file over a new one after a major version, or new properties go missing.

Step 5: Start and check the rules

Start the server and wait until it reports it is ready. Run getsandboxoptions in the console to confirm the rules loaded the way you expect. Then join, check your base, your land claim and the day counter.

The gotcha: old settings are silently ignored after V3.0

V3.0 moved over 150 game rules out of serverconfig.xml into a single SandboxCode property. Properties such as GameDifficulty, XPMultiplier, DayNightLength, BlockDamagePlayer, DropOnDeath and BloodMoonFrequency were removed. A server updated from V2.6 still starts, still loads your save, and simply ignores those lines, so XP, day length and blood moons quietly fall back to the Adventurer defaults (AAAJABJACJADJARFBNC). The V3.0 notes told admins to "recreate your legacy serverconfig.xml settings using the in-game Sandbox Options menu" and paste the code.

It happened again in V3.1, which split density and respawn into day and night values and warned that "invalid codes may default some or all settings". So after any major update, rebuild your code in Sandbox Options on the new game screen, paste it as SandboxCode, and check it with getsandboxoptions.

One more trap: keep the GeneratedWorlds folder. A save needs its exact map, and world generation can change between versions, so regenerating "the same" seed later does not reliably give the same map.

Common problems

• Version mismatch for players: the server and players are on different builds or branches. See the version mismatch fix.
• Settings reset after the update: removed legacy properties or an invalid SandboxCode. Rebuild the code and check with getsandboxoptions.
• Server made a brand new world: GameWorld or GameName changed, or GameWorld is RWG and generated a fresh map. Point it at your old folder names.
• Overhaul mod errors on start: the mod is not updated for the new version. Put the server on the branch the mod supports.
• Console players cannot join: experimental builds are Steam only. Crossplay needs the stable branch.

Updating on GamezServers

A 7 Days to Die server from GamezServers updates itself on every restart, so after a stable patch it is Backup, then Restart. Name, password, world, save name, sandbox code, EAC and crossplay are panel settings that we pass as launch options, and launch options override serverconfig.xml, so paste your new code into Sandbox code in Settings rather than the file. To try experimental or pin an older branch for a mod, set Game version and press Update game. Worlds and saves stay. More in how to change 7 Days to Die server settings.

FAQ

Do I need a new world for a 7 Days to Die update?

Usually not. The Fun Pimps recommend new games for the best experience, but recent updates kept saves compatible. Read each release's notes.

Why did my 7 Days to Die settings reset after updating?

Since V3.0 most rules live in SandboxCode, and old serverconfig.xml properties are ignored. V3.1 also invalidated some codes. Rebuild the code and paste it again.

How do I update a 7 Days to Die dedicated server?

Stop it and run steamcmd +login anonymous +app_update 294420 validate +quit in the install folder, then start it.

Can I go back to an older version after updating?

You can install an older branch, but a save played on a newer version may not load on it. Restore your backup instead.