A small, vanilla Assetto Corsa dedicated server can run with roughly 2–3 GB of RAM and about one to one-and-a-half well-performing vCPUs, but those figures are hosting examples rather than official limits. Kunos has not published a universal acServer CPU or memory requirement. Storage starts with the server and game files, then grows with every custom car, track, weather package, log, staged update and backup. For a self-hosted machine that also runs the operating system and management tools, 16 GB of RAM and an SSD provide useful headroom; neither is an official minimum.
The practical limit is often networking rather than raw hardware. Assetto Corsa’s documented defaults use TCP and UDP port 9600 for race traffic and HTTP port 8081 for lobby traffic. Upload capacity, latency, packet loss and the track’s pit count determine how many drivers can have a reliable session.
What are the official Assetto Corsa dedicated-server requirements?
There is no Kunos-published specification that defines the CPU, RAM or disk required by acServer. The figures shown in the Steam listing describe the game client, not a dedicated server process. Primcast’s hosting guide explicitly notes that Kunos does not publish a processor or memory requirement for acServer.
| Resource | Published figure or fact | How to interpret it for a server |
|---|---|---|
| RAM | Steam client: 2 GB minimum, 6 GB recommended (2014 listing) | Not an acServer limit. Small hosting examples use 1.5–3 GB, but leave additional memory for the operating system, mods, logs and other services. |
| CPU | No Kunos acServer requirement table | Favor strong per-core performance and clock speed. AI traffic, several instances and other applications increase demand. |
| Storage | Steam client: 15 GB minimum, 30 GB recommended | Count server files, custom content, logs, update staging and backups. Large mod collections can reach tens of gigabytes. |
| Network | TCP 9600, UDP 9600 and HTTP 8081 are documented defaults | Open the ports in the host firewall and forward them through a home router when the machine is behind NAT. |
| Operating system | 64-bit Windows and Linux paths are documented | Use the platform you can patch, secure, monitor and back up reliably. |
Steam’s numbers are useful only as a rough indication of the client footprint. Treating 2 GB of RAM or 15 GB of storage as a dedicated-server specification can produce an installation that has no room for custom content or normal operating-system overhead.
How much RAM does an Assetto Corsa server need?
For a basic lobby, plan on 2–3 GB of allocated RAM, then add headroom for the operating system and anything else running on the machine. Current provider examples illustrate the range: Torchlite lists 1.5 GB and 3 GB plans, while Assetto Servers lists a four-player plan with 2 GB. These are provider configurations, not universal requirements.
Vanilla racing server
A server running the standard game content and a modest grid may fit in the 2–3 GB range. The exact footprint changes with the event, connected drivers, logging and the operating system. A plan advertised with 2 GB does not mean every 2 GB server will behave identically; virtualization, background services and provider limits matter.
Custom cars and tracks
Mods do not all consume the same memory. A large collection adds files on disk and can increase the amount of content loaded or cached during a session. Keep spare RAM rather than sizing the machine exactly to the base lobby estimate, especially when several tracks or car packs are available to drivers.
AI traffic and multiple services
RE:NODE’s 2026 vendor guide estimates about 2 GB for a full vanilla grid and 4–8 GB for AssettoServer AI traffic. Those are estimates with lower authority than official documentation, but they show why AI should be treated as a separate workload. Add memory when the host also runs several server instances, a web panel, a database, monitoring, backups or other game services.
Why 16 GB is a sensible self-hosting target
A 16 GB RAM kit is a practical purchase for a self-hosted machine that runs Windows or Linux alongside Content Manager tools, monitoring, backups or more than one lobby. It is a headroom recommendation inferred from the small-plan figures and client requirements, not a Kunos requirement. If the computer is dedicated to one light server and has little else installed, less memory may work; if it is a general-purpose host, 16 GB avoids forcing the operating system and server to compete.
What CPU do I need for an Assetto Corsa server?
Kunos does not publish a minimum or recommended acServer processor. In practice, choose a recent CPU or VPS with strong single-core performance and a clearly allocated vCPU. Starter hosting examples use approximately one to one-and-a-half vCPUs, which is a useful baseline for a small lobby rather than a guarantee for every workload.
Why single-core performance matters
The vanilla server is generally described by hosting providers as sensitive to per-core performance. A modern high-clock desktop core can therefore be a better choice than an older processor with many slow cores. On a VPS, “one vCPU” can mean different physical resources, so look for a provider that states how CPU capacity is allocated and whether it is shared or guaranteed.
When to add CPU capacity
- AI traffic: AssettoServer AI traffic can raise processing demand substantially compared with a normal player-only grid.
- Several instances: Running multiple championships or regions on one host requires capacity for each active process.
- Co-hosted applications: Databases, web panels, monitoring agents, voice services and backup compression all consume CPU time.
- Large or busy events: More connected drivers and frequent state updates leave less idle capacity for the server process.
Monitor actual CPU utilization and frame or tick stability during a representative session. A nominal core count alone cannot predict performance because virtualization and background load vary by host.
How much storage does an Assetto Corsa dedicated server use?
Start with at least the game and server files, then add every piece of content the event requires. The Steam client listing gives 15 GB minimum and 30 GB recommended storage, but a dedicated installation also needs its own executable and configuration files, custom cars and tracks, weather packages, logs, update staging space and backups.
What consumes disk space?
- Base installation: The game files provide a lower-bound reference, not the final server size.
- Custom content: Cars, tracks, skins, weather and physics packages can add many gigabytes.
- Logs and replays: Persistent logging and race records grow over time unless rotated.
- Update staging: Keep free space to download and verify new content before replacing a live installation.
- Backups: A second copy of configuration and content protects against a failed update or accidental deletion.
RE:NODE notes that a mod-heavy traffic server with many cars and a large road network can reach tens of gigabytes. A 1 TB SSD is a convenient option for a large library, but it is not a requirement; size the drive to the content you actually host plus a reserve for backups and updates.
SSD or hard disk?
An SSD makes file transfers, updates and loading custom content more responsive and has no moving parts. Capacity and reliable backups matter more than buying a specific capacity. Keep the live server and its backup plan on storage with enough free space that an update cannot fill the filesystem.
Which network ports must I forward?
The documented defaults are UDP 9600 for race data, TCP 9600 for client connections and HTTP 8081 for lobby traffic. Open all three in the operating-system firewall. If the server is inside a home network, create router port-forwarding rules from the public interface to the machine’s fixed private address.
Port-forwarding checklist
- Assign the server computer a stable local address, preferably with a DHCP reservation or static configuration.
- Allow inbound TCP 9600, UDP 9600 and TCP 8081 in the host firewall. Confirm whether your firewall distinguishes protocol and port.
- Forward the same protocol-and-port combinations on the router to the server’s local address.
- Start acServer and verify that the lobby or web service is listening on the expected ports.
- Have a driver outside your home network test a connection; testing only from the same LAN can hide NAT or firewall errors.
Do not expose additional administration services unnecessarily. Restrict management interfaces, keep the operating system patched and use strong credentials where an interface requires them.
How many players can the hardware and track support?
The usable grid is constrained by both network capacity and the track configuration. Primcast summarizes the acServer rule as: “Your grid can never be bigger than the track’s pit count.” Set MAX_CLIENTS no higher than the track’s available pit places. A server may have enough RAM for more connections on paper, yet still reject drivers when the track has fewer pits.
Upload bandwidth, latency and packet loss affect the experience as much as CPU and memory. Hosting near the majority of drivers reduces round-trip latency. Use acServerManager’s bandwidth estimate when sizing an event, then leave margin for other traffic and avoid saturating the uplink.
Can I run acServer on Windows or Linux?
Yes. The documented deployment paths support 64-bit Windows and Linux, and the acweb management interface also supports both operating systems. Select the platform your team can update, secure and monitor consistently rather than choosing solely on theoretical performance.
Windows considerations
Windows can be convenient when the host already uses Windows-based racing tools. Keep the server directory outside locations subject to automatic cleanup, apply security updates, create firewall rules for the three required ports and schedule backups of configuration and custom content.
Linux considerations
Linux is suitable for an always-on VPS or home server when you are comfortable with package updates, service supervision, permissions and firewall configuration. Use a 64-bit distribution, keep the account running the server appropriately restricted, and document the service’s startup and backup procedure so another administrator can recover it.
acweb and database requirements
The acweb documentation lists 64-bit Linux or Windows and supports MySQL or PostgreSQL. A web panel and database add their own RAM, storage and security requirements; account for them rather than treating the game process estimate as the whole machine budget.
How do I keep server content matched with clients?
After Steam patches the game, run the server-content update process and transfer the refreshed server folder. Cars and tracks must match the versions expected by clients; mismatches can reject drivers before they join the session.
- Stop the live server or use a maintenance window.
- Update the game/server content through the supported Steam process.
- Compare the refreshed cars, tracks and configuration with the installation used by your drivers.
- Copy the updated server folder into the deployment location, retaining a rollback backup.
- Start a test session and have at least one external driver connect before announcing the event.
Keep a staging copy so an update can be validated without replacing the working installation. Record the content versions used for each championship round; this makes it easier to restore a known-good set when a mod update introduces a mismatch.
Should I self-host, use a VPS or rent a game-server plan?
Compare options by guaranteed RAM, single-core CPU allocation, storage quota for mods, upload capacity, latency to your driver group, backup features, port control and support for multiple instances. There is no universal hardware tier because the workload and provider limits differ.
| Option | Strengths | Trade-offs to check |
|---|---|---|
| Home machine | Full control of files, ports and network policy; no recurring game-server slot limit. | Requires reliable power, upload bandwidth, router configuration, patching and security. Residential connections may have changing public addresses or restrictive upstream policies. |
| VPS | Usually available continuously, with a public address and datacenter connectivity. | Check whether the advertised vCPU is shared, how much RAM is guaranteed, where the datacenter is located and whether game traffic is permitted. |
| Managed game-server host | Fast deployment, control panels and provider-managed availability. | Compare slot limits, mod-storage quotas, port access, backup policy, CPU allocation and the ability to run more than one instance. |
For a private group with technical support at home, self-hosting offers the most control. For an always-on public lobby, a nearby VPS or managed host can reduce maintenance, provided its CPU, memory, network and storage terms fit the event.
What should I check before buying hardware or a plan?
- Confirm the plan’s RAM is guaranteed rather than merely burstable.
- Ask how much CPU is allocated to one instance and whether neighboring workloads can throttle it.
- Calculate the size of every car and track pack, then reserve space for two copies during updates.
- Measure upload bandwidth during the hours when the server will be busy.
- Choose a location close to most drivers and check expected latency.
- Verify that TCP 9600, UDP 9600 and HTTP 8081 can be opened or forwarded.
- Check whether backups are included, how long they are retained and where they are stored.
- Confirm that the provider allows multiple instances if you plan separate practice and race servers.
These checks prevent a common mistake: paying for more nominal CPU while overlooking a full disk, unavailable ports or an uplink that cannot serve the intended grid.
What is a sensible starting specification?
For one small, player-only lobby, start with 2–3 GB of RAM, roughly one to one-and-a-half strong vCPUs, an SSD sized for the base installation plus your mod collection and backups, and a stable upload connection. For a self-hosted general-purpose machine, 16 GB of total RAM gives comfortable room for the operating system and supporting services. Move toward 4–8 GB or more when using AI traffic, several instances or a large set of co-hosted applications, and expand storage as your custom-content library grows.
Validate the chosen size with a rehearsal that uses the intended track, car pack, maximum grid and AI settings. Watch memory pressure, CPU saturation, disk free space, packet loss and latency during that rehearsal; those observations are more useful than treating any provider’s starter plan as a universal specification.
Frequently Asked Questions
Does the dedicated server need the same RAM as the Steam client recommendation?
No. Steam’s 2 GB minimum and 6 GB recommendation describe the client application. An acServer installation has a different workload, and its practical memory use depends on content, AI, operating-system overhead and other services.
Can I run two Assetto Corsa servers on one computer?
Yes, if the machine has enough CPU, RAM, storage and network capacity for both processes. Give each instance separate configuration and content paths where needed, and ensure their HTTP and game ports do not conflict.
Why can drivers connect to the port but still fail to join?
A reachable port only proves that traffic can arrive. Version-mismatched cars or tracks, a grid larger than the track’s pit count, insufficient upload capacity or packet loss can still prevent a successful session.
How much free disk space should I leave for updates?
Leave enough for a staging copy of the content being replaced, plus at least one known-good backup. The exact amount depends on your largest car and track packages; a mod-heavy collection may already occupy tens of gigabytes.