What one ARK world asks of the machine
Memory decides the size of your server; cores matter far less. The official community wiki asks for two logical cores per server instance, prefers a fast single thread over extra cores, and says the original game never scales past four. Memory starts with the map, then climbs with players, world age, settings and mods.
| Map | Level name on the launch line | Memory with nobody connected |
|---|---|---|
| The Island | TheIsland | 3.5-4.5 GiB |
| The Center | TheCenter | 3-4 GiB |
| Scorched Earth | ScorchedEarth_P | 3-4 GiB |
| Ragnarok | Ragnarok | 4-5 GiB |
| Aberration | Aberration_P | 3-4 GiB |
| Extinction | Extinction | 3-4 GiB |
| Valguero | Valguero_P | 3-4 GiB |
| Genesis: Part 1 | Genesis | 5-6 GiB |
| Crystal Isles | CrystalIsles | 5.5-6.5 GiB |
| Genesis: Part 2 | Gen2 | 10-12.5 GiB |
| Lost Island | LostIsland | 5.5-7 GiB |
| Fjordur | Fjordur | 4-5 GiB |
Those figures are a fresh save on default settings. Each connected player adds roughly 50 to 150 MiB, so twenty survivors on The Island land between about 4.5 and 7.5 GiB, before the operating system and before the world grows. Usage also jumps while creatures respawn, so leave headroom. Budget about 18 GiB of disk per installation, plus saves, logs, updates and mods.
ARK: Survival Ascended is a different game: app 2430930, Windows only, and far hungrier for memory.
Why a world this hungry wants a whole machine
An ARK world never gets smaller. Bases spread, tames multiply and the game loop keeps leaning on one thread, so a server that felt quick in week one can stutter by month three if anything else competes for that core. On a dedicated game server nobody else runs on the hardware: you choose the machine by its single-thread score and get full root or Administrator access for SteamCMD, mods and your own scripts.
The wiki estimates up to 60 KiB/s per connected player, so even the default 70 slots fit easily inside the 1 Gbps port on the game machines. That port is not shared at the access switch and nothing meters it, so mod downloads on join cost nothing extra. Billing is monthly with no contract.
The server that fits your plans
- One map for friends: a quick quad-core with NVMe and 32 GB carries any single map above with room spare, and the game server page lists one sold in all five cities.
- A cluster: add two logical cores and the map's memory per instance. Several maps outgrow 32 GB fast; the many-core EPYC and Xeon Gold machines reach 1 TB.
- A growing world: memory, disks and port speed can be added later to the same machine, with no migration and no new IP address. Build to order prices each part.
Machines run in New York, Miami, San Francisco, Amsterdam and Bucharest; time the round trip from your browser on the game server page first. A racked machine is handed over about 30 minutes after the order is approved, and the payment check before that is the part that varies.
Up and running on Linux in an evening
The original game runs natively on Linux and needs only glibc 2.17 or newer. Choose Ubuntu, Debian 13 or AlmaLinux 10 at checkout (see Linux dedicated servers), then follow these steps from the official wiki, keeping the game closed off until the passwords are set.
- Create an unprivileged
steamaccount to own the server; the wiki warns that running it as root is unsafe. - Install SteamCMD as Valve's page describes, then, as
steam, download the server:steamcmd +force_install_dir /home/steam/servers/ark +login anonymous +app_update 376030 +quit - Keep SSH open and everything else shut (on Debian, install the firewall first with
sudo apt install ufw):sudo ufw allow proto tcp from any to any port 22 && sudo ufw enable. UFW filters IPv6 too by default; on AlmaLinux the wiki gives firewalld equivalents. - Save the unit below as
/etc/systemd/system/ark-dedicated.service, pointingExecStartPreat your realsteamcmdpath. - Run
sudo systemctl daemon-reload, thensudo systemctl start ark-dedicated, and checksudo systemctl status ark-dedicated. The first start createsShooterGame/Saved. - Stop it with
sudo systemctl stop ark-dedicatedand put your settings inShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini, as in the second block, editing only while it is stopped. - Open the game with
sudo ufw allow proto udp from any to any port 7777,7778,27015, start the service, and runsudo systemctl enable ark-dedicatedso it returns after a reboot (enable alone starts nothing now).
[Unit]
Description=ARK: Survival Evolved dedicated server
Wants=network-online.target
After=syslog.target network.target nss-lookup.target network-online.target
[Service]
ExecStartPre=/home/steam/steamcmd +force_install_dir /home/steam/servers/ark +login anonymous +app_update 376030 +quit
ExecStart=/home/steam/servers/ark/ShooterGame/Binaries/Linux/ShooterGameServer TheIsland?SessionName=MyTribeIsland
WorkingDirectory=/home/steam/servers/ark/ShooterGame/Binaries/Linux
LimitNOFILE=100000
ExecReload=/bin/kill -s HUP $MAINPID
ExecStop=/bin/kill -s INT $MAINPID
User=steam
Group=steam
[Install]
WantedBy=multi-user.target
[ServerSettings]
ServerAdminPassword=REPLACE_WITH_LONG_ADMIN_PASSWORD
ServerPassword=REPLACE_WITH_JOIN_PASSWORD
[SessionSettings]
SessionName=MyTribeIsland
[/Script/Engine.GameSession]
MaxPlayers=20
Keep the admin password in this file, not on the launch line where any process listing shows it. Keep a join password until your tribe is in, and leave RCON (TCP 27020) off unless you use it; if you do, allow it only from your own address.
Several maps, one cluster
A cluster is several server processes that agree where transferred survivors, tames and items are kept. Give each map its own ports on its launch line, counting upward as the wiki does: the second instance takes ?Port=7779?QueryPort=27016 (peer port 7780 follows on its own) and RCON 27021, the third ?Port=7781?QueryPort=27017 and RCON 27022. Each gets its own unit file and its ports in the firewall. Because every map runs from the same installation, keep the SteamCMD update line in only one unit, and stop every map before updating.
Launch every map with the same cluster name and folder, for example ShooterGameServer ScorchedEarth_P?SessionName=MySession2?Port=7779?QueryPort=27016 -clusterid=stonehaven-x7 -ClusterDirOverride="/home/steam/ark-cluster". Maps installed in different folders only see each other's uploads through this shared folder, so set it on every map. Pick an unusual name, since a common one fills your obelisk list with strangers' servers, add -NoTransferFromFiltering to keep single-player characters out, and keep tribute expiry settings identical on every map.
Mods, updates and backups without losing the world
- Mods: add
-automanagedmodsto the launch line, give each Workshop ID its ownModIDS=line under[ModInstaller]inGame.ini, and switch them on withActiveModsunder[ServerSettings]. If Steam throttles anonymous downloads of many mods, the wiki suggests a real Steam login. - Updates: the unit reruns SteamCMD before every start, so a restart is also an update. Back up first.
- Backups:
ShooterGame/Savedholds the world, tribes, players, configuration and logs, plus cluster data unless you set -ClusterDirOverride; with the override, back up that folder (here /home/steam/ark-cluster) as well. Copy them somewhere other than the server, right after an autosave (every 15 minutes by default) or while stopped. - Restores: stop the service, rename the current
Savedfolder instead of deleting it, check the renamed copy exists, then put the backup in place. - Older mods: the wiki documents a
preaquaticabranch (build 358.24) most Workshop mods still work with, but saves touched by 360.1 or later can corrupt on it; switch only with a backup taken before the newer build ran.
Prefer Windows? It works the same way
Windows Server is offered at checkout, its licence priced on the order form. The server needs the Visual C++ 2013 Redistributable (x64) and the DirectX End-User Runtimes (June 2010); the wiki starts it from a start_server.bat in ShooterGame\Binaries\Win64 and opens UDP 7777-7778 and 27015 with an inbound rule in wf.msc. Crossplay with Epic players on Windows Server needs one extra certificate step, also on the wiki.
When this is the wrong place for your server
- You want the game run for you. There is no game panel, no mod installs and no game updates on your behalf.
- Your server is a public PvP magnet. We sell no defence against denial-of-service floods on any machine, so arrange your own before listing publicly.
- You play a few evenings a month. A whole machine billed monthly is more than that needs.
- You need a promised uptime figure. The service agreement credits outages and late part replacements; it states no percentage.
Questions people ask
- Does the original ARK server run on Linux?
- Yes. ARK: Survival Evolved ships a native Linux server, and it needs only a 64-bit system with glibc 2.17 or newer. It is the newer Survival Ascended that is limited to Windows. Linux also saves you the Windows Server licence.
- How much RAM should I get for a cluster?
- Add the empty-map figure for every map, then 50 to 150 MiB per player on each, plus the operating system. Five mid-sized maps need around 20 GiB before anyone joins, and worlds grow, so pick a memory ceiling with room above that.
- Which ports have to be open for players to find my server?
- UDP 7777 is the game port, UDP 7778 is the peer port and always sits one above it, and UDP 27015 answers the Steam server browser. TCP 27020 is only for RCON and can stay closed if you manage the server in-game. Each extra map on the same machine needs its own set.
- Can I bring my existing world from another host?
- Yes. The whole world sits in the ShooterGame/Saved folder: copy it off the stopped old server, install the same map here, and swap the copy in while the new server is stopped. Keep the original until players confirm their characters and tames are back.
- How soon can my tribe log in?
- A machine already in the rack is handed over about 30 minutes after the order is approved, and the payment check before that is the part that varies. After that it is the SteamCMD download (an installation takes about 18 GiB of disk) and your own settings.