How Much RAM Does a TF2 Server Need?

The official Valve documentation for Source Dedicated Server lists 512MB as the minimum RAM to run a server, and 1GB as enough for 60+ player slots. Those numbers come from documentation that hasn’t meaningfully changed since the mid-2000s, when TF2 hadn’t even launched yet. They’re not wrong exactly - TF2’s SRCDS process really is that light - but they leave out almost everything that matters for actually running a server today.

This guide covers what a TF2 server actually uses in practice: the base process, SourceMod plugin stacks, SourceTV, MvM bot loads, and where the CPU fits into the picture. If you just want the quick answer, skip to the recommendations table.

What Valve’s documentation says (and why it’s incomplete)

The Valve Developer Community wiki’s SRCDS page - originally written around 2004-2006 and largely unchanged since - states that 512MB handles a normal server, and 1GB is enough to run over 60 player slots total. By raw process terms, that’s still accurate. A vanilla TF2 dedicated server sitting idle uses somewhere in the 400-600MB range.

The problem is that nobody runs a bare SRCDS process. You have an operating system consuming memory underneath it, SourceMod and Metamod loaded on top of it, custom maps cycling through it, and potentially SourceTV buffering spectator data alongside it. Those layers add up, and the 2004-era baseline tells you nothing about any of them.

TF2 also received a 64-bit server binary update that allows the process to address more than 4GB of RAM. The old 32-bit limit was a ceiling that wouldn’t let you throw more memory at a problem even if you wanted to. That ceiling is now gone, which matters for heavily loaded servers that actually benefit from the extra headroom.

What actually uses RAM on a TF2 server

The base server process

A vanilla TF2 server running 24 slots with no plugins uses roughly 600-800MB in practice once players are connected and a match is in progress. Running 32 slots (the standard maximum) pushes that a little higher, but the difference isn’t dramatic - TF2 doesn’t store much per-player state compared to something like a survival game with persistent world data.

Map changes trigger a memory reload for each new map’s assets, so a server with a long uptime and a large custom map rotation will drift slightly higher than one running stock maps on a fixed cycle.

SourceMod and Metamod

This is where RAM usage gets variable. A base Metamod + SourceMod install with only the default plugins adds modest overhead. A full community server stack - anti-cheat, HLstatsX or equivalent stat tracking, a shop system, custom votemap, RTD, a custom gamemode plugin or two - is a different story. Each plugin loads into the server process and stays resident. There’s no single number for a “plugin-heavy” server because it depends entirely on which plugins and how many, but the difference between three plugins and thirty is measurable.

The other factor is uptime. Some plugins accumulate memory over long sessions - nothing catastrophic, but a server that’s been running for days without a restart will typically sit higher than one that restarted this morning. This is normal Source engine behavior and not specific to any particular plugin.

Custom maps

Stock TF2 maps are well-optimized for memory. Large community-made maps with dense geometry, lots of custom textures, or high entity counts load more assets into memory than something like cp_badlands or ctf_2fort. Running a 24/7 custom map server with detail-heavy maps is worth keeping in mind when sizing RAM, though it’s rarely the deciding factor on its own.

SourceTV

SourceTV lets spectators watch a match live with a short delay without taking up a player slot. It’s common on community servers and tournament servers. When enabled, it adds a small but real overhead - it maintains its own buffer of game state data to handle the broadcast delay. It’s not large, but it’s one more thing contributing to total memory consumption.

MvM bot AI

Mann vs. Machine runs AI-controlled robot bots server-side - pathfinding, targeting, wave management. This load hits the CPU, not RAM. A standard 6-player MvM mission doesn’t use noticeably more memory than a standard 6v6 match. What it does do is keep the server’s single CPU thread busier, which matters more than any RAM consideration for MvM performance.

Community MvM setups with custom wave files, large bot counts per wave, and plugin stacks on top do add incremental memory pressure - but the CPU story is still more important there too.

RAM recommendations by server type

These ranges assume WinterNode’s 4GB minimum as the floor. Going below that isn’t a configuration we support, and for good reason - OS overhead alone on a Linux game server eats into your headroom before SRCDS even loads.

Most community server operators running a standard public server with a reasonable plugin count will be comfortable at 4GB. If your server has been running for a while and memory usage is consistently high, the first questions to ask are: how many plugins are loaded, and when did you last restart?

Why CPU matters more than RAM for TF2 performance

This is the part that gets missed in almost every TF2 server sizing discussion. TF2 runs on the Source engine, which is largely single-threaded. All player physics, hit detection, and game logic processing happens on one CPU core. It doesn’t matter how many cores your host provides - TF2 will use one of them for the heavy lifting.

The practical consequence is that TF2 server performance is directly tied to single-core clock speed. A 24-slot server on a slow processor will show lag, rubber-banding, and poor tick rate at capacity, regardless of how much RAM it has free. Adding RAM to a CPU-bottlenecked server doesn’t help.

The way this shows up in practice: a server feels sluggish with a full player count, but memory usage looks fine. That’s almost always a CPU story. Conversely, a server with genuinely low memory available will usually show it through slower map loads, eventual crashes under load, or the operating system starting to swap - not through gameplay lag alone.

MvM compounds this. Each AI bot adds to that single-threaded CPU load, which is why large-wave custom MvM missions are more demanding than most people expect. The robots aren’t expensive in RAM - they’re expensive in compute cycles.

WinterNode’s TF2 servers are priced at $1.99/GB - so a 4GB server is $7.96/month, and 6GB is $11.94/month. CPU usage is unmetered and unthrottled, which matters for TF2 specifically for the reasons above. Many of our nodes run AMD Ryzen 9000X series hardware, which has strong single-core performance.

Everything’s backed by our 48-hour refund policy, so there’s no risk in starting at 4GB and seeing how your specific plugin stack performs before committing to more. Got questions about your server configuration or want help reading a performance report? Our support team responds to tickets with actual humans, and we’re on Discord if you prefer real-time help.

Get your TF2 server →