Free tools Windows power users keep installed
One-click scans. No signup required.
To let Epic Games Launcher players join a self-hosted ARK: Survival Evolved server, install the dedicated-server files with SteamCMD (app ID 376030), start the server with -crossplay and -PublicIPForEpic=<your public IP>, and forward the game, peer, and query ports to the host. Use -epiconly instead of mixed crossplay when only Epic players should be allowed.
Godlike.Host offers hosted ARK: Survival Evolved servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
The procedure is the same in principle on Windows and Linux, but the executable, service management, and some operating-system prerequisites differ. The steps below cover installation, launch scripts, router and firewall rules, verification, troubleshooting, and ongoing maintenance.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
ARK: Survival Evolved - PlayStation 4 | $12.20 | Buy on Amazon |
| 2 |
|
Ark: Survival Evolved Plush - Poop | Buy on Amazon | |
| 3 |
|
The unofficial ARK Survival Evolved Guide incl. Add-ons up to Genesis Part1 | $16.99 | Buy on Amazon |
| 4 |
|
ARK: Survival Evolved Pins - Dodo | $11.99 | Buy on Amazon |
| 5 |
|
ARK: Survival Evolved Pins - Rex | $11.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What this setup supports
This guide targets PC players using the Epic Games Launcher and Steam versions of ARK: Survival Evolved. The dedicated server is installed through SteamCMD even when no Steam client is used by the players. The documented Steam application ID is 376030.
Adding -crossplay enables Epic-and-Steam access to the dedicated server. Adding -epiconly narrows access to Epic Games Store clients, so use it only when a Steam player must not join. PC crossplay is separate from console crossplay; do not promise Xbox or PlayStation access unless the exact platform combination and server build are supported.
#1 Best Overall
- Capture and Tame Dinosaurs: Discover over 100 different dinosaurs and prehistoric creatures on the island, finding ways to tame them into useful additions for your tribe's dino herd
- Survive Above All: Hunger, thirst, basic safety, and protecting yourself from the weather are all part of the game
- Harvest, Hunt and Build: Cut down trees and turn them into a basic home, which you can quickly expand into a Jurassic estate. Hunt for meat, scavenge for plants (or start your own garden!)
- Customize Everything: An extensive crafting system invites you to mix and match materials scavenged from the island, while also modifying the colors, textures, shapes, and styles
- Explore the Island: Solve the mystery of The ARK as you explore this massive island, discovering Explorer's Notebooks (filled with clues!) throughout
Mods and unusual server settings can change compatibility. Test the precise map, mod list, and game build that your group will use rather than assuming every Steam configuration will work for Epic clients.
Prepare the host
Choose a reachable machine
Run the server on a Windows or Linux computer that can remain online for the intended play schedule. CPU, memory, disk space, and upload capacity must match the planned player count, map, save size, and mod load. Keep the machine on a wired connection where possible and assign it a stable address on the local network so port-forwarding rules do not break after a reboot.
Linux prerequisite
The setup documentation lists glibc 2.17 as the Linux requirement. Confirm the distribution’s glibc version before installing. If the host is a minimal or obsolete distribution, upgrade it or use a supported operating-system image instead of trying to replace system libraries manually.
Windows Server considerations
Windows Server editions can require additional TLS 1.2 and certificate-revocation-list handling for Epic connectivity. Apply current operating-system updates and follow the server documentation’s certificate and revocation guidance before diagnosing the game as the problem. A desktop Windows installation may avoid those server-edition-specific certificate issues, but it still needs current updates and firewall access.
Create a dedicated directory
Use a directory reserved for the server, such as C:ARKServer on Windows or /srv/ark on Linux. Keep saves, configuration, logs, and downloaded files together so they can be backed up and moved without hunting through user profiles.
Install ARK dedicated-server files with SteamCMD
SteamCMD is the documented installation route. The anonymous account can download the public dedicated-server depot; a personal Steam login is not required for this installation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- Official ARK: Survival Evolved licensed merchandise, turning one of ARK's best-known running jokes into a plush
- Approximately 5.1 x 5.1 in (13 x 13 cm) - small enough to sit on a desk or monitor stand
- Soft filled construction that keeps its shape on a shelf
- Works as the punchline alongside the rest of an ARK plush collection
- A gag gift for ARK players and survival game fans
Windows installation
- Download and extract SteamCMD to a folder with write permission.
- Create the destination directory, for example
C:ARKServer. - Open a command prompt in the SteamCMD directory and run:
steamcmd.exe +force_install_dir C:ARKServer +login anonymous +app_update 376030 validate +quitapp_update 376030 validate installs or repairs the ARK server files. The validation pass can take a long time and may download files again when they differ from the depot.
Linux installation
- Install SteamCMD using the method supplied by your distribution, then create the server directory.
- Run SteamCMD with the destination, anonymous login, app ID, validation, and exit commands:
steamcmd +force_install_dir /srv/ark +login anonymous +app_update 376030 validate +quitRun the command as the account that will operate the server, or ensure that account has ownership of the destination and can write saves and logs. Avoid running the game process as root.
Updating later
Stop the server cleanly before running the same SteamCMD command again. Update files first, then start the server and watch the log for a successful world load. Keep a copy of the save and configuration before a major update so you can recover from an incompatible change.
Create the launch script
The launch command contains two parts: the map and query-string settings before the switches, followed by switches such as -server, -log, and the Epic crossplay options. Replace the example map and session name with your own values.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWindows batch file
Save a file such as start-ark.bat in the server directory:
cd /d C:ARKServer
ShooterGameBinariesWin64ShooterGameServer.exe TheIsland?SessionName=EpicCrossplay -server -log -crossplay -PublicIPForEpic=203.0.113.44
pauseTheIsland is an example map. The session name is the name players search for; choose a distinctive name and keep it consistent when troubleshooting. The pause line leaves the window open if the process exits, which makes an immediate error visible.
Linux shell script
Create start-ark.sh:
#!/bin/sh
cd /srv/ark/ShooterGame/Binaries/Linux
./ShooterGameServer TheIsland?SessionName=EpicCrossplay -server -log -crossplay -PublicIPForEpic=203.0.113.44Make it executable with chmod +x /srv/ark/start-ark.sh, then run it from a terminal or a service manager. A service manager is preferable for a long-running host because it can restart the process after a crash and start it after boot; configure that only after you have confirmed the command works interactively.
Choose the Epic access mode
- Mixed Steam and Epic: include
-crossplayand-PublicIPForEpic=<your public IP>. - Epic only: use
-crossplay -epiconly -PublicIPForEpic=<your public IP>. This is a restriction, not an alternative spelling of crossplay. - Steam-only operation: omit the Epic-specific switches, understanding that Epic clients will not be able to use the server.
The public-IP value must be the address reachable from the internet, not the server’s private address such as 192.168.x.x or 10.x.x.x. Do not include brackets or a port in the parameter. If your provider changes the public address, update the script and restart the server; a stale value can prevent Epic discovery even when local players can connect.
Forward the required ports
Forward each port from the router’s internet-facing interface to the host’s stable local IP address. Select UDP or TCP exactly as shown; forwarding the right number with the wrong protocol is equivalent to leaving it closed.
| Function | Protocol and default port | Purpose |
|---|---|---|
| Game | UDP 7777 | Player game traffic |
| Peer | UDP 7778 | Server networking and advertisement support |
| Query | UDP 27015 | Server-browser discovery and queries |
| RCON (optional) | TCP 27020 | Remote administration |
The router rules and host-firewall rules must permit the same traffic. If you change any port in the launch configuration or run another instance, assign a distinct set of ports and document the mapping. Additional instances normally use incremented or otherwise unused ports; two processes cannot reliably share the same game, peer, or query endpoint.
Router procedure
- Give the server host a DHCP reservation or static local address.
- Open the router’s port-forwarding page.
- Create UDP rules for 7777, 7778, and 27015, each targeting the host’s local address.
- If you enable RCON, create a TCP rule for 27020 only when remote administration is genuinely needed.
- Save the configuration and restart the router only if its interface requires it.
Some internet connections use carrier-grade NAT, which prevents unsolicited inbound connections even when your local router is configured correctly. If the router’s internet address does not match the address shown by an independent public-IP check, ask the provider for a publicly routable address or use a hosting arrangement that supplies one.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Host firewall procedure
Allow the server executable, or create inbound rules for UDP 7777, UDP 7778, and UDP 27015. Add TCP 27020 only for RCON. Limit the rules to the appropriate network profile and host where your operating system permits that level of restriction. Do not disable the firewall as a permanent workaround.
Rank #4
- Official ARK: Survival Evolved licensed merchandise, featuring the Dodo sculpted in textured iron
- Compact pin measuring about 1.6 in (4 cm) across and 0.5 in (1.2 cm) thick - light enough for caps, denim and tote bags
- Raised, textured surface gives the design real depth instead of a flat printed look
- Made in Japan - the pin back attaches securely and sits flat without dragging the fabric down
- A gift for ARK players, survival game fans, and dinosaur enthusiasts
Start and verify the server
- Run the batch or shell script and wait for the world to finish initializing. The first start can take longer while directories and configuration files are created.
- Check the console or log for a running server rather than closing the window after the executable appears.
- From the Epic Games Launcher version, open the ARK server browser and select the list that includes unofficial or dedicated servers as appropriate for your configuration.
- Search the exact session name. If the browser supports a direct address, use the public address and game port from your configuration.
- Join with one Epic account first, then test a Steam account if mixed access is intended.
Do the first test from a different network, such as a phone hotspot, when possible. A connection from inside the same home network may succeed through local routing even when the public forwarding rule is broken.
Why Epic players cannot see the server
The server starts but is absent from the browser
- Confirm the command includes both
-crossplayand-PublicIPForEpic=.... One without the other is an incomplete Epic configuration. - Check that the parameter contains the current public IP and no typo, private address, brackets, or port suffix.
- Verify UDP 27015 is forwarded and allowed through the host firewall; the query endpoint is what browsers use for discovery.
- Confirm the server is not hidden by an incorrect browser filter, password expectation, map filter, or session-name spelling.
- Check the console and operating-system logs for a bind failure, which usually means another process already owns a port.
Players see the name but time out
- Recheck UDP 7777 and UDP 7778 on both router and host firewall.
- Make sure the router forwards to the current local address, not an old DHCP address.
- Test from outside the home network to rule out a loopback limitation in the router.
- Check whether a second ARK instance or another application is using the same ports.
Steam works but Epic does not
Steam-only success proves that the process is running, but it does not prove Epic advertisement is configured. Recheck the two Epic switches, the public-IP value, the query port, and any Windows Server TLS or certificate-revocation requirements. Then test with an unmodded configuration before adding workshop content or custom server options.
Windows Server has inconsistent Epic visibility
Apply TLS 1.2 support and the current certificate-revocation-list handling described for Windows Server editions. A server can appear healthy locally while failing the external Epic-related communication required for listing. Reboot after operating-system changes and retest with the same launch command.
A modded server rejects a player
Temporarily remove nonessential mods and use the exact game build expected by the clients. Add content back one item at a time. A successful unmodded Epic connection narrows the fault to mod availability, load order, version mismatch, or a setting that is not supported by the crossplay client combination.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Protect administration and data
Use RCON sparingly
RCON is optional and uses TCP 27020 by default. If enabled, set a strong administrator password, restrict the firewall rule, and avoid exposing the port to every internet source. If you do not need remote console administration, do not forward it.
Back up the world
Stop the process or use a documented safe-save procedure before copying the save directory. Keep multiple dated generations on storage separate from the live machine. Include configuration files and the launch script in the backup so a replacement host can reproduce the same map, ports, and Epic flags.
Best Value
- Official ARK: Survival Evolved licensed merchandise, featuring the Tyrannosaurus sculpted in textured iron
- Compact pin measuring about 1.6 in (4 cm) across and 0.5 in (1.2 cm) thick - light enough for caps, denim and tote bags
- Raised, textured surface gives the design real depth instead of a flat printed look
- Made in Japan - the pin back attaches securely and sits flat without dragging the fabric down
- A gift for ARK players, survival game fans, and dinosaur enthusiasts
Monitor the host
Watch CPU, memory, disk capacity, network upload, and log growth. A full disk can prevent saves; memory pressure can terminate the process; saturated upload can make every player experience delay. Record the player count and major configuration changes alongside incidents so you can identify patterns.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallUpdating and running multiple instances
Schedule maintenance when players are offline. Stop the server, back up the save, run app_update 376030 validate through SteamCMD, and start the same script again. Read the startup log after every update and test one Epic connection before announcing availability.
For multiple maps or communities on one host, give every instance its own game, peer, query, and optional RCON ports. Use separate directories or explicit save paths so one instance cannot overwrite another. Create a separate launch script for each instance and list its public port mapping in your administrator notes.
Self-hosting versus managed hosting
Self-hosting gives you direct control of files, launch switches, mods, backups, and operating-system access. It also makes you responsible for hardware, bandwidth, router configuration, firewall maintenance, updates, recovery, and uptime. A managed ARK host moves much of that infrastructure to a provider, but you must verify current Epic crossplay support, available ports, mod controls, backup policy, region, resource limits, and total recurring cost before ordering.
| Decision factor | Self-hosted machine | Managed ARK host |
|---|---|---|
| Control | Full access to files, scripts, operating system, and network | Control is limited to the provider’s panel and plan |
| Recurring cost | Uses existing hardware and internet capacity, plus electricity and upgrades | Monthly or recurring charge; verify what resources and backups are included |
| Networking | You configure public addressing, router forwarding, and firewall rules | Provider normally supplies the reachable endpoint; confirm the required ports |
| Updates | You run SteamCMD and schedule restarts | Provider may automate updates, but timing and rollback options vary |
| Backups | You design, store, and test your own backups | Check retention, restore access, and whether backups cost extra |
| Mods | Direct file and configuration access | Panel tools and mod limits differ by provider |
| Epic compatibility | Set -crossplay and -PublicIPForEpic yourself |
Obtain written confirmation that the current service and plan support Epic clients |
Choose self-hosting when you already control a suitable machine and want maximum customization. Choose managed hosting when router access, maintenance time, or reliable public networking is the bigger obstacle, and only after confirming the provider’s current compatibility and recovery terms.
Recommended Free Tools
Quick Recap
Pre-launch checklist
- SteamCMD installed and app ID
376030validated. - Stable local address assigned to the host.
- Launch script uses the intended map and session name.
-crossplayis present for mixed Epic and Steam play.-PublicIPForEpic=<current public IP>is present for Epic visibility.-epiconlyis used only when Steam access should be blocked.- UDP 7777, UDP 7778, and UDP 27015 are forwarded and allowed by the firewall.
- TCP 27020 is exposed only when secured RCON is required.
- Windows Server TLS and certificate-revocation requirements are satisfied where applicable.
- Save, configuration, and script backups exist before opening the server to players.
- An external-network Epic connection test succeeds.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
