Enshrouded blends base-building, survival, and action-RPG combat across a large voxel-based world, and its dedicated server released alongside Early Access rather than months later — a genuinely player-friendly choice compared to titles that launch multiplayer-only through informal peer hosting first. Because the world uses voxel terrain destruction and a dynamic "Shroud" fog mechanic that streams and unstreams large chunks of the map, server performance characteristics are a little different from a typical building-survival game, and it's worth understanding before you provision hardware.
This guide walks through downloading and configuring the dedicated server, the JSON-based config file (a change from the INI-style config most survival titles use), realistic hardware sizing given the voxel/Shroud streaming load, and the specific connection and desync issues that show up in real communities.
Because Enshrouded is still under active Early Access development, treat this as a living target rather than a "set it once and forget it" server — Keen Games has shipped meaningful server-side changes across major updates, and admins who keep an eye on patch notes avoid most of the update-related surprises that catch people off guard.
What Is an Enshrouded Dedicated Server?
It's the official standalone server binary (distributed via SteamCMD, Windows and Linux builds both available) that hosts a persistent Enshrouded world independent of any player's own client session. Compared to the in-game "invite friends" co-op hosting:
- Runs continuously without requiring the world's original host to stay logged in
- Supports the game's full multiplayer player cap more reliably under sustained play
- Uses a JSON configuration file (
enshrouded_server.json) rather than the INI format common to ARK/Palworld/Valheim - Persists voxel terrain modifications and base structures on server-side storage, independent of any single player's local save
System Requirements and Pricing
Enshrouded's voxel terrain and Shroud fog streaming push memory and disk I/O harder than a typical low-poly survival title, though it's lighter than full UE5 titles like ARK Ascended.
| Player Count | RAM | CPU | Storage | Typical Monthly Price |
|---|---|---|---|---|
| 1-4 (small group) | 6-8 GB | 2-4 vCPU / 3.8+ GHz | 20-30 GB NVMe | $14-$24 |
| 5-8 (active builders) | 10-12 GB | 4 vCPU / 4.0+ GHz | 35-50 GB NVMe | $28-$42 |
| 9-16 (community server) | 14-16 GB | 4-6 dedicated cores | 60-90 GB NVMe | $48-$70 |
Because terrain destruction and rebuilding is core to Enshrouded's gameplay loop (unlike games where the terrain is mostly static), disk write frequency is meaningfully higher than a typical survival title — NVMe storage is worth prioritizing here even at small player counts.
Why the Shroud Mechanic Affects Server Load
The Shroud is a dynamic fog layer that alters visibility, applies damage-over-time, and unlocks different resource nodes than the clear world outside it. Areas transitioning between shrouded and unshrouded state trigger additional streaming and state-sync work beyond normal terrain loading, and a full party crossing that boundary simultaneously creates a brief but real CPU spike. This is different from a typical survival title where terrain state is comparatively static once generated — Enshrouded's world genuinely changes state dynamically, and the server has to keep track of it continuously.
Step-by-Step Setup
1. Install via SteamCMD
steamcmd +force_install_dir ./enshrouded +login anonymous +app_update 2278520 validate +quit
1a. Choose Windows or Linux Build
Both official builds exist, but the Linux build is the more cost-effective choice for 24/7 hosting since it avoids Windows Server licensing overhead entirely. If your hosting provider offers both, default to Linux unless you have a specific reason (like a Windows-only management tool) to run the Windows build instead.
2. Configure enshrouded_server.json
Unlike the INI-style files most survival titles use, Enshrouded's server config is plain JSON. Key fields:
| Field | Recommended Value | Notes |
|---|---|---|
| name | your server name | Shown to players connecting via direct IP or friend invite |
| password | set for private servers | Leave empty only if you intend a fully open server |
| saveDirectory | ./savegame | Keep this on the fastest available disk given frequent voxel writes |
| logDirectory | ./logs | Useful for diagnosing crashes — don't disable logging to save disk space |
| ip / queryPort / gamePort | 0.0.0.0 / 15637 / 15636 | Default ports; change only if running multiple instances on one box |
| slotCount | match your RAM budget | Higher slot counts increase both RAM and voxel-streaming load per active player |
| enablePermissions | true | Turns on the granular per-player permission groups covered below |
| userGroups | see below | Defines named permission groups (e.g. Admin, Member, Guest) referenced by connecting players |
Since the file is JSON, a single misplaced comma or missing closing brace will prevent the server from starting at all — validate the file with a JSON linter after editing before restarting the service.
2a. Configuring Permission Groups
Enshrouded's userGroups section lets you define named groups with granular permissions — who can modify terrain, place/remove structures, manage the in-game clock, or kick other players. A typical setup defines an Admin group (all permissions, assigned to trusted server owners), a Member group (build and terrain permissions but no server management), and a Guest group (limited or read-only access) for players you're still vetting. Assign players to groups by their platform ID once they've connected at least once, since the field usually populates only after a player's first successful join.
3. Open Firewall Ports
Default ports are 15636 (game) and 15637 (query), both UDP. With UFW: sudo ufw allow 15636:15637/udp.
4. Run as a Persistent Service
As with any long-running dedicated server, wrap the launch in a systemd unit with automatic restart on failure, running under a dedicated non-root user with write access scoped only to the server's own directory.
5. Set Up Regular World Backups
Back up the entire savegame directory (not individual files) on a schedule — because voxel terrain state and structure data are tightly linked, partial or mismatched backups can leave a world in an inconsistent state on restore. Stop the server (or use any built-in save-and-pause command available in your build) before copying, then restart.
6. Manage Multiple Worlds/Instances (Optional)
If you want to run more than one Enshrouded world on the same box (e.g., a public server and a private testing world), give each instance its own working directory, its own gamePort/queryPort pair, and its own saveDirectory — reusing ports or save paths across instances will cause conflicts or, worse, cross-contaminated save data.
7. Keep Up With Early Access Updates
Since Enshrouded is still actively developed, subscribe to official patch notes and test major updates on a non-production copy of your save before applying them to the live community server where possible. Early Access titles occasionally introduce server-config changes (new JSON fields, renamed keys) that aren't always prominently flagged, and a quick pre-update read of the patch notes avoids a confusing "why did my config stop working" session.
8. Set Up Scheduled Restarts
Even though Enshrouded is generally more stable than some Early Access peers, a scheduled restart every 12-24 hours during low-traffic windows clears accumulated memory from long voxel-streaming sessions and gives you a natural checkpoint to verify backups completed successfully.
Common Issues and Troubleshooting
Server Fails to Start After Editing the Config
Check JSON syntax first — a missing comma or unmatched brace is the most common cause, and the server typically won't give a helpful error pointing at the exact line, so run the file through a linter before troubleshooting anything else.
Players Report Terrain "Popping" or Not Loading
This is usually a disk I/O bottleneck rather than a network issue — if you're on spinning disk or a slow shared SSD, voxel chunk streaming can't keep up with fast player movement. Moving to NVMe storage resolves this in almost every reported case.
Connection Drops During Shroud Area Transitions
The Shroud's dynamic fog and altered physics rules trigger a heavier state sync when players cross the boundary. If this causes drops under load, check CPU headroom first — this is a CPU-bound spike, not primarily a bandwidth issue.
Save File Grows Very Large Over Time
Extensive terrain modification (mining, building) naturally grows the save file. Budget more storage than you think you'll need if your community is base-building heavily, and keep an eye on available disk space so you don't run out mid-session.
Server Not Visible via Direct Connect
Confirm both the game port and query port are open — some admins open only the game port and then wonder why the server browser or direct-connect query fails even though gameplay traffic would otherwise work.
Permissions Not Applying to a Player
Check that enablePermissions is actually set to true and that the player's ID is correctly listed under the intended group in userGroups — a player who hasn't connected at least once may not yet have a populated ID field to assign a group to.
Server Update Breaks Existing Config
Since Enshrouded is Early Access, a major update occasionally adds or renames JSON fields. If the server fails to start after an update with no clear error, compare your enshrouded_server.json against a freshly-generated default file from the new version to spot missing or renamed keys.
High CPU Usage With Few Players Online
Check for an unusually large or fragmented voxel terrain area from extensive mining/building — a heavily modified landscape can add ongoing simulation cost even with a small active playerbase, similar to how a sprawling base affects other titles in this genre.
Troubleshooting Reference Table
| Symptom | Likely Cause | Fix |
|---|---|---|
| Server won't start, no clear error | Invalid JSON syntax | Validate enshrouded_server.json with a linter before further troubleshooting |
| Terrain streaming stutters for all players | Slow disk I/O | Move to NVMe storage — this resolves the vast majority of reported cases |
| Server not listed for direct connect | Query port (15637) not open | Open both 15636 and 15637 UDP explicitly |
| Save directory grows unexpectedly fast | Heavy terrain modification by an active community | Budget storage growth proactively rather than reactively |
| Config changes ignored after restart | Editing a copy instead of the active config path | Confirm the server is reading from the file path you're actually editing |
Common Mistakes to Avoid
The most common mistake is running Enshrouded on budget spinning-disk or slow shared-SSD storage, which shows up almost immediately as terrain pop-in and stutter regardless of how much CPU or RAM headroom the plan otherwise offers — this title is unusually disk-sensitive compared to most in this guide. A second mistake is skipping JSON validation after manual edits and then spending time debugging a "server won't start" issue that was really just a missing comma. A third is neglecting to track Early Access patch notes, which occasionally leads to a config file silently falling out of sync with a new server build's expected format.
Buyer's Checklist
- Prioritize NVMe storage specifically for this title given its voxel/terrain write-heavy design
- Confirm the host allows editing enshrouded_server.json directly via SSH/SFTP rather than only through a limited web panel
- Check both game and query UDP ports are configurable and open by default
- Ask whether the host provides automated backups of the full save directory, or plan your own cron job
- Since Enshrouded is a newer, actively-updated title, confirm the host keeps the server binary easy to update without breaking your custom config
- Verify sufficient RAM headroom for your target slot count, not just the game's stated minimum
- Confirm the host lets you run the Linux build if you want to avoid Windows Server licensing overhead
- Ask whether the provider proactively updates alongside Early Access patches or requires you to trigger updates manually
Performance Tuning Walkthrough
Enshrouded's performance profile is unusual enough that generic survival-server tuning advice often points admins at the wrong dial. Work through these steps in order to find your actual bottleneck.
Step 1: Benchmark Disk Latency First
Because voxel streaming is this title's signature load, verify your storage before touching any game setting: a quick disk benchmark on the server (or simply watching I/O wait in htop while a player sprints across unexplored terrain) tells you whether chunk streaming is keeping up. If I/O wait spikes track player movement, no amount of CPU or RAM tuning will fix the pop-in — the storage tier is the problem.
Step 2: Right-Size slotCount to Real Concurrency
A slotCount set far above your actual peak concurrency doesn't just waste RAM headroom on paper — it shapes how much the server pre-allocates for player state. Set it to your realistic peak plus two or three guest slots, not the theoretical maximum, and raise it later if the community genuinely grows.
Step 3: Watch CPU During Shroud Transitions
If complaints cluster around groups entering or leaving the Shroud together, log CPU during those moments specifically. A brief spike is normal; a sustained plateau afterward suggests the box is under-provisioned for your group's size, and this is the specific scenario where moving from shared vCPUs to dedicated cores shows the clearest improvement.
Step 4: Track Save Directory Growth Weekly
Note the savegame directory's size once a week. Steady growth is expected with active building, but the trend line tells you months in advance when storage will become a problem — and a disk that fills mid-session is one of the few failure modes that can genuinely corrupt an otherwise healthy world.
How Enshrouded Compares to Its Genre Peers for Hosting
If you're choosing between building-survival titles partly on hosting characteristics, Enshrouded's profile sits in a distinctive spot.
| Factor | Enshrouded | Valheim | ARK: Survival Ascended |
|---|---|---|---|
| Config format | JSON | Launch flags | INI files |
| Biggest bottleneck | Disk I/O (voxel streaming) | Single-core CPU | RAM |
| Realistic RAM for ~8 players | 10-12 GB | 6-8 GB | 16-24 GB |
| Permission system | Granular userGroups built in | Admin list only | Admin password + RCON |
| Failure mode when undersized | Terrain pop-in, stutter | Localized base lag | Out-of-memory crash |
The takeaway: Enshrouded is the one title in this comparison where paying for better storage beats paying for more CPU or RAM at the margin. Its built-in permission groups are also genuinely ahead of its peers, which matters for communities that would otherwise need mods or third-party tools to manage trust tiers.
Real-World Scenario: An Eight-Player Building Community
Picture a typical Enshrouded community server: eight regulars, heavy builders, live for three months. It launched on a 4 vCPU / 12 GB NVMe plan with slotCount at 10, an Admin group of two, and everyone else in a Member group with terrain and building rights but no server management. The savegame directory started at a few hundred megabytes and tripled within two months as the group carved elaborate bases into hillsides — growth the admin caught early by checking weekly, upgrading storage before it became urgent. The only real incident came after a major Early Access patch, when the server refused to start: comparing the old enshrouded_server.json against a freshly generated default revealed a renamed field, fixed in five minutes because the admin knew to look there first. That's a representative Enshrouded hosting story — the challenges are disk growth and Early Access churn, not crashes or player-count scaling.
Frequently Asked Questions
How many players can an Enshrouded dedicated server support?
Community servers commonly run in the 8-16 player range comfortably with adequate hardware; larger counts are possible but push RAM and disk I/O demands up significantly given the voxel terrain system.
Why is my Enshrouded server config in JSON instead of INI?
That's simply the format the developers chose for enshrouded_server.json — unlike ARK, Valheim, or Palworld, which use INI-style configs, Enshrouded's server settings are structured JSON, so syntax errors behave differently (a broken JSON file usually prevents startup entirely rather than just ignoring one bad line).
Does Enshrouded support cross-platform play with consoles?
Console availability and crossplay support have expanded since Early Access launch — check the current release notes for your target platforms before assuming full crossplay parity with PC dedicated servers.
How often should I back up an Enshrouded world?
Daily at minimum for an active community, with the backup taken right after a clean stop or built-in save trigger rather than while the server is actively writing voxel data.
Can I run multiple Enshrouded worlds on one dedicated server?
Yes, as long as each instance has its own ports and save directory — just make sure your hardware (RAM and disk I/O especially) can handle multiple concurrent worlds without both suffering.
How do permission groups differ from a simple admin password?
A single admin password is all-or-nothing; Enshrouded's userGroups system lets you grant partial permissions (like terrain building without server management rights) to different trust tiers, which is more useful for a growing community than a single shared admin credential.
Will my server config keep working across Early Access updates?
Usually, but not guaranteed — always compare your config against a freshly generated default after a major update to catch new or renamed fields before they cause a silent misconfiguration.
Is NVMe storage really necessary for a small 4-player server?
It matters more here than in most genre peers even at small scale, since voxel terrain streaming is disk-intensive regardless of player count — a small server on slow storage will still show terrain pop-in that the same server on NVMe wouldn't.
Does Enshrouded support a REST API or remote admin tools like some competitors?
Not natively at the level of Palworld's built-in REST API or Satisfactory's web-based Server Manager — most administration happens through the JSON config and in-game permission groups, so factor that into your expectations if you're coming from a title with a more built-out remote-admin toolset.
Enshrouded's voxel-based world makes disk performance matter more than in most survival titles, and getting NVMe storage and a clean JSON config right up front avoids the majority of stability complaints. WebsNP's VPS hosting and Linux dedicated server plans both include NVMe storage as standard — contact our team to size a plan for your expected player count. If you're comparing base-building survival titles, see our Valheim dedicated server guide and our Satisfactory dedicated server guide for factory-building alternatives.