minecraftthesift.com

Inspect the file you already downloaded

Your file never leaves your browser. Only supported package metadata is read locally. No JAR code runs, and no filenames or file contents are sent to a server.

Supported metadata and inspection limits

Fabric JSON, Forge / NeoForge TOML, and Bedrock manifests, including nested .mcpack and .mcaddon files. Java manifests are read only for a declared JAR version. The checker allows 4,096 entries, three nested archive levels, 256 KiB per metadata file, 16 MiB per nested package, 24 MiB total inspected expansion, and a 160:1 maximum compression ratio. Encrypted, split and ZIP64 archives are unsupported.

Author pages for known The Sift projects

What this check tells you

Package metadata describes what the file claims to contain. It is useful for finding a loader mismatch or reading a required Minecraft version. It is not a malware scan, proof of authorship or a gameplay test.

Use the compatibility and download finder to compare the author’s release listing. Keep files paired with the author and project you intended to install.

Safe handling of large files

The checker accepts files up to 64 MiB and reads selected metadata in a browser worker. It stops on excessive expansion, too many entries, damaged archives or unsupported structures. A file that reaches these limits needs manual inspection through its original publisher.

Nothing is uploaded or executed. See how the site handles data.

Illustrated minerals arranged on stone accompany The Sift mod file checker.
Original concept art · imagined setting, not gameplay

How to inspect a package

  1. Choose or drop one supported file.
  2. Read the declared loader, game requirement and pack type.
  3. Select your intended game environment and compare the result with the publisher’s release page.

Example results

Example metadata: a JAR with fabric.mod.json can report a Fabric loader and a declared Minecraft version range. A NeoForge profile would be a loader mismatch for that package.

Unknown: a missing or unsupported version expression stays unknown. The checker never guesses a supported release from the filename alone.

Bedrock: a resource-pack manifest identifies visual resources; it does not establish that a matching behavior pack is already installed. These examples explain result types and are not claims about a tested download.

File-checker questions

Does my file leave this device?

No. The browser reads selected package metadata locally. It does not send file bytes to this site or another service.

Does this prove the file is safe?

No. Metadata is supplied by the package itself. This is not an antivirus scan, a signature verifier or a gameplay test.

Why was a valid-looking archive rejected?

The checker stops on damaged ZIP records, unsupported layouts and size, expansion or time limits. Use the publisher’s package information for manual review.

Can I check a console installation?

You need access to a local package file. Metadata inspection does not establish whether your console permits manual importing.

Read the file checker’s output in context

The Sift mod file checker is most useful when you compare its output with two things: your intended game environment and the publisher’s release page. The archive tells the tool what it declares. Your launcher tells you what you will run. The publisher explains which release you meant to download. Agreement between those three sources helps identify an installation candidate without executing the package.

Begin with the name and package type, then read the loader and Minecraft requirement. A mod’s own version is a separate field. It can help distinguish two releases of the same project, but it does not replace the game-version requirement. If a value is missing or unresolved, keep it unresolved until the publisher supplies the needed information.

Java metadata and loader requirements

Supported Java metadata includes Fabric’s fabric.mod.json, Forge’s META-INF/mods.toml and NeoForge’s META-INF/neoforge.mods.toml. These files can declare identifiers, display names, dependencies and Minecraft version constraints. The checker reads the supported declarations rather than inferring a loader from the archive’s filename.

A declared dependency may have its own version range. Read that range alongside the Minecraft requirement, because satisfying one does not satisfy the other. For some packages, a version is filled from a build-time placeholder or manifest field. When the supported metadata cannot resolve a value, the output stays unknown instead of inventing a release number.

Use the compatibility finder to locate a recorded publisher release for the environment you want. Then compare its file information with this inspection. If the loader differs, return to the publisher’s downloads before placing the package in the profile. Renaming the archive will not change its loader requirements.

Bedrock manifests and paired packs

Bedrock manifests describe the pack identity and its modules. A resource module concerns resources, while data or script modules indicate behavior-related content. An add-on can contain nested packs, and reading one resource pack does not prove that a required behavior pack is present or activated in the world.

A minimum engine version is a minimum declaration. It does not guarantee compatibility with every later release. Read the publisher’s supported game versions and activation instructions as well. The Bedrock add-on guide helps separate package import, world activation and access to the dimension.

Three sources for one installation decision
  1. Your game: edition, version and loader or pack environment.
  2. The archive: declared metadata and dependencies.
  3. The publisher: the selected release and its instructions.

What to do when a check stops

An unsupported result can mean the format or archive layout is outside the checker’s scope. A damaged result can mean the ZIP structure or metadata could not be parsed consistently. A processing-limit result means the archive exceeded a configured bound. These outcomes are different from finding a declared mismatch with your game.

The tool reads selected metadata and applies limits to archive size, entry count, nesting and decompression. This prevents a small-looking archive from causing unbounded work in the browser. Reaching a limit does not establish whether a package is good or bad; it means this inspection cannot complete within its supported limits.

Return to the original publisher for release details or a fresh download when the package appears incomplete. Avoid repeatedly downloading the same file from unrelated mirrors just to obtain a different checker result. Keep the source link and compare the expected package type before trying again.

Keep security and compatibility separate

A readable manifest can exist in an untrusted file. Conversely, a legitimate package may use metadata that this checker does not support. Treat origin, security and compatibility as separate questions. The tool answers a limited compatibility question from declared metadata; it does not verify signatures, scan executable content or certify the author.

Download from the project’s original publisher and review its instructions. Back up an existing world before changing mods. Use a separate profile or test world when practical, and follow the installation guide for the steps that happen after inspection. A successful metadata read is not a substitute for those steps.

Share a problem without uploading the package

For an incorrect result, use the contact page and describe the supported file type, the selected game environment and the displayed error. Include the publisher’s file-page link when available. The first report usually does not need the entire archive, a private download URL or a screenshot of personal folders.

If a screenshot helps explain the issue, remove personal paths and unrelated information before sending it. Avoid including authentication tokens or account details. A small example of the relevant metadata can be more useful than a large package, but only share material that you are entitled to share.

The file stays on your device during the browser inspection. Choosing a file is not a newsletter subscription and does not send its contents as an analytics event. The privacy policy explains the separate handling of optional usage measurements and email subscriptions. You can use the package inspection without giving the site your email address.