Missing Mods After Conversion — Causes and Fixes

Symptom

Your converted ZIP downloads successfully, but when you extract and inspect mods/, fewer JAR files are present than the modpack lists.

Most common cause: dead download URLs

Mod authors sometimes delete old versions or move files. The URL inside the .mrpack manifest then returns a 404. The converter logs each failed download and continues — so the final ZIP is missing those mods.

Fix

Use a newer version of the modpack. The modpack maintainer regularly republishes .mrpack files with updated URLs.

Second cause: network interruption

If your connection drops mid-conversion, some downloads fail. The converter retries each file twice, but a persistently flaky connection causes drops.

Fix

Run the conversion on a stable connection (wired Ethernet, or a strong Wi-Fi signal). For mobile users, switch to Wi-Fi for large packs.

Third cause: browser memory limit

On low-memory devices (some older phones), the browser may abort downloads to free memory.

Fix

Close other tabs, restart the browser, and run the conversion on a desktop if possible for packs over 200 mods.

Less common cause: regional CDN block

In a few regions, the Modrinth CDN is intermittently slow or blocked. A VPN may help, but the more reliable workaround is to retry at a different time of day.