For a small private Empyrion server, start with about 8GB of RAM, 2–4 CPU cores and 35GB of SSD space. A community server for up to roughly ten players is better served by 12GB of RAM, four cores and 40GB of storage. Larger groups or heavily modded scenarios should begin around 16GB RAM, 4–6 cores and 50GB, while large Workshop scenarios such as Reforged Eden may need 24GB or more, six or more cores and at least 60GB of storage.
Those figures are practical sizing guidance, not an Eleon-certified minimum. Steam’s current listing describes the game client: 10GB RAM, a dual-core 2.5GHz processor and 10GB of storage minimum; 16GB RAM, a quad-core 3GHz processor and 15GB storage recommended. Empyrion’s official FAQ still says, “Dedicated server requirements will follow.” Treat the Steam numbers as a baseline, then size the server for active playfields, scenarios, Workshop content, saves and backups.
What are the official Empyrion dedicated-server requirements?
There is no published official hardware specification for the dedicated server that can be treated as a hard minimum. Valve’s 2026 Steam listing provides client requirements, while Empyrion’s official FAQ explicitly states that dedicated-server requirements will follow. That distinction matters: a machine capable of launching the game client is not automatically sized for a persistent world serving several players and multiple playfields.
The most defensible approach is to use the Steam figures as a lower reference point and choose a server tier based on your expected workload. The table separates the published client figures from practical server planning guidance.
| Use case | RAM | CPU | Storage | Evidence and qualification |
|---|---|---|---|---|
| Steam client minimum | 10GB | Dual-core 2.5GHz | 10GB | Valve/Steam listing, current in 2026; client requirement, not a server guarantee |
| Steam client recommended | 16GB | Quad-core 3GHz | 15GB | Valve/Steam listing, current in 2026; client recommendation, not a server guarantee |
| Small private server | About 8GB | 2–4 cores | About 35GB SSD | Practical hosting guidance from HyperDC; not Eleon-certified |
| Community of up to roughly ten players | About 12GB | 4 cores | About 40GB | Practical hosting guidance from HyperDC; not Eleon-certified |
| Larger server | About 16GB | 4–6 cores | About 50GB | Practical hosting guidance from HyperDC; not Eleon-certified |
| Large Workshop scenario, such as Reforged Eden | 24GB or more | 6 or more cores | 60GB or more | Practical starting point from HyperDC; actual demand depends on the scenario and active playfields |
A separate community operations guide describes a deliberately generous Windows Server installation with 256GB of RAM, many cores and a 1TB disk. That is an operations example for substantial headroom, not a minimum requirement for Empyrion.
How much RAM does an Empyrion server need?
Plan around 8GB for a small private world, 12GB for a group of up to about ten players, 16GB for a larger community and 24GB or more for large Workshop scenarios. Keep extra capacity available for saves, scenario files, logs, backups and the operating system instead of allocating every gigabyte to the game process.
Why the player count is not the only factor
Empyrion does not load one uniform world process for every situation. HyperDC states that every planet or sector on which players are present runs as its own playfield server process. Several players spread across different planets can therefore create more simultaneous processes than the same number of players gathered on one playfield.
Reserve playfields, scenario size, Workshop additions and very large faction builds also affect memory pressure. A ten-player server running a lightweight scenario may be comfortable at a lower tier than a ten-player server with many active planets and extensive custom content.
Can you run a server with 8GB?
Yes, 8GB is a reasonable starting point for a small private crew when the scenario and active-playfield count are modest. It is not an official minimum, and it leaves less room for large Workshop content, multiple active planets, backups or other services on the same machine.
If memory use approaches the system limit, the practical symptoms are slow world saves, delayed loading, operating-system swapping and eventual process failure. Move to the next RAM tier before adding more players or enabling a demanding scenario; reducing simultaneous playfields and unnecessary background services can also lower pressure.
What CPU do I need for an Empyrion dedicated server?
Use at least 2–4 modern CPU cores for a small server, four cores for a community of up to roughly ten players and 4–6 cores for a larger server. Large scenarios should start at six or more cores. Per-core speed matters as well as core count, so a newer, faster processor can be preferable to an older CPU with more nominal cores.
Why cores and per-core speed both matter
Each active playfield contributes server work. If players occupy several planets or sectors at once, the host must keep more playfield processes running even when the headline player count has not changed. Scenario scripts, Workshop systems and large structures can add work to those processes.
Do not select a CPU by player count alone. Compare the expected number of simultaneously active playfields, the scenario or mod load, the size of faction bases and the other services sharing the machine. A four-core system may be adequate for a compact private world but leave little headroom for a broad, modded community.
What CPU specifications should you check?
- Physical or allocated cores: use the 2–4, 4, 4–6 and 6-plus core guidance as starting points for the corresponding server sizes.
- Per-core performance: favor a current-generation processor with strong single-thread performance when two otherwise similar options are available.
- Dedicated capacity: on a virtual server, confirm how many vCPUs are actually reserved and whether the provider oversubscribes them.
- Headroom: leave capacity for the operating system, monitoring, backups and file compression rather than running at sustained 100-percent utilization.
How much storage does an Empyrion server use?
Reserve about 35GB for a small private server, 40GB for a community of up to roughly ten players, 50GB for a larger server and at least 60GB for a large Workshop scenario. These are practical starting points, not the size of the game files alone.
What occupies the disk?
- Dedicated-server binaries and updates.
- World saves and automatic or manual save generations.
- Scenario and Workshop files, including large custom content.
- Logs and diagnostic files that accumulate during long-running operation.
- Backups, which can consume several copies of a growing world.
Keep free space beyond the stated tier. A server can fail to save or update when the volume is full even though the initial installation fit comfortably. A large operations setup described by a community guide uses a 1TB disk, but that is generous room for administration and backups, not a requirement for every server.
Do you need an SSD?
An SSD is highly recommended by the Steam listing and is the sensible choice for a dedicated server. It reduces file and save-operation latency compared with a mechanical disk and gives the operating system more responsive access to logs and scenario files. NVMe can provide additional throughput, but the essential decision is to use solid-state storage and maintain backup space; a 1TB drive is useful headroom, not a universal requirement.
What are the Empyrion requirements for Reforged Eden and other large scenarios?
Start large Workshop scenarios such as Reforged Eden at 24GB or more of RAM, six or more CPU cores and at least 60GB of SSD space. This is a practical starting point from hosting guidance, not an official scenario-specific certification.
Scenario size alone does not determine the final load. Count the playfields that are active at the same time, account for reserve playfields and consider how many custom systems and structures the scenario adds. Monitor memory and CPU usage during a peak session, then increase the tier if the server begins swapping, saving slowly or missing its simulation target.
How do playfields change server sizing?
Empyrion’s playfield model makes simultaneous planets and sectors a primary sizing axis. HyperDC describes each planet or sector with players on it as its own playfield server process. A server with the same number of connected players can therefore require different resources depending on whether those players share one world or spread across several.
Use this planning checklist
- Estimate the maximum concurrent players, not only the community’s membership.
- Estimate the maximum number of planets and sectors likely to be occupied simultaneously.
- List the scenario, Workshop packages and scripted systems that will be loaded.
- Allow for reserve playfields that can remain active or load quickly.
- Consider the size and activity of major faction bases and vehicles.
- Leave RAM, CPU and disk headroom for saves, logs and backups.
When comparing two hosts or machines, ask for RAM, allocated cores, per-core speed, SSD capacity, active-playfield limits, scenario support and backup policy—not just a player-slot number.
How do you install the Empyrion dedicated server?
The dedicated-server software is distributed through Steam’s Tools library or through SteamCMD using app ID 530870. The documented Windows launch files are EmpyrionDedicated.cmd for a graphical launch and EmpyrionDedicated_NoGraphics.cmd for headless operation.
- Install Steam or SteamCMD on the machine that will host the world.
- Use Steam’s Tools library, or SteamCMD with app ID
530870, to download the dedicated-server files. - Configure the server and scenario files for your world and confirm that the save location has the reserved SSD space.
- Launch
EmpyrionDedicated.cmdwhen you need the graphical management interface, orEmpyrionDedicated_NoGraphics.cmdfor a headless server. - Test a local connection before opening the server to the internet, then verify that saves, logs and backups are being written.
File names and settings can change with game updates, so use the current Eleon setup guide linked from the developer-pinned Steam discussion when a setting in your installation differs.
Which ports and firewall settings does Empyrion use?
The commonly documented setup uses ports 30000–30004 over both TCP and UDP. Open the required range in the host firewall and forward the same ports from the router to the server’s local address when hosting behind a home gateway.
Exact router labels and firewall procedures vary by operating system, router model and hosting provider. Give the server a stable local address, allow both protocols, and test from a connection outside your home network. If local players can connect but outside players cannot, check port forwarding, the host firewall and whether the internet connection uses carrier-grade NAT.
Should you self-host or rent an Empyrion server?
Self-hosting gives you direct control over files, updates and configuration, while managed hosting trades some control for simpler networking, backups and hardware maintenance. Empyrion’s official dedicated-server page says its official servers are powered by Nitrado and lists Nitrado, GTXGaming, Fox Gaming, Gamerzhost, Pingperfect, BlackBox, Bluefang, LowPing, PlugPayPlay, RoxServers, Citadel and Host Havoc. Provider plans and terms change, so verify current specifications before committing.
| Decision factor | Self-hosting | Managed hosting |
|---|---|---|
| Control | Full access to files, launch options, scenarios and update timing | Control depends on the provider’s panel and policies |
| Backups | You must design, schedule and test them | May be included, but retention and restore limits must be checked |
| Networking | You handle router forwarding, firewall rules and public reachability | Provider supplies the public network endpoint |
| Hardware upgrades | You buy or resize hardware and storage | You can usually change a plan, subject to availability and fees |
| Scenario support | Install and troubleshoot Workshop content yourself | Panel tools may simplify installation, but compatibility still needs checking |
| Cost model | Uses your existing hardware and electricity, with higher administration effort | Recurring rental cost in exchange for operations and infrastructure |
Self-host when you already have suitable hardware, understand port forwarding and want complete control. Rent when reliable public access, off-site backups or low administration effort matter more than owning the machine.
What should you monitor after launch?
Measure the server during the busiest expected session rather than judging it immediately after installation. Watch system RAM, swap use, CPU utilization, disk space, save duration and the number of active playfields.
- RAM repeatedly near capacity: move to the next memory tier, reduce active playfields or remove unnecessary background services.
- CPU saturated while RAM is available: reduce simultaneous playfields or large scripted content, then move to a faster or higher-core CPU.
- Slow saves or loading: verify that the server is on SSD storage and that the volume has ample free space.
- Players cannot connect externally: check TCP and UDP forwarding for 30000–30004, firewall rules and the server’s local address.
- Updates or backups fail: inspect free disk space and confirm that the backup destination is separate from the live save when possible.
What is the practical Empyrion server specification to buy?
For a private crew, choose 8GB RAM, 2–4 modern cores and a 35GB SSD allocation as the floor for a modest scenario. For a community approaching ten players, choose 12GB, four cores and 40GB. If you expect a larger group, several active playfields or substantial Workshop content, start at 16GB, 4–6 cores and 50GB; for Reforged Eden or similarly large scenarios, begin at 24GB or more, six or more cores and 60GB or more.
In every case, reserve additional disk space for saves and backups, use SSD storage, and size for simultaneous playfields rather than the player-slot label alone. These tiers are practical planning targets because no independently published benchmark or official dedicated-server minimum is currently available.
Frequently Asked Questions
Are Empyrion’s Steam requirements enough for a dedicated server?
No. The 10GB/16GB RAM figures and processor specifications on Steam describe the client. Empyrion’s official FAQ has not published a dedicated-server minimum, so a server must be sized for its world workload.
How many players can an 8GB Empyrion server host?
There is no independently published player limit for an 8GB configuration. It is intended as a starting point for a small private crew, and the practical limit changes with active playfields, scenario content and other services on the machine.
Can I run the server and play Empyrion on the same computer?
It may be possible on a powerful system, but the client and server then compete for RAM, CPU time and disk access. Leave headroom beyond the server tier and monitor usage during a busy session before inviting more players.
Why does a server lag when only a few people are online?
Players may be distributed across several planets or sectors, each running its own playfield process. Large Workshop scenarios, reserve playfields and complex faction builds can also create load that a simple player count does not reveal.
Do I need to open both TCP and UDP ports?
The commonly documented Empyrion setup uses ports 30000–30004 on both protocols. Open and forward the range required by your installation, then test from outside the local network because router and firewall behavior differs by setup.