How to make a Minecraft 26.2 server: Java 25, Paper 26.2 and plugins compiled for 26.x

What does Minecraft 26.2 change when you set up a server?

26.2 is the number of a Minecraft Java version, the one released on 16 June 2026. Since 2026, Minecraft no longer counts in 1.x: versions carry a calendar number, 26.1 then 26.2, where the first two digits give the year. It is not a typo and it is not a pirated build. The last version of the old series was called 1.21.11, and the one after it was called 26.1. If you land on a guide claiming 26.2 does not exist, that guide was written before June 2026.

For anybody setting up a server, a version number is not decoration: it decides three things at once. The Java version to install on the machine, first. Java is the programming language Minecraft is written in, and your computer needs that engine installed to run a server, the same way it needs a player app to open a video. The server software, next: it exists in one flavour per Minecraft version. And the plugins, finally, those small programs you drop onto a server to add commands, rules or mini games.

In short, a 26.2 server wants Java 25, a Paper 26.2 build, and plugins compiled for the 26.x series. Compiled means turned into a program ready to load: a plugin is built for one family of versions, and it refuses to start anywhere else. Those three requirements travel together, and missing one of the three is the most common reason a server will not start.

What 26.2 costs you is company. At the public reading of 24 July 2026, roughly 22 percent of servers were running the 26.x series. In other words, some of your players and some of the plugins you know are still somewhere else, on 1.21. Nothing alarming, but it is a number to hold in mind before you switch. The rest of this page starts from there: who is already on 26.2, what you need to install, how to move up without losing your world, and how to decide whether the change is worth it for your own server.

• Released on 16 June 2026, 26.2 follows the calendar numbering opened by 26.1
• It requires Java 25 on the machine, a Paper 26.2 build, and plugins compiled for 26.x
• A plugin compiled for 1.21 does not load on a 26.2 server, and the reverse is true as well
• Roughly 22 percent of the servers counted on 24 July 2026 were running 26.x

Who actually runs a Minecraft 26.2 server, and who stayed on 1.21?

There is an honest way to know what servers really run: bStats, a service that counts the servers who agree to be counted. It is not the whole planet, but it is the largest public sample available. The reading of 24 July 2026 covers 62,948 servers, and here is what it says. 1.21.11 leads with 36 percent, then 26.1.2 with 15 percent, then 26.2 and 1.21.4 at 7 percent each, then 1.21.8 at 6 percent.

Read those numbers the right way. Around 60 percent of the fleet was still on the 1.21 branch, and around 22 percent on the 26.x branch. 26.2 on its own accounted for 7 percent. That is not a verdict on the version: it is the normal rhythm of a server fleet, where people update when their plugins follow, not on release day.

Here is what it changes for you. If you are starting a brand new server, nobody is waiting for you on an older version and 26.2 is a clean choice. If you already run a server with a community on it, some of your players will end up with a game that no longer matches your server version, and you will have to tell them what to do. And if you are counting on one specific plugin you found somewhere, check first that it exists for 26.x: more often than not, that plugin, not you, decides the date of your move.

One word about the Java side, since everything is connected. In the same reading, around half of the servers were already running Java 25 and around 39 percent Java 21. The move to Java 25 is well under way at hosts and at home alike, so going to 26.2 does not make you a lonely pioneer.

• Reading of 24 July 2026, 62,948 servers: 1.21.11 at 36 percent, 26.1.2 at 15 percent
• 26.2 and 1.21.4 at 7 percent each, 1.21.8 at 6 percent
• Around 60 percent of the fleet on 1.21.x, around 22 percent on 26.x
• On the engine side: around half of the servers on Java 25, around 39 percent on Java 21

Which Java version for Minecraft 26.2? Java 25, and nothing older

The rule is short: for a server on the 26.x series, you need Java 25. Not Java 21, not Java 17. The reason is mechanical, not a matter of taste: Paper 26.x is compiled with Java 25, and a Java program does not start on an engine older than the one that built it. It is the same logic as a file saved in a newer version of an app that the older version cannot open.

What happens if you get it wrong is easy to spot, and that is good news: the server does not start at all, and the console, the text window where the server says what it is doing, prints a message naming the Java version it expects. So you never have to guess. Read the first error, install the version it asks for, start again. When a server refuses to start right after an update, this is the first thing to check.

For the other versions, keep the small table in mind, it helps when you choose. A 1.21.x server is happy with Java 21. Versions 1.18 to 1.20.4 want Java 17. And if you hesitate, the universal rule fits in one sentence: install the Java version your Minecraft version asks for, because Paper spells it out at startup.

How do you check what you already have? Open a terminal, the window where you type commands, and run java -version. The number it prints is the one that will answer when you start your server. Watch out for the classic trap on a computer that has been around: several Java versions can live side by side, and it is not always the newest one that answers. If Java 25 is missing, get it from adoptium.net: that site hands out Temurin, a free Java that asks for no account. With a host you install nothing at all: the Java version is a dropdown in the control panel, and it is the first setting to check before you blame a bug.

• 26.x server: Java 25 is mandatory, because Paper 26.x is compiled with it
• 1.21.x server: Java 21 is enough. Versions 1.18 to 1.20.4: Java 17
• Wrong version: the server does not start and the console names the one it expects
• With a host, the Java version is a dropdown in the panel, not an install on your machine

Which server software exists for 26.2: Paper, Spigot, Purpur, Folia

The official Mojang server, the one people call vanilla, does run 26.2, but it accepts no plugins at all: only datapacks, which are far more limited rule packs. If you want commands of your own, protections or mini games, vanilla is not the one you need.

Paper is the default choice, and by far the most used. It is clearly faster than vanilla and it accepts plugins written for Bukkit and Spigot, its ancestors. For 26.2 the important point is dated: Paper has published stable builds for this version since 29 August 2026, the first one being build 121. A build is a numbered compilation of the software: experimental channels exist too, and for a server where people actually play, take a build marked stable.

Spigot and Bukkit are older and slower than Paper while accepting the same plugins, so there is little reason to pick them for a brand new server. Purpur is a Paper variant that adds a long list of settings, handy when you want to bend the rules of the game without writing a plugin.

Folia deserves a paragraph of its own, because this is where badly informed pages promise anything. Folia is a Paper variant that spreads the world across several processor cores, which interests very busy servers. Two reservations. First, not every plugin is compatible with Folia: a plugin has to be written for it. Second, and this one settles it here: as of 24 July 2026, Folia had no published 26.2 build. So this page does not promise you Folia on 26.2. If Folia is essential to your project, check the build list yourself at the time you read this, and plan to stay on a version where Folia exists.

Two families not to confuse with the ones above. Fabric and NeoForge are for mods, not plugins: a modded server forces every player to install the same mods at home, while a plugin server asks nothing of anybody. Velocity is a proxy, meaning a switchboard that links several servers into one network, with a hub and separate worlds. Waterfall and BungeeCord, its ancestors, are at the end of their life.

• Paper 26.2: stable builds since 29 August 2026, the first one being build 121
• Vanilla runs 26.2 but accepts no plugins at all, only datapacks
• Spigot and Bukkit accept the same plugins as Paper, with less performance
• Folia had no published 26.2 build as of 24 July 2026: do not count on it without checking
• Fabric and NeoForge are for mods, Velocity links several servers into a network

Minecraft 26.2 server setup: the steps, one by one

Here is what you will see on screen, in order, for a brand new 26.2 server. Everything happens inside one folder: if you want to start over, you delete it and nothing is left anywhere else on your computer, apart from Java itself.

• 1. Install Java 25 and keep the default choices in the installer. Then check with java -version in a terminal that 25 is the one answering.
• 2. Create an empty folder, MyServer for example, with nothing else inside it. A server that shares its folder with unrelated files always ends up creating confusion.
• 3. Download Paper 26.2 from the official Paper site, papermc.io, on its Downloads page, choosing a build marked stable. You get a single .jar file, the format Java programs come in: that file is the entire server, so put it in your folder.
• 4. Run it once from a terminal opened inside that folder, with the java -jar command followed by the file name. The server stops straight away, which is normal: it has just created eula.txt, which asks you to accept the Mojang terms of use. Open it, replace false with true, and save.
• 5. Run the same command again. This time the world generates and the console eventually announces that the server is ready. Type stop to shut it down cleanly, never the window close button.
• 6. Open server.properties, the settings file created on that first launch: game mode, difficulty, maximum number of players, view distance. Leave online-mode on true, and read the mistakes section further down to see why.
• 7. Drop your plugins compiled for 26.x into the plugins folder the server just created, then restart. Every plugin that loads announces itself in the console, and every plugin that is refused leaves a readable error in the same place.
• 8. Open Minecraft on version 26.2, go to Multiplayer then Add Server, and type localhost, the address that means this computer. You join your own server. For your friends you need a real address and port 25565.

How to update your server to 26.2 from 1.21 without losing your world

This is the question that scares people, and it deserves a method rather than a rushed tutorial. A Minecraft world is a set of folders sitting next to the server: the main world, the Nether, the End. They do not disappear when you change the version of the server software. What can go wrong is the conversion of those folders to the format of the new version, and the plugins that fail to follow.

Step zero, non negotiable: the backup. Stop the server with the stop command, wait until it has finished writing, then copy the whole folder somewhere else, onto another drive or into the cloud. The whole folder means the world, the configurations, the plugins folder and the settings files. That copy is your only time machine: the world is converted on the first launch on 26.2, and you are better off assuming that conversion cannot be undone.

Next step, the plugin inventory, and it is usually the one that fixes your date. List what sits in your plugins folder and ask yourself, for each one, whether it exists for 26.x. The ones that do, you replace with their 26.x version. The ones that do not leave you three options: live without them, find an equivalent, or have a plugin built that does the same job for your version. Never keep a .jar meant for 1.21 hoping it will squeeze through: it will not load, and it can make noise in the console at startup.

Only then, the server software itself. Install Java 25 next to your Java 21 or in its place, swap the Paper .jar for the 26.2 one, and start. Stay in front of the console for the whole conversion without closing the window: the first launch takes longer than usual and that is expected. When the server says it is ready, go in game and take the tour: the spawn, a base you know well, the Nether, the chests that matter.

The right reflex, if you can afford it, is a rehearsal before you play for real. Duplicate your server folder, do the update on the copy, play on it for half an hour, note what breaks, then start over cleanly on the original. And do not delete the backup the same evening: keep it for a few days, long enough for your players to report what you did not see.

• Clean stop, then a copy of the whole folder: it is your only way back
• Plugin inventory before anything else: it is what decides your date
• Java 25 installed, then the Paper .jar swapped for the 26.2 one
• The first launch takes longer than usual: let the console do its work
• Rehearse on a copy of the folder, then update the real one, and keep the backup

Your plugins on 26.2, and what ViaVersion never does

A plugin compiled for the 26.x series requires a 26.x server. That is the sentence to remember, and it works both ways: your favourite plugin from the 1.21 days will not load on your new server, and a 26.x plugin will not load if you go back down. It is not stubbornness, it is simply how a Java program is built for one family of versions.

Then comes the Via family, very often explained badly, and that is where servers get themselves into trouble. Three plugins, three distinct jobs. ViaVersion lets a newer client join an older server. ViaBackwards does the opposite: an older client on a newer server. ViaRewind, on top of the other two, is what you need for 1.8 and 1.7 clients on a server running 1.9 and above. The word client means the game installed on the player side.

Translated for a 26.2 server. If your players stayed on 1.21 and your server moved to 26.2, what you need is ViaBackwards, on top of ViaVersion, and not ViaVersion on its own. And above all, none of the three changes the version of your server: your server stays a 26.2 server, with its blocks, its rules and its plugin requirements. The Via family settles the version of the players, never the version of the machine.

Beyond that, a brand new 26.2 server is a survival world like any other. What makes it yours is what happens on it: a welcoming spawn point, rules that hold, an economy, protections, a mini game that exists nowhere else. With Minax you describe your plugin in plain English, the way you would explain it to a friend, and you get back a .jar compiled for your version, 26.2 included. Before you drop it on your server you can try it in game: the online test server gives you 5 minutes a month without a plan, 15 with a credit pack, and it only hosts one game at a time, so there is a queue. A robot player can also replay your scenario to check that the plugin does what you asked for. To create, a credit pack paid once, with no subscription: 50 credits for €17.99. At today's rates, we estimate that half of plugins come to between 15.4 and 30.7 credits, edits included, and that one in ten goes over 42 credits (estimate from 25/09/2026, not a guaranteed price).

Where should your 26.2 server run: your PC, a host, or free online?

Three families, no brands and no prices, because offers change all the time. On your own PC you pay nothing, but the machine has to stay on while the others play, and you are the one opening port 25565 on the router, which is called port forwarding, or going through a tunnel tool such as playit.gg or ngrok to avoid that setting. Hamachi, the old method, forces every player to install a program on their side, so skip it. One more detail: the public address of a home connection changes from time to time, and you then have to hand out the new one.

With a host you pay every month and the server stays online when your PC is off. What counts when you choose: RAM that is genuinely dedicated to you, RAM being the working memory the server is allowed to use, a fast processor core, a machine close to your players, file access so you can drop in your own plugins, backups you can download, and protection against flooding attacks. For 26.2, add one question to your list: does the panel actually offer Paper 26.2 and Java 25?

Free online services exist too, Aternos being the best known. The limits are out in the open and worth knowing: a queue before it starts, an automatic shutdown when nobody is playing, performance shared with other servers, and, on Aternos, only the plugins from its catalogue: it refuses the ones you upload yourself, the ones Minax builds included. To discover 26.2 with two or three friends, that is perfectly fine. For a server meant to last, it is short. Mojang Realms are simple and paid, but they accept no Java plugins at all: they do not suit anybody who wants to customise.

On the hardware side, keep two orders of magnitude in mind. For a few friends in survival with a handful of plugins, 2 to 4 GB of RAM is reasonable; for 20 to 30 players or a lot of plugins, aim for 6 to 8 GB instead. And above all, smoothness depends more on one fast processor core than on a mountain of memory. The measurement that matters is called TPS, the number of game ticks per second, with a target of 20: when it drops, the world lags, and adding RAM often changes nothing.

And where does Minax fit? Minax does not host servers and does not sell hosting. It builds the plugins that make your server yours, compiles them for your version, and lets you try them in game before your own server even exists. The server that welcomes your players runs on your PC or with the host of your choice.

Should you update to 26.2, or stay where you are?

The honest answer depends on your players, not on fashion. Here is how to settle it without telling yourself stories.

Go to 26.2 without hesitating if you are starting a brand new server: nobody is waiting for you on an older version, and you begin on the series the fleet is slowly joining. Go as well if the new features of that version are the point of your server, if every plugin you depend on already exists for 26.x, and if your host does offer Paper 26.2 and Java 25. It is the most recent version named on this page, 26.2, and a page for a newer one may well exist by the time you read this: the reasoning does not change.

Wait, on the other hand, if a plugin your server makes no sense without only exists for 1.21, if your community is large and slow to change versions, or if your current season needs to finish cleanly. Waiting is not falling behind: in the reading of 24 July 2026, around 60 percent of servers were still on the 1.21 branch, and plenty of them run beautifully.

Three paths sit between the two extremes, and the third one is often the smartest. You can move in one go, on an evening announced in advance. You can wait for the end of your season and open the next one straight on 26.2, which settles the converted world question since you generate a new one. Or you can set up a small 26.2 server next to yours, invite two or three volunteers onto it, and run your plugins there for a week before deciding.

Whatever you choose, having your plugins built does not lock you in: Minax targets 1.12.2 to 26.2, so you can ask for the same mechanic for your current version today and for 26.2 on the day you move. Versions 1.0 to 1.15 are the exception: Paper no longer publishes anything for them, and you should not start a new server on one.

• Brand new server: 26.2 is a clean choice, nothing holds you back
• An essential plugin missing on 26.x: it sets your date, not the calendar
• End of season near: open the next one straight on 26.2, with a fresh world
• Large group: set up a small 26.2 server alongside and test for a week before switching

The mistakes that cost you an evening on a 26.2 server

A 26.2 server that refuses to start, or that disappoints, often falls into one of these seven mistakes. Each of them takes a few minutes to fix once you know where to look.

• Leaving Java 21 in place. Paper 26.2 does not start without Java 25, and the console prints the version it expects. Check with java -version that 25 is the one answering, especially if several versions live on the machine.
• Keeping your old 1.21 plugins in the plugins folder. They will not load on a 26.x server. Take them out, replace them with their 26.x version, and read the console at startup to see who loaded and who failed.
• Counting on ViaVersion to change the version of the server. It does not do that, and neither do ViaBackwards or ViaRewind. They settle the version of the players who connect, and nothing else.
• Hoping for Folia on 26.2. As of 24 July 2026, no 26.2 build of Folia had been published. If your project depends on it, check the list yourself at the time you read this rather than trusting a promise.
• Updating without a backup. Copy the whole folder before you touch the Paper .jar: the world is converted on the first launch and you are better off treating that as final.
• Flipping online-mode to false so a friend without the game can join. It is common, around three counted servers out of four do it, but it opens the door to name spoofing, where anyone can connect using the name of somebody else. If you do it, know what you are taking on and at least protect your staff.
• Downloading a file called 26.2 from a random site. Take Paper from the official Paper site, papermc.io, choosing a build marked stable: a .jar from anywhere else can contain something quite different from what its name says.

Frequently asked questions