The Sift Mod File Checker
Drop a JAR, MCPACK or MCADDON to read its declared name, version, loader and dependencies. File contents stay in your browser.
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.
A matching name or version is not proof that a file is official, authentic, safe, complete, or able to run.
Or drop one file here. Maximum 64 MiB. Nested packages and decompression have additional limits.
Choose a local file to read its metadata.
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
- Mielon's The Sift — Mielon · verified 2026-09-30
- Wellspring — SyddersLMAO · verified 2026-09-30
- The Sift: Backport — Zerw · verified 2026-09-30
- Sift Backport — DerexXD · verified 2026-09-30
- The Sift Dimension | Add-On — trotamundos872 · verified 2026-09-30
- The Sift Dimension Addon — Korvvvik · verified 2026-09-30
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.
How to inspect a package
- Choose or drop one supported file.
- Read the declared loader, game requirement and pack type.
- 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.