Before Changing Versions

First create a manual backup in the panel under Backups. Then stop the server. Stable and Experimental may require different savegame and mod versions; never switch while the server is running.

Also clarify in advance what you actually want to achieve. Switching from Experimental back to Stable is not just a simple downgrade click: a world that has already been saved under a newer build cannot reliably be continued in an older version. In that case, plan either with a fresh world or with the backup that was created before switching to Experimental. If you are just setting up your server, first work through the basic setup of a 7-Days-to-Die server — the settings there are the foundation for everything else.

Choose Stable or Experimental

  1. Open your server and go to Settings → Change Version.
  2. Choose Stable for normal operation. Use Experimental only if your world and all mods explicitly support the desired build.
  3. Confirm the change and wait until installation and restart are complete.
  4. Check the displayed game version in the startup log and connect once with the matching client.

For a major update, you should check the compatibility of your world and every mod beforehand. If startup fails, do not reinstall repeatedly: stop the server, check the first concrete mod or version issue in the log, and restore your backup if necessary.

The client side is important too: your game client must use the same branch as the server. Steam does not automatically switch to Experimental — you set that in the game properties under Betas. If the client remains on Stable while the server is running Experimental, the server either will not appear in the list at all or joining will fail with a version message. That is not a server error and cannot be fixed by restarting.

Upload Large Mods via SFTP

The browser file manager is intended for small files. For large mods or many files, use SFTP:

  1. Stop the server.
  2. Open SFTP/Credentials in the panel and copy the host, port, username, and password.
  3. Connect with an SFTP client such as FileZilla or WinSCP. Explicitly use the SFTP protocol, not FTP.
  4. Extract the mod archive locally. Upload the complete mod folder to /Mods/. In the end, the ModInfo.xml file must be directly inside the respective mod subfolder, for example /Mods/MyMod/ModInfo.xml.
  5. Also upload all dependencies mentioned by the mod. Remove old versions of the same mod so no duplicate DLLs are loaded.
  6. Start the server and search the log for the mod name as well as ERR, Exception, or missing dependencies.

Why SFTP and not the browser file manager? Large mod packages consist of many small files. A browser upload transfers them individually and may fail halfway through the package if the connection is unstable — leaving behind a partially uploaded mod that creates an error on startup that looks like a version conflict. An SFTP client transfers folders as a whole, shows progress, and can resume interrupted transfers. The general credentials and basics are covered in the guide to SFTP access to game server files.

When getting mods, make sure they match the correct game version. Collections such as 7daystodiemods.com list the supported 7DTD version for each mod — a mod for A21 usually does not run on a newer build. You can find a more detailed installation guide under Install mods on a 7-Days-to-Die server.

If the Server Does Not Start

  • Check whether the mod and server support the same major 7DTD version.
  • Check for nested folders like /Mods/MyMod/MyMod/ModInfo.xml; one of those levels is too much.
  • Try starting without the most recently uploaded mod.
  • Restore the backup if the version change itself damaged the world.

Always change only one thing at a time. If you change the version, replace three mods, and adjust the configuration all at once, you will not be able to tell afterward which step prevented startup. The fastest way back is almost always: temporarily remove mods from /Mods/, confirm a clean startup, then add the mods back one by one.

Only when the log does not name a concrete file name or error should you create a support ticket and include the affected mod link as well as the first error block from the startup log.

FAQ

Can I switch from Experimental back to Stable?

The version change itself, yes — but your world may not. Savegames saved under a newer build are often no longer readable in older versions. For the way back, plan with a backup that was created before the switch.

Does my game client need to be changed too?

Yes. Server and client must use the same branch. You set Experimental in Steam under the game properties in the Betas tab. Without this change, joining fails with a version message.

Why is my mod not loaded after upload?

In the vast majority of cases, it is due to the folder depth. ModInfo.xml must be directly inside the mod folder, meaning /Mods/MyMod/ModInfo.xml. An extra level such as /Mods/MyMod/MyMod/ModInfo.xml causes the server to overlook the mod — without an error message.

Will my world and player data be lost when changing versions?

The change replaces the server files, not the saves. With a major update, a world can still become incompatible — that is why you should create a backup before every change.

Why does the browser upload keep failing?

The file manager transfers many small files individually. For large mod packages, an SFTP client is the more reliable choice because it transfers folders as a whole and can resume interrupted uploads.