How to Update a Paper Minecraft Server and Its Plugins Safely
Paper's documentation recommends updating at least once per week, because Paper is patched often. The safe version of that advice is a short routine: back up, update plugins, update Paper while the server is stopped, then read the log. This guide walks through it.
It follows Paper's update and troubleshooting pages, checked on 2026-11-17. The documentation is written for people running their own start script, so where our panel does the job differently we say so. If you are moving from another server type rather than updating Paper, read the migration guide instead.
- Back up first. Paper says to include world folders, server configuration files, plugin configuration files and plugin jars.
- Plugins can be updated with an
updatefolder insideplugins. Put the new jars there and restart. - Stop the server before replacing the Paper jar. Paper warns that replacing it while running may cause issues.
- Paper does not recommend automatic updates, because of plugin conflicts. Be present and read the startup log.
- Downgrading a world is not supported. If an update goes wrong, restore the backup.
On this page
Step 1: Back up
Paper's documentation says to back up the world folders, the server configuration files, and the plugin configuration files and plugin jars, and to keep backups from more than one point in time. It adds that updating Paper itself is unlikely to need a restore, but a plugin that malfunctions or an accident might.
- Back up now
On the Backups tab choose Back up now and select Whole server, because World and settings may not include everything under
plugins. - Keep it
Click the star on the backup so automatic cleanup does not remove it before you have confirmed the update works.
More on restores is in the backup and restore guide.
Step 2: Update plugins
Paper's documented method uses an update folder so plugin jars are swapped safely at startup:
- Create the folder
On the Files tab, create a folder named
updateinsideplugins. - Add the new jars
Upload the new version of each plugin you want to update into
plugins/update. Keep the same plugin names. Do not touch the jars outside that folder. - Restart
Restart the server. Paper's documentation says not to remove or modify the plugins outside the
updatefolder as part of this step.
Step 3: Update Paper
Paper's documentation describes the manual method as: download the new jar, stop the server, rename the file to match the name in your start command, replace the old jar, then start. It warns that replacing the jar while the server runs may cause issues, and says not to replace any jar in a running server unless you know exactly why.
- On ChicagoServers the server software and launch line are managed for you, and the launch line is staff-only. Look on the Startup tab for a version or build field, and if there is none, contact support and ask for the Paper version you want.
- Always stop the server first. Use Stop on the Console tab and wait until it is offline.
- Paper also describes an alternative where you upload the new jar and point the start script at it, taking effect on the next restart. Both methods are described as valid, but that one depends on editing the start script.
Step 4: Start and read the log
Start the server and watch the Console tab. Paper says to check the startup log for plugin conflicts or issues. After startup, the useful things to read are the first error or stack trace and which plugin it names. If something is wrong, the plugin troubleshooting method is in the Paper crash and plugin troubleshooting guide.
For performance after an update, take a profile rather than guessing. See the lag and spark guide.
Automatic updates and downgrades
- Paper does not recommend automatic updates because of possible plugin conflicts. It says to stay present during an update and watch the log afterwards, and if you do automate, to have a working backup strategy in place.
- Paper's troubleshooting page says downgrading a world is not supported. A world saved by a newer version will not open on an older Paper.
- Paper's troubleshooting page warns that forcing the server to start on a newer world with the
-DPaper.ignoreWorldDataVersion=trueflag is unsupported and may permanently corrupt the world. Restore the backup instead.
Frequently asked questions
How often should I update Paper?
Paper's documentation says to update at least once per week to stay patched against bugs. In practice that means checking weekly, backing up, and updating when a new build is available, rather than updating blindly.
How do I update plugins on Paper?
Create an update folder inside plugins, place the new plugin jars in it, and restart the server. Paper's documentation says not to remove or modify the plugins outside that folder.
Can I replace the Paper jar while the server is running?
No. Paper warns that replacing the jar while the server runs may cause issues. Stop the server first, replace the jar, then start it.
Can I go back to an older Minecraft version after updating?
Not safely. Paper says downgrading a world is not supported, and that forcing a newer world to load on an older version may permanently corrupt it. Restore the pre-update backup instead.
Should I turn on automatic updates?
Paper's documentation does not recommend it, because of possible plugin conflicts. If you do automate updates, keep a working backup strategy and watch the log afterwards.