If you run a Paper or Spigot-based Minecraft server, learning how to edit server.properties Minecraft server settings correctly is one of the most useful skills you can have. The server.properties file controls many of the core rules and behavior of your server, including player limits, difficulty, chunk loading, whitelist access, spawn protection, and several important performance-related settings.
For most server owners, this file is where the real setup begins. It affects how the server feels to players and how well it performs under load. A few smart changes can make a noticeable difference, especially on survival servers, community SMPs, and Paper or Spigot forks that need to stay smooth with multiple players online.
This guide explains how to edit server.properties Minecraft server settings on Paper and Spigot forks, what the most important options do, and which settings are usually worth changing first.
What is the server.properties file? #
The server.properties file is the main server configuration file used by Minecraft servers, including Paper and Spigot forks. It contains key-value settings such as view-distance, simulation-distance, max-players, difficulty, spawn-protection, rate-limit, and white-list. Paper’s documentation lists these as standard server.properties options and shows their defaults.
In simple terms, this file controls how your server behaves at a base level before plugins do anything extra.
Where to find server.properties #
On most Paper or Spigot forks, the server.properties file sits in the main root directory of the server, alongside files like:
server.properties
eula.txt
spigot.yml
bukkit.yml
paper-global.yml / config files
plugins/
world/If you use a hosting panel, you will usually find it in the File Manager in the server’s main folder. If you host locally or on a VPS, it will be in the same directory where the server jar runs from.
How to edit server.properties safely #
To edit server.properties Minecraft server settings properly:
- Stop the server before making changes.
- Open
server.propertiesin your panel editor or a text editor. - Change only the values after the
=sign. - Save the file.
- Start the server again so the changes apply.
A typical line looks like this:
view-distance=8The setting name stays the same. You only change the number or value on the right side.
Why server.properties matters so much on Paper and Spigot #
Paper and Spigot forks give you extra optimization tools through their own config files, but server.properties still handles several of the most important core settings. Paper’s reference includes defaults such as view-distance=10, simulation-distance=10, entity-broadcast-range-percentage=100, max-players=20, rate-limit=0, difficulty=easy, allow-flight=false, spawn-protection=16, and white-list=false.
That means even if you use Paper for performance, bad values in server.properties can still create unnecessary lag or a poor player experience.
The most important server.properties settings to edit #
view-distance #
view-distance controls how much world data the server sends to players, measured in chunks in each direction from the player. Paper documents the default as 10, with a minimum of 3 and maximum of 32.
Example:
view-distance=8This is one of the biggest performance settings in the file. Higher view distance means more chunks must be loaded and sent to players. On survival servers, lowering this can make a big difference in lag.
A practical recommendation for many Paper or Spigot servers is:
- Small private server: 8 to 10
- Public survival server: 6 to 8
- Heavier server with more players or plugins: 6 or lower if needed
simulation-distance #
simulation-distance controls how far away living entities and active game logic are updated by the server. Paper documents the default as 10, with allowed values from 3 to 32.
Example:
simulation-distance=6This affects mobs, redstone, and other active world behavior. If your server struggles with farms, mob-heavy areas, or redstone machines, lowering simulation distance often helps more than people expect.
A good starting point for many servers is 4 to 6.
entity-broadcast-range-percentage #
entity-broadcast-range-percentage controls how close entities need to be before they are sent to players. Paper documents the default as 100, and says lower values reduce how far entities are rendered and can reduce lag. Valid values are 10 to 1000.
Example:
entity-broadcast-range-percentage=75This is useful if you want to reduce the amount of entity update traffic without changing core gameplay too aggressively.
A common optimization range is 50 to 75.
sync-chunk-writes #
sync-chunk-writes controls synchronous chunk writing. Paper documents the default as true, but also notes that on Paper it has no effect by default unless a corresponding system property is enabled.
Example:
sync-chunk-writes=falseThis setting is often mentioned in optimization guides, but on Paper specifically, you should understand that it may not change behavior unless you have explicitly enabled the related system property. For many Paper users, this means it is less important than view distance or simulation distance.
max-players #
max-players sets the maximum number of players who can be online at once. Paper documents the default as 20.
Example:
max-players=20This should reflect what your hardware can actually handle, not just the biggest number you want to advertise.
rate-limit #
rate-limit sets the maximum allowed number of packets before a player is kicked. Paper documents the default as 0, which disables the limit.
Example:
rate-limit=5This can help reduce certain spam or packet abuse scenarios. It is not a magic anti-bot setting, but it can be useful on public servers.
difficulty #
difficulty defines the game difficulty. Paper lists allowed values as peaceful, easy, normal, and hard, with easy as the documented default.
Example:
difficulty=normalFor most survival communities, normal or hard feels better than easy.
allow-flight #
allow-flight=false is the Paper-documented default. This setting prevents players in survival from being kicked for flying, which often relates to cheats but can also affect edge cases.
Example:
allow-flight=falseMost servers should leave this off unless they have a specific reason to allow it.
spawn-protection #
spawn-protection controls the side length formula of protected spawn blocks and defaults to 16. Paper notes that setting it to 0 disables spawn protection, and it only works when at least one operator exists.
Example:
spawn-protection=0If you use a land claim plugin or custom spawn system, you may want to disable vanilla spawn protection.
white-list #
white-list defaults to false. When enabled, only approved players can join. Paper also documents enforce-whitelist=false, which controls whether non-whitelisted players are kicked when whitelist rules are enforced.
Example:
white-list=trueThis is useful for private SMPs, creator servers, or testing environments.
Recommended starting values for many Paper and Spigot servers #
If your goal is a balanced survival server with decent performance, this is a practical starting point:
view-distance=8
simulation-distance=6
entity-broadcast-range-percentage=75
sync-chunk-writes=false
max-players=20
rate-limit=5
difficulty=normal
allow-flight=false
spawn-protection=0
white-list=falseThese are not universal best settings for every server, but they are a much more realistic starting point than leaving everything at stock defaults on a busy community server.
What each setting actually changes #
A lot of guides dump settings without explaining the effect. Here’s the plain-English version.
Lower view-distance means fewer chunks are sent to players, which reduces chunk load and network overhead.
Lower simulation-distance means fewer chunks stay actively ticking, which reduces mob, redstone, and farm-related workload.
Lower entity-broadcast-range-percentage means players receive entity updates from a shorter range, which can reduce server and client strain.
Lower spawn-protection or disabling it avoids conflicts with plugins and custom spawns.
A realistic max-players prevents your server from advertising more capacity than it can smoothly support.
A note about Paper and Spigot forks #
If you are using Paper, Purpur, Pufferfish, or another Spigot-based fork, server.properties still matters, but it is only one layer of optimization. Paper also has its own documented config systems for deeper tuning. The base values in server.properties should be treated as your foundation, and then fork-specific configs can be adjusted after that.
In other words, do not ignore server.properties, but do not expect it to solve every lag issue by itself either.
Common mistakes when editing server.properties #
The most common problems are simple:
- Editing the wrong file
- Forgetting to restart the server
- Setting view distance too high
- Setting max players unrealistically high
- Copying old optimization advice that does not fully apply to current Paper behavior
- Changing too many settings at once and not knowing which one caused the result
The safest approach is to change a few values, restart, test performance, and then adjust again if needed.
Best use cases for editing server.properties on Paper or Spigot #
This file is especially important when you are:
- Launching a brand-new server
- Fixing lag on an SMP
- Tuning a public survival server
- Preparing for a player-count increase
- Moving from Vanilla to Paper
- Cleaning up a server that has grown beyond default settings
If you run any kind of active Minecraft community, knowing how to edit server.properties Minecraft server settings is basic maintenance, not an optional skill.
A simple workflow for server owners #
A practical order for most owners looks like this:
- Set
max-playersrealistically. - Lower
view-distancefirst. - Lower
simulation-distanceif farms, mobs, or redstone are causing strain. - Reduce
entity-broadcast-range-percentageif needed. - Review access and gameplay settings like
white-list,difficulty, andspawn-protection. - Test and repeat.
That gives you cleaner results than trying ten random changes at once.
Smoothly tuned servers start here #
For a lot of Paper and Spigot server owners, the easiest wins come from the simplest file. The server.properties file is not flashy, but it controls some of the most important pieces of the player experience. When it is tuned properly, your server feels smoother, loads fewer unnecessary chunks, handles activity better, and gives you more predictable performance.
