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.

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

Can you convert ZIP to MRPack?

Sometimes, but not by simply renaming the file. A valid .mrpack archive needs a modrinth.index.json manifest, dependency metadata, file hashes, download URLs, and an optional overrides folder. A normal Minecraft ZIP may not contain enough information to rebuild that structure automatically.

Last updated: July 8, 2026 Maintained by MRPack Converter

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.

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.