For an Enshrouded dedicated server, plan on a 16 GB RAM host, an SSD with at least 30 GB free, and a modern multi-core CPU. Keen Games recommends about 3.2 GHz with 6 cores and 12 threads for four to six players, or about 3.7 GHz with 8 cores and 16 threads for a full 16-player server. Upload capacity is equally important: allow 2 Mbit/s per active player.
The server process itself is much smaller than the host recommendation. Keen reports approximately 4.4 GB of physical RAM at idle, up to 100 MB more per player, and a total process footprint below 6 GB. The remaining host memory covers Windows, updates, logs, saves, backups and other services.
What are the official Enshrouded dedicated-server requirements?
Keen Games publishes two target configurations. The smaller configuration is intended for a group of four to six players; the larger one is intended for all 16 supported players. Both use 16 GB of host RAM, an SSD with at least 30 GB free and an upload allowance of 2 Mbit/s for every active player.
| Concurrent players | Recommended CPU | Cores and threads | Host RAM | Free SSD space | Upload allowance |
|---|---|---|---|---|---|
| 4–6 | Intel Core i7-class or equivalent AMD, about 3.2 GHz | 6 cores / 12 threads | 16 GB | At least 30 GB | 2 Mbit/s per active player (8–12 Mbit/s for 4–6 players) |
| 16 | Intel Core i7-class or equivalent AMD, about 3.7 GHz | 8 cores / 16 threads | 16 GB | At least 30 GB | 2 Mbit/s per active player (32 Mbit/s for 16 players) |
The frequencies are approximate recommendations, not a guarantee that any processor with the same label will perform identically. Newer architectures, sustained boost behavior and other software on the machine can change the result. For a server that will regularly run at the player limit, use the 16-player CPU target rather than trying to extrapolate from the four-to-six-player specification.
How much RAM does an Enshrouded dedicated server use?
Keen Games’ FAQ states that the server process uses about 4.4 GB of physical RAM while idle. It can add up to 100 MB per player and should remain below 6 GB in total. Those figures describe the server process, not the amount of memory that should be installed in the computer.
What the 4.4 GB idle figure means
An idle process is running without a busy group actively exploring, building and loading areas. Player activity can raise usage, but Keen’s published guidance still places the process under 6 GB. A 16-player calculation using the stated maximum increment is roughly 4.4 GB plus as much as 1.6 GB, or about 6 GB; the FAQ’s “below 6 GB” wording should be treated as the operational ceiling rather than a promise that every session will hit exactly the same number.
Why the host should have 16 GB
A 16 GB machine leaves room for the operating system, security software, updates, monitoring, log files, save operations and temporary files. It also gives you a buffer when another service is running on the same computer. Installing only enough memory to cover the executable’s idle footprint can lead to paging and unpredictable pauses even when the server process itself is within Keen’s limit.
Memory demand is not the clearest reason to move from the four-to-six-player target to the 16-player target: both official configurations specify 16 GB of host RAM. CPU frequency, core count and network upload are the specifications that change most visibly with player count.
What CPU do I need for an Enshrouded server?
For four to six active players, Keen recommends an Intel Core i7-class processor or equivalent AMD CPU running at about 3.2 GHz, with six cores and 12 threads. For 16 players, the recommendation rises to about 3.7 GHz, with eight cores and 16 threads.
Clock speed versus core count
The two recommendations show that both sustained clock speed and parallel capacity matter. Clock speed helps the main game-server work complete quickly, while additional cores and threads provide room for world simulation, networking and background tasks. Do not select a processor solely because its product name contains “i7”; check its actual sustained frequency and physical/logical core configuration.
Choosing between the two targets
- Small private group: The 3.2 GHz, 6-core/12-thread target is the published fit for four to six players.
- Variable attendance: If the same world may grow beyond six players, buying toward the 3.7 GHz, 8-core/16-thread target avoids replacing the host later.
- Full 16-player sessions: Use the higher CPU target and verify that the processor can sustain its advertised frequency under continuous load.
Keen’s figures do not provide a supported minimum for a specific older CPU model, nor do they establish a frame-rate or tick-rate benchmark. Treat them as recommended server specifications rather than a pass/fail compatibility test for every processor.
How much SSD storage is required?
Keen says the uncompressed dedicated-server files occupy about 13 GB and recommends at least 30 GB of free disk space. The 30 GB figure provides installation headroom for updates and working files; it is not the same as the compressed download size.
How large are world saves?
A world save can range from about 1 MB to 100 MB, depending on the world. A heavily developed world can therefore add more storage than a fresh one, although even the published save range is modest compared with the installation. Keep additional room for rotating backups, crash dumps and update staging instead of treating 30 GB as a hard maximum.
Why an SSD is the sensible choice
The official guidance calls for free space on an SSD. Faster random access helps the server read world data and write saves without competing with the operating system. A mechanical drive may have enough capacity, but it does not match the published storage recommendation and can make loading or save operations more noticeable when the disk is busy.
How much upload bandwidth does each player need?
Keen recommends 2 Mbit/s of upload capacity per active player. Multiply that allowance by the number of people connected at the same time, not by the total number of members in your community.
| Active players | Calculated upload allowance |
|---|---|
| 4 | 8 Mbit/s |
| 6 | 12 Mbit/s |
| 16 | 32 Mbit/s |
These are capacity allowances, so leave practical headroom for other traffic, protocol overhead and upload fluctuations. If another person is streaming or a cloud backup is running on the same connection, the server may have less usable upload than the headline speed suggests. A wired connection and a router that can maintain stable upstream throughput are preferable for a persistent world.
What networking settings should I check?
The official FAQ identifies IPv4 and lists 15637 as the default queryPort. Confirm that your host has a usable IPv4 address and that your firewall and router configuration allow the server’s required traffic. The published material specifies the query port, but it does not establish a universal rule for every router, firewall product or hosting provider.
Pre-launch network checklist
- Confirm your internet plan’s upload rate against the active-player calculation.
- Use a stable IPv4 connection and avoid relying on a changing address without a way for players to find the server again.
- Check that the default
queryPort, 15637, is available, or document any deliberate change. - Make sure the operating-system firewall permits the dedicated-server application.
- Test joining from a different network before announcing the server to the group.
If local players can connect but people outside your home cannot, the likely fault is networking rather than RAM or CPU. Check the public address, router forwarding and firewall rules in that order, changing one setting at a time so you can identify the fix.
Can my gaming PC host the server and the game?
A 16 GB host is the official baseline for the dedicated server, while Steam lists 16 GB RAM and 60 GB storage for the game client and recommends an SSD. Those are separate requirements: the client’s 60 GB storage figure is not the dedicated-server requirement, and the server’s 30 GB free-space recommendation is not a substitute for the client installation.
Running both processes on one computer can consume the same memory and CPU headroom that the server needs. It may be workable for a small group on a machine with capacity beyond the baseline, but the published numbers do not guarantee smooth simultaneous play. A separate host avoids having a game crash, reboot or graphics workload interrupt the world.
Should I self-host or use managed hosting?
Self-hosting gives you direct control over the hardware, files, backups and update timing. It also makes you responsible for power, operating-system maintenance, network configuration and recovery when the host is offline.
Self-hosting is a good fit when
- You already have a machine that meets the 16 GB RAM, CPU and SSD targets.
- Your internet connection can provide the required upstream bandwidth continuously.
- You are comfortable managing IPv4 access, the firewall and the default query port.
- You want local control of saves and backup schedules.
Managed hosting is a good fit when
- Your home connection has limited upload capacity or carrier-grade NAT.
- You need a server that remains online while your gaming PC is off.
- You prefer a provider to handle operating-system maintenance, monitoring and network configuration.
- Your players are spread across regions and a data-center location can reduce distance for most of them.
When comparing hosted plans, verify the allocated CPU model or sustained performance, not just the advertised RAM. Also check where the machine is located, how backups are retained, whether the plan permits all 16 players, and what happens when you exceed included storage or bandwidth.
How should I size backups and free space?
Keep the official 30 GB free-space recommendation as a floor, then add capacity for your own retention policy. Because saves can be 1–100 MB, even a daily backup for several weeks is usually small compared with the installation, but multiple worlds and compressed archives accumulate over time.
A practical backup plan
- Stop or safely quiesce the server before copying a save so the backup is not taken during a write.
- Keep several recent local copies and at least one copy on a different physical device.
- Label backups with the world name and date so you can identify a known-good restore point.
- Check that a backup can actually be opened or restored before deleting older copies.
- Monitor free SSD space after updates; remove obsolete archives before the disk approaches capacity.
The 30 GB recommendation concerns free space for the server installation and operation. It does not promise that every future update, log history or backup collection will fit inside exactly 30 GB.
What are the most common sizing mistakes?
Confusing client and server storage
The Steam client listing’s 60 GB storage requirement applies to installing the game. Keen’s dedicated-server guidance says about 13 GB for uncompressed files and at least 30 GB free. Use the correct figure for the task you are planning.
Buying RAM without checking CPU and upload
Both official player tiers specify 16 GB of host RAM, so adding memory alone does not turn a low-clocked processor or weak upstream connection into a 16-player host. Check all three dimensions—CPU, RAM and upload—before upgrading.
Planning for maximum membership instead of simultaneous players
The bandwidth formula is per active player. A community of 16 people that normally has four online needs the four-player allowance during those sessions, while a full event needs the 16-player allowance even if the event is occasional.
Leaving no room for maintenance
Installing into a disk that has only the nominal file size free can block updates or backups. Keep more than the 30 GB floor whenever possible and monitor it as worlds and archives grow.
What should I buy or provision for each player target?
Use the following decision path rather than treating one specification as sufficient:
- Choose the highest number of simultaneous players you expect, including occasional events.
- Match the CPU tier: about 3.2 GHz with 6 cores/12 threads for four to six, or about 3.7 GHz with 8 cores/16 threads for 16.
- Install 16 GB of host RAM and reserve headroom for the operating system and maintenance.
- Use an SSD with at least 30 GB free at deployment, preferably more for backups and updates.
- Confirm upload capacity at 2 Mbit/s per active player and leave room for other household or server traffic.
- Verify IPv4 reachability and the default
queryPortvalue of 15637 before inviting players.
This approach scales the parts that Keen’s recommendations actually change: CPU capability and network upload. It avoids paying for a larger memory figure that the published server-process measurements do not require while still protecting the host from operating-system and maintenance overhead.
Frequently Asked Questions
Does Enshrouded support more than 16 dedicated-server players?
The published recommendations cover a maximum target of 16 players. They do not establish a supported configuration above that number, so treat 16 as the planning limit unless Keen publishes different guidance for your server version.
Will a larger world save require more server RAM?
Keen documents save files from about 1 MB to 100 MB, but the cited guidance does not provide a formula linking save-file size to live RAM usage. Use the published process figures for memory planning and reserve disk space for the larger saves.
Can I use Wi-Fi for a dedicated server?
The requirements specify upload capacity, not a particular access technology. Wi-Fi can work when it delivers stable upstream throughput, but a wired connection reduces the chance that interference or roaming will interrupt the server.
What happens if my upload speed is below 2 Mbit/s per player?
The server may still start, but the connection has less capacity than Keen’s allowance and can become unstable as players join or other traffic runs. Reduce simultaneous players, stop competing uploads or move the server to a connection with more upstream headroom.