The official Arma 3 dedicated-server baseline is a 2.4GHz dual-core CPU, 2GB of RAM and 32GB of hard-drive space. Bohemia Interactive recommends a 3.5GHz quad-core CPU, 4GB of RAM and a 32GB SSD instead. Those figures cover the server package itself, not the operating system, mods, logs, backups or other services sharing the machine. In practice, CPU single-core speed, mission AI density, mod count, available bandwidth and latency can matter as much as the player count.
Use the official figures as a floor, then leave capacity for the workload you actually intend to run. A lightly populated vanilla server can fit close to the recommendation; heavily modded missions, large AI battles and public communities need additional memory, storage and a host with reliable IPv4 connectivity.
What are the official Arma 3 dedicated server requirements?
Bohemia Interactive’s dedicated-server documentation lists these package-level requirements:
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 2.4GHz dual-core | 3.5GHz quad-core |
| RAM | 2GB | 4GB |
| Storage | 32GB HDD | 32GB SSD |
“Minimum” means the server software can be installed and started under those conditions; it does not promise smooth performance for every mission. The recommended figures are also not a universal hardware guarantee. The operating system, SteamCMD files, workshop content, save data, crash dumps, logs and backups all consume resources outside the core package.
For that reason, treat 3.5GHz quad-core, 4GB RAM and a 32GB SSD as the starting point for a small server, not as a complete budget for a busy modded community.
What CPU do I need for an Arma 3 server?
Choose the fastest practical CPU core you can obtain, with at least four physical cores for the official recommendation. Arma 3 can concentrate substantial processing in one or two threads, particularly when a mission contains many AI units, scripts and physics events.
Why single-core speed matters
A processor with many slow cores is not automatically better than a processor with fewer, faster cores. The main simulation thread can become the limiting factor while other cores remain lightly loaded. Clock speed is only a rough indicator—architecture, sustained turbo behavior, thermal limits and host contention also affect real performance—but per-core performance deserves priority.
When extra cores help
Additional cores are useful for operating-system tasks, network handling, logging and multiple server instances. They also make it easier to run a headless client. A headless client can move much of the AI processing away from the main server when it has very low latency and high bandwidth to that server; it is not a substitute for a weak main simulation thread.
CPU planning by mission type
- Vanilla, small co-op: The 3.5GHz quad-core recommendation is a sensible target.
- Large AI battles: Favor stronger per-core performance and thermal headroom before adding many additional cores.
- Several server instances: More total cores and guaranteed CPU allocation become important because each instance competes for processor time.
- Headless-client setups: Count the headless client as another workload and verify the network path between it and the server.
No dated independent benchmark establishes a universal CPU model, player limit or frames-per-second target. Mission design can change the result dramatically, so test the actual scenarios you plan to host.
How much RAM does an Arma 3 dedicated server need?
The documented minimum is 2GB and the documented recommendation is 4GB. Those numbers describe the dedicated-server software, not the total memory required by a modern host.
What consumes memory besides the server
- The operating system and background services.
- Mod files and the memory used while missions load.
- Large scripts, AI groups and dynamic object systems in a mission.
- SteamCMD updates, monitoring tools, databases or voice services hosted on the same machine.
- Temporary files, crash handling and backup processes.
For a private vanilla server, 4GB may be enough if the operating system and workload are kept lean. Add substantial headroom when using large mod collections, persistent missions, high AI density or multiple instances. Allocating 8GB or more is a common planning choice for that headroom, but it is not an official Arma 3 server requirement or a measured performance threshold.
Do more players always require more RAM?
Player count is only one factor. A 10-player mission with thousands of AI units and complex scripts can be more demanding than a 30-player mission with a simple map. Mod quantity, asset size and mission behavior should guide memory planning rather than a player-to-RAM formula; no reliable universal formula is established by the available documentation.
How much storage and what kind of drive should I use?
Bohemia Interactive lists 32GB of HDD space as the minimum and a 32GB SSD as the recommendation. An SSD reduces installation, update and file-access delays and is the better choice for a dedicated host.
Why 32GB is a floor
The operating system occupies part of the disk before Arma 3 is installed. Workshop mods, server profiles, logs, mission files, downloaded updates and backups can quickly exceed the remaining space. A drive with more capacity also prevents an update from failing because there is no temporary working room.
Capacity and endurance considerations
Choose capacity after counting the operating system, the base server, every planned mod set and the number of local backups you will retain. Keep free space for future updates instead of filling the disk to its limit. Consumer SSDs are usually adequate for a small server, while a host writing extensive logs or running several instances benefits from a drive with a documented endurance rating and reliable monitoring.
How many players can an Arma 3 server support?
There is no single hardware-to-player conversion. Bohemia Interactive’s FAQ says that “reasonable maximum player counts depend on the server hardware and available bandwidth,” with typical scenarios ranging from 2 to 64 players. The mission, AI load, mods, scripts and network conditions determine where a particular server falls within that range.
As a planning example rather than a rule, a 2022 IONOS guide maps 2–4 players to a VPS L, 5–16 players to a VPS XL and more than 16 players to a dedicated server. Those labels describe one provider’s products at that time; they are not Arma 3 limits and should not be treated as a benchmark.
| Concurrent players | Provider example | What still needs checking |
|---|---|---|
| 2–4 | VPS L in the IONOS 2022 example | CPU burst policy, mod size, IPv4 and latency |
| 5–16 | VPS XL in the IONOS 2022 example | Guaranteed CPU, memory overhead and mission AI |
| More than 16 | Dedicated server in the IONOS 2022 example | Per-core speed, bandwidth, DDoS policy and storage capacity |
Before committing to a host, run the actual mission with representative mods and AI. Watch the main simulation thread, memory use, disk space and network latency while players join and while the busiest scripted events occur.
Should I use a home machine, VPS, cloud instance or dedicated server?
Each hosting type can work; the right choice depends on guaranteed resources, connectivity and how much administration you want to handle.
| Host type | Advantages | Risks or checks |
|---|---|---|
| Home machine | Full hardware control and no recurring server rental | Requires a real public IPv4 address, suitable upload capacity, power reliability and router configuration |
| VPS | Fast deployment and a predictable virtual environment | CPU may be shared; verify dedicated or guaranteed vCPU performance, RAM and IPv4 availability |
| Cloud instance | Flexible resizing and snapshots | Pricing can vary with storage, traffic and stopped or running time; confirm sustained CPU behavior |
| Dedicated server | Reserved hardware and maximum control for large communities | Higher cost and more administration; you still need to size storage, bandwidth and backup capacity |
Mission design matters as much as nominal player count. A smaller group on a heavily scripted island may need a stronger machine than a larger group running a simple scenario.
What operating system, network connection and ports are required?
The dedicated package is distributed through SteamCMD with application ID 233780. You need a Steam account, a supported server operating system and a network path that accepts the required traffic.
Supported operating systems
Bohemia Interactive documents support for Windows Server 2008 or later and modern Linux distributions. On either platform, keep the operating system patched, create a separate service account where practical and place the server files on the SSD rather than a slow system volume.
IPv4 is mandatory for public hosting
The Bohemia Interactive Community documentation states: “Arma 3 server does not support IPv6 or DSlite IPv4 via IPv6 tunnel. You must have a real IPv4 connection.” A host that offers only IPv6, carrier-grade NAT or DS-Lite tunneling cannot provide a normally reachable public server without an additional compatible solution.
Firewall ports
IONOS lists these TCP and UDP ports for game, query, Steam and BattlEye traffic:
| Port | Traffic noted by IONOS |
|---|---|
| 2302 | Game traffic |
| 2303 | Query traffic |
| 2304 | Steam traffic |
| 2306 | BattlEye traffic |
Open only the protocols and ports your configuration requires, both in the host firewall and, for a home server, on the router’s port-forwarding rules. Check the current server and provider documentation if you change ports or run multiple instances, because each instance needs a non-conflicting arrangement.
How do I install and size an Arma 3 dedicated server?
Install the package first, then measure the real workload before inviting a full community. This sequence prevents you from sizing a server around an empty lobby.
- Choose the host: Confirm a 64-bit-capable operating system, real IPv4 connectivity, SSD space beyond the 32GB baseline and enough CPU and RAM for the operating system.
- Install SteamCMD: Sign in with the required Steam account and download application ID
233780into a dedicated server directory. - Apply the operating-system basics: Patch the OS, create the service account, set time synchronization and configure automatic restart or service supervision.
- Install mods and missions: Add the exact workshop content your clients will use. Record versions so an update does not create mismatched files.
- Configure networking: Permit the required TCP and UDP ports, forward them on a home router if applicable and verify that the public IPv4 address is reachable from outside your network.
- Run a representative load test: Use the busiest mission, expected AI density and full mod set. Observe CPU per core, total memory, disk free space, latency and disconnects.
- Add headroom and backups: Leave room for updates, logs and backups. If the main simulation thread remains saturated, move AI to a low-latency headless client or choose a faster CPU rather than simply adding disk space.
What hardware should I plan for common server scenarios?
The table below separates documented requirements from planning decisions that depend on your workload. Where no universal value is established, the correct answer is to test rather than guess.
| Scenario | CPU focus | Memory plan | Storage and host |
|---|---|---|---|
| Small private, mostly vanilla | At least the 3.5GHz quad-core recommendation | 4GB is the documented recommendation; reserve extra room for the OS | 32GB SSD is the documented recommendation; home machine or small VPS with IPv4 |
| Modded group with moderate AI | High per-core performance; extra cores help with supporting services | More than 4GB may be needed; exact amount is not established | SSD capacity above 32GB for mods and backups; verify guaranteed VPS resources |
| Large public or AI-heavy operation | Fast sustained cores, with additional cores for multiple instances or headless clients | Plan substantial headroom; no universal player-to-RAM formula exists | Dedicated or strongly guaranteed host, ample SSD capacity, reliable IPv4 and measured latency |
What commonly causes poor performance or failed connections?
- Using the minimum as a target: 2GB RAM and a dual-core CPU leave little room for an operating system, mods or AI-heavy missions.
- Choosing cores instead of speed: Many low-frequency cores may not fix a saturated main simulation thread.
- Ignoring storage growth: A 32GB disk can fill with workshop files, logs and backups even when the server software itself fits.
- Assuming player count is enough: Mission scripts and AI density can dominate CPU and memory usage.
- Renting oversubscribed virtual hardware: A listed vCPU count does not prove sustained performance; ask how CPU allocation is enforced.
- Hosting behind DS-Lite or IPv6-only access: Arma 3 requires a real IPv4 connection for normal public reachability.
- Opening the wrong ports: Check both protocol and port, including BattlEye traffic, and avoid conflicts between multiple instances.
- Skipping external testing: A server that works from inside the same home network may still be unreachable from the public internet.
Are Arma 3 client requirements the same as server requirements?
No. The official client requirements are higher and apply to the computer running the game, not the dedicated server process.
| Component | Client minimum | Client recommended |
|---|---|---|
| RAM | 8GB | 16GB |
| Free storage | 50GB | 80GB SSD |
Do not use the client’s 8GB or 16GB figures as a direct server requirement, and do not assume a server meeting the 4GB recommendation can also run the graphical game comfortably. A dedicated host normally runs without the game client, display rendering or client-side graphics workload.
Frequently Asked Questions
Can I run an Arma 3 dedicated server on a VPS?
Yes, provided the VPS supplies sustained CPU performance, enough memory after the operating system, SSD storage and a real public IPv4 address. Confirm that the provider does not restrict the required game, query, Steam or BattlEye traffic.
Does Arma 3 use more CPU or RAM with mods?
It can use more of both, depending on what the mods add. Large assets increase storage and loading needs, while scripts, AI systems and persistent mechanics can increase CPU and memory pressure; the mod count alone does not predict a fixed amount.
Can I host multiple Arma 3 servers on one machine?
You can, but each instance needs its own resources, configuration and non-conflicting network ports. Measure the busiest combined workload rather than adding the official 4GB recommendation mechanically, because operating-system and shared-service overhead does not scale linearly.
Do headless clients remove the need for a powerful server CPU?
No. A headless client can offload much AI processing, but the main server still handles core simulation, networking and scripts. The headless client must also have a very low-latency, high-bandwidth connection to the server to help effectively.
What should I monitor after launching the server?
Track per-core CPU usage, total memory and swap activity, free SSD space, update and log growth, network latency, packet loss and player disconnects. Compare these measurements during the busiest mission events, not only while the server is idle.