Read the CurseForge ZIP
The ZIP is opened locally in the browser and manifest.json is validated before conversion continues.
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.
Use a CurseForge export that contains manifest.json and optional overrides.
The ZIP is read in your browser. CurseForge file metadata is resolved through a protected API proxy.
The ZIP is read in your browser. CurseForge file metadata is resolved through a protected API proxy.
Use this page for CurseForge ZIP exports that include manifest.json plus the optional overrides directory.
The converter reads project and file references from manifest.json, keeps override files as bundled content, and prepares a Modrinth-compatible .mrpack output.
The browser reads the archive, resolves CurseForge metadata, performs Modrinth matching, and then builds the MRPack.
The ZIP is opened locally in the browser and manifest.json is validated before conversion continues.
CurseForge file metadata is requested through the protected API proxy, then compatible files are checked with Modrinth matching.
Matched files become Modrinth references, while CurseForge-only files and overrides are bundled into the output.
These limits describe what the converter can prove safely in the browser and where conversion can stop.
The ZIP must contain a readable manifest.json. Missing or malformed manifests are failure cases because there is no reliable file list to convert.
CurseForge file metadata goes through a protected API proxy. If that proxy or the CurseForge response fails, matching and bundling can be incomplete.
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 whole conversion job.