Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteYou can update a Paper Minecraft server without deleting its worlds. The safe sequence is to schedule downtime, stop the server completely, make a recoverable backup, update plugins for the target Minecraft version, replace the Paper server JAR, restart with the required Java runtime, and inspect the startup log before players return.
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
PaperMC explicitly warns: “Don’t replace any JAR in a running server.” A Paper update changes the server software, not the world folders by itself, but an incompatible plugin, Java runtime, or configuration can prevent startup. Treat the update as a controlled change with a rollback path.
As an Amazon Associate I earn from qualifying purchases.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhat a Paper update actually changes
A Paper server runs from a Java archive (JAR). Updating normally means replacing that executable JAR with a newer Paper build for the Minecraft version you want to run. Your world folders, server settings, plugin settings, and plugin JARs remain separate files, so replacing Paper does not inherently erase them.
The risk comes from compatibility rather than the file replacement itself. A new Minecraft/Paper version may require a newer Java runtime, and plugins compiled for an older server may fail or behave incorrectly. Paper’s documented approach therefore combines a full backup, deliberate plugin updates, a stopped server, and log monitoring after the restart.
#1 Best Overall
Paper also distinguishes a routine Paper-to-newer-Paper update from a migration between server implementations. Do not apply migration instructions casually to a normal Paper update; the file handling and rollback considerations are different.
Check the target version and Java requirement first
Choose the exact Minecraft/Paper target before downloading anything. The target version determines the minimum Java runtime listed in PaperMC’s current getting-started compatibility table:
| Minecraft version range | Required Java version | What this means |
|---|---|---|
| 1.7.10–1.11 | Java 8 | The server must run on Java 8 or a compatible newer setup that Paper supports for that target. |
| 1.12–1.16.4 | Java 11 | Use a Java 11 runtime for these versions. |
| 1.16.5 | Java 16 | This version has its own Java requirement in the table. |
| 1.17–1.19 | Java 17 | Use Java 17 for this range. |
| 1.20–1.21.11 | Java 21 | Current Paper releases in this range require Java 21. |
| 26.1 and newer | Java 25 | Paper lists Java 25 for Minecraft 26.1 and later. |
These are compatibility requirements, not performance benchmarks. A newer Java version is not automatically valid for every older Paper build, so follow the requirement for the exact target shown in Paper’s documentation and use the same runtime when testing and running the production server.
Confirm which Java your startup command uses
Do not assume that the Java version shown by an installed desktop runtime is the one used by the server. The executable selected by your service, control panel, script, or shell command is what matters. Before the maintenance window, identify that executable and make sure it satisfies the target requirement. If you change Java, test the server with the new runtime before inviting players back.
Schedule downtime and prepare an inventory
Paper recommends being present during updates and watching the server log afterward. Choose a maintenance window long enough to stop, back up, replace, start, and test the server. Tell players when the server will close and when it is expected to reopen; do not begin a replacement while players can still connect.
Record the installation details that you will need to restore the previous state:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- The current Paper JAR filename and the startup command that references it.
- Every world folder, including any separate dimensions or custom world directories used by the installation.
- The main server configuration files and any files used by your service or launch script.
- Each plugin JAR and its configuration, data, and permission files.
- The Java runtime and memory settings currently used by the normal launch command.
This inventory prevents a common mistake: backing up only the world while forgetting the exact plugin and configuration state that made the old server work.
Make a backup you can actually restore
Stop the server before making the final backup so that world files and configuration files are not changing while they are copied. Include all world folders, server configuration files, plugin configuration files, and plugin JARs. Keep multiple rolling backups in a safe location rather than overwriting your only copy.
Use a naming scheme that records the server version and date, such as a folder or archive labeled with the old Paper/Minecraft version and the maintenance date. Preserve the old Paper JAR as part of that snapshot. A rollback is much easier when the backup contains the executable, worlds, plugins, and settings from the same known-good point.
Before proceeding, confirm that the backup exists at the destination you intend to use and that its contents are readable. Do not delete the old files until the updated server has started and passed your gameplay checks. If the update fails, stop the server and restore the known-good snapshot instead of trying random downgrades while the server is running.
Free tools Windows power users keep installed
One-click scans. No signup required.
Update plugins for the target version
Plugin compatibility is as important as the Paper build. For every installed plugin, visit its official release page and check whether a version supports the target Minecraft/Paper release. Update plugins deliberately; do not assume that a plugin working on the current server will work unchanged after the Paper update.
Paper supports staging plugin replacements in the plugins/update folder. Place compatible replacement JARs there, then restart the server so Paper applies them. Keep the previous plugin JARs and configurations in your backup until the new server has been verified.
Rank #3
Decide what to do with an unready plugin
If a plugin has no release supporting the target version, choose between postponing the Paper update, running without that plugin after testing the consequences, or selecting a different target version. Do not silently carry an untested plugin into production when it controls permissions, protection, economy, backups, or scheduled tasks. A plugin that loads without an obvious error can still affect gameplay, so test its commands and the features it owns.
Download the correct Paper JAR
Download the runnable server JAR from PaperMC’s official downloads page. Select the Minecraft/Paper version you decided on, not merely the newest file displayed. The newest build may require a different Java version or plugin releases that your installation is not ready to use.
Save the downloaded file outside the live server directory until you have confirmed its version and completed your backup. Paper’s update instructions rely on the JAR being named consistently with the launch command. Either rename the new file to the name already referenced by the command or edit the command to point to the new filename.
Replace Paper safely: the complete procedure
- Announce the start of maintenance. Prevent new connections and allow players time to log out.
- Stop the server cleanly. Use the normal stop action for your service, panel, script, or console. Wait until the process has exited; closing a terminal window or killing the process mid-save is not a substitute for a clean stop.
- Take or confirm the full backup. The snapshot must include worlds, server configuration, plugin configuration, plugin JARs, and the old Paper JAR.
- Stage compatible plugin updates. Put replacement plugin JARs in
plugins/updateif you are using Paper’s supported staging method, or replace them only while the server is stopped. - Preserve the old Paper JAR. Rename it or move it into the dated rollback area rather than deleting it immediately.
- Put the new Paper JAR in the server directory. Rename it to match the filename in the startup command, or change the command so its
-jarargument points to the new filename. - Start with the normal command. A typical command is
java -Xms4G -Xmx4G -jar paper.jar --nogui. Adjust the memory values and filename to match your installation; the example is not a universal sizing recommendation. - Remain at the console during startup. Watch the complete log for Java incompatibility, plugin conflicts, configuration errors, or other failures. Do not leave the process unattended until it reaches a stable running state.
- Test before reopening. Join as an operator and verify login, every world, permissions, important commands, plugin features, and scheduled jobs.
- Reopen to players only after verification. Keep the old JAR and backup available until the maintenance is clearly successful.
Read the startup log instead of guessing
The startup log is the first place to diagnose an update. A clean launch should progress through Paper initialization and plugin loading without fatal errors. Pay particular attention to messages identifying a required Java version, a missing or incorrectly named JAR, or a plugin that cannot load on the target server.
Do not treat warnings as harmless automatically. Determine which component produced each warning and test the related feature. A permission plugin warning matters differently from a message about an optional integration, but both deserve review before players return.
If the server reaches a running state but a feature is broken, stop public access while you investigate. Capture the relevant log section, identify the plugin or configuration named there, and compare it with the compatibility information from that plugin’s official release page.
Recommended Free Tools
Rank #4
Verify worlds, plugins, and scheduled work
Login testing should cover more than entering the lobby. As an operator, check each world and a representative set of gameplay actions:
- Connect with a normal client version matching the server target.
- Teleport or travel between every world and confirm that terrain and player locations are present.
- Run essential commands and verify that permissions still distinguish operators, administrators, and regular players.
- Test protection, claims, economy, chat, moderation, and other plugin features that your community relies on.
- Confirm scheduled jobs such as automated backups, announcements, resets, or maintenance tasks still execute.
- Check that world saves complete normally before declaring the update finished.
Use the same tests after a plugin-only update. A Paper update and a plugin update can fail independently, so knowing which change introduced a problem shortens recovery time.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting common update failures
The server will not start because of Java
Recheck the target version against Paper’s compatibility table and confirm the Java executable used by the launch command or service. Installing the right Java version is not enough if the server still points to an older runtime. Correct the runtime selection, then start again while watching the log.
The launch command cannot find Paper
Compare the command’s -jar filename with the actual file in the server directory. Either rename the downloaded JAR to the expected name or edit the command to use the new one. Check capitalization and the directory from which the service launches; a correct filename in the wrong directory produces the same practical result as a missing file.
A plugin fails during loading
Stop the server and identify the plugin named in the log. Check its official release information for support for the target Paper/Minecraft version. Restore the previous plugin JAR if necessary, or remove the unready update from plugins/update and restart with the last known-good plugin version. Do not repeatedly restart a production server with a plugin that is known to fail.
The server starts but gameplay is broken
Keep players out, reproduce the problem with an operator account, and isolate the affected plugin or setting. Compare the updated plugin configuration with the backed-up configuration. If the issue affects worlds, permissions, or multiple systems and you cannot identify the cause quickly, use the rollback procedure rather than making several untracked changes.
You need to roll back
- Stop the server cleanly.
- Preserve the failed update’s logs for diagnosis.
- Restore the previous Paper JAR, plugin JARs, configurations, and worlds from the same known-good backup.
- Start with the original Java runtime and startup command.
- Confirm that the old server behaves as it did before the update, then schedule a separate test of the newer target.
Paper’s guidance favors restoring a known-good backup over improvising a downgrade. Never attempt to swap JARs while the server process is still running.
Routine Paper updates versus migrations
A routine update replaces one Paper build with a newer Paper build for a planned target. The procedure above applies to that case.
Migration is different. Paper’s migration guidance says to create a full backup first. Paper can replace a Vanilla server JAR directly when moving from Vanilla to Paper, but moving from modern Paper back to Vanilla may require moving specified world-data files. Those instructions are separate from a normal Paper-to-newer-Paper update, so follow the migration guide for the direction you are taking instead of mixing its file operations into a routine update.
Manual updates versus managed control panels
Self-hosting gives you direct control over the JAR, Java runtime, files, and maintenance timing. A managed control panel may automate some of those tasks, but the underlying compatibility decisions still belong to the server owner. Compare the approach using the operational factors below rather than assuming that automation removes risk.
| Factor | Manual self-hosting | Managed control panel |
|---|---|---|
| Downtime control | You choose the exact stop and restart window. | The panel may provide scheduled tasks or one-click restarts; verify how maintenance is queued. |
| Backups and rollback | You must create and retain complete snapshots of worlds, settings, plugins, and JARs. | Look for documented backup scope, retention, restore behavior, and whether restores include plugin files. |
| Paper-build selection | You download and name the exact JAR yourself. | Check whether the panel exposes the exact Paper/Minecraft build or only a limited list. |
| Java management | You install and select the runtime required by the target version. | Confirm which Java versions the panel offers and which runtime the server actually uses. |
| Plugin workflow | You check compatibility and stage files in plugins/update or replace them while stopped. |
Verify whether plugin installation, versioning, and rollback are transparent and reversible. |
| Logs | You have direct console and file access. | Ensure full startup and error logs can be viewed and exported. |
| Automation | Scripts and scheduled jobs are your responsibility. | Panels may automate restarts and backups, but inspect their timing and failure behavior. |
| Cost | Costs depend on your hardware, network, and administration. | Pricing and included features vary by provider; verify current terms before choosing. |
Regardless of hosting model, the safe sequence remains the same: compatible target, complete backup, stopped process, deliberate plugin handling, correct Java, visible logs, and a tested rollback.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →How often should you update?
Paper describes updating as an important part of running every server, but the safest schedule is one you can support operationally. Apply security, compatibility, and bug-fix updates during planned maintenance rather than accumulating many major version jumps. Smaller, documented changes make it easier to identify which Paper build, Java change, or plugin update caused a problem.
Keep a short change record after each maintenance window: target Paper/Minecraft version, Java runtime, plugin versions changed, backup location, test results, and any warnings that remain. That record turns the next update into a repeatable procedure instead of a memory exercise.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
