Guidefor players3 min read
What Minecraft snapshot names mean
26w14a, 26.3-snapshot-5, 26.2-pre1, 26.2-rc1. Four naming schemes, what each one tells you, and how far along a release actually is.
Four names, four meanings
Mojang uses different naming for different stages, and each name tells you something useful about how finished the thing is.
| Looks like | Stage | How finished |
|---|---|---|
26w14a | weekly snapshot | Anywhere from early to nearly done |
26.3-snapshot-5 | numbered snapshot | Aimed at a specific named release |
26.2-pre1 | pre-release | Feature complete, being fixed |
26.2-rc1 | release candidate | Would ship as-is if nothing turns up |
26.2 | release | Done |
They arrive in that order and never go backwards.
Weekly snapshots: 26w14a
The oldest scheme, and still the most common.
- 26 — the year, 2026
- w — week
- 14 — week 14 of that year
- a — the first snapshot published that week
If a second lands in the same week it is 26w14b, then 26w14c. In practice the letter
rarely goes past b, and when it does it usually means the first one had a problem.
What it does not tell you is which release it is heading for. A snapshot published in February 2026 might be aimed at the next drop or at something much further out. Its date and its position in the timeline are the only reliable guide, which is why the version list is ordered chronologically rather than by name.
Numbered snapshots: 26.3-snapshot-5
Newer, and more informative: it names the release it is working towards.
26.3-snapshot-5 is the fifth snapshot aimed at 26.3. You know the target and you know how
many have come before, which the weekly scheme never told you.
Both schemes are in use. Which one appears depends on where in the cycle the work is.
Pre-releases: 26.2-pre1
A pre-release means the features are in. From here the work is fixing bugs, not adding things.
The number counts up as problems are found and fixed: pre1, pre2, pre3. A long
pre-release run usually means something significant turned up.
For a server operator this is the point where testing your plugins becomes worthwhile. Before a pre-release the API can still move; after it, mostly it does not.
Release candidates: 26.2-rc1
A release candidate is the build Mojang intends to ship. If nothing serious is found, the exact same code becomes the release under a different name.
rc2 means something serious was found.
This is the last stop before the version people will actually run, and it is the right moment to confirm your setup works, because the answer will still be true next week.
Then the release
26.2, with no suffix. Everything after that is a hotfix: 26.2.1, 26.2.2, bug fixes and
nothing else.
Running a snapshot safely
Two rules, and the first one is not negotiable:
Copy your world first. Opening a world on a snapshot converts it, and conversion is one way. There is no downgrade. See can you downgrade a world for what that costs when people find out afterwards.
Use a separate installation. In the official launcher, create a new installation for the snapshot rather than switching your existing one. Then your normal setup is untouched and you can go back by launching it.
Also worth knowing:
- Snapshot clients cannot join release servers. Snapshot protocol numbers use a separate range that can never match a release protocol.
- Almost no mods and plugins support snapshots. Loaders sometimes ship snapshot builds; the ecosystem around them mostly does not.
- Things break, and that is the point. A snapshot is published so bugs are found before the release. Report what you find.
Where a snapshot sits in the timeline
The names are not sortable. 26w14a, 26.2-pre1 and 26.3-snapshot-5 follow no common
pattern, and no parsing rule orders them correctly.
The order Mojang publishes in its own version manifest is chronological and covers every naming scheme in one list, which is the ordering this site uses everywhere. Each version page shows what came immediately before and after it, so a snapshot's real position is a click rather than a guess. Which version is newer has the detail if you need to sort them in your own code.