Shooter · Lightweight
Run a Team Fortress 2 Dedicated Server with Swarm Hosts
Host Team Fortress 2 on your own Windows 10/11 or Linux computer. Swarm Hosts gives you a browser control panel to start, stop, monitor, and back up your server.
- Server Actions
- Guided settings
- Backups
Available in Early Access
Hardware and runtime
What Team Fortress 2 needs
Minimum requirements are a starting point. World size, player count, content, and game settings can require more resources.
- CPU
- 2+ cores
- Memory
- 2 GiB minimum
- Player traffic
- TCP and UDP
- Backup coverage
- 2 saved data locations
The guided launch form exposes the server name, password, map, maximum players, and LAN mode. Leave Server Actions password blank to generate one automatically, or set 16–128 letters, digits, underscores, or hyphens. Keep this credential private; players use only the optional join password.
- Gameplay and query: assigned UDP port
- TCP mapping: the same assigned port number
- Persistent data: /home/steam/tf2
- Default map: cpbadlands
- Minimum resources: 2 CPUs and 2 GB RAM
Technical overview
Team Fortress 2 uses Valve's Source dedicated server. Swarm Hosts installs the server anonymously through SteamCMD and persists the runtime and configuration under /home/steam/tf2.
Launch workflow
From host to running server
After launch, use Settings → Team Fortress 2 Settings to change managed values. Saving settings restarts or recreates the server and disconnects players.
- Open Launch and choose Team Fortress 2.
- Set the server name, starting map, maximum players, and an optional player password.
- Keep LAN mode disabled for an internet-accessible server.
- Confirm the requested CPU and memory fit the selected Swarm Host, then launch and wait for the server to report Running. The first launch downloads the server files and can take considerably longer than later starts.
Networking
How players connect
When the Swarm Server is running, copy the player hostname or IP and UDP port from its connection details. In Team Fortress 2, open the developer console and use connect host:port, adding the player password when prompted. Share only that player endpoint and keep the Server Actions password private.
Managed shared relay when the game, host, and current relay path support it.
Server Actions
Manage your Team Fortress 2 server
Available tools depend on the game, server status, and your permissions. The game guide explains any setup needed for Server Actions.
Server status
Read the current map and player summary.
List players
Refresh the verified connected-player list.
List installed maps
Refresh maps installed in the pinned runtime.
List bans
Refresh identities currently banned by the Source server.
Broadcast message
Send a server-authored chat message.
Change map
Change immediately to a freshly verified installed map.
Kick player
Disconnect a freshly verified connected player.
Ban player
Ban and disconnect a freshly verified connected player, then persist the ban list.
Remove ban
Remove a freshly verified Source identity ban and persist the ban list.
Mods & Content status
Mods and custom content
SourceMod plugins are untrusted executable code. Upload compatible files manually and restart the server.
SourceMod plugins can execute server code and are managed manually. Back up and stop the server before uploading a compatible framework and plugin set through Files & Backups. Plugin files belong under tf/addons/sourcemod/plugins. Start the server and verify its logs and player connections afterward. Swarm Hosts has no Team Fortress 2 Mods & Content page and does not install the framework, discover plugins, update them, or roll them back automatically.
Know before launch
Before you launch
- Host on Windows 10/11 or Linux with Docker Desktop in Linux-container mode on Windows, or Docker Engine or rootful Podman on Linux.
- Managed shared relay when the game, host, and current relay path support it.
Windows 10/11 + Linux
Ready to host Team Fortress 2?
Connect the Windows or Linux computer you already own, then follow the game-specific launch path.