Does the folder to MRPACK converter upload my files?

No. Files are read and packaged in your browser. Only JAR hashes are sent to the Modrinth API for version matching; the JAR contents are not uploaded.

Why are some mod JARs unmatched?

A JAR may come from another platform, be locally modified, be unavailable on Modrinth, or differ from the published file. Unmatched JARs can be bundled for private testing, but redistribution rights must be checked.

Can I upload the generated MRPACK to Modrinth?

Treat the result as a draft. Test it in a clean profile, confirm dependencies and environment rules, remove private files, and verify distribution permissions before publishing.

Folder to MRPACK Converter - Build a Modrinth Pack

Create MRPACK from a Minecraft folder

This folder to MRPACK tool turns a clean local instance into a testable Modrinth pack draft. Choose one source: folder mode works best for a normal launcher instance, while ZIP mode is useful when you already exported the instance. Processing stays in this tab.

Minecraft instance folder

Select the folder that contains mods/, config/, and other instance files.

Or use an exported ZIP

The ZIP should contain the instance folders, not an existing .mrpack.

Pack name

Version ID

Minecraft version

Mod loader

Loader version

Pack summary

Bundle unmatched JARs inside overrides/mods/ for private testing. I understand I must check redistribution permissions before sharing.

Choose a folder or ZIP to begin.

File	Result	Action in MRPACK

What this folder to MRPACK converter builds

A valid MRPACK is more than a renamed ZIP. It needs a root modrinth.index.json manifest, Minecraft and loader dependencies, downloadable file records, hashes, file sizes, and an overrides/ area for local pack content. This tool creates that structure from the files you select.

For each JAR under mods/, the converter calculates a SHA-1 hash locally and asks the Modrinth API whether that exact file is known. A match becomes a normal manifest file entry with verified hashes and a Modrinth download URL. Configs, scripts, resource packs, shader packs, default configs, and other selected local content are copied into overrides/. The final archive is generated with JSZip in your browser.

Input

A launcher instance folder or exported ZIP containing folders such as mods, config, resourcepacks, and kubejs.

Processing

Local hashing, Modrinth version matching, safe-path filtering, manifest creation, and override packaging.

Output

A draft .mrpack file plus an on-page report of matched, unmatched, copied, and excluded files.

How to convert a folder to MRPACK

Open the clean Minecraft instance you want to package. Remove saves, logs, crash reports, screenshots, accounts, and unrelated personal files first.
Select the instance folder or an exported ZIP. Enter the exact Minecraft and loader versions required by the pack.
Click Scan and match files. Review every unmatched JAR and excluded file in the results table.
Download the draft MRPACK, import it into a fresh Modrinth App or compatible launcher profile, and test a complete launch.
Before publishing, verify mod permissions, environment rules, dependencies, pack metadata, and any files bundled in overrides.

Example MRPACK output

The generated manifest follows format version 1 and includes the required dependency block. Matched mods are referenced as downloads instead of being silently copied into the archive.

{
  "formatVersion": 1,
  "game": "minecraft",
  "versionId": "1.0.0",
  "name": "My Modrinth Pack",
  "summary": "Generated from a local Minecraft instance folder.",
  "files": [
    {
      "path": "mods/example-mod.jar",
      "hashes": { "sha1": "...", "sha512": "..." },
      "downloads": ["https://cdn.modrinth.com/..."],
      "fileSize": 123456
    }
  ],
  "dependencies": {
    "minecraft": "1.21.1",
    "fabric-loader": "0.16.14"
  }
}

Files the converter excludes

Instance folders often contain machine-specific or private data that should not be distributed. The converter excludes common runtime paths such as logs/, crash-reports/, saves/, screenshots/, backups/, cache/, downloads/, and launcher metadata. It also skips operating-system files such as Thumbs.db and .DS_Store.

Filtering is a safety aid, not a guarantee. Always inspect the result. A custom launcher can store tokens, usernames, server addresses, or private configuration in unexpected paths.

Supported folder layouts

The converter accepts the common layout where mods/, config/, and related folders sit directly inside the selected instance. It also removes one normal wrapper folder, so selecting a directory named after your pack or opening a ZIP with one top-level pack folder should produce the same relative paths.

Recognized mod path: JAR files under mods/ are hashed and checked against Modrinth.
Override content: configs, scripts, KubeJS data, default configs, resource packs, shader packs, and other non-JAR files are preserved under their relative paths.
Nested launcher directory: a leading .minecraft/ or minecraft/ folder is removed before the MRPACK is built.
Unsupported archive: an existing MRPACK should be inspected with the reader instead of being fed back into this builder.

If your export uses a custom hierarchy, review the results table carefully. The path shown there is the path the pack will use after overrides/ is applied by a compatible launcher.

Matched JARs versus bundled JARs

Result	What the tool does	What you should check
Matched on Modrinth	Adds the published file URL, size, and hashes to the manifest.	Confirm the detected file is the version you intended.
Unmatched JAR, bundling off	Leaves the JAR out and reports it as unresolved.	Find an allowed source or replace the file before release.
Unmatched JAR, bundling on	Copies it to `overrides/mods/` for a private test build.	Verify copyright and redistribution permission before sharing.
Non-JAR pack file	Copies it under `overrides/` using its relative path.	Remove personal settings and machine-specific data.

Limitations and publication checks

This is a draft generator, not an automatic Modrinth approval system. It does not infer whether a mod is client-only or server-only, choose optional dependency rules, prove that every bundled file can be redistributed, or guarantee that a pack will run. It cannot match a modified JAR whose hash differs from the published Modrinth file. Other platforms may also host files that the Modrinth hash endpoint does not know.

Use the MRPACK Reader to inspect the finished manifest, the modrinth.index.json guide to understand each field, and the Modrinth upload guide before publishing. For the underlying specification, review Modrinth's official MRPACK format documentation.

Troubleshooting a folder conversion

The Modrinth lookup fails

Check your network connection and try the scan once more. The browser must reach api.modrinth.com to match JAR hashes. Your folder remains local even when the lookup fails, and you can reset the tool without changing the original files.

Every JAR is unmatched

Confirm that you selected the real instance root and that the files are ordinary JARs under mods/. Files downloaded from CurseForge, private servers, development builds, or locally modified copies may not have a matching Modrinth version. Do not bundle an entire unmatched set for public release without reviewing every file's permission.

The generated pack imports but does not launch

Recheck the Minecraft version, loader type, and loader version first. Then look for missing unmatched mods, client/server-only conflicts, Java version requirements, and configs that assume a different mod set. Importing into a new profile gives clearer results than testing over an existing instance with extra files.

The archive is unexpectedly large

Large resource packs, shader packs, and bundled unmatched JARs are stored inside overrides/. Turn off unmatched-JAR bundling, remove assets that should be downloaded separately, and start again from a clean pack folder.

Privacy and network behavior

The selected folder and ZIP contents are not posted to this website. Hashing and archive generation use browser APIs on your device. During matching, the tool sends a list of SHA-1 hash strings to Modrinth's public API and receives version metadata for exact matches. It does not send the JAR bytes, configs, saves, or the generated MRPACK. Like other pages on this site, normal web hosting, analytics, advertising, CDN, and third-party requests may still process technical information as described in the Privacy Policy.

Folder to MRPACK FAQ

Can I convert a Minecraft folder directly to MRPACK?

Yes. Select the instance folder, provide the game and loader versions, scan the files, and download the generated draft. A clean instance gives a safer and smaller result than your everyday profile.

Does the converter upload my folder?

No. File reading, hashing, ZIP creation, and the final download happen locally. The tool sends only JAR hash strings to the Modrinth API to look for exact published files.

Why does the tool require Minecraft and loader versions?

MRPACK launchers use the dependency block to create the correct environment. Guessing these values can produce a pack that imports but fails at launch.

Can I turn a server folder into MRPACK?

You can use a clean server-oriented folder, but review client-only mods, world data, server secrets, and environment rules first. The server installation guide explains the differences.

Is the generated file ready for public upload?

Not automatically. Treat it as a testable draft. Run a fresh-profile import, inspect the manifest, verify licenses and permissions, document external files, and remove private content before distribution.