How to Install a Beta Branch on a Dedicated Server (SteamCMD -beta)

To run a dedicated server on a beta branch, add -beta <branch> to the app_update command in SteamCMD, plus -betapassword <password> if the branch is locked, then run it with validate. For example, +app_update 294420 -beta latest_experimental validate puts a 7 Days to Die server on the experimental build. Players must switch their game to the same branch in Steam (Library, right click the game, Properties, Betas), and you should back up the world first, because many betas change the save format and you cannot always go back.

Before you start: back up

Experimental branches are experimental. Many games convert the world to a new format the first time a beta build loads it, and the stable build then refuses to open it. Before switching:

1. Stop the server.
2. Copy the whole save folder somewhere safe.
3. Note the exact branch and build you are on now.

Our guide on how to back up a game server shows where the common games keep their saves.

The SteamCMD command

The general form is:

steamcmd +force_install_dir /path/to/server +login anonymous +app_update <appid> -beta <branch> validate +quit

With a password protected branch:

steamcmd +force_install_dir /path/to/server +login anonymous +app_update <appid> -beta <branch> -betapassword <password> validate +quit

Rules that trip people up:

• -beta and -betapassword go directly after the app ID, before validate.
• Branch names are case sensitive and must match exactly.
• force_install_dir goes before +login.
• Use validate on the first switch so every file comes from the new branch.

Branch names for popular games

These are the server branches games have used. Developers rename them between updates, so confirm the current name in the game's patch notes or on the game's Steam news page before relying on it.

The Valheim password is the developer's way of making sure you read the warning: back up your world before opening it on a test build.

Get players on the same branch

The server and every player must run the same build, or players get a version mismatch and cannot join. In the Steam client:

1. Open your Library and right click the game.
2. Choose Properties, then Betas (newer Steam versions label it "Game Versions & Betas").
3. Pick the same branch the server is on. For a password branch, type the code into the private beta box first.
4. Let Steam download the update and restart the game.

Tell your players exactly which branch to pick. Someone on stable trying to join an experimental server is the most common "why can't I connect" message after a switch. If they still cannot join, our version mismatch guide covers the other causes.

Scripts and automatic updates

If your server updates itself on every restart, make sure the start script includes the -beta option. Otherwise the next restart updates it straight back to the default branch, often on top of a world that the beta already converted. Many hosting setups and tools like LinuxGSM have a dedicated branch setting for this reason.

How to switch back to the stable branch

1. Stop the server.
2. Restore the backup you made before the switch, if the beta converted the world.
3. Run the update with the default branch, called public:

steamcmd +force_install_dir /path/to/server +login anonymous +app_update 294420 -beta public validate +quit

4. If SteamCMD keeps the old branch, delete steamapps/appmanifest_<appid>.acf in the server folder and run the update again without any -beta option, plus validate.
5. Ask players to set their client back to "None" or the public branch in Steam's Betas tab.

Opening a world on stable after it was saved by a newer beta can crash the server or corrupt the save. That is what the backup is for. If you end up with a damaged world, see how to recover a corrupted game server world.

Mods and betas

Mods are usually built for the stable branch. On an experimental branch, expect mods and frameworks to break until their authors catch up. Run the beta without mods first, then add them back one at a time. For Rust, Oxide and Carbon often release separate builds for staging. For 7 Days to Die, many mods list which build they support.

Common errors

• Password check for AppId returned error Failure: the -betapassword is wrong or missing. LinuxGSM lists this exact message as an incorrect branch password.
• No subscription: the branch may be limited to certain accounts, or the name is wrong.
• Missing configuration: the branch name may not exist for that app. Check the spelling.
• Server still reports the old version: your start script may be running a different folder, or the update ran without -beta. Check the build number in the console on startup.

Running a beta on a hosted server

On a GamezServers server, several games expose the branch in the control panel: a game version field on 7 Days to Die, a beta branch field on Valheim for public-test, a Stable or Experimental choice on Satisfactory, and Build 42 or Build 41 (legacy) as server types on Project Zomboid. Take a one click backup first, change the branch and update. You can always get at the files through the file manager or SFTP if you need to roll back by hand.

FAQ

How do I put a dedicated server on the experimental branch?

Add -beta <branch> (and -betapassword if needed) after the app ID in your app_update command and run it with validate. Players must pick the same branch in Steam.

Can I go back to stable after testing a beta?

Yes for the server files: update with -beta public. Your world may not survive the trip back if the beta changed the save format, so restore the backup you made before switching.

Why does my server return to the stable branch after a restart?

The auto update on startup runs without the -beta option. Add the branch to your start script or panel setting.

Do players need the beta too?

Yes. Server and clients must run the same build. Players switch in Steam under the game's Properties, Betas tab.