Every Enshrouded dedicated server is steered by a single file: enshrouded_server.json. It controls your server name, the ports it listens on, how many players can join, who has admin powers, and how punishing the world feels. Get one character wrong, though, and Enshrouded will quietly throw away your entire config and start fresh. This guide walks through every important setting, the safe way to edit them, and the one mistake that wipes servers without warning.
Where the file lives and how it behaves
The enshrouded_server.json file sits in the root of your server installation and is generated automatically the first time the server boots. Two behaviors trip up almost everyone:
- The server rewrites the file on shutdown. Enshrouded saves its current configuration state back to the JSON when it stops. If you edit the file while the server is still running, your changes are overwritten on exit. Always stop the server first.
- Invalid JSON triggers a silent default-wipe. A trailing comma, a missing quote, or a stray bracket will not produce an error message. On the next startup, Enshrouded discards your broken file and regenerates a clean default config — taking your server name, password, and roles with it. Validate your JSON in any online validator before restarting.
If you would rather not hand-edit JSON at all, our enshrouded_server.json generator builds a syntactically valid file with every field filled in. On managed hosting, you also get a panel that validates and backs up the file automatically — see the full walkthrough in our Enshrouded server documentation.
Core server settings
These top-level fields define the server’s identity and where it stores data.
name— the server name shown in the public server browser. Keep it short and recognizable.password— the join password for the server. Leave it as the default group password handling (see roles below); an empty top-level password generally means open access depending on your role setup.saveDirectory— folder where world and character progress is written.logDirectory— folder for server log files, useful for diagnosing crashes.ip— the address the server binds to.0.0.0.0listens on all network interfaces, which is what most hosts want.slotCount— maximum concurrent players, up to 16 (the hard cap for Enshrouded dedicated servers).
gamePort and queryPort
Enshrouded uses two UDP ports, and they serve different jobs. The gamePort carries actual gameplay traffic; the queryPort is what the server browser uses to discover and ping your server. The defaults are gamePort 15636 and queryPort 15637.
- The two ports must be different values. Setting them to the same number causes a failed or unreliable startup.
- Both ports must be open as UDP in your firewall and, on a home setup, forwarded on your router. If your server runs but nobody can find it, this is the first thing to check.
- On a managed host the ports are usually assigned for you, so leave the defaults unless the panel tells you otherwise.
If players still can’t see the server after the ports are correct, work through our Enshrouded server not showing up fix, which covers query-port and visibility issues in detail.
Roles and user groups
Permissions in Enshrouded are handled through the userGroups array. Each entry is a role with its own password — whichever group password a player enters when joining determines the permissions they get. The three groups created by default are Admin, Friend, and Guest.
Each group exposes permission flags. The exact set can shift between updates, but the common fields are:
name— the group’s display label.password— the password that grants membership in this group.canKickBan— whether members can kick and ban other players.canAccessInventories— access to shared/other players’ inventories.canEditBase— permission to build and modify base structures.canExtendBase— permission to extend the buildable base area.reservedSlots— slots held open for this group even when the server is full.
To add a new role, copy an existing group block, give it a unique name and password, and set the flags you want. For the in-game commands that pair with these roles, see our Enshrouded admin commands and server roles guide.
Difficulty presets
The gameSettingsPreset field is a fast way to tune the whole experience. It accepts Default, Relaxed, Hard, Survival, and Custom. Choosing anything other than Custom configures many gameplay values at once; choosing Custom unlocks the individual gameplay fields so you can hand-tune things like enemy strength, resource yields, and stamina.
| Preset | General intent | Who it suits |
|---|---|---|
| Relaxed | Fewer enemies, more resources and loot, gentler survival pressure | Base-builders and casual co-op |
| Default | The intended balanced experience | Most groups |
| Hard | Tougher combat and tighter resources | Experienced players wanting a challenge |
| Survival | The most demanding preset; stricter survival mechanics | Hardcore survival fans |
| Custom | Unlocks every individual gameplay setting for manual tuning | Server owners who want full control |
The exact multipliers each preset applies are version-dependent and have changed across patches, so treat the table above as intent rather than fixed numbers. If you need precise values, switch to Custom and inspect each field directly. For full installs and migrations, our Enshrouded dedicated server setup guide covers the surrounding workflow.
A safe editing checklist
- Stop the server completely before opening the file.
- Make a backup copy of
enshrouded_server.jsonfirst. - Edit your values; double-check quotes, commas, and brackets.
- Paste the file into a JSON validator to confirm it parses.
- Save, then start the server and confirm your name and settings stuck.
That last step matters: if the server boots and your custom name has reverted to the default, the JSON was invalid and got wiped — restore your backup and find the typo. Want this handled for you with automatic backups and panel-side validation? Our managed Enshrouded hosting takes the JSON guesswork out of the loop entirely.
FAQ
Why did my Enshrouded server reset to default settings?
Almost always a JSON syntax error. Enshrouded does not warn you about invalid configuration — it silently replaces the whole file with defaults on the next startup. A trailing comma or unclosed quote is enough. Restore your backup and validate the file before restarting.
What ports does an Enshrouded dedicated server need open?
By default, 15636 (gamePort) and 15637 (queryPort) — forward both on TCP and UDP. Both must be open in your firewall and forwarded on your router, and the two must be different values. The query port specifically is what makes the server appear in the browser.
How many players can an Enshrouded server hold?
The slotCount field supports up to 16 players, which is the maximum for an Enshrouded dedicated server. For details on group sizes and co-op limits, see our Enshrouded co-op and player count guide.
Every Enshrouded dedicated server is steered by a single file: enshrouded_server.json. It controls your server name, the ports it listens on, how many players can join, who has admin powers, and how punishing the world feels. Get one character wrong, though, and Enshrouded will quietly throw away your entire config and start fresh. This guide walks through every important setting, the safe way to edit them, and the one mistake that wipes servers without warning.
Where the file lives and how it behaves
The enshrouded_server.json file sits in the root of your server installation and is generated automatically the first time the server boots. Two behaviors trip up almost everyone:
- The server rewrites the file on shutdown. Enshrouded saves its current configuration state back to the JSON when it stops. If you edit the file while the server is still running, your changes are overwritten on exit. Always stop the server first.
- Invalid JSON triggers a silent default-wipe. A trailing comma, a missing quote, or a stray bracket will not produce an error message. On the next startup, Enshrouded discards your broken file and regenerates a clean default config — taking your server name, password, and roles with it. Validate your JSON in any online validator before restarting.
If you would rather not hand-edit JSON at all, our enshrouded_server.json generator builds a syntactically valid file with every field filled in. On managed hosting, you also get a panel that validates and backs up the file automatically — see the full walkthrough in our Enshrouded server documentation.
Core server settings
These top-level fields define the server’s identity and where it stores data.
name— the server name shown in the public server browser. Keep it short and recognizable.password— the join password for the server. Leave it as the default group password handling (see roles below); an empty top-level password generally means open access depending on your role setup.saveDirectory— folder where world and character progress is written.logDirectory— folder for server log files, useful for diagnosing crashes.ip— the address the server binds to.0.0.0.0listens on all network interfaces, which is what most hosts want.slotCount— maximum concurrent players, up to 16 (the hard cap for Enshrouded dedicated servers).
gamePort and queryPort
Enshrouded uses two UDP ports, and they serve different jobs. The gamePort carries actual gameplay traffic; the queryPort is what the server browser uses to discover and ping your server. The defaults are gamePort 15636 and queryPort 15637.
- The two ports must be different values. Setting them to the same number causes a failed or unreliable startup.
- Both ports must be open as UDP in your firewall and, on a home setup, forwarded on your router. If your server runs but nobody can find it, this is the first thing to check.
- On a managed host the ports are usually assigned for you, so leave the defaults unless the panel tells you otherwise.
If players still can’t see the server after the ports are correct, work through our Enshrouded server not showing up fix, which covers query-port and visibility issues in detail.
Roles and user groups
Permissions in Enshrouded are handled through the userGroups array. Each entry is a role with its own password — whichever group password a player enters when joining determines the permissions they get. The three groups created by default are Admin, Friend, and Guest.
Each group exposes permission flags. The exact set can shift between updates, but the common fields are:
name— the group’s display label.password— the password that grants membership in this group.canKickBan— whether members can kick and ban other players.canAccessInventories— access to shared/other players’ inventories.canEditBase— permission to build and modify base structures.canExtendBase— permission to extend the buildable base area.reservedSlots— slots held open for this group even when the server is full.
To add a new role, copy an existing group block, give it a unique name and password, and set the flags you want. For the in-game commands that pair with these roles, see our Enshrouded admin commands and server roles guide.
Difficulty presets
The gameSettingsPreset field is a fast way to tune the whole experience. It accepts Default, Relaxed, Hard, Survival, and Custom. Choosing anything other than Custom configures many gameplay values at once; choosing Custom unlocks the individual gameplay fields so you can hand-tune things like enemy strength, resource yields, and stamina.
| Preset | General intent | Who it suits |
|---|---|---|
| Relaxed | Fewer enemies, more resources and loot, gentler survival pressure | Base-builders and casual co-op |
| Default | The intended balanced experience | Most groups |
| Hard | Tougher combat and tighter resources | Experienced players wanting a challenge |
| Survival | The most demanding preset; stricter survival mechanics | Hardcore survival fans |
| Custom | Unlocks every individual gameplay setting for manual tuning | Server owners who want full control |
The exact multipliers each preset applies are version-dependent and have changed across patches, so treat the table above as intent rather than fixed numbers. If you need precise values, switch to Custom and inspect each field directly. For full installs and migrations, our Enshrouded dedicated server setup guide covers the surrounding workflow.
A safe editing checklist
- Stop the server completely before opening the file.
- Make a backup copy of
enshrouded_server.jsonfirst. - Edit your values; double-check quotes, commas, and brackets.
- Paste the file into a JSON validator to confirm it parses.
- Save, then start the server and confirm your name and settings stuck.
That last step matters: if the server boots and your custom name has reverted to the default, the JSON was invalid and got wiped — restore your backup and find the typo. Want this handled for you with automatic backups and panel-side validation? Our managed Enshrouded hosting takes the JSON guesswork out of the loop entirely.
FAQ
Why did my Enshrouded server reset to default settings?
Almost always a JSON syntax error. Enshrouded does not warn you about invalid configuration — it silently replaces the whole file with defaults on the next startup. A trailing comma or unclosed quote is enough. Restore your backup and validate the file before restarting.
What ports does an Enshrouded dedicated server need open?
By default, 15636 (gamePort) and 15637 (queryPort) — forward both on TCP and UDP. Both must be open in your firewall and forwarded on your router, and the two must be different values. The query port specifically is what makes the server appear in the browser.
How many players can an Enshrouded server hold?
The slotCount field supports up to 16 players, which is the maximum for an Enshrouded dedicated server. For details on group sizes and co-op limits, see our Enshrouded co-op and player count guide.
Ready to play?
Run your own Enshrouded server with XGamingServer
Spin up an always-on Enshrouded server your friends can join in minutes — no port-forwarding, no tech headaches.
