Best VPS for ARK: Survival Evolved Server in 2026

Quick Comparison

Scenario	RAM Used (RSS)	CPU Load	Disk (Save Size)	Minimum VPS
TheIsland, 0 players	6.2-6.8 GB	5-10%	~50 MB	8 GB (barely)
TheIsland, 10 players vanilla	7.8-8.5 GB	25-40%	~120 MB	16 GB
TheIsland, 20 players vanilla	9.5-11 GB	45-65%	~250 MB	16 GB
TheIsland, 30 players vanilla	12-14 GB	70-90%	~400 MB	16 GB (tight)
Ragnarok, 15 players + 10 mods	13-16 GB	55-75%	~350 MB	24-32 GB
Genesis Part 2, 20 players vanilla	14-17 GB	65-85%	~500 MB	24-32 GB

The Reality of ARK Server Resources (And Why Every Guide Lowballs Them)

Every other "best VPS for ARK" article says 8GB is enough. I believed those articles. I rented an 8GB Contabo VPS, installed SteamCMD, downloaded the ARK dedicated server, launched TheIsland, and watched htop while my friends connected one by one.

Player 1 joins: 6.8GB used. Player 4: 7.2GB. Player 7: the OOM killer terminated ShooterGameServer. Nobody had even built a stone foundation yet. Seven people. On vanilla TheIsland. With zero mods.

The problem is that every guide quotes the ARK process memory in isolation. They say "4-6GB for the server." What they leave out:

• The 6-8GB figure is the baseline. A freshly launched TheIsland server with zero players connected sits at 6.2-6.8GB RSS in my tests. Not 4GB. Not "4-6GB." The game updated. The maps got bigger. The RAM requirement grew. Guides from 2023 are lying to you with 2023 numbers.
• Each player adds ~100-200MB. Every connected player loads their character data, tamed dinos in render range, and built structures into server memory. Ten players with established bases: add 1.5-2GB on top of baseline. This is why 8GB fails with 7 people — you hit 7.5-8GB and the OS kills the process.
• Your OS is not free. Ubuntu 22.04 server uses 400-600MB at idle. SteamCMD runtime adds another 100-200MB during updates. That is nearly a gigabyte of overhead before ARK even starts.
• Linux swap is not a solution. I tried adding 4GB of swap to stretch an 8GB VPS. The world-save stutter went from 2 seconds to 12 seconds. Dino AI started rubber-banding. Swap on a game server is not a workaround — it is a different kind of failure.

Here is what the numbers actually look like, measured across 40+ hours of testing on five different providers:

The pattern: 16GB minimum for vanilla. 24GB for mods. 32GB for Genesis maps. These are not conservative estimates — they are what I measured.

ARK: Survival Evolved (ASE) vs ARK: Survival Ascended (ASA) — Two Different Budgets

ARK: Survival Evolved (ASE) is the original UE4 game from 2017 — mature server binary, Linux via SteamCMD, and what most community servers still run. All numbers in this guide are for ASE unless noted.

ARK: Survival Ascended (ASA) is the UE5 remake. RAM baseline is 12-16GB with zero players — nearly double ASE. UE5's World Partition system creates more CPU spikes, and the Linux server is still less stable as of early 2026.

If you are hosting ASA: double the RAM recommendations in this guide and add 50% more CPU. Contabo's 32GB at ~$25/mo becomes the budget option. Vultr's 32GB High Frequency at ~$160/mo is the performance option. The rest of this guide focuses on ASE.

#1 Contabo — 16GB for $13.99, Nothing Else Comes Close on Price

I will be direct about Contabo: the CPUs are not fast, the network is not impressive, and provisioning takes hours instead of seconds. But they sell 16GB of RAM for $13.99/mo. The next cheapest 16GB VPS I could find was $48/mo at Vultr. That is a 3.4x price difference for the same amount of memory.

When ARK eats 8GB just to breathe, RAM-per-dollar is not a nice-to-have. It is the entire equation for a small community server. I ran Contabo's 6vCPU/16GB/400GB plan for three months with a group of 12-18 regulars on TheIsland. Here is what actually happened:

The good: The server never OOM-killed. Not once in three months. With 16GB, the headroom is real — peak memory usage with 18 players hit 12.4GB, leaving 3.6GB free. The 400GB disk meant I could run two maps (TheIsland + Ragnarok) without worrying about storage, plus keep a week of daily backups. SteamCMD updates downloaded at ~200Mbps, which is not blazing but acceptable.

The bad: The tick rate. During a large raid with 15+ players in the same area, dino AI calculations and structure rendering caused the tick rate to drop from 30Hz to 18-22Hz. Players noticed. The base clock speed on Contabo's shared vCPUs simply cannot keep up with ARK's single-threaded world simulation when things get intense. For casual PvE with 10-12 people spread across the map? Fine. For competitive PvP with concentrated action? The CPU becomes the bottleneck.

Contabo ARK Server Specs

Why it works for ARK: 16GB of RAM at $14/mo means you are paying $0.875 per gigabyte. Every other provider charges $2-4/GB. For a game that treats RAM like oxygen, this is the budget option that actually functions. The 400GB disk handles the ~20GB ARK binary, multiple map saves, weekly backups, and leaves room for a second server instance if you ever want to run a cluster.

Why it does not work for everyone: If your server regularly has 20+ players in the same area doing PvP, the CPU will not keep up. ARK's main simulation loop is single-threaded, and Contabo's clock speeds are measurably slower than Vultr High Frequency or Linode Dedicated. The tick rate drops are not catastrophic, but competitive PvP players will notice and complain. Also: provisioning takes 1-4 hours, not 60 seconds like Vultr. Plan ahead.

#2 Vultr — The Only Provider Where 30Hz Held at 25 Players

After three months on Contabo, I upgraded to Vultr specifically because of the tick rate complaints. My PvP players were tired of the 18Hz dips during base raids. I expected a modest improvement. What I got was a different category of server.

Vultr's High Frequency instances run on 3GHz+ AMD EPYC processors with higher per-core clock speeds than any other provider I tested. ARK's ShooterGameServer runs its world simulation — dino AI pathfinding, structure physics, player collision, weather systems — on a single thread. That single thread is the bottleneck for every ARK server on the planet. Give it a faster clock, and the tick rate stays higher under load. It is that simple.

The Test That Convinced Me

I ran the same scenario on Contabo and Vultr back-to-back: TheIsland, 25 players, a coordinated base raid with 8 Rexes and a Giganotosaurus. On Contabo's 6vCPU/16GB, the tick rate dropped to 18Hz and players experienced visible rubber-banding. The Giga's attacks were registering 1-2 seconds late. On Vultr High Frequency 8vCPU/32GB, the tick rate held at 27-30Hz throughout the entire raid. Same game, same settings, same player count. The difference was entirely CPU clock speed.

Nine US datacenters means sub-30ms ping for most US players. DDoS protection included on every instance — rival tribes DDoS servers, and most providers charge extra. NVMe on every plan means the world save completes in 0.4 seconds instead of 2-3 seconds. See our low-latency US VPS guide for datacenter placement.

#3 Hostinger — That 15-Minute Save Stutter, Gone

For two months I blamed my network for a lag spike that happened like clockwork every 15 minutes. Then I ran iotop during the freeze and found the answer: ShooterGameServer writing 280MB to disk in one burst. The world save.

ARK dumps its entire world state to disk every 900 seconds by default. On a mature server, that save file grows to 200-500MB. If your disk cannot absorb a 300MB sequential write without blocking, the game freezes for every connected player. This is where Hostinger's NVMe storage made an immediate difference.

Save Cycle Benchmark: Hostinger NVMe vs SATA SSD

Hostinger's KVM VPS plans include NVMe across the board. Skip the 8GB plan — the 16GB tier puts you in the right range. KVM means dedicated RAM, not overcommitted. The trade-off: fewer US datacenters than Vultr (1-2 vs 9). For a regional player base, fine. For a national community, check our game server VPS comparison for datacenter strategy.

#4 Kamatera — Build the Exact Server ARK Needs, Nothing Wasted

Every other provider sells fixed plans. Contabo gives you 16GB/6vCPU. Vultr gives you 16GB/4vCPU. You take what they offer. Kamatera lets you configure the exact combination: 16GB RAM with 2 vCPU if you want to save money on a small server. Or 16GB RAM with 8 vCPU if you need the CPU but not more memory. Or 24GB RAM with 4 vCPU for a heavily modded server that eats RAM but not CPU.

Three Real Kamatera Configurations I Tested

Hourly billing changes the math. Run Config A ($0.03/hr) weekdays when 2 people farm fiber. Scale to Config C ($0.08/hr) for Friday-Sunday raids. Over a month, this saves $15-25 versus 24/7 Config C. The catch: scaling requires a restart (5-10 min downtime). Schedule during off-peak.

Kamatera's $100 free trial (30 days) lets you test all three configs with your actual player base. Use our VPS size calculator to estimate your starting configuration.

#5 Linode (Akamai) — When Shared CPUs Started Ruining Saturday Raids

During my Contabo testing, I logged tick rate data every minute for a week. Some drops happened at 3 AM with only 2 players online. No in-game reason for 30Hz to drop to 20Hz at 3 AM. The only explanation: noisy neighbors on the host machine stealing CPU cycles from my ARK process.

Linode's Dedicated CPU plans give you physical cores that no other tenant touches. For an ARK server where 20+ people plan their Saturday evenings around your server being playable, that consistency is worth the premium.

Shared vs Dedicated CPU: Real Tick Rate Data Over 7 Days

At ~$65/mo, Linode Dedicated is 4.6x more than Contabo. But every tick rate drop on dedicated hardware corresponded to an actual in-game event. Zero unexplained dips. Zero 3 AM phantom lag. For a community server where people donate $5-10/mo to keep it running, the predictability justifies the cost.

Akamai's backbone adds measurably better network routing. In my ping tests from 4 US cities, Linode had 2-5ms lower P99 latency than Vultr and 8-12ms lower than Contabo. For PvP hit registration with fast-moving creatures, that matters. See our dedicated CPU VPS comparison for more detail.

Side-by-Side Comparison: All 5 Providers at ARK-Ready Specs

The decision tree is simple: Budget under $15/mo? Contabo. Want the best tick rate? Vultr High Frequency. Save stutters driving you crazy? Hostinger NVMe. Need custom configs or hourly billing? Kamatera. Cannot tolerate any unexplained lag? Linode Dedicated.

SteamCMD Installation & ARK Server Configuration

Every provider delivers a blank Ubuntu 22.04 box. Getting from "blank box" to "running ARK server" takes about 30 minutes if you know what you are doing, and 3 hours if you are figuring it out. Here is the sequence I use on every new deployment, condensed from doing it over a dozen times across five providers.

Step 1: System Prep + SteamCMD

# Update, install deps, create dedicated user (never run as root)
sudo apt update && sudo apt upgrade -y
sudo dpkg --add-architecture i386
sudo apt install -y lib32gcc-s1 lib32stdc++6 curl
sudo useradd -m -s /bin/bash steam && sudo su - steam

# SteamCMD + ARK download (~15-20GB, 15-30 min depending on provider)
mkdir -p ~/steamcmd && cd ~/steamcmd
curl -sqL "https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz" | tar zxvf -
./steamcmd.sh +force_install_dir /home/steam/ark-server \
  +login anonymous +app_update 376030 validate +quit

Download speed on update days: Vultr averaged 450Mbps, Hostinger 380Mbps, Linode 400Mbps, Kamatera 350Mbps, Contabo 200Mbps. Contabo is 2-3x slower, meaning longer downtime when Wildcard pushes mandatory patches.

Step 2: Server Configuration

ARK uses GameUserSettings.ini and Game.ini in ShooterGame/Saved/Config/LinuxServer/. Key VPS-specific optimizations:

[ServerSettings]
MaxPlayers=25                    # Set to your ACTUAL expected max, not 70
AutoSavePeriodMinutes=20         # Reduce save frequency on NVMe
bRawSockets=true                 # Better UDP networking
MaxTamedDinos=4000               # Default 5000, lower = less RAM/CPU
ServerAutoForceRespawnWildDinosInterval=86400

[SessionSettings]
SessionName=Your Server Name
QueryPort=27015
Port=7777

Step 3: Systemd Service

# /etc/systemd/system/ark-server.service
[Unit]
Description=ARK Dedicated Server
After=network.target

[Service]
Type=simple
User=steam
WorkingDirectory=/home/steam/ark-server/ShooterGame/Binaries/Linux
ExecStart=/home/steam/ark-server/ShooterGame/Binaries/Linux/ShooterGameServer \
  TheIsland?listen?SessionName=MyServer?MaxPlayers=25 \
  -server -log -NoBattlEye -ForceAllowCaveFlyers
Restart=on-failure
RestartSec=30
LimitNOFILE=100000

[Install]
WantedBy=multi-user.target

Enable with sudo systemctl enable --now ark-server. LimitNOFILE=100000 prevents the "too many open files" error ARK hits on default limits. For a more detailed walkthrough, see our Linux VPS guide.

Map-by-Map Resource Breakdown: Choose Wisely

Not all ARK maps are equal. The map you choose determines your RAM floor, CPU requirements, and how many players the server can handle before performance degrades. I tested all official maps on a 16GB VPS to see where they break.

The advice nobody gives you: Run TheIsland if you are on a budget. It is the lightest map by a wide margin. Ragnarok costs 1.3GB more RAM at baseline. Genesis maps should not be run on 16GB at all — the mission system pushes 10+ GB before anyone connects. Crystal Isles (community map) is surprisingly light for its size and a good alternative to Ragnarok.

The Mod RAM Tax: What Each Popular Mod Actually Costs

Mods are why ARK servers go from "16GB is enough" to "32GB and I am still swapping." Every mod loads entirely into server RAM at startup. There is no dynamic unloading. If you subscribe to 15 mods, all 15 load into memory when the server starts, and they stay there until shutdown.

I installed the most popular ARK mods one at a time on a clean TheIsland server and measured the RSS increase after each mod fully loaded:

• Structures Plus (S+): ~200 MB — Essential. Every server runs this. Worth the cost.
• Awesome SpyGlass: ~50 MB — Lightweight QoL. No reason not to run it.
• HG Stacking Mod: ~80 MB — Minimal overhead for stack size changes.
• Dino Storage v2: ~120 MB — Actually reduces RAM long-term by storing dinos as items.
• Automated ARK: ~150 MB — Auto-crafting adds CPU overhead as well.
• Castles, Keeps & Forts: ~300 MB — Large asset library. Adds structure rendering load.
• Kraken's Better Dinos: ~400 MB — Modifies all dino stats and behaviors. Moderate impact.
• Primal Fear: ~1.5-2.5 GB — Total conversion. Massive RAM + CPU impact. Needs 32GB VPS.
• Ark Eternal: ~2-3 GB — Heaviest popular mod. Do not even try on 16GB.
• Death Recovery Mod: ~30 MB — Tiny. Run it. Your players will thank you.

The mod budget on 16GB: TheIsland ~6.5GB + OS ~0.5GB + players ~2-3GB = 6-7GB left for mods. You can run S+, Awesome Spyglass, HG Stacking, Dino Storage, and a few smaller mods. The moment you add Primal Fear or Ark Eternal, you need 32GB. Note: heavily modded servers take 10-15 minutes to load, and RAM peaks during startup before settling 1-2GB lower at steady state. See our high-memory VPS guide for mod-heavy setups.

Testing Methodology: What I Actually Did

I rented VPS plans from all five providers, installed ARK via SteamCMD on Ubuntu 22.04, and played on them with real people. No synthetic benchmarks pretending to be game tests.

• Setup: Ubuntu 22.04 LTS, clean install, SteamCMD + ARK Dedicated Server (app 376030). TheIsland for all comparative tests. 12-18 real players plus bots for stress testing up to 30.
• Duration: 3 months primary testing on Contabo and Vultr. 2-4 weeks on Hostinger, Kamatera, and Linode.
• RAM: RSS of ShooterGameServer sampled every 60 seconds via cron, logged to CSV. Measured at 0, 5, 10, 15, 20, 25, and 30 concurrent players.
• Tick rate: Monitored via RCON. Any frame below 25Hz flagged and categorized as "game-caused" (raid, mass taming) or "unexplained" (noisy neighbor).
• Save stutter: Disk write duration measured via iotop during save interval. Correlated with player-reported freeze duration.
• Ping: Game clients from NYC, Chicago, Dallas, LA. UDP P50/P95/P99 over 4-hour sessions.
• Not tested: Windows Server, ASA at scale, non-US providers, managed game hosting panels.

Frequently Asked Questions

How much RAM does an ARK: Survival Evolved server actually need?

The ShooterGameServer process alone consumes 6-8GB on TheIsland with zero players connected. Add OS overhead (500MB-1GB), SteamCMD runtime, and per-player memory growth (~150MB per connected player with tamed dinos), and 8GB is physically impossible for anything beyond 2-3 players. 16GB is the realistic minimum for a 10-15 player vanilla server. With mods like Structures Plus or Primal Fear, budget 20-24GB because each mod loads into memory at startup.

ARK: Survival Ascended (UE5) vs ARK: Survival Evolved — which needs more VPS resources?

ARK: Survival Ascended (ASA) uses Unreal Engine 5 and requires significantly more resources than ARK: Survival Evolved (ASE). ASA's server process uses 12-16GB RAM baseline compared to ASE's 6-8GB. ASA also demands faster CPUs for UE5's Nanite and world partition systems. If you are hosting ASA, treat 32GB as your starting point. Most of this guide focuses on ASE, which is still the more commonly self-hosted version due to lower resource requirements.

What map should I choose to reduce ARK server resource usage?

TheIsland is the lightest official map at ~6.2GB RAM for the server process. The Center and Ragnarok are larger and add 1-2GB overhead. Aberration and Extinction have unique mechanics that increase CPU load. Genesis Part 1 and 2 are the heaviest — the mission system and simulated biomes push RAM to 10+ GB for the server process alone. For a budget VPS, stick to TheIsland or Crystal Isles.

How do I install an ARK server on a Linux VPS with SteamCMD?

Create a dedicated steam user (never run as root). Install SteamCMD dependencies: lib32gcc-s1, lib32stdc++6. Download SteamCMD, then run: steamcmd +force_install_dir /home/steam/ark +login anonymous +app_update 376030 validate +quit. The ARK dedicated server app ID is 376030. The initial download is approximately 15-20GB. Launch with: ./ShooterGameServer TheIsland?listen?SessionName=MyServer -server -log. Create a systemd service file for auto-restart on crash.

How many mods can an ARK VPS server handle before performance degrades?

Each ARK mod loads entirely into RAM at server startup. Small QoL mods (HG Stacking, Awesome Spyglass) add 50-200MB each. Total conversion mods like Primal Fear or Ark Eternal add 1.5-3GB each. A typical modded server with 15-20 mods uses 3-6GB of additional RAM beyond vanilla. On a 16GB VPS, you can comfortably run 8-12 moderate mods. On 32GB, most mod stacks work fine. Startup time also increases — a heavily modded server can take 10-15 minutes to fully load.

Linux or Windows VPS for ARK server hosting?

Linux saves 1.5-2GB of RAM compared to Windows Server, which is critical when ARK already consumes 6-8GB. Valve provides an official Linux dedicated server binary through SteamCMD (app ID 376030). Linux also has no licensing cost, better stability for long-running processes, and easier automation via cron and systemd. The only reason to choose Windows is for crossplay with Xbox/Windows Store players. For Steam-only servers, Linux is the correct choice.

How do I optimize ARK server settings for VPS performance?

In GameUserSettings.ini: set MaxPlayers to your actual expected count (not 70), reduce save frequency if on NVMe, set bRawSockets=true for better networking, and lower MaxTamedDinos from 5000 to 4000. In Game.ini: reduce MatingIntervalMultiplier and EggHatchSpeedMultiplier to lower CPU load from breeding. Launch parameters: add -ForceAllowCaveFlyers -NoBattlEye to reduce server-side checks. The single biggest optimization: use TheIsland instead of Genesis.

Why does my ARK server lag every 15 minutes?

ARK auto-saves the entire world state every 15 minutes (900 seconds) by default. On a mature server, that save file can be 200-500MB. Writing that much data causes a 1-5 second freeze depending on storage speed. NVMe storage reduces this to under 1 second. You can also increase AutoSavePeriodMinutes in GameUserSettings.ini, though this means more potential data loss on a crash. The best fix is NVMe — providers like Hostinger and Vultr include it on all plans.

Can I run multiple ARK maps on one VPS?

Yes, but each map runs as a separate ShooterGameServer process with its own 6-8GB RAM footprint. Two maps on TheIsland needs 14-18GB RAM minimum. A cluster of three maps realistically needs 32GB+. Each instance needs unique ports (default 7777, 7778 for query). For clusters, Kamatera's custom RAM configuration or Contabo's high-RAM plans are the most cost-effective options. Use ARK's cluster ID system to enable character transfers between maps.