An Enshrouded server is mainly controlled through the enshrouded_server.json file. A clean server name, suitable ports, a sensible slot count, reliable backups, and a controlled restart after changes are important. For stable private or community sessions, you should document every change and then check it in the log and in the server browser.
Requirements
Before changing settings, stop the server completely. Changes to the configuration file while the server is running can be overwritten the next time it saves or may only take effect after a restart. You need access to the server directory, the enshrouded_server.json file, the log files, and ideally SFTP or a hosting panel with a file manager.
The official Enshrouded documentation explains that the configuration file is created after the Dedicated Server is started for the first time and is located in the server directory: documentation at enshrouded.zendesk.com. For the basic installation, you can also find a practical overview in the internal guide Rent and Set Up an Enshrouded Server.
Basic configuration in enshrouded_server.json
The server configuration is located in enshrouded_server.json:
{
"name": "My Enshrouded Server",
"password": "secret",
"saveDirectory": "./savegame",
"logDirectory": "./logs",
"ip": "0.0.0.0",
"gamePort": 15636,
"queryPort": 15637,
"slotCount": 8
}
name is the visible server name. Choose a unique name so players can find your server again in the list. saveDirectory and logDirectory should only be changed if you deliberately use a different folder structure. With rented hosting, it usually makes sense to keep the predefined paths because backups, restore functions, and support processes may depend on them.
In typical setups, ip remains set to 0.0.0.0 so the service listens on the intended network interface. gamePort and queryPort must match the firewall and panel configuration. If players cannot find the server, first check whether the server file, panel, and firewall are using the same ports.
Plan slots, RAM, and performance realistically
Enshrouded depends heavily on world state, active players, building projects, and server hardware. So avoid blanket performance promises. Plan slots so your group can play stably instead of maxing out the maximum number.
| Setting | Recommendation |
|---|---|
| RAM | At least 4 GB |
| Player count | Align with the active group and official server version |
| Autosave | Account for automatic saving and add backups |
| Restart | Once daily, preferably outside peak playtime |
The original recommendation of “at least 4 GB RAM” is useful as a lower limit, but should not be understood as a guarantee. The official FAQ already lists several gigabytes of RAM for the idle server process plus additional requirements per player. If you regularly run with many players, large bases, or multiple worlds, plan in more reserves.
Gameplay and role settings
Enshrouded initially offered only limited server settings; by now, available options depend on the version and configuration schema. After updates, therefore check whether your enshrouded_server.json contains new fields. If you do not understand existing settings, do not change them blindly; back up the file and compare it with the official documentation.
For access rights, newer configurations with user groups are relevant. This lets you separate passwords and permissions for roles such as admins, friends, or guests, provided your server version uses this schema. In older files, a single password may still be present. Do not remove it without a prior backup, because this can change access behavior and the invitation process.
Admin functions and operation
Typical admin tasks include server restarts via the dashboard, savegame management, password management, and log checks. Kick and ban functions depend on the server version, console, role model, and hosting interface. Use such functions carefully and document changes so support and other players can understand what happened.
For multi-game hosting with technical control, the most important thing is to make operating steps repeatable: enter the change, restart the server, check the log, test the connection, and check backup status. Similar principles also apply to other games, such as Configuring Minecraft server.properties Correctly or Rent a Rust Server: RAM, Settings & Plugins.
Backup strategy
- Enable automatic backups (dashboard)
- Manual backup before major expeditions
- Savegames can be downloaded via SFTP
Backups are especially important before updates, extensive building projects, role changes, and configuration rebuilds. Do not only keep the world files, but also the associated configuration. That way, after an error you can restore not only the save, but also ports, slots, and access rights.
Check the result
After every change, restart the server and check three things. First: the log file must not report any JSON errors or port conflicts. Second: the server appears with the expected name in the server browser or can be reached via the intended connection. Third: a test join with password or the matching user group works.
Joining
- Start Enshrouded
- Multiplayer → Search servers
- Enter IP and port
- Enter password and connect
If the server does not appear in the list, also test the favorites or direct connection through the available Steam or game options. Also check whether filters in the server browser are hiding active Dedicated Servers.
Troubleshooting
If the server does not start after a change, the JSON syntax is often faulty. Watch out for commas, quotation marks, and correctly closed brackets. A single extra comma can make the file unreadable.
If players cannot connect, check password, role, slot limit, ports, and restart status. If the server starts but uses old values, you probably edited the wrong file or did not restart the server after saving.
If performance problems occur, first reduce the active player count, check RAM usage, and plan a restart. Large worlds and many buildings can increase load; back up the world before running risky tests.
Updates
Enshrouded continues to receive updates. Treat every time-dependent statement as a snapshot of the currently installed server version. Depending on the hosting setup, the server may update when restarted; after updates, check the logs and compare new configuration fields before continuing to use old files unchanged.
Checks, limits, and a safe rollback path
The guide “Optimize Enshrouded Server Settings” applies to the server type described in the article and the version state visible at the time of checking. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer values to another game, loader, or server version without checking them.
Before changing the world, save, configuration, or extensions, create a backup of the affected files. Then change only one related step at a time and test it with the same client and server version you want to play with later.
| Checkpoint | Expected result | Abort and rollback path |
|---|---|---|
| Server start | The server reaches the ready-to-run state without new error messages. | If startup errors occur, revert the change and restore the latest backup. |
| Connection test | A test account can connect via the address shown in the panel. | If version or connection errors occur, compare version, port, and firewall rules again. |
| Function test | The specific changed function works without damaging existing world or game data. | If side effects occur, stop the server and restore the backed-up files. |
A successful single test is not a performance or availability guarantee. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document the version, change, and test result so you can understand later deviations.
FAQ
Where do I find the Enshrouded server settings?
The central file is called enshrouded_server.json and is located in the server directory. It is created after the Dedicated Server is started for the first time if it does not already exist.
Do I have to restart the server after every change?
Yes, plan for a restart. Many settings are only read during startup, and without a restart you may still be testing the old state.
Which ports are important?
In the initial example, gamePort 15636 and queryPort 15637 are used. What matters is that the file, hosting panel, and firewall use the same values.
How do I prevent data loss?
Enable automatic backups and create a manual backup before updates, configuration changes, and major expeditions. Also download important savegames via SFTP if you need an external copy.
What do I do about JSON errors?
Restore the latest working backup or correct the syntax with a JSON validator. Pay special attention to missing quotation marks, incorrect commas, and accidentally deleted brackets.