Updating Minecraft takes about one click. The reason people dread it is everything that can go sideways on the second click.
For most players an update just happens, quietly, and the game is newer next time you launch. For anyone running mods or attached to a long-running world, an update can also mean a broken modpack, a save that refuses to load, or a multiplayer server nobody can join. Almost all of that pain is avoidable with about five minutes of prep. If you want to know what actually changed in the newest version, that is a separate read, and we covered it in our look at the latest Minecraft update. This guide is about doing the update without breaking anything.
The short version
Back up your worlds before you update, every time, because you usually cannot roll a save back to an older version once it opens in a new one. On Java Edition the launcher updates itself, and you can pick versions under Installations; on Bedrock the update comes through your device’s store. Mods break because they are tied to a specific version, so keep a separate installation pinned to the old version for your modded world and update the mods only when they are ready.
Table of Contents
Back up your world first
This is the step nobody regrets and plenty of people wish they had taken. A world opened in a new version is often stamped with that version, and going back is not simple, so a backup is your only real undo button. On Java Edition, copy the entire world folder out of your saves directory to somewhere safe, the whole folder, not a few files inside it. On Bedrock, worlds live in the minecraftWorlds directory under folders with random names, so open the levelname.txt inside each to find the one you want before copying it. For a modded world, back up the world and its matching mods, config, and resource pack folders together, so the save and the setup that runs it stay paired.
How to update, on Java and Bedrock
The process depends on which edition you play, and they work differently:
| Edition | How it updates | Version control |
|---|---|---|
| Java (PC) | The Minecraft Launcher updates to the latest release automatically | Full: create or pick any version under Installations |
| Bedrock (Windows, console, mobile) | Through your platform’s store, usually as an automatic update | Limited: the store generally serves only the newest version |
On Java, if you just want the latest, launching the game is enough. On Bedrock, check for the update in the Microsoft Store, your console’s store, or your phone’s app store, and turn on automatic updates if you want it handled for you. The official Minecraft Help Center has the current per-platform steps if your store is being stubborn.
Why your mods break, and what to do
This is the single most common update headache, and it is not a bug. Mods, whether Forge, Fabric, or NeoForge, are written for a specific game version, so the moment the game jumps ahead, the mods are built for a version that no longer matches and they stop loading. The fix is not to force them, it is to not update in a hurry. Keep a separate Java installation pinned to your modded world’s version, and leave it there until every mod you rely on has released an update for the new version. Modpack players especially should never let a pack auto-update mid-world without a backup, because one out-of-date mod can take a chunk of your world with it.
Fixing common post-update problems
If the update already happened and something is wrong, work through the usual suspects:
- The game will not launch or crashes on start. Update your graphics drivers, make sure your Java is current on Java Edition, and reinstall the launcher if it persists.
- A world will not load. It is usually a version mismatch, so open it in the version that matches the save, which is exactly what your backup lets you do.
- Multiplayer says the client or server is outdated. The server and every player must run the same version, so update the server or hold players on the matching one.
- The game runs worse than before. Allocate more memory on Java, lower render distance and graphics settings, and check whether a mod is the real cause.
How to go back to an older version
On Java this is easy: open the launcher, go to Installations, create a new one set to the older version, and launch that. Your backed-up world opens there without a fight. On Bedrock it is harder, since the store pushes the newest build, so the practical protection is turning off automatic updates and keeping backups, rather than expecting to downgrade on demand. Either way, this is the moment the earlier backup pays for itself.
Frequently asked questions
How do I update Minecraft?
On Java Edition, the Minecraft Launcher updates to the latest release automatically, and you can choose versions under Installations. On Bedrock Edition, the update comes through your platform’s store, so check the Microsoft Store, console store, or app store, and enable automatic updates if you prefer.
Do I need to back up before updating?
Yes, especially for important or modded worlds. A save opened in a newer version generally cannot be moved back, so copying the whole world folder first is your only reliable undo if the update causes problems.
Why did the update break my mods?
Mods are built for a specific game version, so an update leaves them mismatched until their authors release a new version. Keep a separate installation on the old version for your modded world and update the mods only once they support the new build.
My world won’t load after updating. What happened?
It is almost always a version mismatch. Open the world in the version it was last saved in, which is straightforward on Java through Installations and is why keeping a backup and the matching version matters.
Can I downgrade Minecraft to an older version?
On Java, yes, by creating an installation set to the older version in the launcher. On Bedrock it is much harder because the store serves the newest build, so the better plan there is disabling auto-updates and relying on backups.
Final word
Updating Minecraft is genuinely simple, and the disasters almost always trace back to skipping the boring prep. Back up your world, know whether you are on Java or Bedrock, and keep modded saves on a pinned version until the mods catch up. Do that and updates become a non-event instead of a gamble. For more gaming and tech how-tos, browse The Other Stream’s Tech section.