Minecraft Sift Release Date: Timeline & Announcements

Sift updates: the evidence timeline

The Sift release date depends on the game you mean: Dungeons II has a September 29, 2026 launch plan, while Java and Bedrock are planned for 2027 with no exact date confirmed in the reviewed sources. A game announcement, a mod file upload, and a wiki review are different events. This page records the current research snapshot so you can understand which event a statement refers to and avoid treating historical plans as proof of present availability.

The site was prepared using evidence reviewed on September 27, 2026. At that point, the official Dungeons II launch date remained an announced September 29, 2026 plan, and the vanilla Java and Bedrock announcement pointed to 2027. This Sift release date timeline does not claim that either event has already occurred. It is not a live news feed.

Check the Sift release date for your game alongside the version comparison. The timeline explains when evidence appeared; the comparison explains which game or implementation it applies to. For an installation decision, the version checker turns the same records into a scoped result with a next-step link.

When is the Sift coming to Minecraft?

Game or implementation	Announced timing or file status	What the date means
Minecraft Dungeons II	September 29, 2026	Planned game launch; this review predates it.
Minecraft Java and Bedrock	2027	Announced year, with no exact vanilla date or build confirmed here.
Mielon’s The Sift and Wellspring	Separate author file listings	Unofficial mod uploads, not a Mojang release.

For the source and platform details, read Dungeons II or the Java and Bedrock announcement. To check a particular installation, use the version checker.

August 20: the gameplay trailer article

The official gameplay trailer article was published on August 20, 2026. It introduces the new dimension for Dungeons II and connects rifts with entering it. The article also gives the announced September 29 launch date. These are the central release-context facts carried forward from that source in this snapshot.

For the Dungeons II Sift release date, the significance is the type of evidence: this is official reveal material, not a community interpretation or an independent released-game walkthrough. It can establish the setting and the announced schedule while leaving detailed progression questions open. The Dungeons II page explains that boundary.

When reading a later summary of the trailer, distinguish genuinely new information from a restatement of the same source. A newly published article can discuss an older announcement. Its publication date does not automatically make the underlying claim a new development, and it should not reset the apparent freshness of a release plan without further evidence.

August 31: the gameplay systems overview

The official systems article was published on August 31, 2026. This Sift updates entry connects that announcement to the co-op, gear and exploration reference. Players can now read the available answers together instead of searching several separate announcements. The table describes announced game systems; it is not an independently tested progression walkthrough.

September 17–18: reviewed Mielon files

The reviewed Mielon records include 1.0.2 files for Minecraft 26.2 with Fabric and 1.21.1 with NeoForge, listed on September 17. A 1.0.2-FIX file for 26.3 with Fabric is listed on September 18. These dates belong to a community project, not the official vanilla release schedule.

A mod upload is not an official Sift release date; this part of the timeline explains why the checker keeps exact combinations. A file upload supplies a game version, loader, and release identity. It does not turn every project tag into a compatible pairing, and it does not settle dependencies for another branch. The Mielon guide links to the reviewed files individually.

If you find a later file, compare its actual metadata and notes with the older record. A similar filename may identify a different game branch. The word “fix” also does not establish that every reported issue was resolved. It identifies the author’s release naming; the practical scope still comes from the associated documentation and testing.

September 20: a Wellspring alpha record

The reviewed Wellspring file is 1.1.1-alpha for Minecraft 26.1.2 with NeoForge, listed on September 20, 2026. The project describes an early interpretation of the dimension. Its alpha status and separate identity should remain attached to any instructions drawn from its author page.

This event belongs in a mod timeline, rather than establishing a Sift release date for vanilla Minecraft. It is not evidence that Mojang released the dimension for vanilla Minecraft on that date. Nor does it establish that another project’s instructions apply to this file. The Wellspring guide explains the reviewed combination and the author’s entry concept.

An evolving alpha can receive changes that make older videos or instructions less useful. Preserve the file identity when saving a guide. If you later encounter a different behavior, compare the versions before concluding that a source was necessarily wrong. A dated record can describe an older release accurately while no longer being the right instruction for a newer one.

September 26: the vanilla announcement

The September Minecraft Live recap places the Sift in a broader official roadmap, including a plan for Java and Bedrock in the following year. Since the recap is dated 2026, that means 2027. The announcement is the basis for the vanilla status in this site’s reviewed snapshot.

For the vanilla Sift release date, this is a separate announcement from the earlier Dungeons II reveal and the September mod uploads. It should not be merged into a single “Sift release date.” The Java and Bedrock guide explains what the announcement supports and why it does not supply a confirmed vanilla build or portal recipe.

Relative time language needs its original date. A copied sentence saying “next year” can become misleading if a later page removes the publication context. Our records use the explicit year and link to the source. This helps you interpret the plan correctly even when you encounter a saved result well after the initial announcement.

September 27: this site’s research snapshot

The review date is the point at which the sources used for these Sift updates were checked for the first edition of this website. It is not a game release, a mod upload, or an independent playtest date. Keeping those meanings separate prevents the wiki’s own maintenance activity from being mistaken for new gameplay evidence.

The review confirmed the source distinctions and several exact mod file listings. It did not establish a complete official bestiary, every item recipe, all future release details, or compatibility across arbitrary modpacks. Those gaps remain visible in the field guide and tool results rather than being filled with plausible-looking values.

The September 26 Xbox Wire article was subsequently readable through its search-index text, although direct retrieval still failed. It is now included in the source directory with that limitation. Community-wiki retrieval gaps remain unresolved. A failed retrieval is not proof that a page is absent, and it does not count as a completed content review.

When Sift updates need a new review

A Sift release date review begins with changed evidence. Examples include an official release note identifying a build, a revised launch announcement, a new exact mod file, an updated dependency requirement, or a reproducible gameplay observation. A new headline repeating an old fact is not enough by itself.

When evidence changes, the related records should change together. A newly verified file should update the checker and its mod guide. A confirmed release state should update the relevant edition page and timeline. A new mechanic should remain tied to the game and version that establishes it rather than be copied across the entire wiki.

The review date should reflect actual checking, not an automatic daily timestamp. This protects readers from mistaking an old record for fresh research. It also makes a Sift release date claim easier to audit: you can compare the claim, source, scope, and review event without guessing whether a displayed date is merely the day the page was rendered.

Use Sift updates for a practical decision

If your question is “Can I play now?”, begin with your edition and current primary source. If it is “Why does this guide differ from a video?”, compare the project and release dates. If it is “What was actually announced?”, follow the official announcement link rather than a chain of summaries.

A Sift release date timeline is most useful when it leads to one of those concrete decisions. It is less useful when it creates urgency without adding evidence. This site therefore avoids countdowns that silently become release claims, unverified patch summaries, and claims that a feature is live merely because a scheduled date has passed.

Read the editorial standards for the maintenance method, then continue to the relevant game or mod guide. The timeline is a record of what the sources establish at a known point in time. Keeping that purpose clear allows the wiki to remain useful as new evidence arrives without pretending that its first research snapshot can answer every future question.