For one 24-player Team Fortress 2 dedicated server, plan for a modern CPU with strong single-thread performance, 2–3 GB of RAM, and more than 15 GB of fast local storage. A lightly modded server can run with about 2 GB, while SourceMod, bots, custom maps, logs, backups, or other services make 3–4 GB a safer allocation. The 15 GB figure shown on Steam is the client’s available-storage requirement, not a complete server-sizing recommendation. Valve documents Linux compatibility and server software, but does not publish an official RAM, CPU, or disk table by player count. The figures below are practical planning targets from dedicated-server guidance and measured hosting data, not Valve guarantees.
What are the actual Team Fortress 2 dedicated-server requirements?
Valve’s public requirements page covers the player client. It lists 512 MB of RAM minimum and 1 GB recommended on Windows, 1 GB minimum on SteamOS/Linux, and 15 GB of available storage. Those numbers should not be treated as a dedicated-server specification: a server has different workloads, and Valve does not publish a supported memory or processor requirement for each slot count.
For a single instance, use this planning table:
| Workload | RAM to allocate | CPU planning point | Storage planning |
|---|---|---|---|
| Lightly modded, up to 12 players | 2 GB | About 1.5 vCores | More than the 15 GB installation |
| Typical full server, up to 24 players | 2 GB lean baseline; 3 GB preferred for headroom | About 2 vCores | More than 15 GB, with room for maps, logs and updates |
| Up to 32 players with SourceMod plugins | 4 GB | About 2.5 vCores | Use substantial free space for custom content and backups |
Flux’s 2026 measurements found roughly 700 MB idle with a 64-bit server and SourceMod loaded. SelfServr’s practical guidance says 2 GB is typically enough for a full 24-player server. Treat the table as a starting allocation: plugins, bots, map collections, logging, and co-hosted applications can raise both memory and CPU demand.
How much RAM does a TF2 dedicated server need?
Allocate 2 GB for a lean 24-player instance and 3 GB if you want room for plugins, bots, custom maps, logs, or background services. A 4 GB allocation is sensible for a 32-player server using SourceMod or for a 24-player server with a particularly heavy mod set.
Why the client’s 512 MB figure is misleading
The 512 MB minimum and 1 GB recommended values on the Steam listing describe running the game client. A dedicated server does not render the game, but it maintains world state, networking, entities, plugin state, and log files. Consequently, the client requirement is neither a minimum nor a recommendation for hosting.
How to leave a useful memory margin
- Reserve the allocation for the server process rather than counting only its idle measurement.
- Budget extra RAM when SourceMod or other plugins are enabled, because each plugin can retain state and process events.
- Allow for bots and custom maps, which can increase active entities and file-cache use.
- Keep operating-system memory outside the server’s advertised allocation when comparing hosting plans.
- Do not confuse a provider’s “burst” memory with guaranteed RAM; a server that swaps or is reclaimed during activity can suffer stalls even when its nominal total looks sufficient.
Flux’s figures are measured planning points, not hard limits. If monitoring shows sustained memory pressure, increase the allocation before adding more plugins or a second game instance.
What CPU do I need for a 24-player TF2 server?
Choose a current CPU with high single-thread performance. Team Fortress 2’s main Source-engine simulation is sensitive to the speed of one core, so a fast four-core processor is generally preferable to many slow, oversubscribed virtual cores.
Why single-core speed matters
Flux describes the simulation as running on one thread at 66 ticks per second. SelfServr likewise emphasizes single-core speed for tick-rate stability. Additional cores still help the operating system, monitoring, plugins, compression, and other services, but they do not substitute for a fast core handling the main simulation.
Practical vCore targets
Flux’s 2026 planning points are approximately 1.5 vCores for up to 12 players, 2 vCores for up to 24 players, and 2.5 vCores for up to 32 players with SourceMod plugins. A “vCore” is a provider’s allocation label, not a universal performance unit: two hosts can advertise the same vCore count while using very different physical CPUs and contention policies.
When comparing hardware or VPS plans, ask whether the advertised cores are dedicated, shared, or burstable, and look for the processor generation or an equivalent single-thread-performance measure. A plan with more slower cores may deliver worse frame-time consistency than one with fewer, faster cores.
How much storage does a TF2 dedicated server use?
The installed server is about 15 GB with the 238 official maps reported by Flux. Allocate additional space for custom and Workshop maps, plugins, logs, operating-system files, backups, and future updates. The 15 GB Steam figure is therefore a floor for the base content, not a complete disk allocation.
Why SSD or NVMe storage is worthwhile
Fast local storage helps when the server reads map and plugin files during map changes. It does not make a slow CPU faster, but it can reduce file-loading delays and makes maintenance tasks such as updates and log rotation less disruptive. NVMe is a sensible choice when buying hardware; a 1 TB NVMe SSD leaves ample room for the operating system, multiple content sets, backups, and other services. That 1 TB recommendation is a practical hardware choice, not an official minimum.
How much free space should remain?
Do not fill the disk to the installation’s edge. Keep working room for temporary update files, downloaded maps, compressed logs, and at least one recoverable backup. The exact amount depends on how many custom maps and retention periods you choose, so measure your own directory after installing the content you intend to run.
What software and compatibility prerequisites are required?
SteamCMD installs the dedicated-server files under app ID 232250. On Linux, Valve’s dedicated-server documentation lists GLIBC 2.3.2 as the compatibility floor for Source dedicated servers. That is an old compatibility minimum, not a recommendation to operate an obsolete distribution; use a currently supported Linux release and verify that its libraries and security updates are maintained.
Representative launch commands
SelfServr’s setup example uses these commands after the files are installed:
srcds.exe -console -game tf +map cp_dustbowl +maxplayers 24On Linux, the equivalent example is:
./srcds_run -game tf +map cp_dustbowl +maxplayers 24Place the game configuration at tf/cfg/server.cfg. The default game-server port in the practical setup guide is UDP 27015. If you enable RCON, Flux identifies TCP as the RCON transport; secure the password and expose only the management access you actually need.
What these commands do
-consolekeeps the Windows process in a console-oriented mode for administration.-game tfselects Team Fortress 2’s game directory.+map cp_dustbowlstarts the server on a named map.+maxplayers 24sets the advertised slot limit for this instance.
Change the map and slot value to match your configuration, and confirm that your firewall forwards the chosen UDP port to the server host.
Can I run a TF2 dedicated server on a VPS?
Yes, provided the VPS offers dependable single-core performance, guaranteed memory, fast local SSD or NVMe storage, and a network location close to your players. The virtualization label alone is not enough to judge suitability.
What to compare between VPS plans
| Comparison point | Why it affects a TF2 server |
|---|---|
| Single-core CPU performance | The main simulation is sensitive to per-core speed and tick consistency. |
| Guaranteed versus shared RAM | Guaranteed memory avoids contention and swapping during busy rounds. |
| SSD/NVMe and disk headroom | Map changes, updates, logs, and backups need both speed and free capacity. |
| Player slots and plugin workload | A 32-player modded instance needs more margin than a lightly modded 12-player one. |
| Network location and latency | Players generally perform better when the server is geographically nearer to them. |
| Bandwidth and DDoS protection | Protection and adequate transfer limits reduce disruption during attacks or popularity spikes. |
| Backups and update automation | Managed recovery and patching reduce maintenance risk. |
| Instance scope | Check whether the quoted resources cover one server or several instances. |
A low-cost VPS with oversubscribed CPUs can appear sufficient in an idle test and still miss frame-time targets when players, bots, and plugins are active. Ask the provider how CPU contention is handled and whether the memory figure is dedicated.
How much network capacity does a TF2 server need?
Flux estimates roughly 30–60 KB/s per player at default rates, with UDP 27015 carrying game and query traffic. Actual usage varies with tick settings, plugins, player activity, and custom content, so treat that estimate as a planning range rather than a guaranteed constant.
For 24 active players, multiply the per-player estimate by the number of simultaneous players, then leave additional capacity for connection bursts, updates, administration, and other services. Choose a host with a suitable network route to your audience and DDoS protection if the server will be public.
How should I size a server by player count?
Start with the slot count, then add margin for modifications and co-hosted workloads. The following targets reflect Flux’s measured planning points and SelfServr’s 24-player guidance:
- Up to 12 players: allocate about 2 GB RAM and 1.5 vCores. This is appropriate for a small, lightly modded instance.
- Up to 24 players: use 2 GB as a lean baseline, or 3 GB when SourceMod, bots, custom maps, logging, or other services are present. Plan around 2 vCores with strong single-thread performance.
- Up to 32 players: allow 4 GB RAM and approximately 2.5 vCores when SourceMod plugins are enabled. Keep extra disk space for the larger content and log workload.
These are per-instance planning values. If you host several servers on one machine, add the allocations together and reserve resources for the operating system, monitoring, and backups rather than assuming idle memory or CPU is fully reusable.
What are the common sizing mistakes and how do I fix them?
Using the Steam client requirement as the server minimum
Symptom: a plan advertises 512 MB or 1 GB because those numbers appear on the game page.
Fix: size the dedicated server separately: begin at 2 GB for a lean 24-player instance and increase the margin for plugins, bots, maps, and other services.
Buying cores without checking their speed
Symptom: the provider offers many vCores, but tick stability degrades during busy rounds.
Fix: prioritize a current processor with strong single-thread performance and ask whether the cores are shared or dedicated.
Allocating exactly 15 GB of disk
Symptom: updates fail or logs and custom maps consume the remaining space.
Fix: treat 15 GB as the base installation, then add explicit capacity for custom content, logs, backups, and temporary update files.
Ignoring port and management security
Symptom: players cannot connect, or an exposed RCON service becomes an administrative risk.
Fix: allow UDP 27015 (or your selected game port) through the firewall, verify forwarding, and restrict TCP RCON access to trusted addresses with a strong password.
Assuming the Linux compatibility floor is a current distribution recommendation
Symptom: the server runs on an unmaintained operating system because it meets the documented library minimum.
Fix: use a supported distribution with current security updates; regard GLIBC 2.3.2 only as the oldest documented compatibility boundary.
What is the best practical specification for one 24-player server?
For a public, lightly to moderately modded server, choose a modern high-clock CPU with strong single-thread performance, 3 GB guaranteed RAM, and an SSD or NVMe drive with substantially more than 15 GB free. A 2 GB allocation can work when the instance is lightly modded and runs no other services, while 4 GB gives comfortable room for heavier SourceMod configurations, bots, and co-hosted tools.
Install the server with SteamCMD app ID 232250, keep server.cfg under tf/cfg, expose the required UDP game port, and monitor CPU frame time, memory use, disk headroom, and network traffic during a full round. Adjust the allocation from observed load rather than from the client’s minimum requirements.
Frequently Asked Questions
Does TF2 dedicated-server hosting require a graphics card?
No dedicated graphics card is needed for the server process because it does not render the game for players. Spend the budget on a fast CPU core, guaranteed memory, storage, and network quality instead.
Can I use a shared hosting plan for a 24-player TF2 server?
You can, but verify that the plan guarantees memory and provides consistent CPU time. Shared or burstable resources may work at light load yet produce unstable tick timing when the server is full.
Should I run the server on Windows or Linux?
Both platforms are represented in the standard launch examples. Linux has a documented GLIBC compatibility floor, while the better choice is the platform you can keep patched, monitor, back up, and administer reliably.
How do I estimate disk space for custom maps and logs?
Install the exact map and plugin collection you intend to use, measure its directory, and add room for updates and backups. Content size varies enough that a fixed allowance beyond the 15 GB base cannot be stated accurately.