How to use the server.properties generator
server.properties is the text file that holds the main settings of a Minecraft: Java Edition server, one
key=value pair per line. This generator starts from the file a new 26.3 server writes by itself, so you only touch
the settings you want to change.
- Open a group, such as World or Players and access, and change what you need. Each group header counts your changes.
- Read the notes above the result. Fix means the server would reject the value, so the default is written until you correct it. Check marks a combination that usually causes trouble.
- Choose The full file for a new server. Choose Only the lines I changed when your server already has a file with settings you want to keep, including keys added by other server software.
- Copy the text or download
server.properties, put it in the server folder and restart the server.
Where the server.properties file is
The file sits in the folder the server is started from, next to the server jar and the world folder. The server creates it
the first time it starts, so run the server once if the file is not there yet. On a hosted server, open the file manager in your control
panel and look in the top-level folder. On your own computer, it is the folder that holds your
start script.
Restart the server after every change
The server reads the file once, when it starts. The Minecraft Wiki puts it plainly: after changes are made to the file, the server must be restarted for them to take effect. Stop the server, save the file, then start it again. On startup the server also writes the file back out: it keeps your values, removes any comments and adds every missing key with its default. That is why a file with only your changed lines works.
The settings people most often get wrong
-
white-list. Since Java Edition 26.3 a new server starts withwhite-list=true, so nobody except ops and the players inwhitelist.jsoncan join. Typewhitelist add PlayerNamein the console for each friend, or set it tofalse. -
online-mode. Setting it tofalsestops the account check. Anyone can then join under any name, including the name of one of your ops. -
server-ip. This is not where your public address goes. Leave it blank and the server listens on every address the machine has. Fill it in only when your host gives you a specific address to bind to. -
level-name. It is the folder the world is loaded from. Change it and the server generates a new world in a new folder, which looks as if the old world was deleted. Change the name back and the old world loads again. -
level-seed,level-typeandgenerate-structures. These only shape a world as it is generated. They do nothing to chunks that already exist. -
view-distanceandsimulation-distance. Both are a radius in chunks, from 3 to 32, with a default of 10. The area grows with the square of the number, so 16 covers about two and a half times as many chunks per player as 10. Raise them only if the RAM calculator says your server has room. -
spawn-protection. The value is a radius: 16 protects a square of 33 by 33 blocks where only ops can build. When friends cannot break blocks near spawn, this is the reason. Set it to 0 to turn it off. -
enable-rcon. Rcon gives console access over the network without encryption, and it does not start whilercon.passwordis blank. Leave it off unless a tool you use needs it, and then set a long password. -
motd. Colors and a second line need special codes. Build the message with the MOTD generator, copy its plain § form and paste that into themotdbox here. This tool then writes it in the form the file needs.
Settings that are no longer in the file
Many guides still tell you to edit lines such as pvp=false. A current server does not read them. Use the
/gamerule command for the ones that became game rules. The rule names below are the ones Java Edition has used since 1.21.11;
versions 1.21.9 and 1.21.10 used older names such as commandBlocksEnabled.
| Old key | Removed in | Game rule to use |
|---|---|---|
allow-nether | 1.21.9 | allow_entering_nether_using_portals |
enable-command-block | 1.21.9 | command_blocks_work |
pvp | 1.21.9 | pvp |
spawn-monsters | 1.21.9 | spawn_monsters |
spawn-animals | 1.21.2 | No replacement named by the wiki |
spawn-npcs | 1.21.2 | No replacement named by the wiki |
Which Minecraft version this list matches
The 69 settings and their defaults match Java Edition 26.3, released on 15 September 2026. They were checked on 12 October 2026
against the default file on the Minecraft Wiki, and the full file names that version in its second line. As of 12 October 2026, snapshots of
26.4 add 3 more keys, which are left out until that version is released:
allowed-connection-ids, enable-legacy-status, status-contact-details.
A server on an older version does not use keys that were added after it, and it adds back any key of its own that is missing. Paper
reads the same file, with a few differences listed in
its own reference. Bedrock Dedicated Server also has a file called server.properties,
but its keys are different, so do not use this one there.
Once the server is running with the new file, confirm that others can reach it with the server status checker.
Sources
The data and rules in this tool were last checked on against:
- Minecraft Wiki: server.properties (default file as of Java Edition 26.3)
- Minecraft Wiki: Java Edition, latest release
- Minecraft Wiki: Java Edition 26.3
- Minecraft Wiki: Java Edition 26.3 Snapshot 2, where white-list became true by default
- Minecraft Wiki: Game rule
- Minecraft Wiki: /whitelist command
- Minecraft Wiki: Minecraft Server Management Protocol
- Oracle: java.util.Properties, the syntax of .properties files
- PaperMC docs: server.properties reference