Enshrouded server requirements and RAM
Compare Keen's Enshrouded dedicated-server specifications with process RAM and player-slot limits, including what 1.0 changed. Choose a plan with headroom and monitor real world usage before relying on a slot count.
Keen recommends 16 GB RAM for a self-hosted machine. Its older server FAQ reports about 4.4 GB for the idle game process. Those numbers describe different things.
Official machine specifications
Keen's recommended specifications were published in January 2024:
| Resource | 4–6 active players | 16 active players |
|---|---|---|
| CPU example | i7 3.2 GHz or AMD equivalent; 6 cores / 12 threads | i7 3.7 GHz or AMD equivalent; 8 cores / 16 threads |
| Machine RAM | 16 GB | 16 GB |
| Storage | SSD, at least 30 GB free | SSD, at least 30 GB free |
| Upload | 2 Mbit/s per player | 2 Mbit/s per player |
These are host-machine recommendations, not a per-container allocation table or fresh benchmarks for Enshrouded 1.0.
Process RAM and hosting plans
Keen's February 2025 FAQ reports around 4.4 GB idle and up to 100 MB extra per player. Leave headroom rather than sizing exactly to an idle reading.
| Plan choice | What to check |
|---|---|
| 8 slots | Actual allocated RAM and a busy-session test |
| 12 slots | RAM with the expected group and an established world |
| 16 slots | CPU, peak RAM, and players exploring simultaneously |
A 4 GB allocation is below Keen's published idle figure. Do not assume that fewer player slots makes it sufficient. Check current allocations on Enshrouded hosting and ask support about sizing before buying.
What 1.0 changed
Keen's 1.0 changelog says 1.0 reduced the memory needed for server and client communication, and made several performance improvements. It also reworked the server performance warnings, which previously triggered too soon, and made gliding depend less on the server's tick rate.
Keen hasn't published new RAM figures for the 1.0 server, and the numbers above were measured on Early Access builds. The 1.0 map is also larger, with Cinder's Cradle and wider biome edges. Until new measurements are out, size from your own world using the steps below rather than from the older idle figure.
Check your actual world
Start the server, join with the expected group, and watch memory during exploration and visits to large bases. Check Console for crashes or out-of-memory messages. Keep enough disk space for updates and backups.
If usage stays near the allocation, reduce the load or change plans. Send support the player count, world size, build, and memory readings. Recheck sizing after major updates.
Frequently asked questions
How much RAM does an Enshrouded server need?
Keen's hardware recommendation is 16 GB for the host machine. Its older FAQ reports about 4.4 GB physical RAM for the idle server process, plus up to 100 MB per player. Those figures predate 1.0, which Keen says reduced the memory used for server and client communication. Keen hasn't published new 1.0 figures.
Are player slots the same as RAM capacity?
No. Slots cap simultaneous joins. The world, active players, and runtime still need enough CPU and memory. Check the plan's actual RAM allocation and monitor it during busy sessions.