Minecraft server.properties settings configurator
Generate a starting point for five server properties. These values help you test a configuration; they do not estimate your hardware’s player capacity or replace performance measurements.
An illustrative starting point, not a capacity calculation. CPU, world, mods and plugins change the outcome. The player limit does not guarantee the server can sustain that many players.
view-distance=4 simulation-distance=4 max-players=20 network-compression-threshold=256 entity-broadcast-range-percentage=100
Back up the file, change only the listed properties and restart the server. Proxies need their own configuration and protected access to backend servers.
Apply the snippet without losing your settings
- Identify your server software and version. Edit the game server’s file, not a BungeeCord or Velocity configuration.
- Back up server.properties first. Keep properties that are not included in the generated output.
- Stop the server, replace only the listed keys and save the file. Avoid duplicate keys.
- Start it and compare behavior under a representative load. Restore the backup if results worsen and change one setting at a time.
Distances and the player limit
view-distance controls the range of chunks sent to clients; simulation-distance controls the area where entities are simulated. Increasing them can increase server work. The effect depends on your world, players and software.
max-players is an access limit, not a capacity prediction. RAM alone cannot determine that limit. The generated values are illustrative and must be reviewed for your version.
What this tool covers
The output is a snippet, not a complete file. It does not change authentication, permissions or plugin/mod configurations. Proxies have their own files and requirements; configure distances on each backend.
Read the distance guide to understand the effect before copying a configuration.
Put this into practice
Resource and community pages may contain content in the language chosen by their authors.