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

Comment convertir un MRPack en ZIP

Choisissez votre méthode d'entrée : téléchargez un fichier .mrpack, entrez un ID de projet Modrinth ou collez une URL de téléchargement directe.

L'outil lit modrinth.index.json, copie les overrides et télécharge les JARs de mods depuis leurs URLs.

Enfin, il empaquette le tout dans un fichier ZIP avec un manifeste pack-info.json.

Si certains mods échouent au téléchargement, un fichier FAILED_DOWNLOADS.txt est inclus avec les fichiers manquants et leurs URLs.

Questions fréquentes

La conversion a-t-elle lieu sur mon ordinateur ou sur un serveur ?

Votre fichier .mrpack est lu et le ZIP final est construit dans le navigateur avec JSZip. Nous ne stockons pas votre pack en tant que téléchargement utilisateur. Les overrides sont copiés localement. Les JARs de mods listés sont téléchargés depuis les URLs dans modrinth.index.json. Lorsqu'un CDN bloque le navigateur, la page peut utiliser un petit assistant de téléchargement sur le même site (/api/proxy) uniquement pour récupérer ce fichier public. Ce n'est pas la même chose que de télécharger votre pack sur nos serveurs, mais la conversion nécessite toujours un accès réseau et n'est pas entièrement hors ligne.

Pourquoi certains mods échouent-ils au téléchargement pendant la conversion ?

Certains hôtes ou CDNs refusent la requête, limitent le débit ou expirent les liens. Lorsqu'un fichier ne peut pas être récupéré, le convertisseur construit quand même le ZIP et ajoute FAILED_DOWNLOADS.txt avec le chemin attendu et toutes les URLs de téléchargement pour ce mod. Téléchargez ces quelques fichiers manuellement et placez-les dans les dossiers listés.

Puis-je utiliser le ZIP de sortie avec le lanceur officiel de Minecraft ?

Pas comme une importation de modpack en un clic. Le ZIP est une structure de dossiers normale (mods, configs des overrides, etc.). Installez Fabric, Forge, Quilt ou NeoForge vous-même, puis copiez les dossiers extraits dans votre instance. Les panneaux de serveur qui acceptent une extraction ZIP fonctionnent souvent de la même manière. Prism, MultiMC et les lanceurs similaires peuvent préférer importer le .mrpack original lorsqu'ils le supportent.

Cela fonctionne-t-il avec les packs Fabric, Forge, Quilt et NeoForge ?

Oui pour les fichiers .mrpack valides de Modrinth. Le format est des chemins de fichiers indépendants du chargeur plus un champ de dépendances. Ce convertisseur n'installe pas le chargeur pour vous. Vérifiez pack-info.json dans le ZIP et installez le chargeur correspondant et la version de Minecraft séparément.