How to make a Minecraft 1.21 server, the branch most servers still run

Why do most Minecraft servers still run 1.21?

Look at what servers actually run, and 1.21 is still the middle of the road. The clearest public count comes from bStats, a small plugin many owners install that reports, without naming anyone, which version their server is on. In the count taken on 24 July 2026, across 62 948 servers, 1.21.11 came first on its own. Add the whole 1.21 branch together and you get roughly six servers out of ten. The calendar versions, 26.1 and 26.2, held about two out of ten between them.

That is not inertia, it is a choice a lot of people make on purpose. A version that has stopped moving is a version where everything already exists. The plugins are published and tested, the guides match what you see on screen, and the person you ask for help has run the same thing. When you open a brand new server, that is worth more than having the newest blocks.

It also decides who can walk in. Since 2026, Minecraft Java is numbered by calendar year: 26.1, then 26.2, released on 16 June 2026. Those numbers are not mistakes, and 1.21.11 was the last version of the old numbering. Plenty of players have not opened their launcher, the little program that starts the game, in months. A 1.21 server asks nothing of them, and that alone fills a server faster than any feature list.

So the honest answer to the question this page is named after is short. Building a Minecraft 1.21 server in 2026 is not falling behind. It is picking the version with the most company, the most plugins and the fewest surprises, and leaving the newest branch to the servers that actually need it.

• bStats count of 24 July 2026, across 62 948 servers: 1.21.11 first, at 36 %
• Behind it, 26.1.2 at 15 %, then 26.2 at 7 %, 1.21.4 at 7 % and 1.21.8 at 6 %
• Roughly 60 % of that count sat somewhere in 1.21, and about 22 % in 26.x
• 1.21.11 closed the old numbering, and it is still the most common version out there

Java 21 for Minecraft: which Java version does a 1.21 server need?

Minecraft Java Edition carries that name because the game is written in Java, a programming language. To run a server, your computer needs Java installed, roughly the way it needs a player app to open a video file. The version matters, and for a 1.21 server the answer is short: Java 21. Every Minecraft version from 1.20.5 onwards asks for at least Java 21, and the whole 1.21 branch sits inside that rule.

Newer is not safer here. Java 25 is what Paper 26.x requires, because Paper 26.x is built with it, and it was running on about half the servers in that July count. Around four in ten were on Java 21, which is broadly the 1.21 crowd. Install what your Minecraft version asks for, nothing more: it is one fewer thing that can go wrong on a first launch.

If you get it wrong, nothing subtle happens. The server refuses to start and writes the version it expects into the console, the text window where the server says what it is doing. Read that line before you look anywhere else, because it names the answer. Older branches want older Java: 1.18 to 1.20.4 run on Java 17, and anything before 1.17 is a different world again. The day you move up to 26.x, you install Java 25 and have this same conversation once more.

• A 1.21 server: Java 21, and nothing else to decide
• 1.20.5 and later want Java 21 at least, and 1.18 to 1.20.4 want Java 17
• Java 25 belongs to 26.x servers, because Paper 26.x is compiled with it
• Wrong version? Paper refuses to start and prints the one it expects

Paper 1.21, Spigot, Bukkit or Folia: what actually runs your server?

The server software is the program that holds the world and applies the rules. The official one from Mojang, called vanilla, accepts no plugins at all. Plugins are the small programs that add commands, rules and mini games to a server, and vanilla only takes datapacks, which are far more limited rule packs. If you want plugins, vanilla is not the one.

Paper is the default answer, and it is the one to download for 1.21. It is by far the most widely used, clearly faster than vanilla, and it accepts plugins written for Bukkit and Spigot, its two ancestors. Spigot and Bukkit still work and take the same plugins, but they are older and slower than Paper, so there is little reason to start there today. Paper publishes builds for each point release, a build being a numbered release of the software, so download the one that matches your exact 1.21 version.

Two variants exist if you want to go further. Purpur is Paper with a lot more settings to tweak, useful when you like turning dials. Folia spreads the world across several processor cores, which suits a server with many players far apart, but some plugins are not compatible with it, so check the builds published for your exact version and check your plugin list before you commit. Minax knows how to generate Folia compatible plugins when you ask for them. And if you ever want several servers linked together, a lobby plus a minigame world for instance, that job belongs to a proxy called Velocity, which sits in front and passes players between them.

• Vanilla: official, no plugins, datapacks only
• Paper 1.21: the default, fast, takes Bukkit and Spigot plugins
• Spigot and Bukkit: same plugins, older and slower than Paper
• Purpur for more settings, Folia for multiple cores with a compatibility check first
• Velocity is the proxy that links several servers into one network

Minecraft 1.21 server setup: the steps, one by one

Here is what happens on screen, in order. Everything lives inside one folder, and you can start again from scratch by deleting it: nothing gets installed elsewhere on your computer except Java itself. Take ten minutes and do it once properly, and you will never have to think about it again.

• 1. Install Java 21. Download it from adoptium.net, the site that hands out Temurin, a free version of Java with no account to create. Run the installer, keep the default choices. If you already have another Java, installing 21 alongside it is fine.
• 2. Create an empty folder, My121Server for example, then download Paper for your 1.21 version from papermc.io, the official Paper site, on its Downloads page: take a build marked stable. You get a single .jar file, the format Java programs come in: that file is the entire server.
• 3. Open a terminal, the window where you type commands, inside that folder, and run the java -jar command followed by the file name. The server stops right away, which is normal: it has just written an eula.txt file that asks you to accept the Mojang terms. Open it, change false to true, save.
• 4. Run the same command again. This time the server builds the world and writes in the console that it is done. Your 1.21 server is alive. Type stop to shut it down cleanly, never close the window on it.
• 5. Open server.properties, the settings file created on that first run. Game mode, difficulty, maximum players, the message shown in the server list. Leave online-mode on true, we come back to that in the mistakes below.
• 6. Drop your plugins, which are .jar files too, into the plugins folder the server just created, then restart. Each plugin that loads says its name in the console at startup, and anything that fails complains in the same place.
• 7. Start Minecraft on the same computer, go to Multiplayer then Add Server, and type localhost, the word that means this machine. You join your own server. For your friends you need a real address, which is two steps down this page.

How much memory does a 1.21 server need?

RAM is the working memory a computer lends to a program while it runs. A Minecraft server keeps the loaded parts of the world in there, so the more players you have and the further each of them sees, the more it wants. For a few friends in survival with a handful of plugins, 2 to 4 GB is a sane order of magnitude. For twenty or thirty players, or a long plugin list, plan on 6 to 8 GB, and more again for a world that has been explored for months.

One number matters more than the memory, and it is the one people forget. A Minecraft server recalculates the world twenty times a second, and that rhythm is called the TPS, for ticks per second, with 20 as the target. When the TPS drops, everything feels rubbery: blocks come back after you break them, mobs teleport. What holds the TPS up is the speed of a single processor core, not the amount of RAM, so a machine with a fast core and less memory usually beats the opposite.

The slider below gives an order of magnitude, never a promise. Your world, your plugins and your players all change the answer, and the only honest way to find your number is to watch your own server with people on it.

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

Three families, with no brands ranked and no prices quoted, because rates move constantly and a page cannot keep up with them. On your own PC it costs nothing, but the machine has to stay awake the whole time your friends play, and opening the door on your router is your job. With a host you pay every month, you pick the memory and the region of the machine, and the server stays up while you sleep.

What to actually look at before you pay, whichever family you choose: memory genuinely reserved for you rather than shared, a fast processor core, a machine geographically close to your players, file access through FTP or a file manager so you can drop in your own plugins, backups you can download and keep, and protection against attacks that flood the connection. A host that hides the plugins folder is useless to anyone who wants a custom server.

Free online services exist too, and Aternos is the best known. The limits are stated openly: a queue before your server 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. Good for trying things out with two friends on 1.21, less good for a server you want people to come back to. And Realms, the official Mojang subscription, is simple and steady but takes no Java plugins at all, so it cannot become your server.

How do you open your 1.21 server to your friends?

A Java player joins with an address and a port. The address is either the public IP address of your connection, the string of numbers that identifies your router on the internet, or a domain name pointing at it. The port is the numbered door the game knocks on, 25565 by default. Your friends type the two together, separated by a colon, in Multiplayer then Add Server.

If the server runs at home, your router keeps that door shut. Two ways round it. Port forwarding tells the router to send everything arriving on 25565 to your computer, and you set it from the router settings page. Or a tunnel tool such as playit.gg or ngrok hands you a public address without touching the router at all. Hamachi is the old way and forces every single friend to install it too, so leave it alone. One more trap: the public address of a home connection changes from time to time, and when it does you have to hand out the new one.

With a host, all of this disappears. You get a fixed address and an open port on day one, and the server answers when your computer is off. If you are weighing that up, the hosting page goes through what matters before you pay.

A 1.21 server with plugins: what loads, and what ViaVersion really does

Here is the rule that saves the most evenings. A plugin is compiled for a family of versions, and it loads on a server from that family. A plugin built for 26.x needs a server in 26.x. A plugin built for 1.21 belongs on your 1.21 server. Inside the branch things are usually gentle, and a plugin published for 1.21.4 often runs on 1.21.11, but that is a habit rather than a guarantee: when a plugin names an exact version, believe it and match it.

This is where 1.21 quietly wins. Because the branch has been settled for a long time and carries most of the fleet, almost everything published has a 1.21 build. You will rarely find the plugin you want and then discover it stops one version short of yours, which is the usual frustration on a brand new branch.

Now the family everybody misunderstands. ViaVersion lets a player on a NEWER client join an OLDER server: on your 1.21 server, that is what lets a friend whose launcher has already jumped to 26.2 come in without downgrading. ViaBackwards does the opposite, letting an OLDER client onto a newer server. ViaRewind goes further down again and is what very old clients, 1.8 and 1.7, need on top of the other two to reach a 1.9 or later server. None of the three ever changes the version of the server. Your 1.21 server stays a 1.21 server, with 1.21 blocks, 1.21 rules and 1.21 plugins, whoever is knocking at the door.

• A plugin compiled for 26.x will not load on your 1.21 server, with or without ViaVersion
• ViaVersion: a newer client joins your older server
• ViaBackwards: an older client joins a newer server
• ViaRewind: what 1.8 and 1.7 clients need in addition, to reach a 1.9 or later server
• None of them changes the server version, ever

Which plugins make a 1.21 server yours, and how do you ask Minax for them?

A fresh Paper 1.21 server is just another survival world with your name on the folder. What makes people come back is what happens on it: a spawn point that welcomes them, rules that hold when you are asleep, a bit of economy, some protection, a game nobody else has. All of that is plugins. You can download the ready made ones from the community catalogues, Hangar, which the Paper team runs, and SpigotMC, and you should, but the piece that makes your server yours rarely exists as a download.

That is the part Minax builds. You describe the plugin in plain English, the way you would explain it to a friend, and you get back a compiled .jar for your version, meaning a program ready to load on Paper 1.21. Before it goes near your server, you can try it in game on an online test server: 5 minutes a month without a plan, 15 with a credit pack, and one game at a time, so there can be a queue. A robot player can also replay your scenario to check the plugin does what you asked, when a launcher is free and there is enough time left in the session.

Creating or editing a plugin needs credits, in packs paid once, with no subscription: 50 credits for €17.99 VAT included. To edit a plugin you already made, there is also a pack of 15 credits for €5.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). Credits from a pack stay valid for 36 months. The plans and top ups live on the pricing page. Here are three requests ready to paste, written for a 1.21 server that is just opening its doors.

Should you stay on 1.21, or is it time to move to 26.x?

Staying on 1.21 is defensible, and the numbers back it up rather than excuse it. Most servers are there, the plugin shelves are full, and your players do not have to do anything. If your server works, your plugin list is happy and nobody is asking for the newest content, moving costs you effort and buys you very little. Version churn is not a virtue.

There are three honest signals that it is time to move. The first is your players: if the people you actually play with have updated their game and keep asking for what is new, that is a real reason, and no server survives its own players losing interest. The second is a plugin you depend on that stops publishing for 1.21, because rebuilding around a dead plugin costs more than a version jump. The third is the fleet itself: 26.x held about two servers out of ten at that July count, and the day that share passes 1.21, the plugin world will follow it.

When you do move, know what the move actually involves. You install Java 25, because Paper 26.x is compiled with it. You download a Paper build for the new version, 26.2 being the latest release, out since 16 June 2026. And every plugin has to exist in a 26.x build, which for a custom plugin means asking for it again against the new version. Minax can target anything from 1.12.2 to 26.2, so a plugin you had built for 1.21 can be rebuilt for 26.x when you are ready, without starting from a blank page.

One last piece of advice that costs nothing: keep a copy of your world folder before any version change, on a different disk or in the cloud. A world opened by a newer version does not go backwards cleanly, and a backup is the difference between a bad hour and a lost season.

• Stay if your server works, your plugins are happy and nobody is asking for more
• Move when your own players have moved, not when the internet says to
• Move when a plugin you rely on stops shipping builds for 1.21
• Moving means Java 25, a Paper build for the new version, and every plugin rebuilt
• Back up your world folder before any version change, always

The mistakes that cost you an evening on a 1.21 server

Nearly every 1.21 server that refuses to start, or that quietly disappoints, has fallen into one of these. None of them is hard to fix once you know where to look, and most announce themselves in the console if you read it.

• Installing Java 25 for a 1.21 server because newer sounds safer. Java 21 is what 1.21 asks for. Read the version Paper names at startup and install exactly that.
• Downloading a plugin without checking the version it was built for. A 26.x plugin does not load on 1.21, and the console says so at startup instead of leaving you guessing.
• Expecting ViaVersion to update the server. It lets players on other versions connect, that is all. A 1.21 server with ViaVersion is still a 1.21 server, and a 26.x plugin still will not load on it.
• Mixing point releases without looking. A plugin that names 1.21.11 on a 1.21.4 server may load and misbehave rather than refuse outright. Match the exact number when the plugin asks for one.
• Switching online-mode to false so a friend without an account can join. It is common, but it lets anyone connect under somebody else name, and you will not be able to tell them apart. Know what you are taking on before you do it.
• Confusing mods with plugins. Fabric and NeoForge run mods, and every player has to install the same ones at home. A plugin server asks nothing of its players: if your friends should only have to click Join, stay with Paper.
• Closing the console window instead of typing stop. The world is written to disk on a clean shutdown, and killing the window is how people lose an afternoon of building.

Frequently asked questions