MRPack to ZIP Converter

Convert a Modrinth .mrpack into a standard mods and overrides ZIP. Free, no account. Pack files stay local. Mod downloads need network access.

MRPACK

Drop your .mrpack file here

or click to browse files

No account required. Your .mrpack is read in the browser and the ZIP is assembled there. Mod files are fetched from public download URLs (a same-site helper may be used when a CDN blocks the browser). We do not ask you to create an account to convert a pack.

MC Toolbox · Modpack Utilities

Convert .mrpack to ZIP when your launcher or server cannot import Modrinth packs

A .mrpack is mostly a manifest. It contains modrinth.index.json with each mod path, download URL, and hash. The JAR files are often not inside the archive. Launchers that support Modrinth fetch those files for you. The official launcher, Technic, and many server panels do not, so they reject the .mrpack.

This free MRPack to ZIP converter does the fetch step in your browser. It reads the index, downloads each listed mod when the host allows it, copies override files (configs, scripts, resource packs), and builds a ZIP you can extract into a game instance or server folder. You still need the correct mod loader and Minecraft version. The ZIP is not a one-click install for every launcher.

What actually happens inside

Four steps. Unpacking and ZIP assembly run in your browser tab. Mod downloads use the public URLs from the index (and a same-site helper if a CDN blocks direct browser access).

Step 1

Read the index

Opens the mrpack (it is a ZIP archive) and parses modrinth.index.json for pack name, game version, loader dependencies, and the full mod list.

Step 2

Copy overrides directly

Files in overrides/, client-overrides/, and server-overrides/ are copied into the output. That covers configs, scripts, and bundled resource packs the author included.

Step 3

Fetch each mod

Each mod entry has one or more download URLs. The converter tries them and writes the file at the path in the index. If every URL fails, the path and URLs go into FAILED_DOWNLOADS.txt so you can finish manually.

Step 4

Build and offer the ZIP

Assembles the ZIP with compression, adds a pack-info.json summary (name, version, loader hints), and starts a browser download. Your original .mrpack is not stored as a site account upload.

Which launchers actually support .mrpack

The short version: Prism, ATLauncher, and MultiMC handle .mrpack natively. CurseForge support is partial. The official launcher, Technic, and most server panels need a ZIP instead.

Launcher	Supports .mrpack	Needs ZIP conversion	Notes
Prism Launcher	Yes	No	Import from Modrinth or file
ATLauncher	Yes	No	Import from Modrinth tab
MultiMC	Yes	No	Add Instance, then Import
GDLauncher	Yes	No	Search and one-click install
CurseForge App	Partial	Sometimes	Mainly CurseForge-hosted packs
Official Launcher	No	Yes	Install the mod loader first
Technic Launcher	No	Yes	ZIP import only
Server panels	No	Yes	Pterodactyl, Apex, Shockbyte, and similar

Questions I actually got asked

Plus a few I figured people would ask before they do.

Does the conversion happen on my computer or a server?

Your .mrpack file is read and the final ZIP is built in the browser with JSZip. We do not store your pack as a user upload. Overrides are copied locally. Listed mod JARs are downloaded from the URLs in modrinth.index.json. When a CDN blocks the browser, the page may use a small same-site download helper (/api/proxy) only to fetch that public file. That is not the same as uploading your pack to our servers, but conversion still needs network access and is not fully offline.

Why do some mods fail to download during conversion?

Some hosts or CDNs refuse the request, rate-limit, or expire links. When a file cannot be fetched, the converter still builds the ZIP and adds FAILED_DOWNLOADS.txt with the expected path and every download URL for that mod. Download those few files manually and place them in the listed folders.

What is modrinth.index.json inside an mrpack?

It is a bill of materials: each mod path (for example mods/sodium-fabric-0.5.8.jar), integrity hashes, and one or more download URLs. The .mrpack is often small because the JARs are not always embedded. Launchers or this tool fetch them. Overrides folders hold configs and other files that do ship inside the archive.

Can I use the output ZIP with the official Minecraft Launcher?

Not as a one-click modpack import. The ZIP is a normal folder layout (mods, configs from overrides, and so on). Install Fabric, Forge, Quilt, or NeoForge yourself, then copy the extracted folders into your instance. Server panels that accept a ZIP extract often work the same way. Prism, MultiMC, and similar launchers may still prefer importing the original .mrpack when they support it.

What is the difference between overrides and mod downloads?

Overrides are files packed inside the .mrpack (configs, scripts, resource packs, datapacks). Mod entries are usually URL references. The converter downloads them into the paths from the index. Both end up in the output ZIP when downloads succeed.

Does this work with Fabric, Forge, Quilt, and NeoForge packs?

Yes for valid Modrinth .mrpack files. The format is loader-agnostic file paths plus a dependencies field. This converter does not install the loader for you. Check pack-info.json in the ZIP and install the matching loader and Minecraft version separately.

Other tools you might want while you're here

ZIP → MRPack

Convert a CurseForge modpack export ZIP to .mrpack

Manifest Generator

Create pack.mcmeta and Bedrock manifest.json

Pack Converter

Adapt Java and Bedrock resource pack structure

Cómo convertir un MRPack a ZIP

Elige tu método de entrada: sube un archivo .mrpack, introduce un ID de proyecto de Modrinth o pega una URL de descarga directa.

La herramienta lee modrinth.index.json, copia los overrides y descarga los JARs de mods desde sus URLs.

Finalmente, empaqueta todo en un archivo ZIP con un manifiesto pack-info.json.

Si algunos mods fallan al descargarse, se incluye un FAILED_DOWNLOADS.txt con los archivos faltantes y sus URLs.

Preguntas frecuentes

¿La conversión ocurre en mi ordenador o en un servidor?

Tu archivo .mrpack se lee y el ZIP final se construye en el navegador con JSZip. No almacenamos tu pack como una subida de usuario. Los overrides se copian localmente. Los JARs de mods listados se descargan desde las URLs en modrinth.index.json. Cuando un CDN bloquea el navegador, la página puede usar un pequeño ayudante de descarga del mismo sitio (/api/proxy) solo para obtener ese archivo público. Eso no es lo mismo que subir tu pack a nuestros servidores, pero la conversión aún necesita acceso a internet y no es completamente offline.

¿Por qué fallan algunos mods al descargarse durante la conversión?

Algunos hosts o CDNs rechazan la solicitud, limitan la velocidad o expiran los enlaces. Cuando un archivo no se puede obtener, el conversor aún construye el ZIP y añade FAILED_DOWNLOADS.txt con la ruta esperada y todas las URLs de descarga para ese mod. Descarga esos pocos archivos manualmente y colócalos en las carpetas listadas.

¿Puedo usar el ZIP de salida con el lanzador oficial de Minecraft?

No como una importación de modpack con un clic. El ZIP es una estructura de carpetas normal (mods, configs de overrides, etc.). Instala Fabric, Forge, Quilt o NeoForge tú mismo, luego copia las carpetas extraídas en tu instancia. Los paneles de servidor que aceptan un ZIP extraído a menudo funcionan de la misma manera. Prism, MultiMC y lanzadores similares pueden preferir importar el .mrpack original cuando lo soporten.

¿Esto funciona con packs de Fabric, Forge, Quilt y NeoForge?

Sí, para archivos .mrpack válidos de Modrinth. El formato son rutas de archivo independientes del cargador más un campo de dependencias. Este conversor no instala el cargador por ti. Revisa pack-info.json en el ZIP e instala el cargador correspondiente y la versión de Minecraft por separado.