Moving your Minecraft server to a new version without losing the world
Last updated November 18, 2026
Open that server's Settings tab, open the Version and performance group, pick the new software or version in its Version and software section and press Change version. Nothing is applied when you press it — the request takes a restore point of the whole server first, and the new version is applied only once that restore point is ready, so a failed one leaves the server exactly as it was. That restore point takes one of the server's 10; with 10 already there, the oldest goes, and every restore point is kept at most 30 days. Going up in version is routine; going down is the dangerous direction, because Minecraft cannot load a world saved by a newer version and the server simply will not start until you go back up or restore. Modpack servers cannot change version or software at all, and a Java runtime you pinned by hand stays pinned across the change.
- Open the Version and performance group on the Settings tab
- Pick the target version, the software, or both
- Decide whether to restart after the change is applied
- Press Change version and read every warning the confirmation shows you
- Confirm and watch for the backup banner
On this page · 11 sections
A new Minecraft release lands, or the mod you want exists for one version only, and the question is always the same: can the server move without taking the world into the bin with it. On uniz.host it can, and the copy is made for you before anything is touched. What follows is what the machinery does, in what order, and which direction ends in a server that will not start.
Nothing is applied the moment you press the button
The control lives in the Version and software section of the Version and performance group on that server's Settings tab. Pick the new software or version, then press Change version: that opens a confirmation rather than doing anything. The important sentence is printed both under the selects and at the foot of that confirmation — a safety step runs first, and the change applies only after it succeeds. With restore points that step is a restore point of all the server's data.
Sending the request does exactly two things: it takes a restore point of the server, and it stamps the change as pending. Nothing about the version or the software has moved yet. You get a confirmation that the safety step started, the section grows a banner saying the change will apply automatically once it completes, and the change button stays disabled while that banner is up, so a second request cannot stack on the first.
Usually within a minute, a background loop sees that the restore point is ready and settles the request:
| Restore point outcome | What happens to the change |
|---|---|
| Ready | The new version and software are written to the server, the mods list is cleared if that was part of the deal, and the pod template updates |
| Failed | The pending change is discarded unapplied, the server keeps its current version, and the failure is recorded and sent as a notification |
| The restore point never became ready, or is gone | Treated as a failure — nothing is applied |
That is the whole safety story: the only path to a changed version runs through a restore point that provably exists. It also survives you closing the tab — the request is settled server-side, not by the page you were looking at.
The safety restore point takes one of your 10
The restore point taken here counts toward the server's 10 like every other kind. Ten already there does not stop the change: once this one exists, the oldest goes. Like every restore point, it is kept at most 30 days, so a pre-change state you want to keep longer should be exported and downloaded.
A restore point takes seconds and can be taken while the server runs, on Java and Bedrock alike, so nobody is kicked. A running Java server is asked to save the world first; a point taken on a running server holds what the game had saved.
Change the version, step by step
Open the Version and performance group on the Settings tab
On a Minecraft server's Settings tab, choose the Version and performance group. Its first section is Version and software: the Current line shows the software and the version pinned today, with an Update available marker when your software has published something newer than your pin. You need the settings permission — the owner has it, a team member needs it granted.
Pick the target version, the software, or both
The version list is fetched per software, from that project's own build catalogue, so you can only pick a version your software actually publishes a build for. Above the concrete versions sits LATEST (auto-update).
The Software select appears for Java servers on the thirteen switchable builds. Switching software re-checks your pinned version against the new software's catalogue and moves you to its newest build if that software never made your version. A standard Bedrock (BDS) server has no Software select — it has a version field, plus a one-way "Switch to Endstone" that works only while the server is stopped. An Endstone server has no version field at all: the platform updates it at its next restart, see Endstone on a Bedrock server.
Decide whether to restart after the change is applied
A checkbox under the two selects offers to restart once the change lands, and it is pre-ticked when the server is running. Leave it ticked and the change is live as soon as the restore point settles. Untick it and the change is stored while the running pod keeps the old version until its next restart. On a stopped server it changes nothing: the new version is what boots next time you start it.
Press Change version and read every warning the confirmation shows you
Change version stays disabled until you have picked something different. Pressing it opens a confirmation with one line saying what changes to what, such as Paper 1.21.4 → Paper 1.21.5. Under it are the red boxes: every one names a real failure mode, and more than one can appear at once. The next three sections walk through them.
Confirm and watch for the backup banner
The confirmation's own Change version button stays disabled until every acknowledgement in view is ticked. After you confirm, the banner in the Version and software section is your progress indicator; when it clears, the Current line shows the new software and version.
Downgrading is the direction that breaks worlds
Going up is routine. Going down is the one that ends with a server that will not boot, and the dialog says it plainly: Minecraft cannot load worlds saved by a newer version, so the server will not start until you change back or restore. There is no repair, no converter, no fixing it from the console — the world file is simply newer than the game reading it.
The dialog raises this warning whenever it can prove the target sits below your current pin in the same catalogue, and a softer version of it whenever the direction cannot be proven either way — your server is on LATEST, your pinned version has been dropped from the catalogue being compared against, or you switched to software whose newest build predates your current version. That softer wording is the platform refusing to guess about your world, not the platform being vague. If you are downgrading on purpose — because a mod you need never got updated — do it knowing the return trip is a restore point, and take one yourself first, with a name you will recognise.
Switching software family clears the mods you installed
Server software falls into families: plugins (Paper, Purpur, Leaf, Folia, Spigot, Bukkit), Fabric (Fabric, Quilt), and Forge (Forge, NeoForge, and the hybrids). Plain vanilla belongs to no family, so moving into it counts as leaving whichever one you were in.
Moving inside a family keeps your installed list. Crossing between families cannot, because a plugin cannot load on a mod loader and a mod cannot load on a plugin server — the files are for different software entirely. So the change clears the installed list as part of applying, and while you have file-installed mods the request will not be accepted until you tick the acknowledgement that says they will be removed. The family warning appears whenever you cross; the acknowledgement only when there is something to lose. Write down what you had installed before you cross — the list is cleared, not archived somewhere you can read it back.
Latest versus pinning a version
LATEST (auto-update) is stored as a sentinel, not as a number, and the newest published build for your software is resolved when the server starts. Two things follow. A LATEST server never shows the update marker, because it cannot be behind. And an ordinary restart — including one you did for an unrelated reason — can move it onto a release that landed yesterday. That is fine on a vanilla server and a genuine hazard on a modded one, because mods are built against specific versions and a new major release routinely leaves them behind for weeks.
A pinned server compares itself against its own software's catalogue and shows the update marker when that software has published something newer — but only while the catalogue still lists your pin, so a pin old enough to have been pruned stays quiet rather than nagging. As of 2026-08-14 the newest Minecraft Java release is 26.2, and Mojang's own manifest is what the picker's vanilla list is derived from.
The Java runtime pin survives the change
If you have ever set the Java runtime field (the Java section of the same group) by hand, it stays exactly where you put it across a version change. This is the trap that produces a server crash-looping on Java too old for the version it just moved to — the newest releases require Java 25, so a server pinned to java8 for a 1.12-era pack will not boot on them.
The dialog checks this against the version and software you are moving to, and shows a separate warning naming your pinned runtime, with its own acknowledgement to tick. It is a warning rather than a block: nothing stops the change, and the Java runtime field is never disabled by server state, precisely so you can climb out afterwards. Setting that field back to Auto is the fix in almost every case — the full picture is in the Java runtime guide.
A pinned mod loader version can be cleared
On a Fabric, Quilt, Forge or NeoForge server without a modpack, the Mod loader version field in the same Java section (also offered in the create wizard) pins the loader build the server boots; Latest (auto) lets the server software pick one at every start, so pin a build only when a mod's log asks for a specific loader version. Unlike the Java pin, this one is cleared back to Latest if the server type changes, or if the Minecraft version changes on Forge or NeoForge, and the confirmation warns you before you send the request. It goes when the change is applied, not when you press the button. A Fabric or Quilt pin survives a Minecraft version change, and attaching a modpack clears it too.
Requests the platform will not accept
Some combinations are refused outright rather than warned about:
| Situation | Why |
|---|---|
| A modpack is attached | The pack owns both the software and the version |
| The pack was detached but the software is still the pack type | There is no version catalogue behind that software |
| Changing software on a Bedrock server through this form | Bedrock has no Software select; the only software change is the one-way "Switch to Endstone" |
| Changing the version of an Endstone server | The platform keeps Endstone up to date itself |
| Nothing was actually changed | The request needs at least one axis to move |
| A change is already pending | One safety chain at a time |
| A world reset is pending | Same rule, from the other direction |
| A version that software never built | The picker will not offer it and the API rejects it |
If the new version will not boot
Work down this list rather than restarting and hoping:
- Read the console. A world too new for the game and a Java too old for it fail in visibly different ways, and the first lines after the boot attempt usually name which.
- Check the
Java runtimefield in the Java section of the Version and performance group. If it is anything but Auto, set it back to Auto and start again — that field is editable even while the server is crash-looping. - Change the version back. Going up to where you were is the fastest recovery from a downgrade, and it takes its own restore point on the way.
- Restore from the Restore points tab. The restore point the change took is sitting there, and restoring it (with the server stopped) returns the server to its pre-change state — at the cost of everything built since.
Read next
- The Java runtime guide — which Java each version needs, and how Auto picks it
- Server properties — the server's other settings on the Settings tab
- Gamerules — the settings that live in the world file, not in our database
- Running a Minecraft server yourself — the same job without a panel
Frequently asked questions
Will I lose my world when I change the Minecraft version?
Not from the change itself, and not from a failure either. Every version change starts with a forced restore point of all the server's data, and the new version is applied only once that restore point is ready. If it fails, the pending change is thrown away without being applied and the server stays on the version it was already running. The world does travel with you into the new version — the risk is not the copy, it is the direction, because a world saved by a newer Minecraft cannot be opened by an older one.
Does the safety restore point count toward my 10?
Yes. A server keeps up to 10 restore points and every kind counts, this one included. Ten already there does not block the change; once the new point exists, the oldest goes. Every restore point is also kept at most 30 days, so if the pre-change state matters to you for longer than that, export it and download the file.
I picked an older version and now the server will not start. What now?
That is the downgrade case, and it is a Minecraft rule rather than a hosting one — the newer world data is unreadable to the older game. Two ways out. Change the version back up to where it was, which is the fastest fix and keeps everything that happened since. Or restore the restore point this change took for you from the Restore points tab (stop the server first), which returns the world to its pre-change state and loses whatever was built after it.
Why did my mods disappear after switching from Paper to Fabric?
Because they could never have loaded. A Paper plugin and a Fabric mod are different kinds of file for different software, so crossing between those families clears the installed list rather than leaving files behind that would crash the server at boot. The dialog says so before you commit, and while any file mods are installed it refuses to send the request until you tick the acknowledgement. Moving inside one family — Paper to Purpur, Forge to NeoForge — keeps your list.
What does the LATEST option actually track?
The newest release published for the software your server runs, resolved when the server starts rather than when you save. Two consequences worth knowing. A server set to LATEST never shows the update-available marker, because it is already up to date by definition. And an ordinary restart can move it onto a brand-new release that your plugins or mods have not caught up with yet — which is the argument for pinning a concrete version on any server that runs anything third-party.
Can I change the version of a modpack server?
No, and this is the one refusal with no workaround inside this section. The modpack itself decides the software and the version, so both axes are locked while a pack is attached — the change button is disabled and the section says to detach the pack first. A server that once ran a pack and has had it detached is still refused, because its software is the pack pseudo-type and there is no version catalogue behind it. Building a fresh server on the version you want is the honest route.
Sources
- Minecraft Java Edition 26.1 (link checked August 14, 2026)
- Minecraft version manifest (Mojang piston-meta) (link checked August 14, 2026)
Related guides
Would you rather skip all of this?
A server on uniz.host is up in minutes. You pay by the hour only while it is online, and the smallest top-up is ฿20.