On this page
Key takeaways
5- Paper 26.3 is on the stable channel, with build 178 listed on 12 October 2026.
- Paper 26.3 requires Java 25; confirm your panel or host can provide it.
- Check white-list and enforce-whitelist in server.properties before launch.
- Review data packs, resource packs and plugins on a test copy before updating live.
- Back up, stop fully, replace the Paper jar, then monitor the startup log.
This update is for owners deciding whether to move a Java server to Minecraft 26.3, also called Wilderness Bound. You will find what changed on the server side and a safe update path for a VPS or a hosting panel.
Check Paper 26.3's stable status
Minecraft Java 26.3 was released on 15 September 2026. Paper 26.3 has since moved to the stable channel: Paper's download page lists build 178 as the current release, built on 12 October. That changes the picture from our earlier Paper 26.3 update checklist, which covered the beta period. Stable means the channel has changed; you should still check your own plugins and test your server before opening it to players.
Paper lists Java 25 as the minimum for 26.3. The Paper download page and Paper's update guideSource site are the places to check the build and update steps.
Check Java 25 before replacing the server jar
First check which Java version your server actually uses. A VPS can check from its shell. On Pterodactyl, the Java version comes from the Docker image selected in the Startup tab. The official Pterodactyl yolks repository includes a Java 25 image, but your host must make it available in your panel. Multicraft owners should ask their host which Java versions are available.
java -versionIf the output is below Java 25, arrange the Java change before starting Paper 26.3. On Pterodactyl, check the Startup tab's Docker image selection. If Java 25 is not offered, ask the host to provide it. On Multicraft, ask the host to confirm the runtime before changing the selected server jar.
Review the whitelist and pack formats
In 26.3, white-list in server.properties defaults to true. enforce-whitelist defaults to false; when enforcement is enabled, players who are not listed are kicked after the whitelist is reloaded. Check the values in your own file before launch, especially if you expect an open public server.
white-list=true
enforce-whitelist=falseVersion 26.3 also changes technical pack formats: the data pack format is 121.0 and the resource pack format is 97.1. The game reports data version 5023 and protocol version 777. Packs made for older formats may need their format updated, so check your data packs and resource packs on a test copy before asking players to join.
The update adds the /compute and /posteffect commands, as well as item components including minecraft:block_transformer, minecraft:cooking_fuel and minecraft:brewing_fuel. These details matter most to owners maintaining custom packs, commands or plugin integrations. The update also adds the dappled forest biome, poplar wood, cushions, straw beds, shelf mushrooms and abandoned camp structures.
Check plugins and client version support
Do not assume a plugin works because the server starts. Check each plugin's project page for 26.3 support and test the features players use on a copy. Paper recommends keeping backups of world folders, server configuration, plugin configuration and plugin jars. Our Paper update guide covers a broader compatibility check, and our backup guide explains how to plan and test a restore.
ViaVersion lists 26.3 on its project page and can let newer Java clients join an older server. It does not let older clients join a newer server; ViaBackwards or ViaRewind are the companion projects for that direction. If you use ViaVersion, check its project page and test the protocol translation you need before relying on it.
Update on your server or panel
Make a backup and test the update on a copy first. Paper's update guidance says to stop the server fully, replace the Paper jar, then restart and watch the log. Keep several backups and stay present while updating. For a fuller checklist, see our earlier Paper 26.3 checklist.
- Back up the world folders, server configuration, plugin configuration and plugin jars. Keep a separate copy of the backup.
- Stop the server fully. Check that Java 25 is selected, then download the Paper 26.3 stable jar from Paper's download page.
- Replace the old Paper jar and give the new file the name your startup command expects. If you are also updating plugin jars, Paper says to put them in
plugins/updateso they are applied on restart. - Start the server and watch the log for errors. Test joining, core plugin features, packs and whitelist access before opening to players.
- Use the Backups tab to make a backup. Stop the server from the Console and wait for it to stop fully.
- In the Startup tab, check the Docker image for Java 25. Ask your host if the image is not available.
- Use File Manager or SFTP to upload the Paper 26.3 jar and replace the old jar. Match the filename to the startup command. Put updated plugin jars in
plugins/updateif following Paper's update method. - Start the server from the Console, watch the log, and test before inviting players back.
- Make a backup using the panel's available backup option. Stop the server from the console and wait for it to stop fully.
- Use Files or FTP to upload the Paper 26.3 jar, then select the right jar in the panel's JAR selection. Ask your host to confirm Java 25 support and change the runtime if needed.
- Start the server from the console. Read the startup log and test your plugins, packs and whitelist before opening the server.
