Unturned Server Requirements Calculator

What an Unturned server really needs

Unturned 3 ships with a standalone dedicated server, U3DS, that you install through SteamCMD on Windows or Linux. (There is no supported macOS server.) Compared with most survival multiplayer games it is remarkably lightweight, which is part of why it stays popular for small self-hosted communities.

RAM

Memory use scales gently with players. As a rough baseline drawn from host spec sheets and the official guidance, expect around 2 GB for 2-4 players, 3 GB for 5-8, and about 5 GB at the common 24-player default cap. That works out to a small fixed base of roughly 2 GB plus only about 0.1 GB per active player. A 1-2 GB allocation can technically run a handful of friends, but 2-4 GB is the sensible floor for a vanilla community server once you account for the operating system and Steam Workshop assets. The single biggest RAM variable is not players at all — it is Workshop content. Large curated maps and long mod lists can each add 0.5-1 GB, so a heavily modded 24-slot server is more comfortable at 6-8 GB.

CPU

This is where Unturned's architecture matters: the core game simulation runs on a single thread, so per-core clock speed and single-thread performance dominate over core count. A 2.4 GHz dual-core is the practical minimum for a few players; aim for 3.5 GHz+ for a standard 24-slot server and a fast modern 4.0 GHz+ core if you want to push toward 48 players. Adding more cores rarely helps a single busy server — it mainly benefits the OS, background Workshop downloads, and running several separate server instances on one box. CPU load rises with concurrent players, active zombies and AI, spawned vehicles, and heavy plugins, so trimming those limits is often more effective than buying a bigger CPU.

Storage

The server install itself is modest — budget around 4-6 GB for the U3DS files and a vanilla map. Storage then grows mainly with downloaded Workshop maps and mods rather than with the number of players, since per-player save data is tiny. A few large custom maps plus mod packs can easily push total usage past 10 GB, and routine backups multiply that. An SSD (NVMe ideally) is strongly preferred; it cuts map load and player-join times noticeably versus spinning disks.

Bandwidth

Network needs are also moderate. A stable upload of roughly 10-20 Mbps handles a typical full server, and ongoing monthly transfer lands in the low single-digit GB per active player for normal play. One caveat: when players first join a modded server they download all your Workshop content over Steam, which is a one-time burst per player and per content update rather than continuous traffic. Keeping your Workshop list curated reduces both that burst and connection times.

Vanilla vs modded

Vanilla survival on the official maps (PEI, Washington, Russia, Yukon and the like) fits comfortably in the baseline figures above. Once you add curated Workshop maps, item/vehicle mods, and a plugin framework such as RocketMod or OpenMod, plan for roughly 1.5-2x the RAM and a lower practical player cap, because both memory pressure and single-thread tick cost climb.

Getting more out of your Unturned server

Because the simulation is single-threaded, the most effective optimizations reduce per-tick work rather than add hardware:

• Prioritize CPU clock speed. A fast 4-core will out-perform a slow 16-core for a single server. When choosing a host plan or building a box, look at single-thread benchmarks first.
• Curate your Workshop list. Every extra map and mod adds RAM use and lengthens the download players face on first join. Remove content you do not actively use; bloated lists are a common cause of slow connects and people bouncing off the server.
• Tune spawn and limit settings. High zombie/AI counts, large vehicle limits and dense item spawns all increase tick cost. Lowering these on a busy public server often does more for smoothness than extra RAM.
• Right-size RAM. Allocate what you need plus headroom for the OS, but there is little benefit to over-allocating a lightweight Unturned server — the bottleneck is the CPU thread, not memory.
• Use SSD/NVMe storage to speed map loads and Workshop reads, and keep backups on separate storage so backup jobs do not contend with the live server.
• Run multiple instances for big communities. If you want both a large player count and heavy content, splitting modes across separate server processes spreads load across CPU cores better than one oversized server.
• Keep the server and Workshop content updated after Unturned patches to avoid version mismatches that block players from joining.

What to look for in an Unturned host

Whether you self-host or rent, a few things matter more than headline RAM numbers for Unturned specifically:

• Strong single-thread CPU. Since the game loop is single-threaded, a high clock speed and good per-core performance raise your real player ceiling far more than a large core count. Favor plans built on modern, high-frequency CPUs.
• Right-sized RAM with room to grow. Vanilla servers are light, but if you plan to add curated maps and mods, choose a plan that lets you scale memory up to 6-8 GB without migrating everything.
• SSD or NVMe storage for fast map loads and Workshop reads, with enough space for several large custom maps plus backups.
• Steam Workshop support and easy mod management, since most Unturned communities rely on it. Look for a simple way to add Workshop IDs and a plugin framework if you want RocketMod/OpenMod.
• Adequate, stable bandwidth (comfortably above 10-20 Mbps upload) and good network routing to your players' region to keep latency low.
• Full config access to commands and config files so you can tune player caps, spawns and limits, plus automated backups and a DDoS-protected network for public servers.

Match the plan to your real plans, not the maximum: a modest plan suits a vanilla friends server, while a heavily modded community justifies more RAM and a faster core.

CPU note: Unturned's dedicated server (U3DS) runs the main simulation on a single thread, so per-core clock speed and single-thread performance matter far more than core count. A 2.4 GHz dual-core is the practical minimum for a few friends; aim for 3.5 GHz+ for up to ~24 players and a fast 4.0 GHz+ modern core for 24-48 players. Extra cores mostly help the OS, Steam/workshop downloads and running multiple server instances rather than a single busy server. The server is lightweight by modern standards — even old laptops have hosted 15-20 players. CPU load rises with concurrent players, active zombies/AI, vehicles and heavy workshop content, not with raw RAM.

Figures are for the official Unturned 3 dedicated server (U3DS) on a headless Windows or Linux box (macOS hosting is unsupported). Unturned is genuinely light on RAM compared with games like Rust or modded Minecraft: a baseline of ~2 GB plus roughly 0.1 GB per active player covers most vanilla servers, with 24 players fitting in 4-5 GB. The dominant cost driver is workshop content, not player count — large curated maps and big mod lists inflate RAM use and connection times, so the modded multiplier (~1.8x) is a planning guide, not a hard rule. Allocate extra RAM beyond what you need for the OS itself. Because the simulation is single-threaded, throwing more cores at a busy server does little; a faster core is what raises the practical player ceiling.