How many CPU cores do I need for a Squad server?

Surprisingly few, but they must be fast. Squad's server is heavily single-thread bound, so 2 high-clock dedicated cores can run a full server, with 3-4 cores giving headroom for the OS and networking. A high boost clock (4.0 GHz+) matters far more than core count.

Why does CPU clock speed matter so much for Squad?

Squad runs on Unreal Engine, which concentrates the heavy simulation, ballistics, vehicle physics, AI, and player updates, on a single main game thread. That thread can only use one core at a time, so per-core speed sets the ceiling on server performance and tick rate.

Do mods increase Squad server requirements?

Yes. Extra maps, factions, and assets raise both RAM usage and map load times, and increase the download players must complete to join. Budget roughly 40% more RAM for a large mod list, and use fast SSD/NVMe storage to keep loading screens short.

How much storage does a Squad dedicated server need?

The base server files are about 25-30 GB. A 35-50 GB allocation covers vanilla or lightly-modded servers including logs and maps; heavily-modded setups with many custom maps may want 100 GB or more. Use SSD or NVMe for fast map loading.

Squad Server Requirements: RAM, CPU & Bandwidth

Q: How much RAM does a 100-player Squad server need?

Real-world usage at a full 100 players is around 24-28 GB, so you should provision 32 GB to leave safety margin and avoid swapping during peak load. Smaller servers up to about 50 players run comfortably on 16 GB.

Q: How much bandwidth does a Squad server use?

Plenty at full population. Hosts typically place these servers on a 1 Gbps uplink, and a busy full-time 100-slot server can move several terabytes per month. Look for unmetered or generous bandwidth and low latency to your players.

Quick recommendations for Squad
Setup	Players	RAM	Notes
Small / training (up to 40)	up to 40	16 GB	Comfortable on 16 GB; one fast core handles the game thread. Good for clans, training and modded testing.
Medium (up to 60)	up to 60	16 GB	Observed usage ~14-16 GB. Single-thread performance starts to dominate as ballistics and vehicle physics scale.
Large (up to 80)	up to 80	24 GB	Observed usage ~18-22 GB. Needs a high-clock CPU to hold server tick under heavy combined-arms fights.
Full / licensed (up to 100)	up to 100	32 GB	Observed usage ~24-28 GB at full pop. Use 32 GB for safety; pair with a top-tier high-clock core and a 1 Gbps uplink.

What a Squad server actually needs

Squad's dedicated server is unusual because its bottleneck is almost never RAM or core count, it's single-thread CPU performance. The Unreal Engine server process does the heavy lifting (ballistics for every round in flight, vehicle physics, AI, and constant position updates for up to 100 players) on one main game thread, with a separate networking thread handling replication. That means a CPU's per-core clock speed and IPC determine how well your server holds its tick rate under a full firefight, while extra cores mostly just keep the operating system and logging out of the way.

CPU

Aim for a modern high-clock CPU with a 4.0 GHz+ boost and strong single-core benchmarks. Hosting providers commonly recommend dedicated cores clocked at 3.8 GHz or higher for Squad specifically. In practical terms, two genuinely fast dedicated cores can run a full 100-player server, but allocating three to four cores gives comfortable headroom for the OS, the networking thread, and any overhead from logging or a control panel. Chasing a high core count at the expense of clock speed is a mistake here, an 8-core chip at 2.5 GHz will perform worse than a 4-core chip at 4.5 GHz.

RAM

Real-world memory usage scales roughly with player count. Community and host observations put consumption at about 10-12 GB at 40 players, 14-16 GB at 60, 18-22 GB at 80, and 24-28 GB at a full 100-player server. Because of that, 16 GB is a sensible floor for servers up to ~50 players, while 80-100 player servers should be provisioned with 32 GB to leave safety margin and avoid swapping during peak load. A heavy mod list, extra map layers, custom factions, and additional assets, can push RAM noticeably higher, so budget roughly 40% more memory if you plan to run a large collection of mods.

Storage

Storage needs are modest and largely fixed rather than per-player. The base game server files are around 25-30 GB, and you'll want extra room for maps, logs, configuration, and mods. A 35-50 GB allocation is plenty for a vanilla or lightly-modded server; heavily-modded servers with many custom maps may want 100 GB or more. Use SSD or NVMe storage so map and level loading between rounds is fast, slow disks lengthen the loading screen all players sit through at every map change.

Network and bandwidth

Bandwidth is a real constraint at Squad's player counts. With up to 100 clients receiving continuous state updates, providers typically place these servers on a 1 Gbps uplink, and a 50-slot server realistically wants at least 50 Mbps of dedicated upload. Total monthly transfer depends heavily on average population and uptime; a busy full-time 100-slot server can move several terabytes per month. Low, stable latency to your player base and unmetered or generous bandwidth are more important than raw peak speed.

Getting the most out of a Squad server

Because Squad lives and dies by single-thread speed, the single highest-impact optimization is simply choosing hardware with the best per-core clock and IPC you can get, this does more for server tick rate than any config change. If your host allows it, pin the server's game thread to a dedicated physical core and keep other workloads off it.

Watch your server tick rate (server FPS) as your key health metric. When it drops under heavy combined-arms fighting, the cause is almost always CPU, not RAM or bandwidth. Disable or trim verbose logging in production, since constant disk writes add avoidable overhead. Keep the game files and maps on SSD/NVMe so between-round map loading stays short for everyone.

Be deliberate with mods: each added mod increases RAM use, map load time, and the size of the download players must complete to join. Run only what your community actually uses, and test a new mod list on a private instance before deploying it to a full server. Keep the server build updated, performance fixes ship regularly, and a server running an outdated version can also block players on the current client build. Finally, place the server geographically close to the majority of your players to minimize latency, which matters more to perceived quality than shaving a few milliseconds off tick time.

What to look for in a host

Squad rewards a specific hardware profile, so judge hosts on the details rather than headline specs. The most important factor is CPU clock speed and single-core performance: look for clearly stated high-clock CPUs (4.0 GHz+ boost) and dedicated cores rather than shared or oversold ones. A host advertising many cores at a low clock is a poor fit for this engine.

Confirm the RAM allocation matches your target player count using realistic figures, 16 GB for small-to-mid servers and 32 GB for 80-100 slots, and check whether you can upgrade as you grow. Verify that storage is SSD or NVMe, since disk speed directly affects map loading between rounds.

On networking, look for a generous, ideally unmetered, bandwidth allowance and a 1 Gbps uplink, plus data-center locations close to your player base for low latency. For management, prioritize full control over configuration files, easy mod installation, automatic or one-click updates to keep pace with game patches, and accessible backups. DDoS protection is worth having given that public game servers are common targets.

Finally, weigh support quality and contract flexibility: responsive support and month-to-month or short-term billing let you test real performance under load before committing. Whatever the marketing claims, the true test is sustained server tick rate with a full server during a heavy fight, so a short trial or refund window is genuinely valuable.

CPU note: Squad runs on Unreal Engine and is heavily single-thread bound: the server uses one main game thread plus a networking thread, so high per-core clock speed (4.0 GHz+ boost) matters far more than core count. 2 fast dedicated cores can run a full server; 4 gives headroom for the OS, logging and a layer of safety margin.

RAM figures are real observed-usage ranges, not theoretical minimums. Squad is bottlenecked by single-core CPU speed long before RAM, so prioritize clock speed. Heavy mod sets (extra maps, factions, assets) raise both RAM and load times; budget roughly +40% RAM with a large mod list. Storage is small and largely fixed (game files + maps + logs); it does not scale meaningfully per player.