Guidefor everyones3 min read
When was Minecraft first released? The complete Java Edition history
Minecraft first appeared as an in-development Java game in 2009 and reached its full 1.0 release in 2011. Here is the difference between the first build, Classic, Alpha, Beta and the modern version list.
The short answer
Minecraft has two useful “first release” dates:
- 13 May 2009: the earliest build in the modern version history,
rd-132211, was released. It was a pre-classic development build. - 18 November 2011: Minecraft 1.0.0 launched as the first full release of Java Edition.
Those answers are not contradictory. Minecraft was publicly playable for more than two years before the 1.0 launch. Saying “Minecraft released in 2011” is correct when “released” means the finished game; saying “Minecraft began in 2009” is correct when it means the first public development builds.
The version history before 1.0
The earliest IDs do not look like the versions people know today. Mojang used several naming families as the game moved from an experiment into a commercial release.
Pre-classic and Classic
The rd- builds came first. rd-132211 is an early pre-classic build from 2009. Classic followed with versions such as c0.0.11a, using a different naming family again. These builds are historically important, but they are not “Minecraft 1.0 minus a few features”; the game was still being designed.
Indev and Infdev
Indev and Infdev were development phases focused on turning a small playable world into a generated, persistent one. IDs such as inf-20100618 are dates or dated build labels rather than release numbers. A later-looking string is not automatically a newer build, which is why a chronological manifest is more useful than alphabetical sorting.
Alpha
Alpha brought the game closer to the survival sandbox people recognise. Public Alpha builds used names such as a1.0.16_05. The Alpha label describes the development stage, not a Java Edition major version. Old Alpha clients and servers also have compatibility limits that do not resemble modern mod-loader compatibility.
Beta
Beta began in December 2010. Beta builds added large parts of the systems that made the eventual release possible, but they were still unfinished and changed quickly. Beta IDs such as b1.7.3 are not decimal versions: b1.7.3 means Beta 1.7.3, not a number that should be compared with 1.20.4 or 26.2.
Minecraft 1.0 and the 1.x line
Minecraft 1.0.0 was the first full Java Edition release. After that, Mojang used the familiar 1.x scheme for the main release line: 1.2.3, 1.8.9, 1.12.2, 1.16.5 and eventually 1.21.11.
Snapshots and pre-releases belong to the same development history but are not full releases. For example, a weekly snapshot can be newer than a release with a higher-looking number. When a version matters for a server, check its type, release date, protocol and data version together.
Why 26.1 is not “version 26.1” in the old sense
In 2026, Java Edition moved to calendar versioning. 26.1 means the first release drop in 2026 and 26.2 means the second. It is not a continuation of the old decimal sequence, and there was no Java Edition 1.22 that was later renamed 26.1.
That change is another reason to use the complete version index instead of sorting version strings yourself. The index keeps the old 1.x line and the calendar line in release order, while still showing snapshots, pre-releases, candidates and April Fools builds separately.
The reliable way to compare old versions
For a quick answer, use the release date shown on each version page. For software, use the version's protocol and data version as additional evidence. For code, use Mojang's manifest order or a monotonic data-version field where one exists; never compare the text of 1.21.11 and 26.1 as ordinary numbers.
The Minecraft version index contains the full record for every version MCReference tracks, including official client and server downloads where Mojang's current manifest provides them, checksums, Java metadata, protocol numbers and links to the compatibility page.
