How to Setup ARK Cluster Servers on a Single VPS: Port Configuration and Clustering Guide

Running more than one ARK: Survival Evolved map can make your gaming community much more interesting. Instead of keeping players on a single map, an ARK cluster lets them move between connected maps while keeping their character, items, and creatures available across the cluster.

You do not always need a separate physical server for every map. With enough VPS resources, multiple ARK server instances can run on a single Linux VPS. The important part is configuring each instance with its own ports, directories, and startup settings.

If you are still choosing the right server resources, our guide to ARK VPS server crashes covers the resource and stability issues that commonly affect ARK servers.

This guide explains how an ARK cluster works, how to run multiple maps on one VPS, how ports are assigned, and what you need to configure to enable character transfers.

What Is an ARK Cluster Server?

An ARK cluster is a group of connected ARK server instances that share cluster data.

Each server can run a different map. For example, you could have:

• The Island
• Ragnarok
• Aberration
• Extinction
• Valguero

Note that each map has an exact identifier used in the startup command: TheIsland, Ragnarok, ScorchedEarth_P, Aberration_P, Extinction, Valguero_P. Some maps use a _P suffix — without the exact identifier, the map will not load.

Players can use the in-game transfer system to move their character between the connected servers.

The important thing to understand is that a cluster is not simply one ARK server with several maps loaded at the same time. Each map normally runs as its own server process.

When multiple instances run on one VPS, each instance should have its own configuration, server directory, and network ports.

Can You Run Multiple ARK Servers on One VPS?

Yes, you can run multiple ARK server instances on a single VPS if the server has enough CPU, RAM, storage, and network capacity for the combined workload.

For example, you could run:

• Server 1 — The Island
• Server 2 — Ragnarok

on the same VPS.

The two instances should use separate server directories and separate network ports.

A useful planning rule: each ARK instance is effectively single-threaded and will saturate one CPU core. A typical map needs roughly 1 full CPU core, 6–12 GB of RAM, and about 10 GB of disk space. For two maps, start with at least a 4-core / 16–24 GB VPS, then monitor actual usage.

The number of servers you can run depends on the resources available and the workload generated by each map.

Running two lightly populated maps is very different from running several heavily populated maps with large bases, many creatures, and multiple mods.

What You Need Before Setting Up an ARK Cluster

Before configuring the cluster, prepare your Linux VPS with:

• A compatible Linux operating system
• SteamCMD
• ARK server files (Steam App ID 376030)
• Sufficient RAM (see sizing above)
• Suitable CPU resources
• Enough storage for multiple maps
• SSH access
• Firewall access
• Separate directories for each server

It is also a good idea to keep your server files organized from the beginning.

For example:

/home/ark/
├── server1/
├── server2/
└── cluster/

The exact directory structure can be different, but keeping each server instance separated makes updates, backups, and troubleshooting easier.

Step 1: Create a Dedicated User and Separate Directories

Run the ARK servers as a dedicated non-root user:

sudo useradd -m -s /bin/bash ark
sudo su - ark

Then create one directory per server, plus the shared cluster directory:

mkdir -p /home/ark/server1
mkdir -p /home/ark/server2
mkdir -p /home/ark/cluster

The first directory will contain your first ARK server, while the second contains the other map.

The shared cluster directory is used to store the cluster data that the connected server instances need to access for transfers.

Keeping these files separate prevents one server's configuration from accidentally affecting another.

Important: use the absolute path /home/ark/... everywhere in this guide. Writing ~/ark instead will resolve to the logged-in user's home directory, which may not be /home/ark — and a mismatched path in the cluster flags will silently break transfers.

Step 2: Install the ARK Server Files

SteamCMD is used to download and update the ARK: Survival Evolved dedicated server files.

If SteamCMD is not already installed on your Linux VPS, install it first (Debian/Ubuntu):

sudo apt update && sudo apt install -y lib32gcc-s1 steamcmd

(For other distributions, use the equivalent package from your distribution's repositories.)

For the first server, use:

steamcmd +force_install_dir /home/ark/server1 +login anonymous +app_update 376030 validate +quit

For the second server, use:

steamcmd +force_install_dir /home/ark/server2 +login anonymous +app_update 376030 validate +quit

The 376030 value is the Steam application ID used for the ARK: Survival Evolved dedicated server.

Once the installation finishes, confirm that the server executable is present in each directory:

ls /home/ark/server1/ShooterGame/Binaries/Linux/ShooterGameServer
ls /home/ark/server2/ShooterGame/Binaries/Linux/ShooterGameServer

If you already have a working ARK server, you can use its installation as the starting point for another instance — but copy it into the new directory and delete or rename the copied ShooterGame/Saved folder (or use ?AltSaveDirectoryName= in Step 4). Otherwise both instances will write to the same save files and corrupt them.

Do not simply launch the same server directory twice without separating the configuration and save locations.

Step 3: Assign Different Ports to Each Server

This is one of the most important parts of a cluster setup.

Multiple ARK server instances running on the same VPS need separate network ports so that their traffic does not conflict.

A standard ARK instance uses four ports:

Port	Protocol	Purpose
7777	UDP	Game port
7778	UDP	Peer port (always game port + 1)
27015	UDP	Query port (Steam server browser)
27020	TCP	RCON (optional, remote administration)

The peer port is always the game port + 1 and is used automatically — you cannot set it separately. This means a server on game port 7777 also occupies port 7778. Leave a gap of at least 2 between each server's game port (for example, 7777 and 7779) so the automatic peer ports never collide.

For the example configuration in this guide, the assignments are:

Server	Map	Game Port (UDP)	Peer Port (UDP)	Query Port (UDP)	RCON Port (TCP)
Server 1	The Island	7777	7778	27015	27020
Server 2	Ragnarok	7779	7780	27016	27021

The exact port numbers can be different. What matters is that each server uses its own available ports.

One rule for choosing query ports:

• Query ports above 27019 are not found automatically by the Steam server browser — players must add IP:QueryPort to their favorites manually.

You should also document your port assignments so you know which ports belong to which map.

Step 4: Configure the First ARK Server

Start by configuring your first map.

Before running the startup command, move into the directory containing the ARK server executable:

cd /home/ark/server1/ShooterGame/Binaries/Linux

For the first server, use:

./ShooterGameServer TheIsland?SessionName=MyARKCluster-TheIsland?AltSaveDirectoryName=Island1?Port=7777?QueryPort=27015?RCONPort=27020 -NoTransferFromFiltering -clusterid=x7Kq2mP9vLz4Rt -ClusterDirOverride=/home/ark/cluster

What each part does:

• TheIsland — the map identifier (use the exact identifier from "What Is an ARK Cluster Server?" — for example, Aberration_P for Aberration).
• SessionName=MyARKCluster-TheIsland — the server name players see in the browser.
• AltSaveDirectoryName=Island1 — gives this instance its own save folder, so a copied installation can never overwrite or corrupt another instance's save.
• Port=7777 — the game port. The peer port (7778) follows automatically.
• QueryPort=27015 — the Steam query port.
• RCONPort=27020 — the RCON port (TCP). Each instance needs a different one.
• -NoTransferFromFiltering — an optional command-line flag that some cluster operators include in their startup commands. It is not a required part of the cluster configuration.
• -clusterid=x7Kq2mP9vLz4Rt — identifies the cluster. Both servers must use the same cluster ID, or they cannot see each other.
• -ClusterDirOverride=/home/ark/cluster — tells the server where the shared cluster data directory is located.

About the cluster ID: use a long, unique ID like the example above — not a short, guessable name. Do not publish your real cluster ID anywhere. Your session name (what players see) can stay friendly; your cluster ID should not.

These three cluster flags (-clusterid, -ClusterDirOverride, and -NoTransferFromFiltering) are command-line options. They are not set in the INI configuration files.

The first server must have its own game, peer, and query ports, and it must be able to read from and write to the shared cluster directory.

Step 5: Configure the Second ARK Server

Create a separate startup configuration for the second map.

First, move into the second server's executable directory:

cd /home/ark/server2/ShooterGame/Binaries/Linux

Then use its own map, session name, and ports:

./ShooterGameServer Ragnarok?SessionName=MyARKCluster-Ragnarok?AltSaveDirectoryName=Rag1?Port=7779?QueryPort=27016?RCONPort=27021 -NoTransferFromFiltering -clusterid=x7Kq2mP9vLz4Rt -ClusterDirOverride=/home/ark/cluster

The map, session name, AltSaveDirectoryName, game port, query port, and RCON port are all different from the first server.

The second server uses:

• Game Port: 7779 (peer port 7780 automatically)
• Query Port: 27016
• RCON Port: 27021

Both servers use the same:

-clusterid=x7Kq2mP9vLz4Rt
-ClusterDirOverride=/home/ark/cluster
-NoTransferFromFiltering

The separate session names make it easier for players and administrators to distinguish the maps, while the shared cluster ID associates both instances with the same cluster.

Step 6: Open the Required Firewall Ports

Your VPS firewall must allow the ports required by your ARK servers.

For the example configuration above, allow:

Server 1:
7777/UDP  (game)
7778/UDP  (peer)
27015/UDP (query)
27020/TCP (RCON — only if you use RCON)

Server 2:
7779/UDP  (game)
7780/UDP  (peer)
27016/UDP (query)
27021/TCP (RCON — only if you use RCON)

With UFW, you can add the required ports using:

sudo ufw allow 7777/udp
sudo ufw allow 7778/udp
sudo ufw allow 27015/udp

sudo ufw allow 7779/udp
sudo ufw allow 7780/udp
sudo ufw allow 27016/udp

# RCON (TCP) — only if you use remote administration, and only from your own IP:
sudo ufw allow from YOUR_ADMIN_IP to any port 27020 proto tcp
sudo ufw allow from YOUR_ADMIN_IP to any port 27021 proto tcp

sudo ufw reload
sudo ufw status numbered

Do not open the RCON port to the entire internet. RCON gives full control of the server, and an exposed RCON port is brute-forceable. If you use it, set a strong ServerAdminPassword in GameUserSettings.ini and restrict access to your admin IP, as shown above.

Then check the firewall rules and confirm that the required ports are listed and enabled.

Do not open random ports just because they are available. Only allow the ports your ARK instances actually require.

Also check whether your VPS provider has an additional network firewall or security group — the ports must be open there as well.

Step 7: Configure the Shared Cluster Directory

For a cluster to work correctly, both server instances must point to the same cluster data location:

-ClusterDirOverride=/home/ark/cluster

and use the same cluster ID:

-clusterid=x7Kq2mP9vLz4Rt

The shared cluster directory stores the cluster data used by the connected ARK server instances. It is not a server-to-server communication channel — instead, it provides a common location for the cluster data required by the connected servers.

Two practical notes:

• The actual cluster files are created in a subfolder named after the cluster ID: /home/ark/cluster/x7Kq2mP9vLz4Rt/.
• That subfolder is only created when a player first uploads or downloads through a transfer terminal. An empty cluster directory at first is normal — do not treat it as an error.

Make sure both instances have permission to read and write to the directory. Since the servers run as the ark user:

sudo chown -R ark:ark /home/ark
chmod 755 /home/ark/cluster
ls -ld /home/ark/cluster

If one server cannot access the cluster directory correctly, transfers may not work as expected.

Step 8: Enable Transfers in the Server Settings

The startup flags are not the whole story. A few settings in each instance's GameUserSettings.ini can silently block transfers.

Edit each file:

/home/ark/server1/ShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini
/home/ark/server2/ShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini

Under the [ServerSettings] section, make sure these settings are present (add them if they are missing):

[ServerSettings]
PreventUploadSurvivors=False
PreventUploadItems=False
PreventUploadDinos=False
PreventDownloadSurvivors=False
PreventDownloadItems=False
PreventDownloadDinos=False
noTributeDownloads=False
CrossARKAllowForeignDinoDownloads=True

The critical one is noTributeDownloads=False — if it is set to True, nothing will transfer, no matter how correctly the cluster is configured. If you copied an existing installation for the second instance, double-check these values in the copy.

Step 9: Start Both ARK Servers

Once the configuration is ready, start the first server and make sure it loads correctly. Then start the second server.

Verify that both instances are running:

ps aux | grep ShooterGameServer

Both processes should appear. Then confirm the ports are actually listening:

sudo ss -ulpn | grep -E '7777|7778|7779|7780|27015|27016'

If you enabled RCON, also check the TCP RCON ports:

sudo ss -tlnp | grep -E '27020|27021'

Watch the server log for errors while it starts:

tail -f /home/ark/server1/ShooterGame/Saved/Logs/ShooterGame.log

Check that:

• Both server processes are running
• Each server is listening on its assigned ports
• Both maps appear in the server browser (or in your own favorites as IP:Port)
• The cluster directory is accessible
• Firewall rules allow the required traffic
• Both servers use the same cluster ID
• Both servers use the same cluster directory
• Each server has its own session name

Do not immediately add more maps until the first two are working correctly.

Testing one connection between two maps first makes troubleshooting much easier. Before opening the cluster to players, test the transfer process with a test character.

How Character Transfers Work Between Cluster Servers

The main purpose of an ARK cluster is to allow players to move between connected maps.

Once the cluster is configured correctly, players can use the in-game transfer system to move their character between servers.

A typical transfer process involves:

1. Joining one map.
2. Accessing a transfer terminal on that map.
3. Selecting the destination server from the cluster list.
4. Uploading the character on the source map.
5. Joining the destination map.
6. Downloading the character at a terminal there.

Both servers must share the same cluster ID for each other to appear in the terminal's cluster list.

Before opening the cluster to players, test the transfer process with a test character.

Things to Check When Transfers Do Not Work

If players cannot move between your ARK maps, check the configuration carefully.

Look at:

• Cluster ID — both instances must use the exact same -clusterid
• Cluster directory — both must use the same -ClusterDirOverride path
• Cluster directory permissions — the ark user must own the directory and be able to read/write it
• INI transfer settings — noTributeDownloads, PreventUpload*, and PreventDownload* (Step 8)
• Server startup parameters — all flags present and matching on both instances
• Firewall rules — game, peer, and query ports open
• Server ports
• Peer ports
• Query ports
• Server logs — ShooterGame/Saved/Logs/ShooterGame.log

Both server instances must use the same cluster ID and the appropriate shared cluster data location.

Also make sure the servers are actually running as part of the same cluster rather than using different cluster IDs or separate cluster directories.

Managing Multiple ARK Servers on One VPS

Running multiple maps means you also have more processes to manage.

A process manager can make administration easier.

You can use tools such as:

• systemd
• screen
• tmux

For a small setup, screen or tmux can be convenient.

For a more permanent production setup, use systemd — it automatically starts services at boot and can restart them when they crash. Example unit file for the first server:

# /etc/systemd/system/ark-island.service
[Unit]
Description=ARK: Survival Evolved - The Island (cluster node 1)
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=ark
Group=ark
WorkingDirectory=/home/ark/server1/ShooterGame/Binaries/Linux
ExecStart=/home/ark/server1/ShooterGame/Binaries/Linux/ShooterGameServer TheIsland?SessionName=MyARKCluster-TheIsland?AltSaveDirectoryName=Island1?Port=7777?QueryPort=27015?RCONPort=27020 -NoTransferFromFiltering -clusterid=x7Kq2mP9vLz4Rt -ClusterDirOverride=/home/ark/cluster
Restart=on-failure
RestartSec=30
LimitNOFILE=100000
Nice=5

[Install]
WantedBy=multi-user.target

sudo systemctl daemon-reload
sudo systemctl enable --now ark-island
systemctl status ark-island
journalctl -u ark-island -f

Create ark-ragnarok.service the same way with the second server's values (server2 paths, Port=7779, QueryPort=27016, RCONPort=27021).

Regardless of the method you choose, give each ARK server its own service or session name, for example:

ark-island
ark-ragnarok

This makes it easier to start, stop, and monitor individual maps.

Monitor VPS Resources

Running several ARK servers on one VPS increases the overall resource requirements.

Keep the sizing rule in mind: one ARK instance ≈ one full CPU core + 6–12 GB RAM + ~10 GB disk. If the VPS runs out of RAM, the Linux OOM killer will terminate the ARK process — which looks like a "random crash."

Monitor:

• CPU usage (each instance should have its own core)
• RAM usage
• Swap usage (heavy swap usage causes lag)
• Disk usage
• Network activity
• Server process health

You can check memory with:

free -h

CPU and running processes can be checked with:

top

Disk capacity can be checked with:

df -h

If several maps are active at the same time, watch resource usage during peak player activity rather than only when the servers are idle.

What Happens If the VPS Does Not Have Enough Resources?

If the VPS cannot provide enough resources for all the ARK instances, you may notice:

• Server lag
• High CPU usage
• Memory exhaustion
• Slow world saves
• Server crashes
• Players being disconnected

Adding more server instances does not automatically mean the VPS can handle them.

If resource usage remains consistently high, reduce the workload or move to a VPS configuration with more suitable resources.

Back Up Your ARK Cluster

Backups become even more important when multiple maps are connected.

Keep backups of:

• Map save files
• Player data
• Cluster data
• Server configurations
• Important mod configurations

Store backups separately from the main VPS whenever possible.

A backup on the same VPS does not provide complete protection if the entire server or storage fails.

Common ARK Cluster Problems

One Server Does Not Appear

Check whether the server process is running and whether the required network ports are open.

Also check the query port: if it is above 27019, the Steam server browser will not find the server automatically — add IP:QueryPort to your favorites to test the connection directly.

If the server is missing from the transfer terminal's cluster list instead of the server browser, make sure both instances use the same cluster ID — terminals only list servers from the same cluster.

Both Servers Use the Same Port

Each ARK server instance needs its own available ports when running on the same VPS and IP address.

Remember the peer port (game port + 1) and the RCON port — all of them must be unique across instances. Check your startup commands and make sure the game, peer, query, and RCON ports do not overlap.

Character Transfer Does Not Work

Check that both servers are using the same cluster ID and shared cluster directory.

Then check the INI transfer settings (Step 8) — especially noTributeDownloads=False — and verify cluster directory permissions and server startup parameters.

One Map Crashes Frequently

Check the server logs and monitor VPS resources. The problem may be related to memory usage (including the OOM killer), CPU pressure, mods, corrupted files, or other configuration issues.

Players Cannot Connect

Check the VPS firewall, provider-level firewall, server IP address, and the ports assigned to the affected ARK instance.

Make sure the game, peer, and query ports required by that server are allowed.

Final Thoughts

Running an ARK cluster on a single VPS can be a practical way to connect multiple maps without maintaining a separate VPS for every server.

The key is proper separation and configuration. Each ARK instance should have its own server directory, map configuration, session name, save directory, and network ports, while the connected servers should use the same cluster ID and appropriate shared cluster data location.

Start with two maps, test connectivity and character transfers, and monitor CPU, RAM, storage, and network usage before adding additional servers.

With organized directories, clearly assigned ports, regular backups, and resource monitoring, you can build an ARK cluster that is easier to manage and troubleshoot.

Frequently Asked Questions

Can I run two ARK servers on one VPS?

Yes. You can run multiple ARK server instances on one VPS if the available CPU, RAM, storage, and network capacity are sufficient for the combined workload. As a planning guide, budget roughly one full CPU core and 6–12 GB of RAM per map.

Do multiple ARK servers on one VPS need different ports?

Yes. Each server instance needs its own available network ports when they are running on the same IP address. That includes the game port, the peer port (always game port + 1), the query port, and — if you enable it — the RCON port.

Can players transfer characters between ARK servers on the same VPS?

Yes, when the server instances are correctly configured as part of the same ARK cluster (same cluster ID and shared cluster directory) and the transfer settings in GameUserSettings.ini are enabled — in particular noTributeDownloads=False and the PreventUpload*/PreventDownload* settings set to False.

Do both ARK servers need the same cluster directory?

Yes. Connected servers should use the same -ClusterDirOverride path and the same -clusterid so that the cluster system can handle transfers between the maps.

How much VPS RAM do I need for an ARK cluster?

There is no single RAM requirement for every cluster, but each ARK instance typically uses roughly 6–12 GB of RAM depending on map, active players, mods, and world activity, plus about 10 GB of disk space. For two maps, start with at least a 4-core / 16–24 GB VPS and monitor actual usage before adding another map.

Why can't players connect to one of my ARK cluster servers?

Check whether the affected server is running, its assigned game, peer, and query ports are open, the VPS firewall allows the required traffic, and any provider-level firewall or security group is configured correctly. Also, if the query port is above 27019, players must add IP:QueryPort to their favorites.

Best ARK VPS Configurations: RAM, Core Count, and Storage Requirements for Smooth Gameplay, Explained Simply

 

Choosing a VPS for an ARK server can get confusing quickly. One hosting plan offers more CPU cores. Another gives you extra RAM. A third advertises NVMe storage but costs more than the rest.

So which specification actually matters?

For an ARK server hosting VPS, you need to look at CPU performance, RAM, storage, player count, map size, and mods together. A lightly modded private server for a few friends doesn't need the same resources as a busy Ragnarok server with large bases and dozens of active players.

This guide breaks down the practical VPS resources you should consider before choosing a plan.

What Does an ARK Server Actually Need?

An ARK dedicated server has to process much more than player connections. While the server is running, it handles creature activity, player movement, structures, inventories, world events, resource spawning, saves, and any additional features introduced by mods.

As your world grows, its resource requirements can change. The four VPS resources worth paying the most attention to are:

• CPU performance
• RAM
• SSD or NVMe storage
• Network capacity

Don't choose a server by looking at only one of these numbers. A VPS with plenty of RAM but weak CPU performance can still struggle. Likewise, a fast CPU won't compensate for a server that regularly runs out of memory.

How Many CPU Cores Does an ARK Server Need?

There's no universal core count that fits every ARK server. A small private world with relatively few players can start with a modest CPU allocation. Larger communities, active bases, and heavier mods create more processing work.

More importantly, don't judge CPU performance only by the advertised vCPU count. Individual core performance matters.

A VPS with fewer high-performance CPU cores may handle an ARK workload better than a plan offering a larger number of slower or heavily shared vCPUs.

When comparing plans, ask whether the CPU resources are shared or dedicated. That distinction can matter considerably for a game server.

Shared CPU vs Dedicated CPU for ARK

A shared CPU VPS means your virtual server uses physical CPU resources alongside other virtual machines on the host. This isn't automatically bad. For a small private ARK server, shared CPU resources may be enough and can keep hosting costs lower.

The problem appears when you need consistently available CPU performance. Other workloads on the physical host may affect the processing capacity available to your VPS.

A dedicated CPU plan generally provides more predictable CPU allocation. That can make it a better fit for:

• Larger ARK communities
• Resource-heavy maps
• Modded servers
• Large player bases
• Servers with frequent peak activity
• Environments where consistent performance matters more than minimum cost

If you're comparing cheap VPS for ARK plans, find out what you're actually receiving rather than comparing prices alone. A cheaper plan isn't necessarily better value if CPU contention makes gameplay inconsistent.

How Much RAM Does an ARK VPS Need?

RAM requirements aren't fixed. The amount your server needs depends on the map, number of players, mods, and how complex the world has become.

As a practical starting point, use these ranges for planning:

ARK Server Type	Starting RAM Range
Small private server	6–8 GB
Growing server	8–12 GB
Larger or modded server	12–16 GB+
Heavy community setup	16 GB+ depending on workload

These figures are planning ranges rather than guarantees. Monitor actual memory consumption after deployment.

On Linux, check memory with:

free -h

You can also use:

htop

If the server regularly consumes nearly all available RAM and begins relying heavily on swap, additional memory may be necessary.

ARK Map RAM Requirements Can Vary

The map you run is part of the resource equation. A small server shouldn't automatically receive the same configuration as a busy server running a larger world with many active areas.

Maps such as Ragnarok can be paired with demanding player-created environments, mods, large bases, and extensive creature populations.

Instead of asking only, "How much RAM does Ragnarok need?", ask:

"How much RAM does my Ragnarok server need for this player count, these mods, and this world?"

Start with enough headroom for the expected workload and monitor memory as the server develops. If you plan to install many mods or expect the community to grow quickly, leaving additional RAM available from the beginning can reduce the need for an immediate upgrade.

Is 8 GB RAM Enough for an ARK Server?

For some smaller configurations, 8 GB can be a reasonable starting point, but it shouldn't be treated as a universal recommendation.

A server that begins with a handful of players and minimal modifications may run comfortably. Months later, that same world may contain larger bases, more creatures, more explored areas, and additional mods.

Your original 8 GB plan may no longer provide enough headroom. This is why monitoring matters more than blindly following a specification chart.

How Much Storage Does an ARK VPS Need?

Don't size storage around the initial installation alone. Your VPS also needs room for:

• Game files
• Map and world data
• Mods
• Configuration files
• Logs
• Updates
• Backups
• Temporary working space

Leaving free disk space is important. A server running close to full storage can create operational problems, particularly when an update or backup suddenly requires additional space.

For an active ARK server, SSD or NVMe storage is preferable to slower storage options.

SSD vs NVMe for ARK Server Hosting

Both SSD and NVMe storage can be suitable for ARK. NVMe generally offers higher storage performance, but storage type shouldn't distract you from CPU and RAM requirements.

Choosing NVMe storage won't solve a server that constantly reaches its CPU limit.

For a larger ARK server, a combination of good per-core CPU performance, sufficient RAM, and fast storage is more useful than maximizing one specification while ignoring the others.

What About Network Speed?

Players connect to your ARK server over the network, so network quality matters too.

• Port speed
• Included bandwidth
• Data transfer limits
• Server location
• Network stability

If most players are in one region, placing the VPS reasonably close to them can help reduce network latency. A powerful server located far from most players may still deliver a poor experience because network distance and routing affect latency.

Recommended VPS Configurations by Workload

Rather than treating one plan as the best VPS specs for ARK server, match the resources to the actual workload.

Small Private ARK Server

Suitable for a few friends and a relatively simple setup.

• 2–4 capable vCPU cores
• 6–8 GB RAM
• SSD or NVMe storage
• Enough disk capacity for game files, saves, and backups

Growing ARK Server

• 4+ capable vCPU cores
• 8–12 GB RAM
• NVMe or fast SSD storage
• Additional storage headroom
• Reliable network connectivity

Larger or Heavily Modded ARK Server

• Strong CPU performance with adequate core allocation
• 12–16 GB RAM or more based on actual usage
• NVMe storage
• Sufficient backup capacity
• Stable network performance

For this workload, dedicated CPU resources may be worth considering.

Don't Forget Backup Storage

Backups are part of your storage requirement. If your live ARK installation uses a significant portion of the disk, keeping multiple local backups can quickly consume the remaining capacity.

Decide how backups will work before the server becomes large. You may keep a limited number locally and move additional copies to separate storage.

Test your restore process as well. A backup you have never successfully restored shouldn't be blindly relied upon.

How to Know When Your ARK VPS Needs More Resources

Don't upgrade simply because one monitoring graph briefly spikes. Look for consistent patterns.

• CPU stays near its limit during normal gameplay
• RAM is regularly exhausted
• Swap usage becomes excessive
• Player count has increased significantly
• Mods have increased server workload
• Large bases cause repeated performance problems
• The world has become substantially more complex

If you're already seeing CPU-related problems, read this ARK server hosting VPS troubleshooting guide for practical ways to diagnose high CPU usage before moving to a larger plan.

Upgrading hardware won't necessarily fix a badly configured server or a problematic mod.

A Practical Configuration Rule

High RAM + weak CPU = possible CPU bottleneck

Fast CPU + insufficient RAM = memory pressure

Good CPU and RAM + nearly full disk = storage problems

Powerful hardware + distant server location = possible latency issues

Your goal is to avoid creating an obvious weak point. Start with resources appropriate for your expected workload, monitor the server, and scale when real usage shows that you need more capacity.

Frequently Asked Questions

What are the best VPS specs for an ARK server?

There isn't one configuration that fits every server. CPU performance, RAM, storage, player count, map, and mods should all be considered. Small private servers can start with fewer resources, while larger or heavily modded servers need additional headroom.

How much RAM should I choose for an ARK VPS?

A small server may start around 6–8 GB, while growing or modded environments may need 8–16 GB or more. Monitor actual RAM usage because requirements change as the world develops.

Is a shared CPU VPS good for ARK?

It can work for smaller private servers. For larger or more demanding environments, dedicated CPU resources may provide more consistent processing capacity.

Is NVMe necessary for an ARK server?

It isn't an absolute requirement, but fast SSD or NVMe storage is preferable for an active game server. Storage speed is only one part of performance; CPU and RAM still need to match the workload.

Is a cheap VPS good enough for ARK?

Possibly, for a small workload. Check CPU performance, RAM, storage, network limits, and whether CPU resources are shared before choosing purely on price.

Does Ragnarok need more VPS resources?

Resource needs depend on more than the map name. Player count, mods, structures, creature populations, and overall world activity can substantially change CPU and RAM requirements.

Should I choose more cores or faster CPU performance?

Both matter, but adding more vCPU cores isn't always a substitute for strong individual-core performance. Look at the actual CPU environment rather than choosing a VPS solely by its core count.

Final Thoughts

The best ARK VPS configuration isn't the plan with the biggest numbers. It's the configuration that matches what your server is actually doing.

For a small private world, moderate CPU and RAM resources may be enough. As the player count, mods, bases, and world complexity increase, additional CPU capacity and memory become more important.

Start with a balanced configuration, leave room for growth, and monitor actual resource usage.

If performance begins to drop, find the bottleneck first. Knowing whether CPU, RAM, storage, a mod, or the network is causing the problem makes your next upgrade far more useful—and can save you from paying for resources you don't actually need.

How to Configure Automatic Backups and Cron Jobs for Your Minecraft VPS — Here's What You Need to Know

Running a Minecraft server means putting time into your world, builds, player progress, and server settings. Losing that data because of a server crash, failed update, mod problem, or corrupted world can be frustrating.

That is why automatic backups are worth setting up from the beginning.

If you host Minecraft server on VPS, you can use simple Linux tools such as cron jobs to create regular backups without having to remember to do them manually.

In this guide, we'll explain how automatic Minecraft backups work, how to create a backup script, how to schedule it with cron, and how to restore your server when something goes wrong.

Why Should You Back Up Your Minecraft Server?

Your Minecraft world contains more than just the map.

It may include:

• Player progress
• Builds and structures
• Inventory data
• World settings
• Plugins
• Mods
• Server configuration
• Permissions
• Custom files

If the world becomes corrupted or important files are accidentally deleted, restoring a recent backup can save hours or even months of work.

Manual backups are useful, but they are easy to forget. Automatic backups solve that problem by running at scheduled times.

What Is an Automatic Minecraft Backup?

An automatic backup is a copy of your Minecraft server data that is created on a regular schedule.

For example, you could configure your VPS to create a backup:

• Every day
• Every six hours
• Every week
• Before major updates
• Before installing new mods or plugins

The backup can be stored on the same VPS or copied to another storage location.

For important Minecraft servers, keeping a backup somewhere separate from the main VPS is safer because a VPS failure could affect both the live server and local backups.

What Is a Cron Job?

Cron is a scheduling tool available on Linux systems.

It allows you to tell your VPS to run a command or script at a specific time.

For example, you could create a cron job that runs your Minecraft backup script every night at 2:00 AM.

Instead of logging into the server every day and starting the backup yourself, cron handles the task automatically.

Step 1: Create a Backup Directory

First, create a directory where your Minecraft backups will be stored.

For example:

mkdir -p ~/minecraft-backups

You can use a different location if your server has a dedicated backup drive or storage volume.

Keeping backups in a separate directory makes them easier to manage.

Step 2: Create a Minecraft Backup Script

Next, create a simple backup script.

For example:

nano ~/minecraft-backup.sh

Add a script similar to this:

#!/bin/bash

SERVER_DIR="/home/minecraft/server"
BACKUP_DIR="/home/minecraft/backups"
DATE=$(date +"%Y-%m-%d_%H-%M-%S")

mkdir -p "$BACKUP_DIR"

tar -czf "$BACKUP_DIR/minecraft-$DATE.tar.gz" -C "$SERVER_DIR" world world_nether world_the_end

The exact folder names may be different on your server, so change the paths to match your Minecraft installation.

This script creates a compressed backup containing the main Minecraft world folders.

Step 3: Make the Script Executable

After saving the script, give it permission to run:

chmod +x ~/minecraft-backup.sh

You can then test it manually:

~/minecraft-backup.sh

Check your backup directory afterward:

ls -lh ~/minecraft-backups

You should see a backup file with a date and time in its name.

Step 4: Schedule the Backup With Cron

Now you can tell Linux when to run the script.

Open your cron configuration:

crontab -e

To run the backup every day at 2:00 AM, add:

0 2 * * * /home/minecraft/minecraft-backup.sh

Save the file.

The cron job will now run automatically at the scheduled time.

Understanding the Cron Format

A cron schedule contains five time fields:

minute hour day month weekday

For example:

0 2 * * *

means:

• Minute: 0
• Hour: 2
• Day: Every day
• Month: Every month
• Weekday: Every day of the week

So the backup runs every day at 2:00 AM.

Another example:

0 */6 * * *

This runs the backup every six hours.

Choose a schedule based on how frequently your world changes and how much backup storage you have available.

Should You Stop Minecraft Before Taking a Backup?

This depends on how the backup is created and how important data consistency is for your server.

Copying files while Minecraft is actively writing to them can sometimes result in an incomplete or inconsistent backup.

For a simple server, you may choose to stop the server briefly before creating a full backup.

Another option is to use Minecraft's save commands and then perform the backup.

For example:

/save-all

This tells Minecraft to save the current world data.

After saving, the backup process can copy the required files.

For larger or busy servers, it is worth testing your backup method before relying on it for recovery.

Automatically Remove Old Backups

If you create a backup every day, your storage directory will eventually become full.

You can automatically remove old backup files with the find command.

For example:

find /home/minecraft/backups -type f -name "*.tar.gz" -mtime +7 -delete

This removes backup files older than seven days.

You can change +7 to another number depending on how long you want to keep your backups.

A longer retention period gives you more recovery options, but it also requires more storage.

Store Minecraft Backups on Separate Storage

Keeping every backup on the same VPS has a limitation.

If the VPS has a serious hardware, storage, or filesystem problem, your backup files may also become unavailable.

For important servers, consider copying backups to another storage location.

Possible options include:

• Separate VPS storage
• Object storage
• Remote backup servers
• Cloud storage
• External storage services

The exact method depends on your infrastructure and budget.

The important principle is simple: don't keep your only backup beside the original data.

How to Test Your Minecraft Backup

Creating backups is only half of the job.

You should also test whether they can actually be restored.

Choose a backup and extract it into a separate test directory.

For example:

mkdir ~/minecraft-restore-test

Then extract your backup:

tar -xzf minecraft-2026-09-21_02-00-00.tar.gz -C ~/minecraft-restore-test

Check that the important world files are present.

A backup that has never been tested should not be considered completely reliable.

How to Restore a Minecraft Backup

If your Minecraft world becomes corrupted or important files are deleted, you can restore a previous backup.

Before replacing your current world, stop the Minecraft server.

Then move the damaged world directories somewhere safe instead of deleting them immediately.

For example:

mv world world-old

Extract your backup into the Minecraft server directory:

tar -xzf minecraft-backup.tar.gz

Check the restored files and then start the Minecraft server again.

Always make sure the backup you're restoring is compatible with your Minecraft server version and configuration.

How Often Should You Back Up Minecraft?

There is no single schedule that works for every server.

A small private server may only need a daily backup.

A busy community server with frequent player activity may benefit from backups several times a day.

Consider:

• Number of active players
• How frequently the world changes
• Server activity
• Available storage
• How much progress you can afford to lose

If players make important changes throughout the day, more frequent backups can reduce the amount of progress lost after a problem.

Common Minecraft Backup Mistakes

Keeping Only One Backup

If that backup becomes corrupted, you have nothing else to restore.

Keep multiple backup versions when possible.

Saving Backups Only on the VPS

A VPS failure can potentially affect both your live server and its local backups.

Keep important copies somewhere separate.

Never Testing Restoration

A backup file existing on disk does not guarantee that the restoration process will work.

Test your backups periodically.

Keeping Unlimited Backups

Storage space is limited.

Set a retention policy so old backups are removed automatically.

Forgetting Server Configuration Files

Your world files are important, but don't forget other useful data.

Depending on your setup, you may also want to back up:

• server.properties
• Plugin configuration
• Mod configuration
• Permissions
• Whitelist files
• Server scripts

A Simple Automatic Backup Strategy

For a small Minecraft VPS, you could start with a straightforward setup:

Daily backup at 2:00 AM.

Keep the last seven daily backups.

Copy important backups to separate storage.

Test restoration regularly.

This gives you a simple system without making server administration unnecessarily complicated.

As your Minecraft community grows, you can increase backup frequency and use more advanced remote-storage solutions.

Final Thoughts

Automatic backups are one of the simplest ways to protect a Minecraft server.

A basic Linux VPS already provides the tools you need to automate the process. With a backup script and a cron job, you can create scheduled copies of your Minecraft world without having to remember to do it manually.

However, automation should not stop at creating files. Keep multiple backup versions, store important copies separately, and test restoration from time to time.

That way, if a mod causes problems, a world becomes corrupted, or a server update goes wrong, you have a practical way to recover your Minecraft world and get back to playing.

Frequently Asked Questions

1. How often should I back up my Minecraft VPS?

For a small private server, once a day may be enough. Servers with frequent player activity may benefit from backups every few hours.

2. Can I automate Minecraft backups with a cron job?

Yes. Linux cron can run a backup script automatically at scheduled times, such as every day or every six hours.

3. Should Minecraft be stopped during a backup?

For a basic file backup, saving the world before copying the files is important. For more complex setups, stopping the server briefly can help ensure the backup is consistent.

4. Where should I store Minecraft backups?

For important servers, keep copies somewhere separate from the main VPS. Remote storage, object storage, or another backup server can provide an additional recovery option.

5. How long should I keep Minecraft backups?

It depends on your storage capacity and recovery needs. A simple setup could keep seven daily backups, while larger servers may use a longer retention period.

6. How do I know if my Minecraft backup actually works?

Test the restoration process. Extract a backup into a separate directory or test server and verify that the world and required configuration files are available.