iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For an ARK: Survival Evolved (ASE) dedicated server, size the machine for the map first, then add memory for connected players, world age, settings, mods, the operating system and other services. Empty-map measurements reported by the ARK Official Community Wiki range from about 3 GiB on several maps to 10–12.5 GiB on Genesis: Part 2, before players and system overhead. A practical host therefore needs more memory than the map figure alone.
CPU performance matters more than a large core count: the same guidance recommends two logical cores per server instance, favors strong single-thread performance and reports diminishing gains beyond four cores. Reserve about 18 GiB for the installation, plus space for saves, profiles, logs, updates and mods, and use a 64-bit operating system with incoming network traffic allowed through the firewall and router.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
ARK: Survival Evolved (PS4) | $19.49 | Buy on Amazon |
| 2 |
|
ARK Ultimate Survivor Edition for PlayStation 4 | $46.99 | Buy on Amazon |
| 3 |
|
ARK: Survival Evolved - PlayStation 4 | $12.20 | Buy on Amazon |
| 4 |
|
ARK: Survival Evolved (PS4) | $28.50 | Buy on Amazon |
| 5 |
|
ARK Ultimate Survivor Edition PS4 Game | $39.59 | Buy on Amazon |
At-a-glance requirements
- RAM: Map baselines run from roughly 3–4.5 GiB on many maps to 10–12.5 GiB on Genesis: Part 2 for a new save, default settings and no connected players. Average additional use is 50–150 MiB per connected player, with further variation from world age, settings and mods.
- CPU: Plan two logical cores for each instance. Favor high single-thread performance; adding cores has diminishing returns and the workload is described as not scaling beyond four cores.
- Storage: Allow approximately 18 GiB for one installation, then add headroom for saves, player and tribe profiles, logs, updates and modifications.
- Operating system: The dedicated-server executable is 64-bit, so the host needs a 64-bit operating system.
- Network: Your firewall and router must permit incoming traffic and forward it to the computer running the server.
These are planning figures, not a guaranteed player capacity. The ARK Official Community Wiki is a community-maintained technical reference, so treat its measurements as useful baselines and validate your own configuration under load.
Free tools Windows power users keep installed
One-click scans. No signup required.
How much RAM does an ARK server need?
There is no single RAM number that fits every ASE server. A lightly used server on a small map can start with substantially less memory than a mature, modded world on a large map. The published map figures below were measured on a new world save with default server settings and no connected players. They do not include the operating system or other applications.
#1 Best Overall
- Use cunning strategy and tactics to tame, train, ride and breed the 100+ dinosaurs and other primeval creatures roaming the dynamic, persistent ecosystems across land, sea, air, and even underground Build your character's strengths and gain items, skills, and pet creatures using in-depth role-playing systems
- Start a tribe with hundreds of other players to survive and dominate competing tribes...and ultimately discover ARK's true purpose
- Build a fire or shelter, then craft customizable clothing & armors to help protect against damage and extreme temperatures on your way to unlocking advanced technologies and equipment
- Chop down trees and mine metal and other precious resources to build massive multi-leveled structures composed of complex snap-linked parts
Empty-map memory by map
| Map | Reported memory on a new save | Planning implication |
|---|---|---|
| The Island | 3.5–4.5 GiB | Leave room above the upper value for the OS, players and configuration. |
| The Center | 3–4 GiB | Baseline is relatively low, but mods and an older save can increase use. |
| Scorched Earth | 3–4 GiB | Use the upper end as the starting point, not as a hard maximum. |
| Aberration | 3–4 GiB | Actual usage still depends on save age and installed modifications. |
| Extinction | 3–4 GiB | Reserve additional memory for connected players and background services. |
| Valguero | 3–4 GiB | Do not treat the empty-map estimate as a hosting-plan limit. |
| Ragnarok | 4–5 GiB | Start with more headroom than the 3–4 GiB maps. |
| Genesis: Part 1 | 5–6 GiB | A higher baseline makes an undersized machine run out of headroom sooner. |
| Crystal Isles | 5.5–6.5 GiB | Account for the larger baseline before adding player and mod overhead. |
| Genesis: Part 2 | 10–12.5 GiB | This is the highest reported baseline in the cited list; plan system and workload headroom on top. |
| Lost Island | 5.5–7 GiB | Use the upper end for initial capacity planning. |
| Fjordur | 4–5 GiB | Player count, world age and mods can move the requirement well above the baseline. |
Memory can also fluctuate while creatures spawn, so a server that appears comfortable immediately after launch may use more RAM later. Measure the process after the world has been running through normal activity rather than sizing from startup alone.
How players change the estimate
The same wiki guidance reports an average increase of 50–150 MiB for each connected player. That is an average increment, not a promise that every player consumes the same amount or that the increase remains perfectly linear. For illustration only, ten simultaneous players would add approximately 0.5–1.5 GiB to the measured map baseline before operating-system and mod overhead. The resulting total still depends on the map, save, settings and activity, so it should not be advertised as a fixed “10-player” requirement.
Use this process instead of a universal player-slot number:
Recommended Free Tools
- Take the upper end of the published baseline for your map.
- Add a scenario allowance for the expected connected players using the 50–150 MiB average as a range, not a guarantee.
- Add memory for the operating system, monitoring, backups and any other services on the machine.
- Add extra headroom for mods, custom rates, clusters and an older world save.
- Run the server under a representative peak and watch committed memory, swap activity and crashes before inviting more players.
Is 8 GB enough for an ARK server?
Eight gigabytes is not a dependable general-purpose target. Steam’s 8 GB Windows minimum belongs to the ARK player client, not the dedicated server. On a low-baseline map with few players, no heavy mods and a machine dedicated to the server, 8 GB may be workable in a narrowly controlled setup, but it leaves little room for the operating system and growth. It is especially unsuitable as a blanket recommendation for Genesis: Part 2, larger maps, mature saves or mod collections. Treat the client minimum and server capacity as separate figures.
Rank #2
- Theme/Subject: Action / Adventure
- Gender: Unisex
- Number of Pieces: 1
- Application/Usage: Indoor
- Foldable Design: No
What CPU do you need to host an ARK server?
Core and thread count
The server guidance recommends two logical cores per instance. A four-thread processor can therefore be a reasonable starting point for one lightly loaded instance if its per-thread performance is strong. More cores do not automatically produce a faster server: the cited guidance says performance gains diminish beyond four cores and that the workload does not scale beyond that point.
Why single-thread performance matters
ASE’s server simulation has important work that benefits from fast individual cores. When comparing otherwise similar machines, prioritize newer architecture, high sustained clock performance and adequate cooling over a very high core count with weak single-thread performance. Two instances should be planned as two separate workloads: reserve roughly two logical cores per instance, then check total CPU contention, memory and disk activity.
Can you run the server on the same PC where you play?
Yes, but the machine must run both the player client and the server at the same time. The client’s own memory and CPU demand is in addition to the dedicated-server workload, and background applications consume part of the remaining capacity. This arrangement is most realistic for a small private session on a higher-specification PC with spare RAM and strong single-thread performance. It is less suitable when the world must remain online while the player’s computer is shut down, when several instances are required or when client and server compete for the same limited memory.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →If the game begins stuttering while the server’s CPU is saturated, reduce other workloads, move the server to a separate machine or rent an instance. If the server process causes paging or the host reports out-of-memory events, add RAM before chasing CPU upgrades.
Rank #3
- Capture and Tame Dinosaurs: Discover over 100 different dinosaurs and prehistoric creatures on the island, finding ways to tame them into useful additions for your tribe's dino herd
- Survive Above All: Hunger, thirst, basic safety, and protecting yourself from the weather are all part of the game
- Harvest, Hunt and Build: Cut down trees and turn them into a basic home, which you can quickly expand into a Jurassic estate. Hunt for meat, scavenge for plants (or start your own garden!)
- Customize Everything: An extensive crafting system invites you to mix and match materials scavenged from the island, while also modifying the colors, textures, shapes, and styles
- Explore the Island: Solve the mystery of The ARK as you explore this massive island, discovering Explorer's Notebooks (filled with clues!) throughout
Storage, operating system and network requirements
Disk capacity
Plan approximately 18 GiB for one ASE server installation. That is only the initial program footprint. Saves, player and tribe profiles, logs, updates and mods require additional space, and update processes may temporarily need more free capacity than the installed files themselves.
- Keep a reserve rather than filling the volume to its limit.
- Place saves and logs where they can be backed up without interrupting the running instance.
- Use reliable storage; a fast SSD can reduce load and update times, but capacity and durability still matter more than a headline sequential-speed number.
- For multiple maps or a cluster, multiply the installation and update allowance and then add shared backup space.
64-bit operating system
The dedicated server is a 64-bit executable and requires a 64-bit operating system. Confirm the operating-system architecture before installing. A 32-bit environment cannot satisfy this requirement regardless of installed physical memory.
Incoming connectivity
Players must be able to reach the host from outside the local network. The host firewall and, where applicable, the router must allow the server’s incoming traffic and forward it to the correct local computer. Exact port values depend on the distribution and configuration you use, so follow the current server setup documentation for those values rather than copying an unverified port list.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteTest from a different network, such as a phone hotspot. A server that works from the same LAN can still be unreachable from the internet because of a missing port-forward rule, a blocked firewall rule, carrier-grade NAT or a changing public address.
Rank #4
- UK IMPORT VERSION , REGION FREE WORKS IN USA , UK PSN ACCOUNT REQUIRED FOR GAME DLC ADD ON'S TO WORK
A practical sizing method
- Choose the map and edition. Record whether you are running one map or a cluster and whether the server is the standard ASE dedicated build.
- Start with the map baseline. Use the upper value in the table for a new save, recognizing that the measurements were made with default settings and no players.
- Define the peak scenario. Write down the maximum simultaneous players, mod list, custom rates, scheduled events and whether the world is new or mature.
- Budget non-game memory. Reserve RAM for the 64-bit operating system, remote administration, monitoring, backups and any other applications sharing the host.
- Provide growth margin. Leave capacity for save growth, creature-spawn fluctuations, updates and additional players. Avoid sizing so tightly that normal activity reaches swap.
- Load-test before opening access. Start the server, travel through active areas, trigger normal spawning and connect the expected number of players. Record peak RAM, CPU utilization, disk latency and network behavior.
- Recheck after changes. New maps, mods, configuration changes and a larger or older save can invalidate the original estimate.
Self-hosting versus renting an ARK server
Self-hosting gives you direct control but makes you responsible for hardware, operating-system updates, backups, security and network access. A rented game server shifts machine administration to the provider, but the useful comparison is not the advertised slot count alone. Verify the actual memory and CPU allocation, supported maps, mod handling and recovery features for the plan you are considering. If you decide to rent, Godlike.Host offers ARK servers with a built-in mod installer and updater, up to three free backups a day with restore, and upgrades or downgrades from the panel if your map or player count outgrows the first plan; see the current plans.
| Decision factor | Self-hosted machine | Rented game server |
|---|---|---|
| Hardware control | You choose and upgrade the CPU, RAM and storage. | Limited to the provider’s plan and upgrade options. |
| Administration | You handle installation, updates, firewall rules, monitoring and backups. | Provider handles the underlying machine; you still manage game settings and often mods. |
| Configuration access | Full access to files, command line and operating system. | Depends on the control panel and permitted configuration. |
| Memory and CPU | Capacity is shared with any other services you run. | Confirm whether advertised resources are dedicated, shared or capped. |
| Maps and clusters | You can design the layout, subject to your hardware and administration time. | Check how many instances and maps the plan actually permits. |
| Mods | You control installation and update timing, but must troubleshoot conflicts. | Check supported mod workflows, update behavior and storage limits. |
| Location and latency | Depends on your home or data-center connection. | Choose a region close to most players and verify the provider’s network quality. |
| Backups and restore | You must schedule, store and test your own backups. | Confirm backup frequency, retention, restore process and whether backups are downloadable. |
| World portability | You own the files and can move them if you preserve the required data. | Check whether saves and configuration can be exported before subscribing. |
| Total cost | Uses existing equipment but adds electricity, storage and maintenance. | Predictable recurring charge; price and limits vary by verified plan. |
When self-hosting fits
- You already have spare RAM after accounting for the operating system and your normal applications.
- You can configure inbound access and keep the machine online when players need it.
- You want complete control over files, mods, maps, backups and upgrades.
- You are willing to monitor resource use and maintain the host.
When renting is the simpler choice
- You do not want to expose or maintain a home network.
- The world must remain online while your personal computer is off.
- You need a location closer to a distributed group of players.
- You prefer a control panel and provider-managed hardware, and the plan supplies enough verified RAM, CPU, storage and backup access.
Symptoms of an undersized server and what to change
Out-of-memory errors, crashes or heavy swapping
Check peak committed memory rather than idle usage. Stop unrelated applications, reduce the number of simultaneous instances, remove unnecessary mods or move to a host with more RAM. Increasing swap can prevent an immediate crash in some operating systems, but it is not a substitute for physical memory and can make gameplay unresponsive.
High CPU usage and simulation lag
Confirm whether one or two logical cores are saturated even when total CPU utilization looks moderate. A processor with faster individual cores may help more than adding many slower cores. Lowering nonessential server activity and separating multiple instances can also reduce contention.
Players cannot connect
Check that the server is listening on the configured interfaces, the host firewall permits the required traffic, the router forwards it to the correct internal address and the public address has not changed. Test from outside the LAN and check whether the internet connection uses carrier-grade NAT, which can prevent inbound forwarding.
Best Value
Save corruption or no room during updates
Inspect free disk space, retain versioned backups and leave temporary room for update files. Back up saves and configuration before changing mods or major settings, and test that a restore actually starts a playable world.
Example planning scenarios
Small private group on The Center
The reported empty-map baseline is 3–4 GiB. A small group still needs additional RAM for the operating system, connected players, creature-spawn fluctuations, the save as it ages and any mods. An 8 GB machine may work only if the entire workload is tightly controlled and monitored; it is not a safe universal recommendation.
Modded Genesis: Part 2 server
Genesis: Part 2 is listed at 10–12.5 GiB before players and system overhead. A host sized near that figure has no practical room for the operating system or a mod collection. Choose substantially more memory, verify peak use under real activity and keep other services off the machine.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Two-map cluster
Run the sizing exercise for each instance, reserve roughly two logical cores per instance and account for combined memory, storage and update activity. Do not assume that one map’s idle measurement predicts the cluster’s peak; monitor both processes while players travel and saves occur.
Bottom-line decision
Choose hardware from the map and peak workload, not from Steam’s 8 GB client minimum. Use the map table as a baseline, add the reported 50–150 MiB average per connected player with a clear uncertainty margin, and reserve RAM for the operating system, world growth and mods. Favor two strong logical cores per instance, provide at least the installation’s approximate 18 GiB plus operational headroom, use a 64-bit OS and verify inbound connectivity. Self-host when you want full control and can maintain the machine; rent when uptime, location or administration effort matters more than owning the hardware.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
