VGKAMI
Advertise Get listed

Game Guides

How to Make an ARK: Survival Ascended Server: Step-by-Step Setup Guide

October 26, 2026 11 min read
Avatar photo
Written byVGKami Team

To make an ARK: Survival Ascended dedicated server, use a 64-bit Windows host (or a Windows-compatible environment), install the server files with SteamCMD app ID 2430930, launch the map with the current ASA command-line syntax, and allow the game and query ports through both Windows Firewall and your router. A default installation uses UDP 7777, UDP 7778 and UDP 27015, with TCP 27020 only if you enable RCON. Once the process has finished loading, find the server in the unofficial browser or add its address and query port to the Steam server favorites list.

This guide covers the hardware and network planning, exact SteamCMD commands, a safe launch-script pattern, port forwarding, configuration files, updates, backups and the common reasons a server does not appear.

What do I need before creating an ASA dedicated server?

Plan the host, storage and network before downloading anything. The ARK Official Community Wiki states that ASA has no native Linux support, so use 64-bit Windows or a Windows-like environment that can run the Windows dedicated-server executable.

Host hardware and storage

  • The dedicated-server installation is about 11 GiB. Reserve additional space for saved worlds, player and tribe data, logs, updates and mods.
  • A practical ASA setup guide recommends at least 16 GB of RAM and about 20 GB of disk space for one server. These are planning recommendations rather than an official Wildcard minimum; a stronger CPU gives more headroom as player count, structures and mods increase.
  • Use a reliable, always-on machine. A desktop or spare workstation is easier to maintain than a laptop that sleeps or changes networks.
  • Keep the server on a fixed local IP address, either by creating a DHCP reservation in the router or by assigning a static address in Windows. Port forwarding breaks when the host receives a different address.

Internet connection and router access

The Official Community Wiki highly recommends a home connection of at least 100 Mb for a good number of players. Actual bandwidth use varies with player count, world activity and mod complexity. Wired Ethernet is preferable to Wi-Fi; a Cat6 Ethernet cable is a suitable choice if the host is near the router.

You must be able to change Windows Firewall rules and the router’s inbound port-forwarding settings. If your ISP uses carrier-grade NAT, or blocks unsolicited inbound traffic, normal forwarding may not work even when the local rules are correct.

How do I install the ASA server with SteamCMD?

SteamCMD downloads and updates the dedicated-server files. ASA uses Steam app ID 2430930.

  1. Download SteamCMD for Windows from Valve’s official distribution and extract it to a folder you can administer, such as C:steamcmd.
  2. Create a separate server directory, for example C:arkserver. Keeping the server outside the SteamCMD program folder makes backups and permissions easier.
  3. Run steamcmd.exe. At the SteamCMD prompt, enter:
force_install_dir C:arkserver
login anonymous
app_update 2430930 validate
quit

app_update 2430930 validate both installs missing files and checks the existing installation. Use the same command whenever you update the server. The first download can take time and needs free space for temporary files as well as the final installation.

After completion, the executable should be under C:arkserverShooterGameBinariesWin64. If SteamCMD reports a locked file, close any running server process and run the update again. Do not start a second update while the first SteamCMD session is still active.

How do I create an ASA launch script?

A batch file gives you a repeatable startup command and a place to keep your chosen map, name and ports. Open ShooterGameBinariesWin64, create a file named start_server.bat, and add the command for your instance.

Use the current ASA argument rules

  • Put the map name immediately after ArkAscendedServer.exe. A common example is TheIsland_WP.
  • Map and session-style options use question-mark syntax, such as ?SessionName= and ?MaxPlayers=.
  • When changing the game port, ASA uses the hyphen form -port=7777; do not substitute the older ?Port=7777 form.
  • Options such as BattlEye and some server switches are hyphenated, for example -UseBattlEye.
  • The ASA parser can require ?ServerAdminPassword=... to be the final appended option. Keep the administrator-password argument in that final position when using append syntax, and check the current configuration reference after a major patch.

Example single-server batch file

This example uses the default ports, a 20-player limit and BattlEye. Replace the example passwords and name with your own values; do not publish an administrator password in a screenshot or repository.

@echo off
cd /d C:arkserverShooterGameBinariesWin64
ArkAscendedServer.exe TheIsland_WP?SessionName=VGKamiCommunity?ServerPassword=PlayOnASA?QueryPort=27015?MaxPlayers=20 -port=7777 -UseBattlEye?ServerAdminPassword=ChangeThisAdminPass
pause

Command parsing has changed between ASA patches. If a switch is rejected, copy its spelling and placement from the current server-configuration reference rather than mixing syntax from older ARK: Survival Evolved guides. Add mod arguments only after confirming that each mod has an ASA-compatible ID and current instructions.

For an unpassworded public server, omit ?ServerPassword=. A server password prevents casual joining but does not replace a strong administrator password. Keep the batch file readable so you can identify the map and ports when troubleshooting.

Which ports does an ARK: Survival Ascended server use?

For one default instance, allow these ports in both the host firewall and the router. The game port and peer port are UDP; the Steam browser query is also UDP. RCON is optional and uses TCP.

Port Protocol Purpose Required?
7777 UDP Game traffic Yes
7778 UDP Peer port, normally game port plus one Yes
27015 UDP Steam query and server-browser information Yes for browser visibility
27020 TCP RCON administration Only when RCON is enabled

Windows Firewall rules

  1. Open Windows Defender Firewall with Advanced Security.
  2. Select Inbound Rules, choose New Rule, select Port, choose UDP, and enter 7777,7778,27015. Allow the connection and apply the profiles appropriate for your network.
  3. Create a separate TCP rule for 27020 only if you use RCON.
  4. Alternatively, create an application rule for ArkAscendedServer.exe, but explicit port rules make it easier to audit a multi-instance setup.

Windows may prompt for network access the first time the executable runs. Allowing the prompt on the wrong network profile can leave the server blocked later, so verify the inbound rules manually.

Router forwarding

In the router’s port-forwarding page, send UDP 7777, UDP 7778 and UDP 27015 to the host’s fixed local IP. Add TCP 27020 only for RCON. The dedicated server expects manual forwarding; it does not rely on UPnP automatic forwarding.

For multiple instances, every server needs distinct game, peer, query and (if used) RCON ports. For example, a second instance could use a different game port and its next peer port, plus a separate query and RCON port. Change the batch file and forwarding rules together, and never point two instances at the same query port.

How do I start the server and find it in ARK?

  1. Double-click start_server.bat from the Win64 directory.
  2. Leave the console window open. Initial shader, world and mod loading can take several minutes, especially after an update.
  3. Wait until the log shows that the world has finished loading and the server is accepting connections. Searching while it is still starting can produce a false “missing server” diagnosis.
  4. In ASA, open the unofficial-server browser, select the correct platform and filter, and search for the exact session name from ?SessionName=.
  5. If the in-game list is slow or truncated, add the public IP and query port to the Steam server browser favorites. Use the query port, normally 27015, not the game port.

A server can be reachable by direct address before it appears in a broad in-game search. Search-name spelling, platform filters and browser limits all affect discovery.

Where are ASA settings stored, and how do I change them?

Server settings are stored in ShooterGameSavedConfigWindowsServerGame.ini and GameUserSettings.ini. Stop the server before editing, save the files, and restart the process; changes are not reliably applied to a running instance.

GameUserSettings.ini

Use this file for player-facing and server-session settings exposed by ASA, such as server name, password, player limit and many gameplay toggles. Some values are also accepted on the command line. If the same setting is supplied in two places, use the current ASA configuration guidance to determine which takes precedence.

Game.ini

Use Game.ini for deeper gameplay and progression configuration. Make one controlled change at a time, restart, and inspect the log or in-game behavior before adding another. A malformed section or typo can prevent a setting from loading, so retain a known-good backup.

Mods

Use the mod syntax documented for ASA rather than copying an ASE-only example. Confirm the current mod ID, load order requirements and ASA compatibility on the mod’s own listing. Mods can increase download time, memory use and startup time; remove the newest mod first when a previously working server stops loading.

How do I update, automate and back up an ASA server?

Updating with SteamCMD

Stop the running server, open SteamCMD and run:

force_install_dir C:arkserver
login anonymous
app_update 2430930 validate
quit

Restart with the existing batch file and watch the console for errors. Schedule updates during a maintenance window so players are not disconnected unexpectedly.

Automatic startup

Use Windows Task Scheduler to launch start_server.bat at system startup or user logon. Configure a delay if the machine needs time to bring up networking, and set the task to restart after failure. Test the task after a reboot while you can still access the machine locally.

Backups

The ShooterGameSaved tree contains world, player, tribe, configuration, log and cluster data. Stop the server or use a safe copy procedure before backing up so files are not captured mid-write. Keep at least one backup on another disk or machine, and make a dated copy before an ASA update, major configuration change or mod replacement.

Why is my ASA server not showing up?

Check the failure points in this order. Changing several settings at once makes the cause harder to identify.

  1. Confirm the process is ready. The server console must still be running and must have completed world startup. A crashed process or a window closed by a batch-file error cannot appear online.
  2. Check the exact ports. Compare the launch script with the firewall and router rules. ASA needs UDP 7777, UDP 7778 and UDP 27015 for a standard instance; a typo in one digit is enough to block discovery.
  3. Verify protocol selection. A UDP rule does not open TCP, and a TCP-only rule does not carry game traffic. RCON’s TCP 27020 is not a substitute for the UDP game ports.
  4. Check the forwarding destination. Confirm that the router points to the host’s current local IP. A DHCP change is a frequent cause after a reboot.
  5. Test the public address. Make sure the host has a reachable public IPv4 address and that the ISP is not using carrier-grade NAT or blocking inbound connections. Ask the ISP about a public address if router forwarding appears correct but outside connections fail.
  6. Search correctly. Use the unofficial-server category, the right platform filter and the exact session name. For a slow or incomplete list, use the Steam browser favorite with the public IP and query port.
  7. Review recent edits. Temporarily remove the newest mod or revert the last configuration change, then restart. Keep the original files so you can restore a known-good state.

Should I self-host or use managed ASA hosting?

Self-hosting is best when you want direct file access and can maintain Windows, SteamCMD, firewall rules and backups. Managed hosting trades some control for a provider-managed machine and usually a recurring fee.

Consideration Self-hosting Managed hosting
Control Full access to launch scripts, configuration files and save data Depends on the provider’s panel and file access
Network setup You must handle router forwarding, firewall rules and public reachability Provider normally supplies a reachable server address
Maintenance You install updates, restart after crashes and monitor storage Some maintenance is handled by the provider, but policies vary
Backups You design and test your own backup routine Backup frequency and restore access vary; verify them before subscribing
Mods and files Direct control, with responsibility for compatibility and load order Workflow depends on the provider’s panel and supported mods
Cost Uses your hardware, electricity and internet connection Recurring rental cost, often influenced by slots and location
Latency Usually favorable for players near your home connection Choose a region near the player group; distant locations add latency

Before buying a managed plan, verify current ASA support, available maps and mods, player-slot limits, backup retention, migration options and the provider’s licensing terms. One consulted hosting reference notes a licensing restriction for non-personal or commercial operation; review the current license before charging for access or operating a public business.

What security and administration practices prevent avoidable problems?

  • Use a long, unique administrator password and do not reuse it for Windows, Steam or the router.
  • Expose RCON only when needed. If enabled, restrict TCP 27020 to trusted sources where the router and firewall support source filtering.
  • Run the server under a dedicated Windows account with only the permissions it needs, and keep Windows and SteamCMD updated.
  • Record the map, ports, mods and configuration changes in a dated text file. This makes recovery after a failed update much faster.
  • Warn players before restarts and updates, especially when replacing mods or restoring a save.

Frequently Asked Questions

Can I run an ASA dedicated server on Linux without Windows compatibility?

The ARK Official Community Wiki says ASA has no native Linux support. A Linux machine would therefore need a Windows-compatible environment, and compatibility or performance can change with updates; a 64-bit Windows host is the straightforward supported choice described by the setup references.

Do players need the same mods installed manually to join my ASA server?

ASA can download enabled server mods for connecting players when the mod is available and compatible, but download time and failures depend on the mod and the player’s client. Tell players the mod list and keep the server’s load order stable so a client does not join with an outdated or incompatible version.

Can I run more than one ASA map on the same computer?

Yes, but each simultaneous instance needs its own game, peer, query and optional RCON ports, plus enough CPU, RAM and storage. Give every instance a separate launch script and save/configuration location, then forward each external port to the same host without reusing a port.

Why can friends join locally but not from outside my home?

Local success proves the server process and LAN firewall path work, but not internet reachability. Recheck the router’s destination IP, confirm the forwarded rules use UDP for 7777, 7778 and 27015, and determine whether your ISP places the connection behind carrier-grade NAT.

How do I safely change the server’s map?

Stop the server, back up the entire ShooterGame\Saved tree, change the map token immediately after ArkAscendedServer.exe in the batch file, and start a controlled test. Treat each map’s save as separate data and do not overwrite the old backup until the new world loads correctly.