Skip to content
Powered by Pagefind
English
Minecraft Updates

Minecraft Version Numbers Explained: The 26.x System

Why Minecraft versions jumped from 1.21 to 26 — the year-based numbering system explained: Java steps per drop, Bedrock steps by tens, and what 26.52 means.

9/29/2026 26.3 / 26.52 Minecraft Wiki Team Last updated: 10/7/2026 2 min read
Minecraft Version Numbers Explained: The 26.x System

FAQ

Why did Minecraft version numbers change?
Mojang retired the 1.x scheme at the end of 2025 so both editions share a year prefix — all 2026 releases begin with 26. The remaining digits differ because Java ships quarterly drops while Bedrock releases more often.
Is Bedrock 26.3 the same as Java 26.3?
No — the editions version independently after the shared year. Wilderness Bound shipped as Java 26.3 but Bedrock 26.50 (now 26.52 after hotfixes). The year matches; everything after it doesn't.
What is Bedrock's internal version number?
1.26.xx.yyy — Bedrock keeps the long build number (e.g. 1.26.52.3) inside JSON files, APIs, and dedicated-server versions, while the game displays the short 26.52 label.

What changed in 2026?

Mojang retired the 1.x numbering that ran from 1.0 (2011) to 1.21.x (2025). Every release now starts with the year: all 2026 versions begin with 26. The change was announced in December 2025, previews adopted it immediately, and the first full releases under the new system shipped in early 2026.

The 2025 drops would have been 25.x under this scheme — Spring to Life ≈ 25.1, Chase the Skies ≈ 25.2, The Copper Age ≈ 25.3, Mounts of Mayhem ≈ 25.4 — which is why they appear labeled that way in version-history views.

How does each edition count?

Edition Pattern Current
Java Year + drop index — 26.1, 26.2, 26.3, 26.4 for the four 2026 drops; patches add a third digit (26.3.1) 26.3 (26.4 snapshots live — the drop content landed in Snapshot 3, Oct 6)
Bedrock Year + release line stepping by tens — 26.10, 26.30, 26.50; hotfixes tick the tail (26.50 → 26.51 → 26.52) 26.52
Bedrock internal Long build number for APIs/JSON: 1.26.xx.yyy (e.g. 1.26.52.3) —
Preview/beta Bedrock Preview runs ahead on its own line (1.26.60.x = Drop 4 experiments) —

The 2026 release line so far

Drop Java Bedrock
Tiny Takeover — Mar 24 26.1 26.10 line
Chaos Cubed — Jun 16 26.2 26.30 line
Wilderness Bound — Sep 15 26.3 26.50 → 26.52
Ice Caves — expected Dec 26.4 (snapshots live) ~26.60 experiments

Why don’t the numbers match?

Java ships one release per quarterly drop. Bedrock ships continuously across ten platforms, so its release lines advance faster — the trailing digits just don’t correspond. A Java 26.3 feature set ≈ a Bedrock 26.5x feature set; comparing “26.3 vs 26.3” across editions is meaningless.

Related Articles

Was this helpful?