ARK: Survival Ascended Server Requirements Calculator

ARK: Survival Ascended dedicated server requirements

ASA runs on Unreal Engine 5, and that single fact drives every requirement on this page. Compared to the original ARK (ASE, on UE4), an Ascended server consumes far more memory and is even more dependent on single-core CPU speed. The headline number to remember: each map instance wants roughly 10-16 GB of RAM, not the 4-8 GB veterans remember from the old game.

RAM

RAM is the resource you are most likely to run out of. According to the official wiki, an empty ASA server idles at roughly:

• The Island: 8-10 GiB
• The Center: 10.5-12 GiB
• Scorched Earth: 7.5-9 GiB
• Aberration: 8-10 GiB
• Extinction: 7-8.5 GiB

Those are bare maps with nobody connected. Newer or larger maps added since (for example Lost Colony, and big Ragnarok-class maps) run heavier, with admins reporting idle usage closer to 15 GiB. Fresh server starts also spike a few GiB higher for the first ~10 minutes until distant regions enter stasis, then settle. Players add a relatively modest amount (tens to a few hundred MiB each), but the world itself grows over time as structures, tames, and item containers accumulate. The practical floor for a single lighter map is 16 GB (covering map + OS); 32 GB is the comfortable, future-proof choice once you add mods, run a heavier map, or push past ~20 players.

Mods are the biggest wildcard. A handful of light, server-side mods adds a few GB; large asset packs or total conversions can push usage 1.5-2.5x. Plan 64 GB for a 15+ mod server and 96-128 GB for a multi-map cluster.

CPU

ARK's world simulation runs predominantly on a single thread per map (physics is the main exception). That means clock speed and per-core IPC dominate; a 4-core CPU at 4.5 GHz will out-host a 16-core CPU at 3.0 GHz for a single map. Aim for 4.0 GHz+ (4.5 GHz+ preferred) and budget the official wiki's guideline of roughly 4 logical cores per map instance. Extra cores only pay off when you run several maps (a cluster) on one machine. Modern chips with large caches (e.g. AMD X3D parts) help because they cut memory-latency stalls in ARK's real-time simulation. CPU utilization on a lightly populated single map is often low (single-digit percentages); the danger is the simulation thread saturating one core during dense combat or with thousands of structures and tames.

Storage

The ASA dedicated server binary installs to about 11 GiB via SteamCMD. That sounds small, but reserve at least 40 GB: Steam needs temporary headroom to apply large game updates (which are frequent and can be sizeable), and save files, profiles, logs, DLC maps, and mods accumulate on top. A cluster or a mature, heavily-built world will want 60-100 GB+. NVMe SSD is strongly recommended: ARK does a lot of save/load I/O, and slow disks cause stutters and long startup times. Avoid HDDs for live servers.

Network

Per-player bandwidth is moderate at roughly 80-150 KB/s upload per active player (about 0.6-1.2 Mbps), spiking toward ~300 KB/s during dense action. That works out to roughly 30-40 GB of egress per active player per month for a steadily-populated slot. Self-hosters on residential connections should have headroom on upload (25 Mbps+); below that, distant players see lag spikes in combat regardless of CPU. Open UDP 7777 (game), UDP 7778 (raw/peer), UDP 27015 (Steam query), and optionally TCP 27020 for RCON. Each additional map instance in a cluster needs its own non-overlapping port set.

Operating system

The ASA dedicated server is a Windows-only binary. There is no native Linux build, so Linux hosts run it through a Windows compatibility layer (Proton/Wine), which most managed hosts handle for you. Budget separate RAM for the OS (roughly 2-4 GB on a lean Windows install, and 8-10 GB on a full desktop Windows 11).

Optimizing an ASA dedicated server

Because ASA is single-thread-bound and memory-hungry, most real-world performance wins come from reducing simulation load and keeping memory healthy rather than buying more cores.

Prioritize the right hardware

• Fast single-core over many cores. A 6-8 core CPU at 4.5 GHz+ beats a many-core chip at lower clocks for a single map. Large-cache (3D V-Cache) CPUs reduce simulation-thread stalls.
• NVMe, always. Sub-5ms read/write keeps saves and world streaming from stuttering.
• Leave RAM headroom. Size for the post-launch spike, not the settled idle figure, so you never touch the page file.

Tame the simulation

• Lower DinoCountMultiplier (e.g. ~0.8) to cut wild-creature CPU load.
• Cap building density with a sensible MaxStructuresInRange; very large bases are a top cause of tick-rate drops.
• Tune HarvestAmountMultiplier up and ResourcesRespawnPeriodMultiplier down together so you respawn fewer resource nodes for the same gathering experience.

Memory hygiene and restarts

• Schedule automatic restarts every 48-72 hours to clear accumulated memory growth; many admins report a tick-rate recovery afterward.
• On Windows, the -UseLargePages launch flag can improve memory access efficiency; combine with sensible save intervals.
• Monitor per-core CPU (watch the simulation core, not the average), RAM, disk I/O latency, and server tick-rate so you catch saturation before players feel it.

Manage mods aggressively

• Mods are the number-one cause of instability. Prefer server-side mods and keep individual mod size reasonable (avoid 500 MB+ asset packs unless you've sized RAM for them).
• Use a deliberate load order (frameworks → map extensions → creatures → items → QoL) and re-test after every mod update.
• Audit periodically and drop mods that are unmaintained or rarely used.

Clusters

For multiple maps, run each as its own instance with its own port set and CPU/RAM budget (~4 logical cores and 12-16 GiB per active map), sharing a cluster directory for transfers. Stagger restarts so the whole cluster isn't down at once.

What to look for in an ASA server host

ASA's quirks make a few host capabilities matter more than headline price. Use this as a neutral checklist rather than a shopping list.

• High single-thread CPU. Ask which CPU generation and clock speed the plan runs on. A modern chip at 4.5-5.0 GHz with large cache will outperform an older many-core server for a single map. This is the most important spec for ASA and the one hosts are least transparent about.
• Generous RAM headroom. Confirm the plan's RAM comfortably exceeds your map's idle figure plus mods and the launch spike. Beware slot-based plans that quietly cap RAM below what a modded or heavier map needs.
• NVMe storage. Save-heavy, constant read/write I/O means SSD/NVMe is effectively required; ask about disk type, whether storage is shared or dedicated, and whether there's enough free space for update headroom.
• Low latency to your players. Pick a data-center region close to the bulk of your community. A ping difference of 40-80 ms is very noticeable in ARK combat.
• DDoS protection. Survival servers are common targets; built-in network-layer filtering is worth confirming.
• One-click / managed mod installation. Native CurseForge mod support and easy mod-list management save real hassle, since mods are central to ASA.
• Full config access. You want FTP/file access plus an RCON or web console to edit GameUserSettings.ini and Game.ini, schedule restarts, and run a cluster.
• Automated backups and scheduled restarts. Frequent world backups and a restart scheduler protect against corruption and memory growth.

Whether you self-host or rent, verify the actual CPU and RAM numbers against the calculator above before committing.

CPU note: Heavily single-thread-bound: each map's world simulation runs predominantly on one core, so high clock speed (4.5 GHz+) and per-core IPC matter far more than core count. A fast 4-6 core chip beats a slow many-core one for a single map. Extra cores only help when you run several map instances (a cluster) on one box. The official wiki recommends ~4 logical cores per map instance.

ASA is built on Unreal Engine 5 and uses substantially more RAM than ASE (UE4). Figures are for vanilla unless noted; mods are the single biggest variable and can multiply RAM use. Empty-server idle RAM per official map (ASA wiki): The Island 8-10 GiB, The Center 10.5-12 GiB, Scorched Earth 7.5-9 GiB, Aberration 8-10 GiB, Extinction 7-8.5 GiB. Newer/larger maps added since (e.g. Lost Colony, Ragnarok-class maps) run heavier, idling around 15 GiB; size accordingly. Fresh servers briefly spike higher at launch, then settle as distant regions enter stasis. Per-player RAM is modest (tens to a few hundred MiB); world age (structures, tames, item stores) grows memory and disk over time more than raw player count. Storage: the server binary is ~11 GiB, but reserve 40 GB+ because Steam needs temporary headroom for large updates and DLC maps add up.