Shooter · High-resource
Host Killing Floor 2 Servers in Staging (Staging)
Staging: awaiting manual game-client validation. Player connections are not yet verified. Evaluate this server before inviting players.
Host Killing Floor 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.
- Backups
Staging · client validation pending
Hardware and runtime
What Killing Floor 2 needs
Minimum requirements are a starting point. World size, player count, content, and game settings can require more resources.
- CPU
- 4+ cores
- Memory
- 8 GiB minimum
- Player traffic
- UDP
- Backup coverage
- 1 saved data location
Start with 4 CPU cores and 8 GiB memory on a Linux host with fast storage and enough free disk for server downloads, generated worlds, and backups. These are evaluation allocations, not a maximum-player performance promise. Downloads and initial world setup may take several minutes.
Technical overview
Swarm Hosts offers the native Linux runtime for evaluation. Read Staging games before inviting players.
Launch workflow
From host to running server
The default evaluation map is KF-BioticsLab in Survival mode with six player slots. Web administration is not published.
The internal routes are 7777/UDP for players, 20560/UDP for Steam, and 27015/UDP for server queries. Share the assigned public player endpoint shown on the server page. Container ports can differ from public relay ports. See Relays and Port Forwarding. Private administration services are not player routes.
- Choose Killing Floor 2 from Staging and select a suitable host.
- Read the settings below and use a new disposable test deployment.
- Launch, inspect startup logs, and monitor resources before attempting a client connection.
Networking
How players connect
Use the PC server browser with the matching game version. Check both the player route and query route; a local query response does not establish public listing. See the publisher guidance). Check the reported server version before selecting a client; the template does not promise that a later download has the same build as the staging test.
Managed shared relay when the game, host, and current relay path support it.
Game management tools
Manage your Killing Floor 2 server
Available tools depend on the game, server status, and your permissions. The game guide explains any setup needed for Server Actions.
Use the settings, files, backups, logs, and server controls available for this game. The complete guide documents any game-specific action prerequisites.
Mods & Content status
Mods and custom content
Killing Floor 2 workshop content is managed through server config files. Track ids here, then apply them to the persisted config.
A desired Workshop-ID list can record content for later manual work; it does not install, validate, or roll back artifacts. Custom maps and Workshop content need separate manual evaluation. Preserve a backup before modifying server files and repeat connection and persistence checks after a change.
Know before launch
Before you launch
- Awaiting manual game-client validation. Fresh image startup, five-minute stability, and generated configuration persistence on restart were tested locally on 2026-10-09. Manual client connection and public network validation remain pending.
- 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 Killing Floor 2?
Connect the Windows or Linux computer you already own, then follow the game-specific launch path.