Source Pack
- Name
- -
- Minecraft
- -
- Loader
- -
- Mods
- -
Free CurseForge to Modrinth utility
Upload a CurseForge modpack export containing manifest.json and download a Modrinth-compatible .mrpack. Files are matched by hash, overrides are preserved, and anything missing is listed instead of silently guessed.
Required: manifest.json at the ZIP root. Other ZIP layouts are rejected.
Choose a CurseForge modpack export ZIP to begin.
Your .mrpack download will appear after conversion.
Download MRPackMatched and unmatched files will be listed after conversion.
Download ReportStart with the ZIP created by CurseForge's modpack export feature. A normal instance folder or renamed ZIP does not contain the metadata required for verified conversion.
Export the modpack with its manifest and overrides. Do not rename or rearrange the ZIP.
Drop the export above. The archive is inspected locally before conversion begins.
Check how many files matched Modrinth and which required files need manual attention.
Download the MRPack and report, then import the result into Prism Launcher or Modrinth App.
CurseForge identifies files with project and file IDs. MRPack uses download URLs and cryptographic hashes. This converter connects those formats without guessing from JAR filenames or pretending every ZIP contains enough metadata.
The browser checks the Minecraft version, mod loader, file references, and overrides path.
CurseForge file hashes are compared with Modrinth so only byte-identical files are selected.
A new modrinth.index.json is created and valid overrides are copied into the output.
The result is reopened and checked. Any unmatched CurseForge files are listed separately.
Use the ZIP created by the CurseForge app's modpack export feature. It should contain
manifest.json at the root and may include an overrides folder
for configs, scripts, resource packs, and other pack-specific files.
| Input | Supported | Reason |
|---|---|---|
| CurseForge export ZIP | Yes | Contains project IDs, file IDs, Minecraft version, loader, and override metadata. |
| Normal Minecraft instance ZIP | No | Local JAR filenames alone are not reliable enough to reconstruct a safe MRPack manifest. |
| ZIP containing modrinth.index.json | Already MRPack-like | It may only need the correct .mrpack extension and validation. |
Some CurseForge files are unavailable on Modrinth or cannot be redistributed. This tool does not silently bundle those JAR files or replace them with a similarly named version. It creates a partial output only when at least one verified match exists and records every unmatched item for review.
Use the main converter when you already have a Modrinth MRPack and need a normal ZIP for a server panel, manual inspection, or a launcher that cannot import MRPack files.
Resolve a Modrinth pack into a familiar ZIP layout.
Read pack metadata and file rules without converting it.
Understand which ZIP formats can be converted and why manifest data matters.
No. This tool requires a CurseForge export ZIP with manifest.json at its root. Ordinary instance ZIPs do not contain reliable project and version metadata.
The file is excluded from the generated index and added to the conversion report. The result is labeled as a partial MRPack so missing files are never hidden.
No. The archive stays in your browser. Only the project IDs and file IDs from the manifest are sent to the protected metadata service for matching.
Yes. Valid files from the CurseForge overrides folder are copied into the MRPack overrides folder after path and archive safety checks.
Launchers with native MRPack support include Modrinth App, Prism Launcher, ATLauncher, and other compatible launchers. A partial pack may still need manual repair first.
Different mod versions can have similar filenames. SHA-1 matching confirms that the CurseForge file and Modrinth file contain identical bytes before the Modrinth URL is added.