The honest answer to "how much RAM and CPU does an Assetto Corsa server need?" is: it depends entirely on which kind of server you're running. A racing server is light — a small grid, no AI, modest resources. A freeroam server with AI traffic is a different animal — CPU-hungry, disk-hungry, and bottlenecked by things RAM can't fix. Sizing them the same way is how people end up with a stuttering cruise server or an over-bought race box.
Search this question and you'll mostly get client PC specs — what your gaming rig needs to play the game. That's not what a server needs. This is the server-side answer, split by the two server types, because they're genuinely different.
The short version
- Racing (Kunos server): light. RAM is rarely the limit; the grid caps at ~24 anyway. A mid-tier plan handles a full grid comfortably.
- Freeroam (AssettoServer with AI traffic): heavy on CPU and disk, light on RAM. Single-thread CPU clock is the real spec, and traffic density × player count is what drives the load.
- RAM is almost never your bottleneck. If a host is selling you an Assetto Corsa server purely on gigabytes of RAM, they're quoting the wrong number.
What does a racing server need?
A stock Kunos racing server is contained. There's no AI traffic to simulate, and the grid is capped at the track's pit-box count — around 24 on most tracks. That puts a ceiling on how much work the server can be asked to do.
What matters:
- CPU: still single-thread sensitive — a full 24-car grid needs clean netcode, so clock speed helps — but you're not simulating extra cars beyond the grid. A couple of solid cores is plenty.
- RAM: modest. A race server's memory footprint is small; 2–4 GB covers most leagues.
- Disk: modest. Official cars and tracks plus a few mods — nowhere near freeroam's appetite.
For most leagues, a Starter or Cruise plan runs a full grid without breaking a sweat. You'd only step up for very large mod-track packs or to run several concurrent race servers.
What does a freeroam server need?
This is where it gets interesting, because the cost model is unusual. AI cars are simulated on the server and streamed to nearby players, so load scales with traffic density multiplied by player count, not just how many people are connected. Two players on an empty map is nothing; forty players on a dense Shutoko traffic server is a serious workload.
The three things that actually matter:
1. Single-thread CPU clock — the real spec. Assetto Corsa's physics and netcode are heavily single-threaded per instance. A 4-core CPU at 4.5 GHz will hold more traffic smoothly than an 8-core at 3.0 GHz. Ask a host about clock speed, not just core count.
2. Disk — bigger than you'd expect. Freeroam maps and traffic-car packs are large. Shutoko Revival Project alone is 1–1.9 GB, and a real server hosts a map plus car packs, often several gigabytes total. Disk is a genuine spec line here.
3. RAM — the least of your worries. It scales gently with player and AI count. The table below is a reasonable guide; you'll hit CPU or disk limits long before RAM.
As a starting-point guide (this comes from hosting-industry testing, not an official Assetto Corsa benchmark — treat it as directional):
| Target players | CPU guidance | RAM | Storage |
|---|---|---|---|
| 16 | 4 cores / ~3.5 GHz | 8 GB | 40 GB SSD |
| 32 | 6 cores / ~4.2 GHz | 16 GB | 60 GB NVMe |
| 64 | 8 cores / ~4.5 GHz | 24 GB | 80 GB NVMe |
The practical working band is 50–100 concurrent AI cars, and the rule of thumb is to leave 20–25% CPU headroom rather than running flat out. The despawn radius is your biggest lever — only cars near players are simulated — which is what makes 50–100 cars viable on a huge map. We go deeper on this in what AI traffic costs in CPU and RAM.
Why RAM isn't the number to shop on
Game hosts love to sell RAM because it's an easy, comparable number. But an Assetto Corsa server isn't RAM-bound. A race server barely touches memory; a freeroam server runs out of CPU or disk first. If two plans have the same RAM but one has a faster CPU clock and more NVMe storage, that's the one that runs a traffic server better — even though the RAM line looks identical.
This is why our Assetto Corsa plans publish RAM and storage and scale CPU alongside them, rather than hiding behind a single RAM figure:
| Plan | Price / month | RAM | Storage |
|---|---|---|---|
| Starter | $3.99 | 2 GB | 25 GB |
| Cruise | $6.99 | 4 GB | 50 GB |
| Pro | $10.99 | 6 GB | 100 GB |
| Max | $14.99 | 8 GB | 200 GB |
For a racing league, start around Starter/Cruise — the grid cap means you rarely need more. For a freeroam server, weight your choice toward the higher tiers as your player count and traffic density climb, because that's where CPU and disk headroom come from. Same plans, same prices for both products — you're picking capacity, not paying a premium for one side.
Frequently Asked Questions
How much RAM does an Assetto Corsa server actually need?
Less than most hosts imply. A racing server is happy with 2–4 GB; a freeroam server scales gently with players and traffic but still isn't RAM-bound — you'll hit CPU or disk limits first. Don't choose a plan on RAM alone; look at CPU clock and storage.
Is Assetto Corsa server hosting CPU or RAM intensive?
It depends on the type. A racing server is fairly light on both. A freeroam server with AI traffic is CPU-intensive — every AI car is simulated on the server — and disk-intensive because maps are large, but it's not especially RAM-hungry. Single-thread CPU speed is the spec that matters most for freeroam.
Why does my Assetto Corsa server lag with lots of players?
On a freeroam server, more players means more AI traffic being simulated and networked at once, so CPU load climbs faster than player count alone. If it stutters, you're almost certainly CPU-limited — either raise the plan's CPU headroom or reduce traffic density. On a racing server, lag with a full grid usually points to a weak single-thread CPU or a poor network route.
What size server do I need for a Shutoko cruise server?
Shutoko plus AI traffic plus a big population is one of the more demanding setups in Assetto Corsa. Budget for strong single-thread CPU and generous NVMe disk (the map alone is 1–1.9 GB), and lean toward the higher plans as you push past 30–40 players with dense traffic.
Not sure which plan fits your community? For a racing league a mid-tier server runs a full grid easily; for a freeroam traffic server weight toward CPU and disk headroom as your density grows. Our plans publish RAM and storage and scale CPU with them, so you can size honestly.
