Why is ZIP to MRPack harder than MRPack to ZIP?

MRPack files usually reference remote mod files by project, version, URL, and hash. A normal ZIP often contains local JAR files without enough metadata to rebuild those references automatically.

Format guide

How to convert CurseForge ZIP to MRPack

Q: Can I rename a ZIP file to MRPack?

Renaming a ZIP file to .mrpack does not create a valid MRPack unless the archive already contains a valid modrinth.index.json manifest and the expected overrides structure.

You can convert a CurseForge modpack export ZIP when it contains manifest.json at the archive root. The converter uses the project and file IDs in that manifest to verify identical Modrinth files, preserve overrides, and create a compatible .mrpack without guessing from JAR filenames.

Last updated: August 13, 2026 Maintained by MRPack Converter

Convert a CurseForge modpack in five steps

Export the pack from CurseForge. Use the modpack export function and keep the resulting ZIP unchanged.
Check the archive. The ZIP must contain manifest.json at its root. An optional overrides folder may contain configs, scripts, resource packs, and other pack files.
Upload it to the converter. Open the CurseForge ZIP to MRPack converter, select the ZIP, and start conversion.
Review the result. Check the matched count and download the conversion report if required mods were not found on Modrinth.
Import the output. Download the generated .mrpack and import it into Prism Launcher, Modrinth App, ATLauncher, or another compatible launcher.

Expected time: a small or medium pack normally takes only a few minutes, but conversion time depends on the number of files and the metadata services used for verification.

How to export the correct ZIP from CurseForge

Open the modpack profile in the CurseForge app and use its export function rather than compressing the instance folder yourself. Keep the manifest and project references in the exported archive. If the ZIP opens directly into folders such as mods and config but has no root-level manifest.json, it is an ordinary instance ZIP and this converter will reject it.

New tool: if the ZIP was exported by CurseForge and contains manifest.json, use the ZIP to MRPack converter. The stricter limitations below still apply to ordinary Minecraft instance ZIP files.

Short answer: if your ZIP already contains a valid modrinth.index.json, it may already be an MRPack-like archive. If it only contains mods, config, and local JAR files, it cannot be safely converted into MRPack without reconstructing the missing metadata.

Why ZIP to MRPack is not the reverse of MRPack to ZIP

MRPack to ZIP is mostly an extraction and download workflow: read the manifest, fetch the files listed by URL when possible, copy overrides, and produce a familiar folder layout. ZIP to MRPack is different because the tool would need to identify every mod JAR, match it to the correct Modrinth project and version, calculate hashes, decide client or server environment flags, and write a correct manifest.

That matching step is the hard part. Many Minecraft mods are distributed from multiple hosts, have similar filenames, or publish separate files for Fabric, Forge, Quilt, NeoForge, and different Minecraft versions. Guessing incorrectly can create a pack that imports but breaks when launched.

What a valid MRPack needs

modrinth.index.json at the archive root.
Pack name, version ID, format version, and Minecraft dependencies.
Loader dependencies such as Fabric, Forge, Quilt, or NeoForge when required.
File entries with paths, hashes, environment flags, and download URLs.
An overrides folder for configs, resource packs, or other bundled files.

When renaming ZIP to MRPack works

Renaming only works when the ZIP already has the MRPack structure. For example, if you downloaded a file that was incorrectly named .zip but it contains modrinth.index.json at the root, changing the extension to .mrpack may let a launcher recognize it. If the archive only contains a normal Minecraft instance folder, renaming it will not add the required manifest.

Safer alternatives

If you want to play a pack, import the original MRPack in a launcher such as Modrinth App or Prism Launcher.
If you want to inspect an MRPack, use the MRPack Inspector before changing files.
If you need a normal ZIP for server hosting or manual repair, use the MRPack to ZIP converter.
If you need to publish a Modrinth pack, rebuild the manifest from verified project and version metadata instead of guessing from filenames.

Convert a CurseForge export ZIP

A CurseForge modpack export is different from an arbitrary ZIP because its manifest.json lists the Minecraft version, loader, project IDs, and file IDs. The ZIP to MRPack converter uses those IDs to obtain hashes and accepts a Modrinth match only when the file contents are identical. Unmatched items go into a report instead of being guessed from their filenames.

What to do when the output is partial

Some CurseForge files are not published on Modrinth or do not have an identical Modrinth version. The converter deliberately leaves those files out of the index and records them in the downloadable report. Review every required item before launching the pack. Do not replace a missing file with the newest similarly named mod unless its Minecraft version, loader, and dependency requirements all match the original pack.

How to import the converted MRPack

In Prism Launcher, choose Add Instance, select Import, and open the downloaded .mrpack. Modrinth App can also import compatible pack files. If the original pack is already available in Modrinth App, installing it directly is usually simpler than converting a CurseForge export. Use conversion when you specifically need to move an exported CurseForge pack into an MRPack-based workflow.

ZIP to MRPack questions

Can I rename a ZIP file to MRPack?

Only if the archive already contains a valid modrinth.index.json and MRPack structure. Renaming an ordinary Minecraft ZIP does not create the required metadata.

Can every CurseForge mod be moved to Modrinth?

No. A file may be exclusive to CurseForge or may not have an identical Modrinth release. Those items are reported as unmatched instead of being replaced automatically.

Does the converter upload my whole ZIP?

No. The archive is read and packaged in your browser. Only the CurseForge project and file identifiers required for metadata matching are sent to the protected lookup service.

Official format reference

The output structure follows the Modrinth MRPack format documentation, including its root manifest, dependency fields, hashes, download URLs, and overrides behavior.

Related guides

For the supported direction, see how to convert MRPack to ZIP. If you are using Prism Launcher, read how to import MRPack in Prism Launcher. If downloads fail, use the missing mods troubleshooting guide.