How Do You Update a Minecraft Server Safely?

Start Here: Update Your Minecraft Server Safely

To update a Minecraft server safely, stop it, copy its key files, replace the server JAR, then test the new build. Never update a live server while players are connected. A clean backup gives you a way back if the update fails.

These updating Minecraft server steps work for a basic Java server. They also help with many hosted setups. Your control panel may use different button names. The files and checks remain much the same.

First, note your current Minecraft version and server type. Write down the Java version, launch command, mod loader, and plugin list. This small record can save time after a failed start.

Back Up the Minecraft Server Folder

A backup protects your worlds, player data, and settings. It also protects files that server tools may change during startup. Make the backup before downloading or replacing anything.

Stop the server with the stop command. Do not close the terminal window without stopping first. This lets the server save recent world changes and close files cleanly.

1. Open the main Minecraft server folder.
2. Check that the server process has fully stopped.
3. Copy the whole folder to another drive or backup service.
4. Give the copy a clear name, such as server-backup-before-1-21-5.
5. Open the copy and confirm that the world folders are present.

At minimum, keep copies of the world folders, server.properties, whitelist.json, and ops.json. Also save banned-players.json, banned-ips.json, and any custom scripts. If you use mods or plugins, copy those folders too.

Keep one backup outside the server machine. A second copy helps if the disk fails or a bad command removes files. For a busy server, keep several dated backups instead of one rolling copy.

Download the New Server JAR

Download the new server JAR from Minecraft's official server download page. Avoid random download sites. They may offer old files, altered files, or unsafe software.

Check the release number before you download. Your world may load in a newer version, but the change can be one way. A copy lets you test the update without risking your main world.

1. Open the official server download page.
2. Choose the server JAR for the version you want.
3. Save it to a temporary folder on your computer.
4. Scan the file with your normal security tool.
5. Compare its file name with the release you planned to install.

Do not overwrite the old JAR yet. Rename the new file to match your launch script only when needed. For example, a script may look for server.jar. In that case, rename the old file to server-old.jar. Then rename the new file to server.jar.

Install the Server Update

With the server stopped and backed up, install the new file in the main server folder. Keep the old JAR for your first test. It gives you a quick way to return to the old version.

1. Open the folder that contains your current server JAR.
2. Rename the old JAR with its version number.
3. Move the new JAR into the same folder.
4. Match the new file name to your launch script.
5. Review the script before you run it.

A common launch command is java -Xms2G -Xmx4G -jar server.jar nogui. The first value sets starting memory. The second value sets the memory limit. Do not give Java all available system memory.

Start the server once and watch the console. It may create new files or change old settings. Stop it again after the first full startup. This creates any files that the new version needs.

If the console shows a missing Java version, install the version required by your server release. If it reports a world error, stop at once. Restore the backup and check the release notes before trying again.

Accept the EULA and Check Settings

Many fresh server starts create an eula.txt file. Open it with a plain text editor. Read the Minecraft End User License Agreement before changing the file.

To accept the agreement, change eula=false to eula=true. Save the file, then start the server again. This step is needed for a normal Java server launch.

Next, open server.properties. This file holds many gameplay and network settings. Make a backup before changing it. One wrong value can stop the server from starting.

• motd sets the message shown in the server list.
• gamemode sets the default player mode.
• difficulty sets the world difficulty.
• max-players sets the player limit.
• view-distance affects how much world data the server sends.
• white-list limits access to approved player names.

Keep each setting on its own line. Use the exact key names. Do not add spaces around the equals sign unless the file already uses them. Change one or two settings at a time. That makes faults easier to find.

Handle Mods, Plugins, and Hosting Tools

Modded servers need extra care. The server JAR alone may not be enough. Your mod loader, mods, and client files must support the same Minecraft version.

Check the loader release before you replace files. Then check every mod for support on that release. Remove outdated mods only from a backup copy first. A missing library can cause a crash during startup.

Plugins need the same check. Some plugins work across small releases. Others break when the game adds new code or changes an API (a set of rules for software links). Read the plugin maker's release notes before you update.

• Back up the mods or plugins folder.
• Save the loader or hosting tool version.
• Check each add-on for the new game version.
• Update one group of add-ons at a time.
• Test with no players online first.

Server hosting programs may manage the JAR for you. Use the host's version selector if it offers one. Still download your own backup first. A host rollback may not restore your world files or settings.

Start and Test the Updated Server

Start the updated server with your usual script or hosting control. Watch the console until it reaches its ready message. A normal start should show no repeated errors or crash loops.

Join with a test account if possible. Check the spawn area, player inventory, homes, permissions, and key commands. Visit several loaded areas. This can reveal missing chunks or broken plugins before players return.

Check the server log after your test. Look for errors tied to mods, plugins, permissions, or world data. Do not ignore warnings that repeat on every startup. They may point to a failure that appears later.

If the server works, tell players which version they need. Keep the old JAR and the pre-update backup for several days. If the update fails, stop the server, restore the old JAR, and restore changed files from the backup.

FAQs About Updating Minecraft Servers

How do I update a Minecraft server without losing my world?

Stop the server and copy the full server folder first. Keep the world folders and restore them if the new version causes trouble.

Where can I download the Minecraft server JAR?

Use Minecraft's official server download page. Check the version before saving the JAR to your server folder.

Do I need to edit eula.txt after every update?

Usually, no. Edit it when the file says eula=false or when a new server setup creates it.

Will my mods and plugins work after an update?

Not always. Check each mod, plugin, and loader for the new Minecraft version before starting a public server.

What should I do if the updated server will not start?

Read the first error in the console, then stop the server. Restore the old JAR or backup, and test the update again in a separate copy.