Server Properties Guide
Essential server.properties settings explained for Minecraft server owners.
By Lodgichost Team · Last updated: August 19, 2026
Your server.properties file is the control centre of your Minecraft server. It controls how many players can join, your view distance, difficulty, PvP, spawning, and dozens of other settings — all in a single plain-text file. Getting these values right is one of the fastest ways to improve both the play experience and the performance of your server, which is why it deserves a guide of its own.
What Is server.properties?
server.properties is a plain-text file stored in the root directory of your server. It uses a simple key=value format with one setting per line, and it is read every time the server starts. There is no database or control-panel plugin involved: you edit the file, save it, and restart the server for changes to take effect. Because it is plain text, you can edit it from anywhere — the portal's file manager, SFTP, or a command-line text editor. Lines that begin with # are comments and are ignored by the server, which is handy for jotting down what you changed and why you changed it.
File Location
The server.properties file is located in your server's root directory at /home/minecraft/server.properties. You can edit it directly through the portal's file manager, via SFTP, or by using the in-game /reload command after making changes.
# Minecraft Server Properties max-players=20 view-distance=8 simulation-distance=6 difficulty=normal pvp=true allow-flight=true white-list=false enable-command-block=false spawn-protection=16 level-seed=42 level-name=world motd=A Lodgichost Minecraft Server network-compression-threshold=256 max-tick-time=60000 max-world-size=29999984
Key Settings Reference
| Setting | Description | Recommended Value |
|---|---|---|
| max-players | Maximum number of players that can join the server simultaneously. | 20 |
| view-distance | Number of chunks sent to players. Lower values reduce bandwidth and CPU usage. | 6-8 |
| simulation-distance | Number of chunks that process entities, redstone, and game logic. | 4-6 |
| difficulty | Game difficulty level affecting mob damage, hunger, and spawn rates. | normal |
| spawn-protection | Radius around spawn where only operators can modify blocks. | 16 |
| pvp | Enables or disables player-vs-player combat. | true |
| allow-flight | Allows players to fly without cheats enabled. Required for some plugins. | true |
| enable-command-block | Enables command blocks for custom maps and adventure modes. | false |
| white-list | When enabled, only whitelisted players can join the server. | false (true for private servers) |
| network-compression-threshold | Sets the threshold for network packet compression. Lower values increase compression. | 256 |
| max-tick-time | Maximum time in milliseconds a single tick can take before the server watchdog stops it. | 60000 |
Beyond the Basics: Settings Server Owners Forget
A few properties cause frequent confusion even for experienced owners because they are easy to overlook. With multiple worlds on one server, spawning, packet compression, and monitoring endpoints, understanding the following values will save you hours of debugging later. For example, enable-query turns on a lightweight status endpoint that monitoring tools and some dashboards can poll to confirm your server is reachable:
enable-query=true query.port=25565
- level-name: The name of the folder inside the server directory that contains your world. When you import an existing world, this value must match the imported folder name exactly.
- level-type: Controls world generation. Use minecraft:normal for the default overworld, or point it at a custom generator data pack for alternative terrain.
- spawn-protection: As covered above, this stops non-operators from building near spawn. Reduce it for casual build servers or set it to 0 when using WorldGuard regions for that area.
- network-compression-threshold: Values between 64 and 256 strike a good balance of bandwidth saving and CPU usage. Very high values reduce compression and can hurt players on slow connections.
- max-world-size: The world border radius in blocks. It is a hard cap rather than a suggestion — players cannot travel past it, so set it intentionally for long-running worlds.
Troubleshooting
- Changes not applying: Make sure to restart the server after editing server.properties.
- Server crashing on startup: Check for invalid values or typos in the file.
- Players cannot join: Verify that online-mode and white-list settings are configured correctly.
- Performance issues: Lower view-distance and simulation-distance to reduce server load.
Frequently Asked Questions
Why won't my changes to server.properties apply?
server.properties is only read at startup. For most property changes, do a full stop-and-start restart instead of /reload. Values such as view-distance and simulation-distance are locked in when the server boots and ignore /reload.
What is the difference between view-distance and simulation-distance?
view-distance controls how many chunks are sent to the client for rendering. simulation-distance controls how many chunks actually run game logic such as mobs, redstone, and block ticks. Lowering simulation-distance is one of the most effective performance tweaks: you keep a long draw distance without paying for full simulation everywhere.
Is it safe to run a server with online-mode=false?
Setting online-mode to false lets unauthenticated (cracked) players join, but it removes skin data and opens the door to account impersonation. Only use it in clearly labelled trusted communities, and always pair it with a whitelist and your own verification steps.
Why can't my players break blocks near spawn?
spawn-protection creates a radius around the world spawn where only operators can modify blocks. If players cannot build near spawn, reduce the radius or use a region plugin like WorldGuard to control an area you actually manage.
What should I do if the server crashes right after I edit server.properties?
A crash immediately after editing usually means a typo or an invalid value — for example a non-numeric value where the server expects a number. Revert the last change, validate your values against this guide, then restart.
Related Guides
- Optimising Server Performance — tune performance settings
- Custom Seeds and World Generators — configure seed settings
- Import an Existing World — set level-name for imported worlds