How to Make an Empyrion Server: Step-by-Step Setup Guide for Windows

To make an Empyrion: Galactic Survival server, install the Empyrion Dedicated Server tool on a 64-bit Windows 10 or 11 PC, edit its dedicated.yaml configuration, launch the supplied command file, and forward ports 30000–30004 (TCP and UDP) to the host computer. Use Steam’s Library → Tools list when the tool is available; otherwise install App ID 530870 with SteamCMD. You must also allow the server through Windows Firewall and test a connection from outside your home network. This guide covers installation, configuration, router setup, automatic startup, backups, updates, and the failures most likely to prevent friends from joining.

What do you need before making an Empyrion server?

A dedicated server is a continuously running copy of the game’s server software. It stores the world independently of a player’s game session, so friends can connect while the administrator is not actively playing. The host must stay powered on, have dependable upload bandwidth, and be reachable at a stable address on the local network.

Hardware and operating-system baseline

Requirement	Published baseline	How to interpret it
Operating system	64-bit Windows 10 or Windows 11	The dedicated-server instructions and current Steam requirements target Windows. Keep Windows updated, but schedule reboots so they do not interrupt an active world.
Memory	10 GB minimum; 16 GB recommended	These are Valve’s current game requirements, not a guaranteed player-capacity promise. Scenarios, active playfields, mods, and player activity can increase actual use.
Storage	10 GB minimum; 15 GB recommended; SSD highly recommended	Leave additional free space for save growth, logs, scenario files, backups, and updates.
Network	Reliable upload and a stable local address	Your router rules must always point to the same private IP address. An unstable address can make a correctly configured server disappear after a reboot.

Valve lists the memory and storage figures on its Empyrion technical-support and system-requirements page. Treat those values as a starting point rather than a sizing calculator for a large public server; no authoritative universal player limit exists.

Prepare a backup location

Create a folder outside the installation directory for copies of dedicated.yaml, save folders, scenario files, and any custom startup scripts. Back up before every game or server-tool update. Keeping dated copies lets you restore a known-good configuration if a new build changes a setting or makes a scenario incompatible.

How do you install the Empyrion Dedicated Server tool?

The recommended installation route is Steam’s Tools library. If the tool is missing there, SteamCMD can download the Windows 64-bit dedicated-server files with App ID 530870.

Install through Steam Library → Tools

1. Open the Steam client and select Library.
2. Use the library filter or drop-down to show Tools.
3. Find Empyrion Server (the installed folder is normally named Empyrion - Dedicated Server) and install it.
4. Open the installation folder after Steam finishes downloading it. Keep the path handy because you will edit the configuration and launch scripts there.

The official dedicated-server guide notes that, from version 4.0, the Server Tool is installed from STEAM → LIBRARY → TOOLS → Empyrion Server. Interface labels can change, so search the Tools list for “Empyrion” if the exact filter layout differs.

Use SteamCMD when the tool is not listed

SteamCMD is Valve’s command-line Steam client. Download and extract it, run it once on Windows so it creates its files, then open a Command Prompt in the SteamCMD directory. Replace the example path with the folder where you want the server installed:

steamcmd.exe +force_install_dir "C:EmpyrionServer" +login anonymous +app_update 530870 validate +quit

+force_install_dir selects the destination, +login anonymous uses the tool’s anonymous download access, +app_update 530870 validate downloads or repairs the dedicated-server files, and +quit closes SteamCMD. SteamDB identifies 530870 as the free Windows 64-bit dedicated-server tool and records an update on 31 August 2026; build metadata and launcher behavior are volatile, so check the current SteamDB configuration record if installation behavior changes.

How do you configure the Empyrion server?

Stop the server before editing its active YAML file. Open dedicated.yaml in a plain-text editor, preserve indentation, and copy the original file before changing anything. YAML treats spacing and property names as data; a misplaced space or misspelled key can cause a setting to be ignored.

Core settings to review

Setting	Purpose	What to check
Srv_Port	Main server port	The documented default is 30000. The external forwarding range is 30000–30004 unless your installed build documents a change.
Srv_Name	Name shown to players	Choose a distinctive name so friends can identify the correct listing.
Srv_Password	Optional join password	Set one for a private friends-only world; distribute it through a separate channel.
Srv_MaxPlayers	Connection limit	Set a limit appropriate to your hardware and scenario. Do not assume a published universal capacity.
Srv_ReservePlayfields	Reserved playfield capacity	Keep the value consistent with the scenario and available memory.
Srv_Description	Server description	Explain rules, mods, region, and any scheduled maintenance.
Public-server visibility	Controls listing visibility	Enable Srv_Public when you want the server listed. A private server can still be joined directly if networking is correct.
Telnet options	Remote administration	Enable Telnet only if needed, then set its port and a strong password. Do not expose an administrative port unnecessarily.
SaveDirectory	Location of world saves	Point it to the save location you intend to back up. This setting is a common cause of apparently missing worlds.
Blueprint restrictions	Allowed blueprint types	Review restrictions before inviting players, especially on a survival server with a shared ruleset.
GameName	World identity and save selection	Use the exact existing world name when reopening a save; a different value starts a separate world.
Game mode, seed, scenario	Defines the world setup	Choose survival or creative, set the seed, and select the intended custom scenario. Every client must have compatible scenario and mod files.

The full property list and current examples are maintained in the official Empyrion dedicated-server guide. Do not copy a setting into a different section or change the spelling shown by the installed template.

Keep custom launchers safe from updates

If you maintain more than one configuration, copy the original YAML and give each copy a clear name. Add -dedicated your-copy.yaml to a copied startup script so an update cannot silently replace your custom launcher or make it point to the wrong world. Record which script starts which configuration in your backup notes.

How do you start an Empyrion dedicated server?

Launch from the installed Empyrion - Dedicated Server directory after saving your YAML changes. There are two supplied command files:

• EmpyrionDedicated.cmd opens the rudimentary server GUI.
• EmpyrionDedicated_NoGraphics.cmd starts without graphics and is the better choice for a headless machine or a host you administer remotely.

1. Double-click the selected .cmd file.
2. Watch the console or GUI for startup messages and errors. Confirm that the expected world name and scenario are loaded.
3. Leave the process running while players connect. Do not close the console window as a way to “end” the server.
4. Before shutting down or logging off, enter saveandexit 0 in the server console and wait for the save-and-exit operation to finish.

Start automatically after Windows login

Create a shortcut to the chosen .cmd file and place it in %appdata%MicrosoftWindowsStart MenuProgramsStartup. Test the shortcut manually first. Automatic startup is useful for a household server, but it does not protect against a power outage, a Windows update that reboots the machine, or a router failure; use a restart plan and regular backups as well.

Which ports must you forward for an Empyrion server?

The documented default is port 30000, and the official setup guide instructs administrators to forward ports 30000–30004 using both UDP and TCP. Forward those ports from the router to the host computer’s stable private IP address, then allow the server executable through Windows Firewall.

Traffic	Ports	Destination	Why it matters
UDP	30000–30004	Host’s fixed local IPv4 address	Required game traffic and discovery behavior documented by the server guide.
TCP	30000–30004	Host’s fixed local IPv4 address	Forward alongside UDP; forwarding only one protocol can produce failed or inconsistent joins.

Set the local address and router rule

1. Give the Windows host a DHCP reservation in the router, or configure a static address using your network administrator’s preferred method.
2. In the router’s port-forwarding page, create rules for TCP 30000–30004 and UDP 30000–30004, both targeting that reserved address.
3. Save the router configuration and confirm the rules did not target an old address left by a previous DHCP lease.
4. In Windows Firewall, allow the Empyrion server executable or the server command file when Windows prompts. If you create manual inbound rules, include both TCP and UDP for the same port range.

Some internet providers use carrier-grade NAT (CGNAT), which gives the home router no directly reachable public IPv4 address. In that situation, correct local forwarding cannot make the server reachable from the internet; ask the provider for a public address or use a hosting arrangement that supplies one.

How do friends join and how should you test the server?

First test from the host’s local network if you want to verify that the process and save load correctly. Then test from a different network, such as a friend’s connection or a phone hotspot. A loopback or same-LAN connection proves only that the local process is running; it does not prove that the router, firewall, public address, or ISP path is configured correctly.

1. Start the server and wait until the expected world has loaded.
2. Confirm that Srv_Public is enabled if you expect a public listing.
3. Have a player outside the home network search for the server name or use the direct-join address and port supported by the current client.
4. Ask the tester to report whether the server appears, connects, and loads the intended world. Test with the same scenario and mods that the server uses.

If the server is visible but a player cannot finish loading, compare the client and server builds, scenario files, and mods before changing router settings. The server log can reveal a missing scenario file or another content mismatch.

What should you do when the server is not visible or loads the wrong world?

The server does not appear in the list

• Confirm the server process is still running and did not stop on a startup error.
• Check that public visibility is enabled when you intend to publish the listing.
• Verify the host’s private IP address and router destination; DHCP changes are a frequent cause of stale rules.
• Confirm that both UDP and TCP rules cover every port from 30000 through 30004.
• Allow the executable through Windows Firewall on the network profile in use.
• Test from outside the local network. If external testing fails while local testing works, investigate the public address and possible CGNAT rather than reinstalling the server.

A direct join reaches a loading screen

Check that client and server builds match and that every participant has the required scenario and mod content. Read the server log for missing scenario files. A port-forwarding fix will not correct an asset or version mismatch.

The world starts from scratch

Stop the server and inspect GameName and SaveDirectory in the active YAML file. They must point to the existing world and save location. If you changed the launcher, make sure it still includes the intended -dedicated file rather than silently using the default configuration.

Settings appear not to apply

Stop the process, edit the YAML file that the running script actually loads, and check indentation and exact property names. Restart and verify the startup output. Editing a spare copy while the launcher reads another file produces no visible change.

Progress is missing after shutdown

Use saveandexit 0 before stopping or logging off. If the machine lost power or Windows terminated the process, restore the latest verified save backup rather than repeatedly launching and overwriting the affected files.

How should you update and back up an Empyrion server?

Before updating through Steam or SteamCMD, copy the entire save directory, dedicated.yaml, custom scenarios, mods, and modified startup scripts. Label the backup with the date and server build if known. After updating, start the server privately, load the world, and verify that the scenario, mods, player inventories, and configuration still work before inviting everyone back.

Updates can introduce incompatibilities between a server build and scenario or mod files. Keep the previous files until the new build has been tested, and document which backup corresponds to which configuration. Never rely on a single copy stored on the same disk as the live world.

How many players can one Empyrion server support?

There is no reliable universal player-capacity number. Practical capacity changes with host hardware, active playfields, scenario complexity, installed mods, simulation load, and network conditions. Set Srv_MaxPlayers conservatively, observe memory and CPU use during a busy session, and increase the limit only after the server remains responsive.

The published 10 GB RAM minimum and 16 GB recommendation describe the game’s baseline requirements, not a guarantee that a machine with 16 GB can support a particular number of simultaneous players. A lightly used private world and a heavily modded public scenario can have very different resource needs.

Should you self-host or use managed Empyrion hosting?

Self-hosting gives you direct access to saves, configuration, scenarios, and mods, but you also own every maintenance task. Managed hosting can reduce operating work, although you trade some control and must evaluate the provider’s current plan, region, support, and backup policies.

Decision factor	Self-hosting at home	Managed hosting
Up-front cost	Uses an existing Windows PC, but electricity and replacement hardware remain your responsibility.	Requires a recurring service fee; current plans and availability vary.
Files and mods	Full access to YAML, saves, scenarios, and startup scripts.	Access depends on the provider’s control panel and policies.
Maintenance	You patch the server, resolve compatibility issues, and maintain Windows.	The provider may handle platform maintenance, but you still manage game content and configuration.
Uptime and network	Depends on home power, router, ISP upload, public addressing, and CGNAT.	Usually supplied from a data-center region, subject to the provider’s service terms.
Backups	You must create and verify your own copies.	Ask exactly whether backups exist, how often they run, and how restoration works.
Scalability	Limited by your PC, connection, and available playfield resources.	May offer larger plans, but performance claims and player limits require current verification.

Empyrion’s official dedicated-server page lists hosting providers. Treat provider names, prices, regions, and partner terms as changeable and verify them directly before purchasing. For a small group that already owns a suitable Windows machine, self-hosting maximizes control; for users who cannot maintain uptime or port forwarding, managed hosting may remove the most troublesome operational work.

What is the safest operating routine for a small server?

• Keep the server on a stable, preferably wired network and reserve its local IP.
• Use a strong Telnet password and expose administrative access only when necessary.
• Announce the scenario, mod list, password, restart schedule, and maintenance windows to players.
• Run saveandexit 0 before planned shutdowns.
• Back up saves and configuration before every update and after major world changes.
• Test an external join after router, firewall, ISP, or server-build changes.
• Keep at least one backup off the live disk so a drive failure does not remove both the world and its recovery copy.

Frequently Asked Questions

Can I run an Empyrion server without owning a second game copy?

The dedicated-server tool is distributed separately through Steam’s Tools library or SteamCMD App ID 530870. The tool download is free, while each player’s ability to join is governed by the game’s current licensing and account requirements.

Why can my friends join only when they are on my Wi-Fi?

That pattern usually means the server process works but internet reachability does not. Recheck the host’s reserved private IP, both TCP and UDP forwarding rules, Windows Firewall, the public address, and whether the ISP uses CGNAT.

Where are Empyrion dedicated-server saves stored?

The active location is controlled by the SaveDirectory value in the configuration, together with the world identified by GameName. Check those values in the YAML file loaded by your startup script instead of assuming a default folder.

How do I change a server from private to public?

Enable the public-server visibility setting, restart the server, and verify the listing from an external connection. Public visibility does not replace port forwarding or firewall rules, and a password can still restrict who joins.