Guide

SteamCMD Setup on Windows and Linux

Install SteamCMD on Windows or Ubuntu, check server App IDs and login requirements, update game servers, use validate, and troubleshoot common errors.

Steam artwork associated with the SteamCMD game server installation tool
Source: coop-legends.de

Overview

SteamCMD is Valve's command-line client for Steam. Many dedicated-game-server packages use it to download and update their server files. SteamCMD is not the game server itself: it downloads a server application supplied by the developer. That game's ports, configuration, save files, and launch parameters still need to be set up separately.

This guide covers Windows and Ubuntu 24.04/26.04, dedicated-server App IDs, anonymous versus authenticated logins, installation directories, app_update, validate, repeatable updates, and common errors.

Reviewed: October 19, 2026. Always confirm the correct App ID, operating system, and login method in the current documentation for the specific game.

What SteamCMD can and cannot do

Valve allows developers to distribute dedicated-server software as a separate Steam Tool with its own App ID. As explained in Steamworks documentation, developers may enable anonymous SteamCMD downloads for such packages. Therefore login anonymous works for some servers, but not all.

SteamCMD can install and update eligible server applications and verify Steam-managed files with validate. It does not decide which ports a game needs, which config files you must edit, or whether crossplay is available. Those details are game-specific.

Check the App ID, login method, and operating system first

An App ID is Steam's numeric identifier for an application. A dedicated server may have a different ID from the game sold in the store, because Valve supports a separate application of type Tool for server distribution.

  1. Open the current official server documentation for your game.
  2. Record its dedicated-server App ID.
  3. Check whether anonymous download is supported or a Steam account is required.
  4. Confirm the supported server operating systems and any required Steam branch.

For example, the official Rust server guide documents dedicated-server App ID 258550 and anonymous downloads. That ID applies to Rust, not to SteamCMD servers in general.

Expected outcome: Before running app_update, you know your game's correct server App ID, login method, and operating system.

Install SteamCMD on Windows

  1. Create a dedicated folder, for example C:\steamcmd.
  2. Download the SteamCMD ZIP from Valve's CDN.
  3. Extract the archive into the new folder.
  4. Run steamcmd.exe. SteamCMD downloads any additional files it needs on first launch.
  5. Wait for the Steam> prompt. Type quit to exit.

Keep SteamCMD and the actual game server installation in separate directories where practical. This makes the tool and game files easier to maintain.

Expected outcome: SteamCMD launches without errors and displays the Steam> prompt.

Install SteamCMD on Ubuntu 24.04 and 26.04

Ubuntu's official package index lists steamcmd for Ubuntu 24.04 LTS and 26.04 LTS as an i386 package in the multiverse repository. If multiverse or the i386 architecture is not enabled, configure them on these Ubuntu releases before installing:

sudo add-apt-repository -c multiverse
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install steamcmd:i386

The Ubuntu documentation for add-apt-repository describes the -c COMPONENT option for enabling a repository component. Run your game server itself under an unprivileged user rather than as root, following Ubuntu's least-privilege recommendations.

Scope: These steps are intended for Ubuntu 24.04/26.04; do not copy them unchanged to Debian or another Linux distribution.

Expected outcome: The steamcmd command opens its interactive console.

Install a game server using SteamCMD

A typical installation consists of choosing a destination directory, authenticating, downloading the app, and exiting. Replace APPID and the login method with the verified values for your specific server:

force_install_dir C:\Gameserver\MyServer
login anonymous
app_update APPID validate
quit

On Linux, use a Unix path such as /home/gameserver/myserver. Set force_install_dir before installing the application. If the developer requires an authenticated Steam account, do not use login anonymous.

Expected outcome: SteamCMD finishes app_update successfully and the downloaded server files appear in the chosen directory. Game-specific configuration comes next.

What app_update and validate actually do

app_update APPID installs or updates the selected Steam application. Adding validate checks the Steam-managed files against the distributed version and downloads missing or altered files when needed. Facepunch provides an example of app_update ... validate in its official Rust documentation.

This may resolve missing or corrupted original files, but it is not a backup. Facepunch also warns that updates can restore original files and require some mod files to be installed again. Do not assume every game behaves exactly like Rust; check your particular mod or plugin system.

Make server updates repeatable

A maintained game server benefits from a predictable update procedure:

  1. Notify players and stop the running server cleanly.
  2. Back up world saves and important configuration files.
  3. Run SteamCMD with the verified destination path, login method, and App ID.
  4. Inspect the output for installation or access errors.
  5. Check whether installed mods and plugins are compatible with the new server build.
  6. Start the server again, check logs, and test a connection.

On Windows, the update command might be saved in a separate update-server.bat file:

C:\steamcmd\steamcmd.exe +force_install_dir C:\Gameserver\MyServer +login anonymous +app_update APPID validate +quit

Use this example only after confirming that your server App ID allows anonymous installation. The command makes an update repeatable; it does not by itself schedule automatic updates.

Troubleshoot common SteamCMD errors

SymptomWhat to check first
No subscription or access deniedCheck the exact server App ID and whether the package requires a Steam account or license.
Files installed in the wrong directoryCheck force_install_dir and the active user's write permissions.
Server fails to launch even after SteamCMD succeedsSeparate download errors from server configuration: inspect game-specific launch parameters, runtime dependencies, config files, and logs.
Mods fail after an updateVerify mod/plugin compatibility with the new build and restore files from backups where appropriate.
Missing Linux librariesCheck the distribution, processor architecture, and package dependencies; avoid blindly copying commands from another distribution.

SteamCMD is only the starting point

SteamCMD provides the common download and update workflow, not a universal configuration for every game. Server App IDs, startup flags, ports, save locations, and licensing requirements must be checked in the relevant game's official documentation. Keep separate configuration notes for each server you run, especially when managing several games on the same machine.

Start with the game's current official server documentation. A dedicated server may use a separate Steam Tool App ID, so the store App ID is not necessarily correct.

Not universally. Developers can enable anonymous downloads for dedicated-server tools, while other packages may require a Steam account or license.

Yes. SteamCMD is Valve's separate command-line client. Whether your chosen server can be downloaded anonymously is a separate question.

It checks Steam-managed application files and downloads missing or altered files where needed. It does not replace a backup.

Usually SteamCMD is used to install or update the server application, while the actual server process runs separately. Any additional Steam services or logins required at runtime depend on the game.

Administrative rights may be needed for software installation. The running game server should normally use a non-privileged account, particularly on Linux.