How to Set Up an Enshrouded Dedicated Server (2026 Guide)

There are two ways to run an Enshrouded dedicated server: self-host it on your own Windows machine using SteamCMD, or rent a managed server that's online in minutes with updates, backups, and DDoS protection handled for you. This guide walks through both — the full self-hosted setup step by step, and when the managed route makes more sense.

With Enshrouded 1.0 launching October 15, 2026 (PS5 players can't join dedicated servers at launch, but Keen is working on it), there's never been a better time to get a persistent world running for your group. One note before we start: no save wipe has been announced for 1.0, and existing servers just need the 1.0 update on launch day.

What you'll need: server requirements

Enshrouded's server is heavier than older survival games — Embervale is a big, voxel-terraformed world, and Keen's official recommendations are steeper than most people expect:

Those are Keen's published recommendations — in practice small servers often run in less RAM, but if you're buying or renting hardware, spec to the official numbers. On Linux: officially, only Windows is supported ("Linux support is planned for later" per Keen's docs); the community runs the Windows binary through Proton/Wine (with 32-bit libraries like lib32gcc-s1 for SteamCMD), and it works, but you're off the supported path — another point for managed hosting if your group isn't comfortable there.

Step 1 — Install the server with SteamCMD

The Enshrouded dedicated server is a free tool on Steam (you don't need to own the game to host). Keen's official route is installing it from your Steam library's Tools section; for an always-on server box, SteamCMD does the same thing headlessly: steamcmd +login anonymous +force_install_dir C:\enshrouded-server +app_update 2278520 validate +quit

App ID 2278520 is the official dedicated server. The validate flag checks file integrity — keep it in the command you'll reuse for updates. Keen recommends launching enshrouded_server.exe directly rather than through Steam's Launch button.

Step 2 — Configure enshrouded_server.json

Run enshrouded_server.exe once to generate the config file, then stop it and open enshrouded_server.json. The settings that matter:

• name — your server's name as it appears in the in-game browser (default "Enshrouded Server").
• queryPort — the server's port, default 15637 — the only port in Keen's server config.
• slotCount — player slots, 1 to 16.
• userGroups — Enshrouded doesn't use one server password. Instead you get four default permission groups — Admin, Friend, Guest, Visitor — each with its own password and its own rights: kicking and banning, opening inventories, editing the world and bases, plus reserved slots to guarantee seats for your core group. Give Admin a strong unique password and hand the Guest or Visitor password out freely.
• gameSettingsPreset — difficulty preset, plus optional voice/text chat toggles.

Save the file and start the server again to apply.

Step 3 — Open the port and connect

Forward UDP 15637 on your router to the machine running the server (Steam's own standard ports also need to be reachable, per Keen's docs), and allow enshrouded_server.exe through the Windows firewall. Players then join via the in-game server browser (search your server name) or direct-connect with your public IP and port, entering the password for whichever permission group you've given them.

If friends can't see the server: it's almost always the port forward, a firewall rule, or your ISP using CGNAT (in which case you can't port-forward at all — a rented server is the practical fix).

Step 4 — Updates, backups, and launch day

The self-hosted server does not update itself. Every time Enshrouded patches — including the big one on October 15 — you need to stop the server, re-run the SteamCMD command from Step 1, and start it again. Clients on a newer version can't join an outdated server, so an unpatched server is an offline server as far as your players are concerned.

The server writes a save every 5 minutes (files run 1–100 MB as your world grows), and one detail worth knowing: the world lives on the server, but character progression is stored on each player's client — so your players' characters are safe even if the server save has a bad day. Back up the save folder regularly (and always before a major update). On launch day for 1.0: take a backup, run the update, verify, and you're in.

Self-hosting vs. a managed server

Self-hosting is free if you already have the hardware, and it's a fine weekend project. The trade-offs show up over time:

If your group plays a few evenings a week and expects the world to be there when they log in, a managed server stops being a luxury pretty quickly — especially during a launch window when patches land daily.

Comparing managed options? We've ranked the 5 best Enshrouded server hosting providers on hardware, RAM, locations and support.

Frequently Asked Questions

How much RAM does an Enshrouded server need?

Keen's official recommendation is 16 GB even for a 4–6 player server, alongside a modern 6-core CPU (8 cores for 16 players). Small private servers often get by with less in practice, but spec to the official numbers if you're choosing hardware.

Will the Enshrouded 1.0 update wipe my server?

No wipe has been announced. Your world should carry over — and character progression is stored on each player's client anyway, not on the server. Take a backup before updating on October 15, 2026, as you should before any major patch.

Does the Enshrouded server run on Linux?

Officially no — Keen supports Windows only, with Linux support planned. The community runs the Windows server binary via Proton/Wine, which works but is unsupported.

How many players can join an Enshrouded dedicated server?

Up to 16. The 1.0 release is expected to further improve performance in full 16-player sessions.