Running an Ark: Survival Evolved dedicated server lets you host persistent worlds for friends or communities with greater control, stability, and performance than peer-to-peer play. This guide covers the core requirements, two main installation paths, configuration essentials, networking setup, backups, updates, and common troubleshooting steps. Whether you run a server on Windows or Linux, you can achieve a reliable host with predictable behavior and minimal downtime. The process is straightforward but benefits from careful preparation and routine maintenance.
Ark Dedicated Server System Requirements
Before installing, confirm your hardware and network meet baseline expectations for a stable Ark dedicated server. Requirements scale with player count, mods, and custom maps, but a conservative starting point helps avoid crashes and latency.
Minimum and Recommended Specs
For small, local, or low-population servers, modest resources suffice. Larger public or modded deployments demand significantly more CPU, RAM, and disk throughput to handle simulation, many dinos, and frequent autosaves.
| Component | Minimum | Recommended | Notes |
|---|---|---|---|
| Operating System | Windows 7/10 64-bit | Windows 10/11 64-bit or Linux (Ubuntu 20.04+) | Linux can reduce overhead and simplify automation |
| CPU | Dual-core 2.4 GHz | Quad-core 3.0+ GHz | Server performance is CPU-bound; prioritize high single-thread speed |
| RAM | 8 GB | 16–32 GB | Allocate no more than 75% of system RAM to the server process |
| Storage | 20 GB SSD | 50–100 GB SSD | Use SSD to improve save and load performance |
| Network | 5 Mbps upload stable | 10+ Mbps upload, low latency | Upload capacity matters most for multiple players and dinos |
Install the Dedicated Server
You can install an Ark dedicated server via SteamCMD, which works on both Windows and Linux, or use an all-in-one script on Linux for faster deployment. SteamCMD gives you more control and is the primary method endorsed by developers.
Option A: SteamCMD (Cross-Platform)
SteamCMD downloads and runs the server build used by both clients and dedicated hosts. It supports automatic updates and lets you choose specific versions for stability or mod compatibility.
- Install SteamCMD
- Create a dedicated directory (e.g.,
ark-server) - Run SteamCMD with the command:
steamcmd +login anonymous +force_install_dir ./ark-server +app_update 376030 validate +quit - Accept the EULA by creating
ShooterGame/Saved/Config/LinuxServer/GameUserSettings.iniwithServerAdminPassword=andQueryPort=QueryPortNumber
Option B: Linux All-in-One Script
Community scripts simplify installation on Ubuntu/Debian by automating user creation, SteamCMD steps, firewall rules, and systemd service setup. Use these scripts cautiously, review changes, and understand how updates may affect custom configurations.
Configure Server Settings
After installing the binaries, adjust configuration files to set difficulty, PvP behavior, server name, autosave intervals, and allowed players.
Key Configuration Files
GameUserSettings.ini: Game rules, server password, PvP, difficulty, server name, and query port.ShooterGame.ini: Advanced sessions, tribe flags, taming multipliers, and rates.Engine.ini: Network settings, query configuration, and server browser visibility.
Always back up files before editing. Common changes include setting bIsAdminFlyAllowed=False, adjusting DifficultyOffset, configuring ServerPassword and AdminPassword, and tuning SaveIntervalSeconds to balance performance and data safety.
Open Ports and Network Setup
For external players to connect, forward the necessary ports on your router and, if applicable, configure your firewall. Use a static internal IP for the host to prevent port mapping changes after reboots.
Required Ports
| Protocol | Port | Direction | Use |
|---|---|---|---|
| TCP | 27015 | Inbound | Server query and RCON |
| UDP | 27015 | Inbound | Game client traffic |
| UDP | 27020 | Inbound | Query browser traffic |
| UDP | query port (same as QueryPort in config) | Inbound | Server browser query |
On Linux, ensure QueryPort is set in GameUserSettings.ini and not blocked by iptables or ufw. On Windows, create inbound rules for the port range used by sessions. Test connectivity with an external query tool or from a remote client before announcing the server.
Backups and Maintenance
Regular backups protect your world from corruption, accidental resets, or destructive updates. Automate saves and store copies off-server to guard against hardware failure.
- Schedule frequent backups (at least every 1–4 hours for active servers).
- Back up both the save folder and configuration files.
- Keep a rolling set of backups (e.g., daily for a week, weekly for a month).
- Test restores periodically to verify integrity.
Updates, Mods, and Performance Tuning
Dedicated servers must be updated to remain compatible with the current Steam build. Plan update windows to minimize disruption, and verify mods and configurations after applying patches.
Performance Tips
- Use server tick rate 30 unless higher rates are required for gameplay.
- Monitor CPU and RAM usage; consider process priority adjustments if necessary.
- Consolidate dino counts and manage large tribe structures to reduce server load.
- Disable unused mods and avoid resource-intensive structures near spawn.
Running an Ark dedicated server demands attention to hardware, configuration, and ongoing care, but it delivers a stable, shareable world for your community. Follow these steps, automate where possible, and document your setup so future changes remain predictable and manageable.