SteamCMD on a Dedicated Server: Installing and Updating Game Servers

SteamCMD is Valve’s command-line tool for downloading and updating dedicated server files for hundreds of Steam games. On a dedicated box it is the backbone of multi-game hosting: one tool, one update loop, and every game server from CS2 to Palworld managed the same way. This guide covers installation, the app_update workflow, running servers as unprivileged users, and automating updates so your game servers patch themselves.

What SteamCMD is and when you need it

Most Steam games distribute dedicated server binaries through Steam’s depot system, and SteamCMD is the official client for pulling those files without a desktop Steam install. You need it whenever a game’s server files are only available through Steam — which covers the majority of modern multiplayer titles. A few games (Minecraft, Valheim’s standalone tooling) still ship server files directly; SteamCMD handles the rest.

Installing SteamCMD on Ubuntu

On Ubuntu 22.04/24.04 the package route is cleanest:

sudo apt update && sudo apt install -y steamcmd lib32gcc-s1

If the package is unavailable, download the tarball from Valve’s CDN (steamcdn-a.akamaihd.net) and extract it to /opt/steamcmd. Either way, the 32-bit compatibility library is mandatory — skip lib32gcc-s1 and you will hit loader errors on first run.

The app_update workflow

steamcmd +login anonymous +force_install_dir /opt/games/rust \
        +app_update 258550 validate +quit

Break that command down: anonymous login works for public server files; force_install_dir sets where files land; app_update downloads or updates; validate checks file integrity (slow — run it on first install and after suspected corruption, not on every update); quit exits. Give every game its own directory so updates never cross-contaminate.

Common server app IDs

App IDs occasionally get reorganized, so verify on SteamDB before scripting, but these are stable as of mid-2026:

Game	App ID	Notes
Rust	258550	run validate after every wipe update
CS2	740	dedicated server files via SteamCMD
Valheim	896660	also distributed standalone
Project Zomboid	380870	needs -Dzomboid.steam=1 flag
Palworld	2394010	large download, plan disk headroom
7 Days to Die	294420	beta branch for experimental builds
V Rising	1829350	check branch before major updates

Running servers as an unprivileged user

Create a dedicated user (adduser steam), own every game directory with it, and run server processes as that user — never root. SteamCMD will happily run as root and then every game server inherits that privilege. A compromise on a root-owned Rust server is a compromised box.

Automating updates

The classic failure mode is a server that updates itself out from under running processes or, worse, never updates and breaks after a game patch. The clean pattern: a script that stops the server (systemctl stop), runs app_update, then starts it again (systemctl start), triggered by cron or a systemd timer:

0 5 * * * /opt/scripts/update-rust.sh

Stagger update times across games so a Steam-wide patch day does not try to pull 40 GB through one uplink at once. If bandwidth is metered, throttle SteamCMD with the -rate flag or schedule updates in the cheapest window.

Beta branches and validation

Use +beta to pin experimental builds — many games ship server betas for crossplay or balance patches. Pin the branch inside your script so an update never silently moves you to a different channel. Run validate after any beta switch: mixed file states are the number one cause of “server won’t start” tickets.

Sizing and disk planning

Multiple game servers add up fast: Palworld alone can exceed 15 GB of files, ARK clusters pass 100 GB, and every update needs staging headroom. Plan for roughly 2× the installed size in free disk, put SteamCMD’s content on NVMe (file verification is I/O-heavy), and check disk before patch day. If your current box cannot keep up with the game library you run, compare dedicated server plans in our provider table and size the upgrade with real numbers.

Bottom line

SteamCMD turns a bare dedicated server into a multi-game host in about ten minutes: install the tool, learn the app_update command, run everything as an unprivileged user, and automate updates with a stop-update-start script. Get those four pieces right and patching a dozen game servers becomes a zero-touch operation.

Need dedicated hardware that can run this workload without breaking a sweat? InterServer’s dedicated server lineup offers current-generation CPUs, NVMe storage, and always-on DDoS protection — check InterServer dedicated servers here.