Arma Reforger has no fixed, Bohemia Interactive-published minimum for dedicated-server CPU, RAM, storage, or bandwidth. For planning, start with a fast, high-clocked x86-64 CPU, about 8GB of RAM for a monitored 16–32-player server, and 25–40GB of free SSD/NVMe space. A server approaching 64 players, running many AI units or demanding mods, is better started with 12–16GB of RAM and at least 50GB free. The headless server does not need a gaming GPU. These figures are practical estimates, not certification; validate them with your exact player count, scenario, AI load and workshop collection.
What are the Arma Reforger dedicated server requirements?
Bohemia Interactive provides dedicated-server software and hosting documentation, but its official pages do not specify a universal processor, memory, disk or bandwidth minimum. Resource use changes substantially with connected players, AI, scripts, scenario complexity and workshop mods. A sensible specification is therefore a starting tier with measurable upgrade headroom, followed by a peak-load test.
| Target workload | CPU planning estimate | RAM planning estimate | Free SSD/NVMe space |
|---|---|---|---|
| Small or 16–32 players | About four strong, high-clocked cores; prioritize single-thread speed | About 8GB as a monitored starting point; leave room for AI and mods | Roughly 25–40GB for updates, workshop files, logs and rollback copies |
| 32–64 players or heavier scripts | Six to eight modern, high-clocked cores with strong per-core performance | About 12–16GB; 16GB is the safer upper-range starting point | At least 50GB is prudent |
| Very large or unusually mod-heavy instance | No fixed figure is established; use the fastest per-core CPU available and measure peak load | More than 16GB may be appropriate, based on observed peak use | Keep substantially more than 50GB and separate logs or backups when possible |
These ranges are community planning guidance. A heavily scripted 20-player scenario can need more CPU or memory than a lightly configured larger session, so player count alone is not a sizing rule.
How much RAM does an Arma Reforger server need?
Memory demand rises with connected clients, AI, mission objects, scripts and downloaded mods. Do not size from the process’s idle or startup footprint. Watch the highest usage during a full session, including map changes and mod activity, and keep enough unused memory to prevent paging.
What published figures exist?
| Source and date | Published figure | How to interpret it |
|---|---|---|
| Pterodactyl game-eggs contributors, page state in 2026 | 3,328 MiB bare-minimum RAM; 6,144–8,192 MiB listed as recommended | A hosting-template table, not a Bohemia-certified requirement; it also specifies recent x86/64 hardware and no ARM support |
| TheMartian Steam guide, 2022 | Up to 20GB memory and 5GB disk space | An older community setup reference paired with Windows 10 or Windows Server 2016+ 64-bit and a quad-core processor |
| iTechGuides Team, 2026 | About 8GB for 16–32 players; 12–16GB for 32–64 players | A current planning estimate that also allows 25–40GB free for a normal installation and at least 50GB for larger or heavily modded servers |
The differing numbers reflect different assumptions rather than a hidden official minimum. If monitoring shows peaks close to physical memory, lower the workload or add RAM before raising the player cap.
How many CPU cores does an Arma Reforger server need?
Prioritize high per-core performance and clock speed. The simulation and parts of networking benefit strongly from a fast main thread; simply buying a processor with many slower cores is not automatically better. Four strong cores are a practical small-server starting point, while six to eight modern high-clocked cores provide more room for larger populations, scripts and background services.
Extra cores still help the operating system, networking, logging, monitoring and other services. During testing, inspect utilization by individual core rather than relying only on the total CPU percentage. One saturated core alongside several mostly idle cores can explain poor server performance even when overall usage looks moderate.
How much storage does an Arma Reforger dedicated server use?
A small install footprint is not a safe capacity plan. The server needs working space for the game, updates, workshop downloads, temporary files, logs and rollback or backup copies. Use an SSD; NVMe is preferable when practical because faster storage reduces update and loading delays.
Reserve about 25–40GB free for a normal 16–32-player deployment and at least 50GB for a larger or heavily modded instance. Keep additional capacity when you retain multiple rollback versions or extensive logs, and place backups on a separate disk or host if possible. Recheck free space after adding a large workshop collection rather than assuming the initial install size remains representative.
Do I need a GPU to host an Arma Reforger server?
No dedicated gaming GPU is required for the headless process. A dedicated server does not render a playable view; it processes game state and network synchronization. A basic display adapter can be useful for local administration, but spending on graphics hardware does not improve server simulation in the way a faster CPU does.
What internet connection and ports are required?
Community guidance suggests 50–100Mbps upload as a starting range, with busy public servers potentially needing more. Sustained upload is only one part of the experience: latency, packet loss, routing quality and CPU time can cause problems even when headline bandwidth is ample.
Which UDP ports should be opened?
| Port | Protocol | Purpose | Requirement |
|---|---|---|---|
| 2001 | UDP | Public game traffic | Officially listed game port; forward and allow it when hosting publicly |
| 17777 | UDP | A2S server queries | Optional; open only if you need external server queries |
| 19999 | UDP | RCON | Optional; expose it only when remote administration is configured and secured |
Allow only the ports you actually enable. Configure both the host firewall and, for a home server, the router’s port-forwarding rule. Self-hosting also puts NAT behavior, public addressing, power failures, patching and monitoring on you.
Can I run an Arma Reforger server on Windows or Linux?
Yes. The Steam setup documented by TheMartian uses Windows 10 or Windows Server 2016 or newer, 64-bit, with SteamCMD and the stable dedicated-server app ID 1874900. The executable is launched with -config and -profile; the profile path determines where server saves are written.
Bohemia Interactive’s BIKI also documents Linux and Docker deployment, including an Ubuntu-based container path. The stable app uses ID 1874900; the experimental branch uses 1890870. Use recent x86-64 hardware: the maintained Pterodactyl requirements table states that ARM is unsupported.
What does the launch shape look like?
ArmaReforgerServer.exe -config <server-config> -profile <profile-directory>Replace the paths with your actual configuration and profile locations. Keep experimental and stable files separate when evaluating updates so a test build cannot overwrite a production server’s saves or configuration.
Should I self-host or rent an Arma Reforger server?
Both approaches can work. Self-hosting offers direct control over hardware and upgrades; rented hosting can supply datacenter connectivity and managed operations. Compare the following factors rather than looking only at monthly price.
| Consideration | Self-hosted | Rented or managed |
|---|---|---|
| CPU and RAM | You choose the processor and can upgrade it, but must buy and install parts | Choose a plan with strong single-thread CPU performance and enough memory headroom; upgrades depend on the provider |
| Storage | Control SSD/NVMe capacity and backup layout | Check included free space and the cost of expansion; workshop growth can exceed the initial allocation |
| Network | Your upload, latency, NAT, power and DDoS exposure are your responsibility | Datacenter connectivity and network protection may be included, but quality varies by location and plan |
| Operations | You handle firewall rules, patches, monitoring, backups and recovery | Management tools and support can reduce routine work, while access to low-level settings may be limited |
| Mod workflow | Direct control of files, update timing and rollback copies | Convenient panels may simplify deployment; verify how workshop downloads and custom configurations are handled |
How should I test whether my hardware is sufficient?
Use a representative peak session, not an empty server. The following process turns the estimates into evidence for your particular configuration.
- Define the workload. Set a target player population and choose the actual scenario, expected AI count, scripts and workshop mods.
- Start with a tier that has headroom. Select the appropriate CPU, memory and free-space range from the planning table instead of sizing to the smallest possible install.
- Run a peak-load session. Test with the expected number of players or a realistic simulation, including the busiest phase of the scenario and map transitions.
- Monitor the right signals. Record per-core CPU utilization, peak RAM, disk latency, sustained upload, packet loss and any server tick or frame warnings.
- Apply safe limits. Keep
fastValidationenabled for public hosting and set-maxFPSin the official recommended 60–120 range so the process does not consume every available CPU cycle. - Retest after change. Repeat the test after major game or mod updates because resource use can change even when your player target has not.
What problems indicate an undersized server?
One core is saturated while total CPU looks low
This usually points to a main-thread limit. Move to a processor with stronger per-core performance, reduce script or AI complexity, or lower the player target rather than assuming more slow cores will solve it.
Memory climbs throughout a session
Check mod and scenario behavior, then compare peak use with installed RAM. Keep free memory for the operating system and services; if the peak approaches the limit, reduce workload or add RAM before increasing capacity.
Players report rubber-banding despite adequate bandwidth
Inspect latency, packet loss, routing and CPU headroom together. A fast upload link cannot compensate for a saturated simulation thread, unstable route or overloaded host.
Updates or mod downloads fail with disk errors
Check free space, not just the nominal game-install size. Remove obsolete rollback copies only after preserving a known-good backup, then leave room for temporary update files and future workshop growth.
What is the safest baseline for a new server?
For a lightly modded 16–32-player server, use a recent x86-64 machine with a fast four-core-or-better CPU, about 8GB of RAM, SSD/NVMe storage with 25–40GB free, and a stable upload connection. Move toward six to eight fast cores, 12–16GB of RAM and 50GB or more free space as population, AI or mod complexity increases. Treat those figures as starting points, cap server FPS, monitor peak behavior and adjust from measurements rather than from an advertised minimum.
Frequently Asked Questions
Is an ARM VPS suitable for an Arma Reforger dedicated server?
The maintained Pterodactyl requirements table marks ARM as unsupported. Choose a recent x86-64 VPS or physical host instead, and confirm that the provider exposes the CPU performance and UDP networking the server needs.
What is the difference between the stable and experimental dedicated-server builds?
The stable build uses Steam app ID 1874900, while the experimental build uses 1890870. Keep a separate test directory and profile for experimental updates so production saves and settings remain isolated.
Where are dedicated-server saves written on Windows?
The directory supplied with the -profile argument controls where server saves are written. Set that path deliberately and include it in your backup plan rather than relying on an unknown default location.
Can I run the server on a home internet connection?
Yes, provided your connection can sustain the traffic and your router permits the required UDP forwarding. You must also account for changing public addresses, NAT restrictions, power interruptions, patching and monitoring that a datacenter host may otherwise handle.