An Enshrouded dedicated server is the difference between playing on someone else’s rented world and owning the whole map. Keen Games’ voxel survival RPG has grown from 1 million players in its first days of Early Access to more than 5 million by January 2026, and a huge share of that community plays on self-hosted servers rather than peer-to-peer co-op. Running your own box means the world stays online while you sleep, you control who joins, and you decide exactly what data leaves your network.
This tutorial walks through a complete Enshrouded server build in 12 numbered steps: installing SteamCMD, downloading the dedicated server tool, configuring enshrouded_server.json, opening the correct ports, connecting from the game client, and – because this is a security publication – locking the whole thing down with a non-root service account, a firewall, and an automated backup routine. The core install takes about 30 minutes on a fresh Linux or Windows box.
Every fact below was checked against the Steam store listing, Keen Games’ public announcements, and multiple independent hosting guides in mid-2026. Enshrouded is still in Early Access as you read this, with a confirmed 1.0 launch on October 15, 2026 – so this guide also flags exactly what is likely to change once the game leaves Early Access, instead of pretending the ground is more settled than it is.
What Is Enshrouded, and Why Run a Dedicated Server?
Enshrouded is an open-world survival action RPG developed and published by Keen Games, a German studio, using its own Vulkan-based voxel engine. It launched into Steam Early Access on January 24, 2024, and combines base building, crafting, and exploration with cooperative combat against enemies that grow more dangerous inside a spreading toxic mist called the Shroud. The game reached 1 million players within its first few days on sale, passed 3 million by August 2024, and Keen Games announced it had surpassed 5 million players in January 2026, timed to the game’s second anniversary – a trajectory detailed on the game’s Wikipedia entry and confirmed on its official Steam store page, where it currently holds a “Very Positive” rating across nearly 48,000 reviews.
Every purchase of Enshrouded already includes a free, official dedicated server tool on Steam – you are not paying twice or relying on an unofficial fork. Hosting it yourself, instead of playing on a public community server or paying for a managed slot, gives you three concrete advantages. First, control: you decide who can join, which admin commands exist, and when the world resets. Second, uptime: an always-on Enshrouded dedicated server keeps your base building and Shroud progress persistent even when every player is offline, unlike the game’s built-in “host from the client” co-op mode. Third, data ownership – a real concern on a security site, since a public server logs every connecting player’s IP address and Steam ID, information that deserves the same handling discipline you’d apply to any other service you run.
The trade-off is that Enshrouded’s official server binary is Windows-only, which surprises a lot of players coming from Linux-friendly titles like Valheim or Project Zomboid. This guide covers the native Windows path, the Linux-via-Docker path, and exactly where each one breaks.
Enshrouded Dedicated Server at a Glance
| Detail | Value |
|---|---|
| Developer / Publisher | Keen Games GmbH (Germany) |
| Early Access release | January 24, 2024 |
| Full 1.0 release | October 15, 2026 (PC, PS5, PS5 Pro); Xbox Series X/S early 2027 |
| Current price | $29.99 / €29.99 |
| Players / copies sold | 5 million+ (announced January 2026) |
| Steam review score | Very Positive – 86% of 47,992 reviews |
| Dedicated server SteamCMD app ID | 2278520 |
| Default ports | 15636 (game), 15637 (query) – UDP |
| Max players per server | 16 (slotCount) |
| Config format | JSON – enshrouded_server.json |
| Official Linux server binary | None – Windows-only; Linux via Wine/Proton or Docker |
| Latest Early Access patch | “Forging the Path,” April 21, 2026 (v0.9.1.0) |
Enshrouded’s Road From Early Access to a Confirmed 1.0
It’s worth understanding the timeline before you invest time in a server, because Enshrouded is mid-transition. The game spent more than two years in Early Access, shipping eight major content updates that progressively added new biomes, building systems, and endgame content. The eighth and final one, “Forging the Path” (game version 0.9.1.0), landed on April 21, 2026, and – notably – added no new map area at all. Instead it focused entirely on stability, UI, and balance passes, which independent coverage at outlets like Game Informer read as Keen Games deliberately clearing the decks for a 1.0 release rather than continuing to expand scope.
That reading was confirmed in January 2026, when Keen Games marked the game’s second anniversary by announcing both the 5-million-player milestone and a firm 1.0 release window of autumn 2026 – later locked to the specific date of October 15, 2026, alongside the game’s first console launch on PlayStation 5 and PS5 Pro. An Xbox Series X/S version is planned to follow in early 2027. For a title that started as a PC-only Early Access experiment, reaching a simultaneous PC/PlayStation 1.0 within three years is a fast trajectory, and it’s the single biggest reason to build your dedicated server knowledge now rather than waiting – the self-hosting community around Enshrouded is about to get significantly larger.
Prerequisites and System Requirements
Keen Games has not published a single official minimum-spec sheet for the dedicated server binary the way some studios do. The table below combines player-count benchmarks published by three independent hosting guides – RedSwitches, IONOS, and XGamingServer – using the more conservative figure at each tier so you don’t under-provision. Treat it as a planning guide, not a hard official minimum.
Hardware Requirements by Player Count
| Players | CPU | RAM | Storage |
|---|---|---|---|
| 1–4 | 4 cores, strong single-thread clock | 8–16 GB | 30 GB SSD |
| 5–8 | 6–8 cores | 16 GB | 30 GB SSD |
| 9–12 | 8 cores / 16 threads | 16–24 GB | 30 GB SSD |
| 13–16 (full lobby) | 8+ cores / 16 threads, 3.7 GHz+ | 16–24 GB | 30 GB+ SSD |
Bandwidth planning is simpler: budget roughly 2 Mbps of upload per connected player, so a full 16-slot server wants at least 30–40 Mbps of sustained upload. For comparison, the official Steam system requirements for the client (not the server) call for 16 GB RAM and a GTX 1060-class GPU – but your dedicated server never renders a frame, so it does not need a GPU at all.
Software and Accounts You Need First
- A legitimate copy of Enshrouded on Steam to test connections as a client. The host machine itself does not need the full game installed.
- A Steam account – unlike some survival titles, the Enshrouded dedicated server tool downloads with anonymous SteamCMD login, so you do not need to own the game on the hosting account.
- A Windows 10/11 host for the native path, or a Linux host with Docker for the containerized path covered in Step 11.
- Basic command-line comfort. If you can run
sudo apt updateor open PowerShell, you can finish this guide. steamcmd, and on Linux,dockeranddocker compose– both installed below.
Self-Hosted vs Managed Enshrouded Server Hosting
Because the dedicated server tool is free on Steam, the only real cost of self-hosting is the machine itself – and you likely already have a spare PC, home server, or cheap VPS that can run it. Here’s how that compares to renting a slot from a managed Enshrouded server hosting provider.
| Factor | Self-hosted (this guide) | Managed hosting provider |
|---|---|---|
| Software cost | Free (included with the game) | Free tool, but you pay for the slot |
| Typical monthly cost | $5–$20 VPS, or $0 on hardware you own | $10–$35 for an 8–16 slot package |
| Root / OS access | Full | Usually a control panel only |
| Patch and update timing | You control it | Often automatic, sometimes delayed |
| Security hardening | Your responsibility (covered in Step 12) | Partially handled by the provider |
| Data ownership | Complete – logs and saves never leave your infrastructure | Shared with the host |
| Best for | Long-term worlds, technical hosts, privacy-conscious groups | Short-term groups who want zero setup |
This guide takes the self-hosted route because it teaches you the full stack and keeps your players’ connection data under your own roof. The same provision-configure-harden rhythm carries over directly from our other gaming server tutorials – if you’ve already set up Palworld or Project Zomboid, most of Steps 1–4 below will feel familiar.
There’s also a data-handling angle worth flagging before you publish a server address anywhere. A managed host’s control panel typically logs connecting IP addresses on infrastructure you don’t control and can’t fully audit. A self-hosted box puts those same logs – which, for players in the EU, fall under the GDPR’s definition of personal data – entirely inside a system you own. If you plan to run a public or semi-public Enshrouded server for an EU audience, that’s a meaningful reason to prefer self-hosting over a third-party panel you can’t inspect.
Step 1 – Choose Windows, Linux, or Docker as Your Host
Before installing anything, pick a path, because it changes every command that follows. Keen Games ships only a Windows binary (enshrouded_server.exe) – there is no officially supported Linux executable. You have three legitimate options:
- Native Windows. The simplest, most predictable path. Best if you’re repurposing a spare Windows PC or a Windows VPS.
- Linux with Wine/Proton. Runs the Windows binary directly on a Linux host without containers. Workable, but dependency management is fiddly and this guide does not recommend it as a first attempt.
- Linux with Docker (recommended for Linux hosts). A community-maintained Docker image wraps Wine internally, so you get Linux’s process isolation, easy backups via volume mounts, and a one-line upgrade path. Step 11 covers this in full.
Steps 2–9 below assume a Windows or Linux-with-Wine host running the binary directly, since that’s the path Keen Games documents. If you already know you want Docker, install Docker and Docker Compose now and skip to Step 11 after reading Step 6 for the config file reference.
Which path is “correct” depends entirely on what you’re already running. If you have a spare Windows gaming PC sitting idle, native Windows gets you online fastest with the least troubleshooting surface, since it’s the exact environment Keen Games builds and tests against. If your only spare hardware is a Linux home server, NAS, or a cheap Linux VPS – which is most of this site’s audience – Docker is worth the extra 15 minutes of setup in Step 11, because it isolates the Wine environment from the rest of your system and makes the entire server portable: back up two folders, and you can redeploy it on any other Docker host in minutes.
Step 2 – Update Your Server and Create a Service Account
On a fresh Linux box (Ubuntu 24.04 LTS in these examples), start with a full update and a dedicated, unprivileged account for the server process. Never run a public-facing game server as root or as your personal administrator account – if a malicious mod or a compromised dependency ever escapes the process, you want the blast radius contained.
sudo apt update && sudo apt upgrade -y
sudo apt install -y curl wget tar lib32gcc-s1 ufw
sudo adduser --disabled-password --gecos "" enshrouded
sudo su - enshroudedOn Windows, create a standard (non-administrator) local user account for the server, and run the executable from that account rather than a personal admin login.
Step 3 – Install SteamCMD
SteamCMD is Valve’s command-line tool for downloading dedicated server files without launching the full Steam client. On Ubuntu, enable the 32-bit architecture and multiverse repository first, since SteamCMD itself is a 32-bit binary.
sudo dpkg --add-architecture i386
sudo add-apt-repository multiverse -y
sudo apt update
sudo apt install -y steamcmdOn Windows, download steamcmd.exe from Valve’s official SteamCMD documentation page, extract it into its own folder (for example C:\steamcmd), and run it once so it can self-update before you request the Enshrouded files.
Step 4 – Download the Enshrouded Dedicated Server Files
The dedicated server ships as its own free Steam app, separate from the paid game. Its SteamCMD app ID is 2278520. Unlike several other survival titles, this one downloads with an anonymous login – you don’t need to authenticate with an account that owns the game.
steamcmd +force_install_dir /home/enshrouded/server \
+login anonymous \
+app_update 2278520 validate \
+quitOn Windows, the equivalent command from inside your SteamCMD folder is:
steamcmd.exe +force_install_dir C:\enshrouded-server +login anonymous +app_update 2278520 validate +quitThe download is a fraction of the size of the full client since it excludes textures, audio, and rendering assets – expect it to finish in a few minutes on a reasonable connection. A successful run ends with SteamCMD’s standard confirmation line, which is your signal the files are ready:
Downloading update (0 of 187,204 KB)...
Update complete, launching...
Success! App '2278520' fully installed.If app_update appears to hang instead, it is almost always a full disk or an outbound firewall blocking Steam’s content delivery network, not a broken app ID.
Step 5 – Understand the Server Folder and File Layout
Once SteamCMD finishes, your install directory contains a predictable set of files and folders:
enshrouded_server.exe– the server executable (Windows binary, even on a Linux/Wine or Docker host).enshrouded_server.json– the main configuration file you’ll edit in Step 6.savegame/– the world save directory, set by thesaveDirectoryfield.logs/– server logs, set by thelogDirectoryfield, useful for the troubleshooting table later in this guide.
Back up this entire folder before you touch the config file for the first time. It costs nothing and saves you from re-downloading or, worse, losing a save you can’t reproduce.
Step 6 – Configure enshrouded_server.json
Open enshrouded_server.json in a plain text editor. It is standard JSON, so a single missing comma or stray bracket will stop the server from starting – validate the syntax before your first launch if you’re not confident hand-editing JSON. A representative configuration looks like this:
{
"name": "Shattered's Enshrouded World",
"password": "",
"saveDirectory": "./savegame",
"logDirectory": "./logs",
"ip": "0.0.0.0",
"gamePort": 15636,
"queryPort": 15637,
"slotCount": 8,
"userGroups": [
{
"name": "Admin",
"password": "change-this-admin-password",
"canKickBan": true,
"canAccessInventories": true,
"canEditBase": true,
"canExtendBase": true,
"canBuildAndClaim": true
},
{
"name": "Friend",
"password": "change-this-friend-password",
"canKickBan": false,
"canAccessInventories": true,
"canEditBase": true,
"canExtendBase": true,
"canBuildAndClaim": true
},
{
"name": "Guest",
"password": "",
"canKickBan": false,
"canAccessInventories": false,
"canEditBase": false,
"canExtendBase": false,
"canBuildAndClaim": false
}
]
}The most important fields to review before your first launch are summarized below.
| Field | Purpose |
|---|---|
name | Server name shown in the in-game browser |
gamePort / queryPort | Network ports players connect to and the browser queries (defaults 15636 / 15637) |
slotCount | Maximum concurrent players, 1–16 |
saveDirectory / logDirectory | Where world saves and logs are written – point these at a path you back up |
userGroups | Array defining Admin, Friend, and Guest permission tiers and their join passwords |
Set slotCount to the number of players you actually expect, not the maximum of 16 “just in case.” Every additional slot reserves resources whether or not it’s occupied, and the hardware table earlier in this guide scales directly with this number.
Step 7 – Set Up Admin, Friend, and Guest User Groups
The userGroups block in the config above is Enshrouded’s built-in permission system, and it’s worth understanding before you hand out passwords. Each group defines a separate join password and a distinct set of capabilities:
- Admin – full permissions, including kick/ban and unrestricted building. Reserve this password for yourself and co-owners only.
- Friend – can build, extend the base, and access shared inventories, but cannot kick or ban other players. This is the right tier for your regular play group.
- Guest – read-only or highly restricted access, useful for a public or semi-public server where you want visitors to explore without touching your base.
Treat these passwords the same way you’d treat any shared credential: generate them randomly, never reuse a password from another service, and rotate the Admin password if anyone with access leaves your group. Leaving password empty for the top-level server (as in the example above) means anyone can join and self-select a group by entering that group’s password – leave a real value there if you don’t want the server publicly joinable at all.
Step 8 – Open the Required Network Ports
Enshrouded needs exactly two inbound ports forwarded on your router and allowed through your host firewall – both UDP, using the values from your enshrouded_server.json.
| Port | Protocol | Purpose |
|---|---|---|
| 15636 (default) | UDP | Game traffic – what players actually connect to |
| 15637 (default) | UDP | Query port – powers the in-game server browser listing |
| 27015–27036 | UDP/TCP (outbound) | Steam backend services used by the server process itself |
On a Linux host with ufw, allow only those two inbound ports rather than opening a wide range:
sudo ufw allow 15636/udp
sudo ufw allow 15637/udp
sudo ufw enable
sudo ufw status verboseIf your server sits behind a home router, forward the same two UDP ports to your machine’s local IP in the router’s admin panel. This is the single most common source of “server not visible” reports – see the troubleshooting table later in this guide.
Step 9 – Launch the Server for the First Time
On Windows, double-click enshrouded_server.exe or launch it from a terminal in the install directory:
C:\enshrouded-server\enshrouded_server.exeOn a Linux host running the binary through Wine directly (rather than Docker), the equivalent looks like:
cd ~/server
WINEPREFIX=~/.wine-enshrouded wine enshrouded_server.exeA healthy first launch prints the server name, loads or creates the save under saveDirectory, and reports that it is listening on your configured game and query ports – representative output looks like this:
[Server] Loading configuration from enshrouded_server.json
[Server] Server name: Shattered's Enshrouded World
[Server] Save directory: ./savegame (creating new world)
[Server] Listening on gamePort=15636, queryPort=15637
[Server] Ready. Waiting for connections (0/8 slots)...If the process exits immediately instead of reaching that “Ready” state, re-check your enshrouded_server.json for a JSON syntax error – that’s the most common first-launch failure by far.
Step 10 – Connect From the Game Client
With the server running, launch Enshrouded on your own PC and use the in-game multiplayer menu’s direct-connect option, entering your server’s public IP address and game port (for example 203.0.113.10:15636). If you’re testing from the same local network as the host, use its local IP instead of the public one to rule out router/NAT issues while you confirm the config is correct.
If the direct-connect attempt times out, work through this order: confirm the server process is still running and didn’t crash, confirm both ports are open on the host firewall, then confirm the router’s port forward targets the correct local IP. Only after all three check out should you suspect an ISP-side block, which is rare but not unheard of on some consumer connections.
Step 11 – Run Enshrouded in Docker on Linux (Alternative Path)
Since there’s no native Linux binary, running the server in a community-maintained Docker image is the cleanest way to self-host on Linux without hand-managing a Wine prefix. Docker also makes upgrades and backups trivial, since your persistent data lives entirely in mounted volumes outside the container.
First, install Docker and the Compose plugin if you haven’t already:
curl -fsSL https://get.docker.com | sudo sh
sudo usermod -aG docker enshrouded
sudo apt install -y docker-compose-pluginThen define the service in a docker-compose.yml, mapping the same two UDP ports you opened in Step 8 and mounting a local folder for persistent config and saves:
services:
enshrouded:
image: sknnr/enshrouded-dedicated-server:latest
container_name: enshrouded-server
restart: unless-stopped
ports:
- "15636:15636/udp"
- "15637:15637/udp"
volumes:
- ./config:/home/steam/enshrouded/config
- ./savegame:/home/steam/enshrouded/savegame
environment:
- SERVER_SLOT_NAME=ShatteredWorld
- SERVER_MAX_PLAYERS=8Bring it up with docker compose up -d, then edit the generated enshrouded_server.json inside the mounted ./config folder exactly as described in Step 6 – the file format doesn’t change just because it’s running inside a container. Because this is a third-party community image rather than an official Keen Games release, pin it to a specific tag instead of latest once your server is stable, and review the image’s source before trusting it with your firewall-exposed ports.
Step 12 – Automate Backups, Updates, and Security Hardening
A working server is only half the job. The last step covers the three habits that separate a server that survives a bad patch or a bad actor from one that doesn’t.
Automated Backups
Compress and timestamp your savegame folder on a schedule, and keep at least a few days of history so a single corrupted save doesn’t erase your entire world’s progress:
#!/bin/bash
# enshrouded-backup.sh
SRC=~/server/savegame
DEST=~/backups
mkdir -p "$DEST"
tar -czf "$DEST/enshrouded-$(date +%F-%H%M).tar.gz" -C "$SRC" .
find "$DEST" -name "enshrouded-*.tar.gz" -mtime +7 -deleteSchedule it with cron to run every few hours, and – critically – copy at least a weekly snapshot somewhere off the host entirely (cloud storage, a second machine) so a drive failure or ransomware incident on the host itself can’t take the backups down with it.
crontab -e
# Add: back up every 4 hours
0 */4 * * * /home/enshrouded/enshrouded-backup.shKeeping the Server Updated
Re-run the same SteamCMD command from Step 4 to pick up server updates – app_update only downloads changed files, so repeat runs are fast. Always update the server binary before the majority of your players update their clients; a version mismatch between server and client is the most common cause of “can’t connect” reports right after a patch.
steamcmd +force_install_dir /home/enshrouded/server +login anonymous +app_update 2278520 validate +quitSecurity Hardening Checklist
- Run as a dedicated non-root/non-admin user – created in Step 2, this limits the damage from any process compromise.
- Firewall only the two required UDP ports – no reason to expose SSH, RDP, or any management interface to the public internet on the same host without a VPN in front of it.
- Use unique, randomly generated passwords for the Admin and Friend user groups – never reuse your Steam password or a password from another service.
- Keep the Admin password out of Discord and public config repos. If you version-control your
enshrouded_server.json, keep secrets in a separate, gitignored file or environment variables. - SSH key authentication, not passwords, if the host itself is remotely administered – disable password login entirely once your key is confirmed working.
- Offsite backups, as covered above, so a compromised or failed host doesn’t cost you the world save along with the server.
Scaling Your Server as Your Group Grows
If you started at slotCount: 4 and your group has grown, scaling up is mostly a hardware question rather than a configuration one. Raise slotCount in enshrouded_server.json and restart the server, then check your host against the hardware table earlier in this guide for the new player tier. Single-thread CPU performance matters more than raw core count for world simulation, so when you outgrow your current VPS, prioritize a plan with a faster clock speed over one that simply advertises more vCPUs. Bandwidth scales linearly too – recalculate at roughly 2 Mbps of upload per additional player before you assume a lag complaint is a CPU problem.
World size matters as much as player count once you’re past a handful of slots. Enshrouded’s building system lets a dedicated group construct sprawling bases across multiple biomes, and every placed object is state the server has to track and persist. If you notice save times creeping up or RAM usage climbing steadily over weeks rather than spiking under load, that’s usually accumulated world size rather than a concurrent-player problem – the fix is more RAM headroom and, eventually, encouraging your group to consolidate rather than sprawl.
Adding Mods to a Dedicated Server Safely
Enshrouded does not have official mod support as of mid-2026, but an active community has built reliable tooling around it anyway. Mod loaders like Shroudtopia and EML are the two most widely used options, both distributed through Nexus Mods, and a UI-driven Mod Manager updated on February 18, 2026 now supports one-click installation for both loaders.
Treat unofficial mods on an internet-facing server with the same caution you’d apply to any third-party binary running with access to your files – this is a security site, and “just a game mod” is exactly the kind of software supply chain most people don’t think to scrutinize. Some concrete practices:
- Only install mods from Nexus Mods, checking the author’s history and existing user comments rather than a random download link shared in a Discord server.
- Test on a cloned copy of your world first. Copy your
savegamefolder to a second install, apply the mod there, and confirm it doesn’t corrupt the save before touching your live server. - Back up before every mod install and every game update – the community explicitly warns that mods can corrupt worlds, especially right after a patch changes underlying save formats.
- Pin mod versions rather than auto-updating, since a mod that worked on the last client patch can silently break after Keen Games ships a new one.
Common Pitfalls When Self-Hosting Enshrouded
- Assuming a native Linux binary exists. It doesn’t. Every Linux path – Wine or Docker – is running the same Windows executable under a compatibility layer.
- Forgetting the query port. Forwarding only the game port (15636) lets direct-IP connections work while the server stays invisible in the in-game browser, because that listing depends on the query port (15637).
- Setting slotCount to 16 “just in case.” Unused slots still reserve planning headroom, and under-provisioned RAM at a high slot count causes exactly the stutter and desync reports that get blamed on “bad optimization.”
- Reusing passwords across Admin, Friend, and your personal accounts. The
userGroupspasswords are plaintext in a config file – never let one double as a password you use anywhere else. - Skipping backups before mod installs or major patches. This is the single most common cause of “I lost my world” reports in the community, and it is entirely preventable.
- Running the process as root or a personal admin account, especially on a Linux host, when a dedicated low-privilege user (Step 2) costs nothing extra to set up.
Troubleshooting Enshrouded Dedicated Server Problems
| Symptom | Likely Cause | Fix |
|---|---|---|
| Server missing from in-game browser | Query port (15637/UDP) not forwarded | Open and forward 15637/UDP on both host firewall and router |
| Players get connection timeout on direct IP | Game port (15636/UDP) blocked | Open and forward 15636/UDP; confirm process is actually running |
app_update hangs or fails | Disk full, or outbound traffic to Steam CDN blocked | Check free disk space; allow outbound HTTPS/Steam traffic through firewall |
| Server crashes immediately on launch | Malformed enshrouded_server.json (trailing comma, missing bracket) | Validate the JSON with a linter before launching |
| Memory usage climbs over a long session | Known behavior on very long uptimes | Schedule a nightly or weekly automated restart |
| Save appears corrupted after a mod update | Mod incompatible with the current game patch | Restore the most recent backup; wait for the mod author to update |
| Docker container can’t be reached externally | Port mapping in docker-compose.yml doesn’t match the JSON config | Confirm ports: entries match gamePort/queryPort exactly |
| Admin commands rejected in-game | Wrong group password entered, or not joined under the Admin group | Re-check the password against the userGroups entry in the config |
| Server shows in browser but stuck at 0 players | Stale cached listing on the client | Restart the Enshrouded client to refresh the server browser |
| Wine-based (non-Docker) Linux install crashes on startup | Missing 32-bit dependencies or a broken Wine prefix | Switch to the Docker path in Step 11, which bundles a known-working environment |
What Enshrouded’s October 2026 1.0 Launch Means for Server Admins
Enshrouded’s final major Early Access update, “Forging the Path” (v0.9.1.0), shipped on April 21, 2026, focused on polishing existing systems rather than adding new biomes – a clear signal Keen Games was preparing the systems that 1.0 will be judged on rather than expanding scope further. The studio has confirmed 1.0 launches on October 15, 2026 for Windows PC and PlayStation 5/PS5 Pro, with an Xbox Series X/S edition following in early 2027.
For anyone running a dedicated server, treat the 1.0 launch the same way you’d treat any major version bump on a production service: expect a mandatory server binary update, back up your world before updating, and don’t assume old saves are guaranteed forward-compatible until Keen Games confirms it in the 1.0 patch notes. Keen Games has not yet detailed whether Windows-hosted dedicated servers will support incoming PlayStation 5 clients at launch – if your group is planning to play across PC and console, confirm cross-play support through official channels closer to the release date rather than assuming it based on this guide.
Advanced Tips for Enshrouded Server Admins
- Run a staging copy. Clone your install to a second directory on a different port (for example 15646/15647) to test updates and mods before they touch your live world.
- Supervise the process. On Linux, wrap the launch command in a systemd unit with
Restart=on-failureso the server comes back automatically after a crash. On Windows, a tool like NSSM can run the executable as a proper background service. - Watch the logs, not just the player count. The
logDirectoryfrom Step 6 will show connection errors and warnings well before a player bothers to report them. - Version-control your config. Keep
enshrouded_server.jsonin a private git repository (with passwords stripped out or templated) so every change is diffable and reversible. - Don’t max out slotCount immediately. Start conservative, watch RAM and CPU headroom under real load for a week, then raise it – it’s a one-line config change and a restart, not a re-install.
Related Coverage
- Palworld Dedicated Server: 12 Steps, 30 Min [2026]
- Satisfactory Dedicated Server: 12 Steps, 30 Min [2026]
- Project Zomboid Dedicated Server: 12 Steps, 30 Min [2026]
- ARK Dedicated Server: 12 Steps, 30 Min [2026]
- FiveM Server Setup: 12 Steps to GTA RP, 30 Min [2026]
- Minecraft Server Setup: 12 Steps, 30 Min [2026]
- Valheim Dedicated Server: 11 Steps, 30 Min [2026]
- All gaming coverage on Shattered
Frequently Asked Questions
What is the SteamCMD app ID for the Enshrouded dedicated server?
2278520. It’s a separate, free Steam app from the paid game itself, and it downloads with an anonymous SteamCMD login – no game-owning account required on the host.
How many players can an Enshrouded server support?
Up to 16 players, set via the slotCount field in enshrouded_server.json. Set it to the number you actually expect to host rather than the maximum, since higher slot counts require more RAM and CPU headroom.
Can I run an Enshrouded dedicated server on Linux?
Yes, but not natively – Keen Games only ships a Windows binary. Linux hosts run it through a Wine compatibility layer, most reliably packaged inside a community-maintained Docker image (Step 11), which handles the Wine environment for you and keeps saves and config in mounted volumes.
Is Enshrouded server hosting free?
The dedicated server software itself is free for anyone who owns Enshrouded ($29.99 on Steam) – there’s no separate license fee. Your only cost is the machine or VPS you run it on, typically $5–$20 a month for a self-hosted box, versus $10–$35 a month for a managed hosting slot.
What ports does Enshrouded need forwarded?
Two UDP ports: 15636 (game) and 15637 (query), both configurable in enshrouded_server.json. The game port handles direct connections; the query port is what makes your server appear in the in-game public server browser.
Does Enshrouded support mods on a dedicated server?
Not officially, as of mid-2026. Community mod loaders (Shroudtopia and EML, both on Nexus Mods) work on dedicated servers, but Keen Games has not published an official modding API. Always back up your world before installing or updating any mod.
When does Enshrouded leave Early Access?
Keen Games has confirmed 1.0 launches on October 15, 2026 for PC, PS5, and PS5 Pro. An Xbox Series X/S version is planned for early 2027. Expect a mandatory server update on launch day – back up your world beforehand.
How much RAM does an Enshrouded server need?
Hosting-guide consensus puts it around 8–16 GB for a small group of up to four players, scaling to 16–24 GB for a full 16-player lobby. Keen Games has not published an official minimum for the server binary, so treat these as planning figures rather than a hard requirement, and monitor real usage on your own hardware after launch.
Your Enshrouded Server, Ready for the Shroud
You now have a working Enshrouded dedicated server: SteamCMD pulling app 2278520, a configured enshrouded_server.json with proper Admin/Friend/Guest tiers, both required ports open through a firewall that exposes nothing else, and an automated backup routine protecting the world you’ve built. That’s the same foundation a long-running community server runs on – you’ve just built it yourself, on hardware and infrastructure you actually control.
Revisit this setup around October 15, 2026, when Enshrouded’s 1.0 release is likely to ship a server-side update and possibly new configuration options alongside it. Until then, the habits that matter most – back up before every update, keep the Admin password off Discord, and firewall only what you need – don’t change with the version number.
If this is the first game server you’ve self-hosted, the instincts you practiced here transfer almost unchanged to every other title: create a low-privilege service account before you run anything internet-facing, forward only the ports the game actually documents, treat any config file holding a password as a secret, and never let “it’s just a game” talk you out of backing up before you update. Those four habits are what separate a server that survives its first bad night from one that doesn’t – and they cost nothing extra to build in from Step 1.
