Plan your next Minecraft version
Check MRPack Mods for Another Minecraft Version
Open an .mrpack, choose a target Minecraft version and loader, and find which mods have a published version on Modrinth.
MRPack input · Modrinth data · Local file processing
Your pack stays in your browser. Only file hashes and your selected target are sent to Modrinth.
This checks published version availability. It does not test whether the whole pack will launch.
Choose a pack to see its current version.
Version availability
A target version found here may require different dependencies or configs. Mods bundled inside overrides are not checked.
| File | Result | Current version | Target version |
|---|
No files match this filter.
How to check Minecraft mod versions from an MRPack
- Open your pack. Select an
.mrpackup to 50 MB. The checker reads the current Minecraft version, loader and referenced mod JARs. - Choose the target. Enter the exact Minecraft version and select Fabric, Forge, NeoForge or Quilt. Stable mod releases are checked by default.
- Review and export. Run the check, filter files that need review, open the published version links and download the JSON report.
For the complete workflow, read how to check a modpack before upgrading Minecraft.
What the version check results mean
| Result | Meaning and next step |
|---|---|
| Already supports target | The exact current file is listed for the selected version, loader and release filter. Review its dependencies before testing the pack. |
| Target version found | A different file from the same Modrinth project is published for your target. Open its version page to review requirements and changes. |
| No target version found | The source file was identified, but no matching published release was returned for the selected target and filters. Check the author's releases before changing the target. |
| Not identified on Modrinth | The exact file could not be matched, or its manifest SHA-1 is missing. It may come from another source; this is not a verdict on compatibility. |
| Query failed — retry | A network, rate-limit or response-verification error prevented the check. Retry later; this does not mean the mod lacks a target release. |
| Not a referenced mod JAR | The manifest entry is outside the checked mods/*.jar files, such as a resource pack. It has not been checked. |
Example: check Sodium from Minecraft 1.20.1 to 1.21.1
This is a single-mod example verified against Modrinth on , not a live result for your pack.
- Source file
sodium-fabric-0.5.13+mc1.20.1.jar- Selected target
- Minecraft 1.21.1 · Fabric · Release only
- Result
- Target version found: mc1.21.1-0.8.13-fabric
The source version was identified by its file hash. A corresponding release exists for the target, but this does not test other mods, dependencies or world compatibility. Future queries may return a newer release.
What this check covers
The checker reads referenced mod JARs from your MRPack manifest and identifies their exact SHA-1 hashes on Modrinth. It then looks for a published version matching your target Minecraft version, loader and release filter. No mod files are downloaded or changed.
“No target version found” means no matching release was returned by Modrinth. “Not identified” means this exact file could not be identified there. Neither result proves a mod cannot work. The report does not validate dependency chains, scripts, configs, worlds or runtime conflicts.
MRPack compatibility checker FAQ
Can I upload individual JAR files, a CurseForge export or a normal ZIP?
This checker accepts .mrpack files only. It checks referenced JARs directly under mods/ in the manifest. It does not scan JARs bundled inside overrides. A CurseForge export can first be processed with the ZIP to MRPack converter, but unmatched files will still need separate review.
Does this Minecraft mod compatibility checker detect conflicts?
It checks published version availability for a Minecraft version and loader. It does not analyze bytecode, resolve dependency chains, inspect crash logs or detect all conflicts between mods.
Why is a mod not identified on Modrinth?
The exact file hash may not be indexed on Modrinth, the file may come from another platform, or the MRPack manifest may have no valid SHA-1. This result means the checker could not identify the file; it does not mean the mod is incompatible.
Why was no compatible target version found?
After identifying the source file, Modrinth returned no release matching the selected game version, loader and release filter. Check those settings and the author's published versions. Beta or alpha releases are excluded unless you opt in.
Can I launch the whole modpack if every target version is found?
That result alone is not enough. Dependencies, configs, scripts, client/server requirements and world data may still differ. The checker does not change your pack; review the results and test a separate instance as described in the upgrade checking guide.