Convert CurseForge modpack exports into Modrinth-compatible .mrpack files.
The ZIP is read in your browser. CurseForge file metadata is resolved through a protected API proxy.
.zip
Drop your CurseForge ZIP hereOutput Slot
Use a CurseForge export that contains manifest.json and optional overrides.
Use this page for CurseForge ZIP exports that include manifest.json plus the optional overrides directory. It is not a general ZIP converter and does not infer a Minecraft modpack from an arbitrary archive.
The converter reads project IDs and file IDs from manifest.json, keeps override files as bundled content, and prepares a Modrinth-compatible .mrpack output. A ZIP to MRPack conversion depends on that manifest because CurseForge exports store file identity as project and file numbers instead of direct Modrinth version references. Without those IDs, there is no reliable way to confirm which public mod file should be matched.
Before a ZIP to MRPack run starts, the browser checks the archive shape and keeps the source ZIP local. The page expects a normal CurseForge export, not a hand-made mods folder, a launcher instance backup, or a random compressed directory. That boundary keeps the conversion predictable and makes error messages easier to understand. It also helps you decide whether a failed upload is a format issue, a missing manifest, or a mod file that needs manual attention before you try the export again.
When possible, CurseForge file metadata is compared with Modrinth version files by SHA-1 so matched files can become Modrinth references instead of bundled downloads. If a safe match is not available, the converter can bundle a resolvable CurseForge file, while still reporting when a download cannot be proven or fetched.
The browser reads the archive, resolves CurseForge metadata, performs Modrinth matching, and then builds the MRPack. This ZIP to MRPack flow is intentionally narrow: it follows the CurseForge manifest, preserves overrides, and avoids guessing at missing files.
The ZIP is opened locally in the browser and manifest.json is validated before conversion continues. The converter checks that the archive has the expected CurseForge export structure, then records the Minecraft version, loader data, files list, and overrides that should move into the MRPack.
CurseForge project IDs and file IDs are requested through the protected API proxy, then compatible files are checked with Modrinth matching and SHA-1 metadata. A successful match can become a Modrinth dependency reference; an unmatched but downloadable file can be bundled when that is safer than inventing metadata.
Matched files become Modrinth references, while CurseForge-only files and overrides are bundled into the output. The result is a focused ZIP to MRPack package that favors explicit manifest data over automatic editing or broad modpack repair.
These limits describe what the converter can prove safely in the browser and where conversion can stop. They also explain why a failed ZIP to MRPack attempt is usually a metadata, matching, or download boundary rather than a generic ZIP problem.
The ZIP must contain a readable manifest.json. Missing or malformed manifests are failure cases because there is no reliable file list to convert. If the archive was created by zipping a `.minecraft` folder or a launcher profile manually, it may include mods and configs but still lack the IDs needed for Modrinth matching.
CurseForge file metadata goes through a protected API proxy. If that proxy or the CurseForge response fails, matching and bundling can be incomplete. The proxy is used for file metadata and download authorization; it is not a place where the complete ZIP is uploaded for server-side conversion.
The archive is read in the browser. The privacy boundary is that file metadata may be sent to the proxy for lookup, while the local ZIP itself is not uploaded as a complete conversion package. This keeps the ZIP to MRPack tool focused on metadata resolution and output assembly instead of storing user archives.