Read an MRPACK file
This reader runs locally in your browser. It opens the archive, finds modrinth.index.json, and shows the details that matter for troubleshooting: dependencies, file paths, hashes, download hosts, overrides, and client/server environment rules.
What the reader checks
- Pack metadata, Minecraft version, and mod loader dependencies.
- Referenced mod files, declared file sizes, download hosts, and hash fields.
- Client-only and server-only environment rules that affect manual installs.
- Override, client-overrides, and server-overrides files when a full archive is uploaded.
When to use this instead of converting
Use the MRPACK reader when you need to understand a pack before changing it. If you only want a normal ZIP output, use the MRPACK to ZIP converter. If you want to know what every manifest field means, keep the modrinth.index.json guide open next to this tool.
Manifest summary
Dependencies
| Dependency | Version |
|---|
Referenced files
The table shows up to 250 file entries so large packs remain readable in the browser.
| Path | Environment | Size | Hashes | Download hosts |
|---|
Override files
| Path | Group |
|---|
Download hosts
| Host | Files |
|---|
Raw manifest
What is an MRPACK reader?
An MRPACK reader is a small utility that opens a Modrinth modpack archive and reads the manifest inside it. The manifest is named modrinth.index.json, and it defines the pack name, version, dependencies, file list, hashes, download URLs, and environment rules. Reading those fields helps you decide whether to import the pack directly, convert it to ZIP, prepare it for a server, or troubleshoot a failed install.
The reader does not install mods and does not download every referenced file. That is intentional. It is for inspection and diagnosis. For a playable instance, use a launcher such as Modrinth App or Prism Launcher. For manual review or server staging, convert the MRPACK to ZIP after checking the manifest.
How to inspect an MRPACK file
- Choose the local
.mrpackfile from your computer. - Wait for the browser to find and parse
modrinth.index.json. - Check the Minecraft version and loader under dependencies.
- Review file paths, download hosts, hashes, and client/server rules before manual installation.
- Inspect override folders if the pack includes custom configs, resource packs, shader packs, or server-specific files.
Example checks before server setup
| Check | Why it matters | What to do next |
|---|---|---|
| Minecraft and loader versions | A Fabric pack will not run correctly in a Forge server profile, and a version mismatch can cause immediate crashes. | Create the server with the exact Minecraft and loader versions shown in dependencies. |
| Server-unsupported files | Client-only mods may be required for players but wrong for a dedicated server. | Review files marked server: unsupported before copying mod JARs. |
| Override folders | Configs and server-overrides may change gameplay or fix compatibility issues. | Copy the right override group for your target environment. |
| Download hosts | Some files come from external hosts and may fail in browser-based conversion because of CORS rules. | Use the host list to identify files that may need manual download. |
Privacy and limitations
Local archive reading happens in the browser tab. The file is not uploaded to this site. Pasted JSON also stays in the current page unless you copy it elsewhere. The tool can inspect the manifest and archive structure, but it cannot prove that every remote download URL is still available, safe, or compatible with your launcher. Treat the output as a technical checklist, not as a security guarantee.
Reference docs used for this reader
The field names and import workflow notes on this page follow the official Modrinth MRPACK format documentation, the Modrinth modpacks help page, and Prism Launcher's ZIP/MRPACK import documentation. CurseForge profile ZIP behavior is different, so check CurseForge's profile sharing documentation before assuming a raw MRPACK file will import there.
FAQ
Can I use this as an MRPACK viewer?
Yes. The page works as an MRPACK viewer for the manifest and archive structure. It shows the important metadata and file references without converting the whole pack.
Why are some mod JAR files not visible inside the archive?
Many MRPACK files store download references instead of bundling every JAR. The files array tells the launcher where to download each file and which hash should match after download.
Can I edit modrinth.index.json here?
You can paste and inspect edited JSON, but this page does not rebuild or sign a pack. If you are creating a public modpack, use a proper pack management workflow so file paths, hashes, and dependencies stay correct.
What should I do after reading the manifest?
If the pack looks correct and your launcher supports MRPACK, import it directly. If you need manual files, use the converter. If you are preparing a dedicated server, read the server setup guide and pay close attention to environment rules.