How to Downgrade Minecraft Version

Minecraft updates on Mojang's schedule and mods update on thousands of independent authors' schedules, so the two are permanently out of step. When a new version launches, essentially nothing works on it for weeks.

More significantly, large modpacks settle on a version and stay there for years, because moving hundreds of mods to a new Minecraft release means waiting for the slowest of them. That is why 1.20.1 remains the centre of gravity for modded play long after the game moved on, and why 1.12.2 packs still have an active following.

So downgrading is not an unusual repair operation. It is the normal state of affairs for anyone playing modded, and the launcher is built to accommodate it.

Open the Minecraft launcher and go to the Installations tab, then click New Installation. In the version dropdown, pick the release you want — every version back to the earliest is listed.

Give it a name you will recognise later, something like '1.20.1 Forge' rather than the default, because you will accumulate several of these.

Click Create. Nothing is downloaded until you launch it for the first time, at which point the launcher fetches that version's files and the matching Java runtime automatically.

Your existing installations are entirely untouched. This adds a version rather than replacing one, and you switch between them from the dropdown next to the Play button.

By default every installation shares one .minecraft folder, which means they share one mods folder, one config folder and one saves folder. For modded play that is actively harmful.

A 1.20.1 Forge mod sitting in the same folder as your 1.21.4 Fabric mods will be loaded by neither, and both setups will generate errors about the other's files.

In the installation's settings there is a Game Directory field. Point it somewhere specific — a folder named for that version. The launcher creates it on first launch and keeps everything for that installation inside it.

Do this for every modded installation you create. It takes ten seconds and prevents an entire category of confusing problems.

Adding an old version is harmless. Opening a world created in a newer version using an older one is not.

Minecraft world files change format between versions, and newer formats contain blocks, biomes and data structures older versions have never heard of. Opening such a world on an older build can strip chunks, delete unfamiliar blocks, and produce corruption that is not recoverable.

The launcher warns you about this, and the warning is genuine rather than boilerplate. Do not click through it on a world you care about.

The rule is simple: a world can move forward to newer versions, and cannot move backward. Treat each downgraded installation as needing its own new worlds.

Copy your saves folder somewhere outside the Minecraft directory before doing anything version-related. It takes seconds and it is the only reliable protection against the failure above.

Keep the copy outside .minecraft entirely, because some operations replace folders wholesale and a backup stored inside goes with them.

If you specifically want to try an old version on a newer world — sometimes worth doing to recover something — work on a copy and accept that the copy may be destroyed.

Prism Launcher, MultiMC and similar tools are built around exactly this problem. Every instance is a self-contained version with its own mods, configs, saves and Java runtime.

Creating a 1.12.2 instance alongside a 1.21.4 one requires no thought about directories, because separation is the default rather than something you configure.

They also let you pin the Java version per instance, which matters here — 1.12.2 needs Java 8 while current versions need Java 21, and getting that wrong produces confusing failures.

If you routinely play more than two different versions, switching to an instance launcher will save more time than any other single change.

Older Minecraft versions need older Java, and this catches people who assume newer is always compatible.

Versions from 1.20.5 need Java 21. The 1.18 through 1.20.4 range needs Java 17. Anything 1.16.5 or older wants Java 8.

The official launcher handles this automatically, downloading the correct runtime per installation. Third-party launchers do not, and will use whatever you point them at.

If a downgraded installation fails with UnsupportedClassVersionError, this is the cause, and the class file version number in the message tells you which Java it wanted.

If a specific pack or mod prompted this, the answer is whatever it requires and there is no decision to make.

If you are choosing freely because you want a deep mod selection, 1.20.1 is the strongest option. It carries the largest mod library of any version, it has both Forge and Fabric support, and most large packs target it.

1.16.5 is the other notable stop, home to a generation of packs from that era. 1.12.2 is the classic Forge branch, frozen in time, with an enormous back catalogue that will never be ported.

Newer than 1.20.1 gets you fewer mods, not more, which is counterintuitive until you look at the numbers.

The launcher's version list includes snapshots — pre-release builds — if you enable them in the settings.

Do not mod these. Snapshots change internal code weekly, so mods built against one break on the next, and loaders often do not support them at all.

They are useful for previewing upcoming features in vanilla. For modded play they are a reliable source of frustration.

Nothing about downgrading is permanent. Select your current installation from the dropdown and play as before — the older one sits alongside it indefinitely.

Worlds created in the old version can be opened in the newer one, and Minecraft upgrades them automatically. That direction is safe, though the upgrade is one-way and the world will no longer open in the old version afterwards.

If you upgrade a modded world, expect the mods to need replacing too, and expect some of them not to exist for the newer version at all.

Once you have three or four versions installed, naming and organisation stop being optional.

Name installations for what they are rather than accepting defaults — '1.20.1 Forge — ATM9' tells you something in six months, while 'New Installation (3)' does not.

Point each at its own game directory, named to match. Keeping the directory name aligned with the installation name means you can find the right mods folder without opening the launcher.

Keep a short note of which Java version, loader version and mod versions each setup uses. When one of them breaks after an update, that note is the fastest route back to a working state.

It is worth naming the cases where downgrading is the wrong instinct, because people reach for it after a crash and it rarely helps there.

If mods are crashing on a version they officially support, the cause is a conflict or a missing dependency rather than the Minecraft version, and moving to an older release simply changes which mods are broken.

If a mod supports several versions, there is no advantage to picking the oldest. Choose whichever version the rest of your list agrees on.

Downgrading is the right move for exactly one reason: the content you want only exists on an older version. If that is not your situation, the problem is somewhere else.