How to Set Up a Dedicated ARK Survival Server and Fix Common Errors (2026)

Running your own ARK dedicated server gives you complete control over the game experience. You decide the rules, the mods, the map, and who gets to join. Our team has set up dozens of ARK servers over the years, and this guide walks through every step of the ARK dedicated server setup process from scratch.

Whether you want a private server for friends or a community PvP arena, the fundamentals are the same. You need the right hardware, SteamCMD, correct port configuration, and properly edited config files. We also cover the most common errors that stop servers from working, because those are the problems that frustrate new server admins the most.

One important distinction before we start: this guide focuses on ARK: Survival Evolved (ASE), not ARK: Survival Ascended (ASA). ASE uses SteamCMD with app ID 376030 and ShooterGameServer.exe. ASA uses a different server binary called ArkAscendedServer.exe and a different installation path. If you are setting up the original Survival Evolved, you are in the right place.

By the end of this guide, you will have a fully functional dedicated server that players can connect to, complete with admin access, custom settings, and a troubleshooting playbook for when things go wrong.

Prerequisites and Hardware Requirements

Your hardware determines how many players and creatures your server can handle before performance tanks. ARK is notoriously resource-hungry, and cutting corners here leads to lag, crashes, and frustrated players.

RAM Requirements by Map Size

RAM is the single most important factor for ARK server performance. Here is what we recommend based on real-world testing:

• The Island, Scorched Earth, Aberration (smaller maps): 8 GB RAM minimum, 12 GB recommended for 10+ players

• Ragnarok, Valguero, Crystal Isles (medium maps): 12 GB RAM minimum, 16 GB recommended for active servers

• Genesis 2, Fjordur, Lost Island (large maps with heavy spawn density): 16 GB RAM minimum, 24-32 GB recommended for modded servers or high populations

• Modded servers with multiple stack mods, dino overhaul mods, or structure mods: Add 4-8 GB on top of the base requirement

Memory spikes happen during server saves and when large numbers of tamed dinos are loaded. If your server hits the RAM ceiling during a save, it will crash. Always leave headroom.

CPU Requirements

ARK runs primarily on a single CPU core. This means high clock speed matters far more than core count. A 4-core processor running at 4.5 GHz will outperform a 16-core processor running at 2.5 GHz for ARK.

We recommend at least a 4-core CPU with a clock speed of 3.5 GHz or higher for servers hosting 20 or more players. The game server process is single-threaded, so that single-core performance directly translates to server tick rate and responsiveness.

Storage Requirements

Use NVMe SSD storage whenever possible. ARK server files, save data, and especially mods require fast read speeds. A traditional HDD will work for a basic setup, but expect long load times and slower chunk generation. Plan for at least 100 GB of free space to accommodate the base server files, multiple map saves, and workshop mods.

Save files grow over time as players tame more dinos and build larger bases. A server that starts at 20 GB of save data can easily reach 60-80 GB after months of active play.

How to Set Up a Dedicated ARK Survival Server: Step-by-Step Installation

This is the core ARK dedicated server setup process. Follow each step in order, and do not skip ahead. Many of the most common errors come from jumping steps or rushing the installation.

Step 1: Download and Install SteamCMD

SteamCMD is Valve’s command-line tool for downloading and updating Steam applications. It is how you get the ARK server files without owning a separate copy of the game.

Download SteamCMD from the official Valve developer page. On Windows, extract it to a folder like C:SteamCMD. On Linux, install it through your package manager or download the tarball and extract it to /home/user/steamcmd.

Once installed, launch SteamCMD. On first run, it will update itself. Wait for the prompt to return before proceeding.

Step 2: Download ARK Dedicated Server Files

Log in anonymously and download the ARK server using app ID 376030. Run these commands in SteamCMD:

login anonymous
force_install_dir C:ARK_Server
app_update 376030 validate

This download is large, typically 30-40 GB, so be patient. The validate flag checks every file for corruption, which prevents a whole class of startup errors. If the download stops or errors out, run app_update 376030 validate again until it completes successfully.

On Linux, the path would be something like /home/user/ARK_Server. The process is identical otherwise.

Step 3: Open the Right Ports on Your Firewall and Router

Port forwarding is the step that trips up more server admins than any other. If your ports are not open and properly forwarded, no one outside your local network can connect.

You need to forward these ports on your router to the machine running the server:

• Port 7777 UDP – Game port (primary game traffic)

• Port 7778 UDP – Game port +1 (used in some configurations)

• Port 27015 UDP – Query port (server discovery and Steam listing)

• Port 27020 TCP – RCON port (remote console for admin commands)

Opening only one UDP port causes inconsistent server visibility. Many server admins report that their server appears in the list intermittently or not at all until all UDP ports are forwarded correctly.

Also check your Windows Firewall or Linux firewall rules. You need inbound rules allowing UDP traffic on 7777, 7778, and 27015, plus TCP on 27020. This is separate from router port forwarding and just as important.

Step 4: Launch the Server with Startup Commands

Navigate to your server binary at ShooterGameBinariesWin64ShooterGameServer.exe on Windows. The launch command includes the map name, port assignments, and key flags.

Here is a working startup command for The Island:

ShooterGameServer.exe TheIsland?SessionName=MyServer?ServerAdminPassword=YourPassword?MaxPlayers=70?Port=7777?QueryPort=27015?RCONPort=27020 -server -log

Break down the key flags: SessionName is what players see in the server browser. ServerAdminPassword is the password you type with EnableCheats to access admin commands in-game. MaxPlayers sets the player cap.

Always include the -log flag so a console window stays open and shows server output. Without it, the server runs in the background and you have no visibility into errors or status.

On Linux, the binary is at ShooterGame/Binaries/Linux/ShooterGameServer and you run it with similar arguments. Use a tool like screen or tmux to keep the process running after you disconnect.

Configuring Game.ini and GameUserSettings.ini

Configuration files control everything from taming speed to XP multipliers to structure decay. Two files do the heavy lifting: GameUserSettings.ini handles most server-level settings, while Game.ini handles game-level overrides.

Finding the Config File Paths

The config files live in a specific directory that depends on your operating system:

• Windows: ShooterGameSavedConfigWindowsServer

• Linux: ShooterGame/Saved/Config/LinuxServer/

If these files do not exist yet, start the server once and then shut it down. The server generates default config files on first boot. Edit those files rather than creating new ones from scratch.

Essential GameUserSettings.ini Settings

Under the [ServerSettings] section, these are the most commonly adjusted values:

ServerPassword= – Leave blank for a public server, or set a password for private access.
ServerAdminPassword=YourPassword – Sets the admin password (also set in the startup command).
XPMultiplier=1.0 – Increase for faster leveling.
TamingSpeedMultiplier=1.0 – Increase for faster taming.
HarvestAmountMultiplier=1.0 – Increase for more resources per node.
MaxPersonalTamedDinos=500 – Caps tamed dinos per player to prevent server overload.
ShowFloatingDamageText=True – Shows damage numbers in-game.
AllowThirdPersonPlayer=True – Enables third-person view.
PvEStructureDecayPeriodMultiplier=1.0 – Adjusts how fast structures decay in PvE mode.

After editing, save the file and restart the server for changes to take effect. The server reads these values at startup.

Essential Game.ini Settings

Game.ini is where you override engrams, adjust dino spawns, or change level-up stat multipliers. The most common use is adjusting per-stat multipliers using the PerLevelStatsMultiplier_Player and PerLevelStatsMultiplier_DinoTamed arrays.

These arrays have multiple entries corresponding to different stats (health, stamina, weight, and so on). Each entry increases how much that stat gains per level point spent.

Be careful with formatting in Game.ini. A single syntax error can prevent the server from starting or silently ignore your settings. Always back up the file before making changes.

ARK Server Port Configuration: The Complete Reference

Getting ports right is non-negotiable. Here is the definitive reference for what each port does and which protocol it uses.

Port Assignments

• 7777 (UDP): Primary game port. All in-game traffic flows through this port. If this is blocked, players cannot connect at all.

• 7778 (UDP): Secondary game port. Some server configurations use this for the second game connection. Forward it even if you are not sure you need it.

• 27015 (UDP): Query port. This is how Steam discovers and lists your server. If 27015 is blocked, your server will not appear in the public server list.

• 27020 (TCP): RCON port. Used for remote administration tools and sending console commands without being in the game. Optional but highly recommended for server management.

UDP and TCP are different protocols. Opening a UDP port does not automatically open TCP on the same number, and vice versa. Make sure you select the correct protocol for each port in your firewall and router settings.

If your server is running but not appearing in the list, the query port (27015) is the first thing to check. Verify it is forwarded as UDP, not TCP.

Map Selection and Server IDs

The map name in your startup command determines which map the server loads. Here are the map IDs for the most popular ASE maps:

• The Island: TheIsland

• Scorched Earth: ScorchedEarth_P

• Aberration: Aberration_P

• Extinction: Extinction

• Genesis: Genesis

• Genesis 2: Gen2

• Ragnarok: Ragnarok

• Valguero: Valguero_P

• Crystal Isles: CrystalIsles

• Lost Island: LostIsland

• Fjordur: Fjordur

To change maps, simply update the map ID in your startup command and restart. Save files are stored per map, so switching maps does not delete progress on other maps. This is what makes cluster setups possible.

Installing Mods from Steam Workshop

Mods transform ARK from a vanilla survival game into a completely custom experience. Stack mods, dino overhaul mods, and structure mods are the most popular categories. Here is how to install them correctly.

How to Add Mods

Each Steam Workshop mod has a unique numeric ID. Find the ID in the mod’s Workshop page URL. Add the mod IDs to your server’s startup command using the -automanagedmods flag and the ActiveMods= setting in GameUserSettings.ini.

In GameUserSettings.ini under [ServerSettings], add:

ActiveMods=ModID1,ModID2,ModID3

Comma-separated, no spaces. The server downloads and installs mods automatically on startup when -automanagedmods is included in the launch command.

Mod Load Order Matters

This is one of the most misunderstood aspects of modded servers. Load order determines which mod takes priority when two mods modify the same game element. A wrong load order causes crashes, missing items, or broken mechanics.

The community best practice is to always test the base server without any mods first. Confirm the server starts and players can connect. Then add mods one at a time, restarting between each addition. This makes it obvious which mod causes a problem if one appears.

Crossplay and Mods Are Mutually Exclusive

This is a critical warning that catches many server admins off guard. If you enable crossplay with the -crossplay flag, you cannot use mods. Epic Games Store players cannot download Steam Workshop content, so the server disables mods to maintain compatibility.

If mods are important to your server experience, you must choose between crossplay and mods. There is no workaround for this limitation as of 2026.

Setting Up Crossplay (Steam and Epic)

Crossplay allows both Steam and Epic Games Store players to join the same server. Enabling it is simple but comes with the mod limitation described above.

Add the -crossplay flag to your startup command. That is all it takes on the server side. Steam players connect through the in-game server browser as usual. Epic players connect using the server’s IP address and port directly.

Epic players will need your server’s public IP address and port 7777 to connect manually, since the Epic launcher does not have the same server browser integration as Steam.

Remember: enabling crossplay means no mods. Weigh this trade-off based on your community’s needs.

ARK Cluster Setup for Multi-Map Worlds

A cluster lets players transfer characters, items, and tamed dinos between multiple maps running as separate server instances. This is how communities offer The Island, Ragnarok, and Aberration all connected together.

Cluster ID Configuration

Each server in the cluster needs the same -clusterid=YourClusterName flag in its startup command. All servers sharing the same cluster ID can transfer data between each other.

Use a unique cluster ID that is unlikely to conflict with other servers. Something like -clusterid=MyCommunityCluster2026 works well.

Cluster Directory Structure

The server creates a shared cluster directory where transfer data is stored. On Windows, this defaults to ShooterGameSaved but you can specify a custom path with the -ClusterDirOverride= flag.

If all your cluster servers run on the same machine, they share the cluster directory automatically. If they run on different machines, you need a network share or a dedicated cluster directory accessible to all server instances.

How to Fix Common ARK Dedicated Server Errors

This is the section we wish existed when we first started running ARK servers. Here are the specific errors we have encountered and how to fix them, based on community reports and our own experience.

Server Not Showing in the Server List

This is the number one issue new server admins face. The server is running, you can see the console output, but no one can find it in the in-game browser.

The fix almost always involves the query port. Verify that port 27015 UDP is forwarded on your router and allowed through your firewall. Test with an external port checker tool to confirm the port is actually open from the outside.

If ports are correct, check that your SessionName does not contain special characters that can break the listing. Players can also try connecting directly using the server IP and port 7777 in the Steam server favorites or the in-game direct connect option.

Connection Timeout When Friends Try to Join

If you can connect locally but your friends time out, the issue is port forwarding or firewall rules on the host machine. Double-check that ports 7777 and 7778 UDP are forwarded, not just 27015.

Some routers require you to forward ports to the specific local IP of the server machine. If your server machine uses DHCP, its IP might have changed since you set up port forwarding. Assign a static IP to the server machine and update your port forwarding rules accordingly.

Session Not Found Error

The “Session not found” error typically means a version mismatch between the server and the connecting client. ARK updates frequently, and if your server falls behind, players on the latest client version cannot join.

Run app_update 376030 validate in SteamCMD to update your server to the latest version. Do this every time ARK releases an update. Many admins set up a scheduled task to check for updates daily.

This error can also occur if the server has not finished loading. Large maps with many mods can take 10-20 minutes to fully start. Check the server console for the line indicating the world has loaded before attempting to connect.

Version Mismatch Between Server and Client

Related to the “Session not found” error, a direct version mismatch happens when the server is ahead of or behind the client version. Always update the server within minutes of a game update dropping.

If your server auto-updates, make sure the update process fully completes before players try to reconnect. A partially updated server will reject all connections.

Server Crashes on Startup

If the server process closes immediately after launch, the most common causes are a corrupted mod, a syntax error in a config file, or missing server files from an incomplete SteamCMD download.

First, try launching without any mods by removing the ActiveMods= line temporarily. If the server starts clean, one of your mods is the culprit. Re-add them one at a time to identify the problem mod.

If that does not help, run app_update 376030 validate again to check for missing or corrupted files. The validate flag redownloads any files that do not match the expected checksum.

Memory Leak and RAM Crashes

ARK servers are known for gradual memory increases over time, especially on long-running servers with many tamed dinos. If your server crashes every few days with no obvious cause, RAM exhaustion is the likely culprit.

The fix is scheduled restarts. Set up a daily restart during your server’s low-traffic hours using a batch script or scheduled task. Most communities restart once every 24 hours. High-population servers may need restarts every 12 hours.

Also review your MaxPersonalTamedDinos setting. Each tamed dino consumes server memory and CPU. If players have hundreds of tames, the server load compounds quickly.

Firewall Blocking Connections Silently

Some antivirus programs and third-party firewalls block the ShooterGameServer process without any visible warning. If everything looks correct but connections still fail, temporarily disable your antivirus or firewall to test.

If the server works with the firewall disabled, add an exception for ShooterGameServer.exe (or the Linux equivalent) to your security software. This is a common issue that does not produce any error logs.

Performance Optimization Tips

Once your server is running, these optimizations keep it stable and responsive over the long term.

Schedule Regular Restarts

We mentioned this in the troubleshooting section because it solves so many problems. A daily restart clears accumulated memory, refreshes the server state, and prevents the gradual performance degradation that ARK servers experience.

Set restarts during off-peak hours and give players a warning countdown if possible. Some admin tools support in-game broadcast messages before restarts.

Cap Tamed Dinos

Set MaxPersonalTamedDinos to a reasonable number based on your server size. We recommend 200-300 for smaller servers and 500 for larger communities. Every tamed dino consumes CPU cycles for AI, positioning, and stat tracking.

Without a cap, players accumulate massive dino armies that drag server performance down. A cap forces intentional choices about which tames to keep.

Configure Structure Decay

In PvE mode, abandoned structures never decay by default, which clutters the map and wastes server resources. Set PvEStructureDecayPeriodMultiplier to a reasonable value so unused bases eventually disappear.

A multiplier of 1.0 gives roughly 12 days for thatch, 18 days for wood, and longer for metal structures. Increase the multiplier for slower decay or decrease it for faster cleanup.

Backup Strategies and Automated Restart Scripts

Losing a server save means losing hundreds of hours of player progress. Backups are not optional, they are mandatory.

Manual Backups

Save files are located at ShooterGameSavedSavedArks on Windows or ShooterGame/Saved/SavedArks/ on Linux. The .ark files are your world saves.

To manually back up, stop the server, copy the entire SavedArks folder to a separate location, and restart. Never copy save files while the server is running, as this can produce a corrupted backup.

Automated Backup Approach

Create a scheduled task or cron job that stops the server, copies the save files to a timestamped backup folder, and restarts the server. Keep at least 7 days of backups so you can roll back to any point.

Store backups on a different drive than the server if possible. If your primary drive fails, local backups on the same drive are useless.

Automated Restart Scheduling

On Windows, use Task Scheduler to run a batch file that gracefully stops the server process, waits for cleanup, and relaunches it. On Linux, a cron job combined with a screen session works well.

A simple restart script stops the process, waits 30 seconds for cleanup, then relaunches with your standard startup command. Schedule it for the same time every day to build player expectations.

First-Boot Verification Checklist

Before declaring your server ready for players, run through this checklist. It catches the issues that cause 90% of first-day problems.

• Server console window is open and showing output (the -log flag is working)

• Console shows the map has fully loaded (look for the world load completion message)

• Session name appears correctly in the console output

• You can connect locally using open 127.0.0.1:7777 from the in-game console

• A friend can connect using your public IP and port 7777

• The server appears in the Steam server list with the correct name and player count

• EnableCheats YourPassword works and gives you admin access

• Settings like XP multiplier and taming speed are applied (test by checking values in-game)

• If using mods, all mods downloaded successfully and no errors appear in the console

• A manual save works without crashing (use the saveworld admin command)

If every item on this checklist passes, your server is ready for players. If any item fails, refer to the troubleshooting section above for the specific fix.

FAQs

Conclusion

Setting up an ARK dedicated server is a straightforward process once you understand the pieces: SteamCMD for installation, port forwarding for connectivity, config files for customization, and scheduled restarts for stability. The ARK dedicated server setup process rewards patience and attention to detail.

Start with a vanilla server, verify it works using the first-boot checklist, then layer in mods and advanced features one at a time. When errors appear, work through the troubleshooting section systematically, starting with ports and version checks. Your next step is to install SteamCMD, download app ID 376030, and follow the step-by-step installation above.