Best Enshrouded Server Settings for Performance and Stability

Running an Enshrouded dedicated server that stays smooth for all players requires attention to hardware sizing, configuration choices, and regular maintenance. This guide covers the settings and practices that have the biggest impact on server performance and stability, based on the official Keen Games recommendations and real-world hosting experience.

Hardware Sizing: Get the Baseline Right

CPU

Enshrouded’s server logic is heavily dependent on single-thread performance. A CPU with high clock speeds (4.0 GHz and above) will deliver better results than a chip with many slower cores. For a server hosting up to 6 players, a 6-core CPU at 3.2 GHz is the minimum. For 8 to 16 players, aim for an 8-core CPU at 3.7 GHz or higher.

RAM

The server process uses roughly 4-5 GB of RAM at idle. As players explore, build, and interact with the world, memory usage climbs. Here is a practical breakdown:

Player count	Recommended RAM	Notes
1-4 players	8 GB	Sufficient for small groups with modest bases
5-8 players	12 GB	Handles moderate building and exploration
9-16 players	16 GB	Recommended for developed worlds with large structures

If you are on a managed hosting plan, choose a tier that provides at least 8 GB. Going below that risks crashes during peak activity.

Storage

Use an SSD. Enshrouded loads and saves world data frequently, and spinning disks create noticeable hitching during autosaves and chunk loading. NVMe drives are ideal but any SSD will be a significant improvement over HDD.

Bandwidth

Keen Games recommends 2 Mbit/s of upload bandwidth per connected player. For a 16-player server, that means 32 Mbit/s of upload capacity. Most managed hosting providers and modern VPS plans meet this easily.

Key Configuration Settings

All server settings live in enshrouded_server.json. The following have the most direct impact on performance and gameplay quality.

slotCount

Set this to your actual group size plus a small buffer, not the maximum of 16. Each player slot increases the server’s CPU and memory overhead even when empty slots are reserved. A group of six should use 8 slots, not 16.

gamePort and queryPort

Defaults are 15636 (game) and 15637 (query). Change these only if you are running multiple Enshrouded servers on the same machine. Misconfigured ports are one of the most common reasons players cannot connect.

Server password

For private groups, always set a password. Public servers without moderation tools configured will attract random players who may grief your world. If you do run a public server, combine a password-free setup with the Visitor role to limit what strangers can do.

Performance Optimization Practices

Schedule automatic restarts

This is the single most effective optimization for Enshrouded servers. Memory usage accumulates over time, especially on worlds with many player-built structures and complex terrain modifications. Restarting the server every 8 to 12 hours clears this bloat and restores baseline performance.

On Linux, a simple cron job works:

0 */12 * * * systemctl restart enshrouded-server

On managed hosting platforms like Reactor, scheduled restarts can be configured through the control panel.

Keep players in proximity when possible

When players are spread across multiple distant regions, the server must simulate terrain, enemies, and physics for each area simultaneously. This is one of the heaviest loads an Enshrouded server handles. Groups that explore the same region at roughly the same time will see smoother performance than groups scattered across the entire map.

This does not mean everyone must stand in the same spot. Exploring the same biome or working on the same base project is enough to keep the load manageable.

Reduce slot count if performance degrades

If you experience persistent lag or rubber-banding and a restart does not fix it, try lowering the slot count temporarily. A server struggling at 16 slots with 12 active players may run smoothly at 12 slots. This is a quick diagnostic to determine if you are hitting hardware limits.

Update after every patch

Keen Games releases performance improvements alongside content patches. The Wake of the Water update (November 2025) and its follow-up hotfixes included server-side optimizations that noticeably improved stability for larger groups. Running an outdated server version means missing these fixes and blocking players on the current client version from connecting.

Difficulty Settings That Affect Server Load

Some gameplay settings in enshrouded_server.json indirectly affect server performance.

Enemy spawning

Higher enemy density increases the number of active AI entities the server must process. If your server is on the edge of its hardware capacity, reducing enemy spawn rates or health (which leads to faster kills and fewer simultaneous active enemies) can ease the load.

Resource yield

Higher resource yields mean players spend less time in resource-heavy gathering loops, which reduces the number of active terrain interactions per session. This is a minor optimization but worth noting for servers at capacity.

Day/night cycle length

Shorter cycles mean more frequent transitions and potentially more enemy spawn waves. Longer days reduce the frequency of night-time enemy activity, slightly lowering the average AI load.

Backup Strategy

Performance tuning is pointless if a crash or corruption wipes your world. Back up your server’s save directory regularly. A good backup schedule:

• Automatic backups every 4-6 hours during active play periods
• Manual backup before any server configuration change or patch update
• Off-site storage so backups survive a disk failure

On Reactor’s Enshrouded hosting, automatic backups are included with one-click restore. If you self-host, script your own backup routine and test restores periodically.

Summary

The core principles for a well-performing Enshrouded server are:

1. Size your hardware for your actual player count, not the theoretical maximum
2. Use an SSD and prioritize CPU clock speed over core count
3. Restart the server every 8-12 hours
4. Keep the server updated after every patch
5. Monitor RAM usage and adjust slot count if needed
6. Back up regularly and test your restores

Follow these practices and your group will spend their time exploring Embervale instead of troubleshooting server issues.