minecraftthesift.com

Find the right build for your setup

Choose your game, implementation, Minecraft version and loader. A matching published file is a starting point; dependencies and author instructions still matter.

Use the author’s project page for downloads. This site hosts no mod files.

Author pages and verification date

Read the result before downloading

A matching record means the publisher lists that combination. It does not mean we ran the mod in your world. A result with no verified match leaves compatibility unknown; it is not proof that the project cannot work.

Dependencies are attached to a specific file. If they are unknown, open that file’s page before installing. Back up your world and follow the installation guide.

Already have a file?

The local file checker reads package metadata in your browser. It can help identify a loader or declared version requirement without uploading the file.

Books and a map in an illustrated archive accompany The Sift mod compatibility checker.
Original concept art · imagined setting, not gameplay

How to check a release

  1. Select your edition and author.
  2. Enter your exact Minecraft version and, for Java, choose the loader.
  3. Open the result’s file page and check its dependency list before downloading.

Example results

Recorded match: Mielon + Java 1.21.1 + NeoForge finds file 9011966. Its recorded requirements include NeoForge 21.1.62+ and GeckoLib 4.6.6+.

Unknown: Mielon + a version absent from the records produces no verified matching build. Try the author’s files; do not interpret this as a definitive incompatibility result.

Official game: selecting Dungeons II gives its released status and the official announcement instead of a community download.

Invalid version format: enter a release number such as 1.21.1 or 26.3. Snapshot labels require checking the publisher’s exact file. A format error is separate from a valid version absent from this site’s records.

Compatibility questions

Does a match guarantee my modpack will run?

No. It matches publisher records for that file, game and loader. Other mods and your local setup still matter.

Why do some dependencies say not verified?

Requirements are recorded per file. The checker does not borrow a dependency list from another release.

What does a publisher-tag result mean?

The author attached those version or loader tags to a file. Multiple tags are not proof that we tested every combination.

Where is the download hosted?

Every download link opens the original publisher’s file page. This site does not mirror mod files.

Get a useful answer from The Sift mod compatibility checker

The Sift mod compatibility checker compares your choices with recorded publisher releases. Start with the environment you intend to play, then choose the author’s project. The resulting file is useful only when its edition, Minecraft version and loader match that environment. Reading those fields before downloading prevents a common problem: selecting a familiar project name while overlooking a different release target.

For an existing modpack, use the version and loader already set by that pack. For a new profile, choose the project first and follow one of its documented release environments. Changing several variables at once makes a failed launch harder to diagnose. Keep the chosen release and its dependency list together so that you can reproduce the setup later.

Read your launcher profile first

The game version is the Minecraft version, not the mod’s own release number. Those numbers can appear close together on a file page but have different purposes. A mod version identifies an iteration of the project; a Minecraft version identifies the game environment for which that file was released.

The loader is another separate requirement. NeoForge, Forge and Fabric should be treated as different options unless the author’s specific file record supports the combination you intend to use. A loader mentioned somewhere on the project page may describe another release. Match the selected file rather than relying on the project’s broad list of tags.

For Bedrock, a pack’s minimum engine declaration and the publisher’s supported versions need careful reading. A minimum is a lower bound, not a promise that every future game update has been tested. The Bedrock guide explains how behavior and resource packs fit into that installation path.

Understand the three useful result types

A recorded match means the stored release information includes your selection. Use the file link to verify the publisher’s current notes and dependencies. The record makes the download easier to find, while the author’s page remains the source for that release. This site does not host replacement copies of the package.

A result based on publisher tags identifies information attached to the file listing. When several loaders or versions are listed together, the result should retain that evidence label. It should not silently become a claim that the site has launched every listed combination. If the file’s description adds restrictions, follow those restrictions.

A result with no verified match means the catalog cannot identify a matching recorded file. Check whether the edition, author, game version and loader were entered correctly. If they were, visit the publisher’s full file list. The absence of a record here does not establish that the author has never released a suitable build.

What to do with the result
  1. Recorded match: inspect that file’s current notes and dependencies.
  2. Publisher tags: preserve the listing’s evidence boundary.
  3. No recorded match: check your inputs, then the author’s complete file list.

Keep dependencies attached to the file

Dependencies can differ between releases. A requirement from an older upload should not be copied automatically to a newer one, even when the mod name is unchanged. Read the selected file’s dependency section and any version constraints the author provides. Install those requirements in the same launcher profile as the mod.

If the checker leaves a dependency unresolved, use the linked file page instead of assuming that no dependency exists. The distinction matters: an empty requirement established by the publisher and an unverified requirement are different findings. The installation guide provides the next steps for assembling and checking the profile.

Compare projects without mixing their instructions

The mod catalog separates Mielon, Wellspring, backport authors and Bedrock authors. Use it when choosing between projects. This checker then narrows the release within that choice. A compatible package from one author should still be paired with that author’s installation and entrance instructions.

For example, finding a release of Mielon’s project leads naturally to its project guide and portal song. Selecting a different author should send you to that project’s documentation. Shared names and visual themes do not establish shared portal mechanics, creatures or material uses.

After downloading, the file checker can read the package’s declarations. Compare those with this finder’s release record. A discrepancy is a reason to stop and recheck the download source, filename and selected file. Metadata supplied by an archive is useful evidence about its declaration, but it is not proof of authenticity or a security assessment.

Official-game choices answer availability

Dungeons II and vanilla Minecraft are included so that a player who wants the official experience can find the right route. Those choices should not produce an unrelated community download. Mojang has a separate Dungeons II overview, while the announced Java and Bedrock rollout is covered on the versions page.

Use the release-date guide when comparing a released game with an announced window. The date of a community file does not change the official release schedule. Likewise, an official announcement does not certify the compatibility of a third-party package.

Preserve a repeatable installation

Before modifying an existing world, save a backup and retain the chosen file’s source link. If you encounter a problem, record the failed stage and the relevant error. A failure while loading dependencies calls for a different investigation from an entrance that does not activate after the world has opened.

For multiplayer, compare the client and server environments using the publisher’s requirements. A working local launch does not by itself establish that a server has the matching files. Share the author’s file link and the specific game and loader versions with the server maintainer so that both sides can inspect the same release.