Idle
Enter a Modrinth project ID or slug before converting.
MRPACK TO ZIP
MRPack to ZIPConverter
Use this MRPack converter to turn Modrinth .mrpack files, project slugs, or download links into launcher-ready ZIP files in your browser.
Runs in your browser as a Modrinth pack to ZIP tool. Your local .mrpack file is not uploaded to a server; referenced files are fetched directly from their source URLs.
MRPack to ZIPCurseForge ZIP to MRPackBrowser-first conversion
Crafting Converter
Idle›
Output Slot
ZIP archive
Local files stay in this browser session. Project ID and URL modes fetch files directly from public URLs.
Local files stay in this browser session. Project ID and URL modes fetch files directly from public URLs.
Converting...
Preparing MRPack source... Reading modrinth.index.json... Downloading referenced files... Building ZIP archive...
ZIP generated
Conversion complete. Click the button to download the ZIP.
Conversion failed
Referenced downloads can still fail when a source URL is missing, blocked by CORS, too large, rate limited, or temporarily unavailable. The converter fails fast for unsafe inputs and reports partial download problems instead of silently hiding them.
What is an .mrpack file?
MRPack vs ZIP is mainly a format and launcher compatibility question. An .mrpack file is Modrinth's modpack format: it keeps the pack metadata and tells the launcher where to fetch each required mod, resource pack, shader, or config file.
Inside most packs, modrinth.index.json records the Minecraft version, loader, dependencies, file paths, hashes, and download URLs. Local files such as configs, default options, shader presets, and custom assets usually live in overrides, which must be copied into the rebuilt archive.
A regular ZIP modpack is more portable because many launchers, panels, and manual install workflows already know how to unpack a standard archive. MRPack to ZIP conversion keeps the important manifest and override content together so you can move the pack into places that do not understand .mrpack directly.
This MRPack to ZIP page is deliberately focused on one job: read the Modrinth pack structure, collect the referenced files that the browser can access, keep the override folders intact, and produce a launcher-ready ZIP without changing the tool into a general modpack editor.
How the converter flow works
Choose a source, resolve the manifest, copy overrides, fetch the referenced files, then download the rebuilt archive.
Choose a source
Enter a Modrinth project ID, paste a direct .mrpack URL, or upload a local file. Project ID mode looks up the selected Modrinth release, while upload mode keeps the source file inside your browser session.
Resolve referenced mods
The browser reads modrinth.index.json, copies overrides, and fetches referenced files from their listed URLs. That keeps the Minecraft modpack converter focused on the real manifest contents instead of guessing which mods belong in the pack.
Prepare the ZIP
The output is a standard ZIP archive with the converted pack files, copied overrides, and any FAILED_DOWNLOADS.txt report needed for missing files. The goal is a practical MRPack to ZIP result that common launchers can inspect or import.
Real conversion limits
The browser enforces a 100 MB MRPack source limit, a 250 MB referenced file limit, a 1 GB total referenced files limit, and a 3000 manifest files limit before or during conversion.
Referenced downloads can still fail when a source URL is missing, blocked by CORS, too large, rate limited, or temporarily unavailable. The converter fails fast for unsafe inputs and reports partial download problems instead of silently hiding them.
When some files cannot be fetched, the ZIP includes FAILED_DOWNLOADS.txt so you can see the original path, source URL, and reason that needs manual attention. This makes the MRPack to ZIP output easier to repair when a mod host blocks browser downloads.
Which launchers need ZIP?
Some launchers support .mrpack directly. Others work better with a standard ZIP archive, especially when you are importing manually or preparing files for a server panel.
Import targetMRPack pathZIP pathUse case
Prism Launcher / MultiMC / ATLauncher
MRPack path
Usually supportedZIP path
OptionalUse native .mrpack import first. Convert only when you need a standard archive for sharing, inspection, or manual repair.
CurseForge and generic ZIP importers
MRPack path
PartialZIP path
UsefulZIP can be easier when the launcher expects an archive layout instead of a Modrinth manifest.
Official Minecraft Launcher / Technic
MRPack path
Not directZIP path
Often neededThese workflows usually need manual profile files, copied mods, and configs rather than a raw .mrpack import.
HMCL / PCL2 / regional launchers
MRPack path
Varies by versionZIP path
Helpful fallbackA ZIP archive is useful when the exact launcher build does not recognize Modrinth packs.
Server panels and manual installs
MRPack path
Not idealZIP path
PreferredZIP archives are easier to upload, unpack, audit, and distribute outside a dedicated Modrinth-aware launcher.