How to Update Your Minecraft Mods in Bulk (Free, In Your Browser)

A new Minecraft version dropped, you want to move your mods to it, and you're staring at a mods folder full of cryptic JAR file names. Updating each one by hand — figuring out which mod it even is, then hunting down the matching build — is tedious. Mod Updater does the whole batch for you, right in your browser.

What Mod Updater does

Drop in your .jar files and it:

• Identifies each one by fingerprinting the file with a SHA-1 hash and matching it against Modrinth's database — so you learn exactly which mod and version every JAR is, even with a meaningless file name.
• Finds the right build for a loader (Fabric, Forge, NeoForge, Quilt) and Minecraft version you choose, for every recognized mod at once.
• Bundles the results into a single ZIP you can drop straight into your new mods folder.

Everything happens locally. Your files are hashed inside the browser and never uploaded — the only network requests are public Modrinth API lookups of those hashes.

What you'll need

• The .jar files from your current mods folder.
• The loader and Minecraft version you want to move to.
• A modern browser (Chrome, Firefox, Edge, Safari). Nothing to install.

Step by step

1. Add your JARs. Drag the .jar files from your mods folder into the tool, or click to select them. Identification starts automatically.
2. Review what was found. Each row shows the recognized mod with a ✓. Mods that couldn't be matched are flagged so you know to handle them separately.
3. Pick a target. Choose your loader and Minecraft version. Results refresh automatically — no "Find" button to press.
4. Check the matches. A ✓ means a build exists for your target. For any mod without one, an inline override lets you pick from the loaders and versions that mod actually publishes.
5. Download. Hit Download all as ZIP to grab every resolved build in one archive, then drop them into your new mods folder.

Mods that won't match

Matching relies on an exact file hash, so two kinds of JARs won't be recognized:

• CurseForge-exclusive mods. Only mods indexed on Modrinth can be matched.
• Repackaged or modified JARs. If a file has been altered after release, its hash no longer matches the original, so it can't be identified.

For those, update them manually from wherever you originally got them — Mod Updater handles the rest of the batch.

Is it private?

Yes. Your mod files never leave your device. Only the SHA-1 hashes are sent to the public Modrinth API to look up matches — never the JARs themselves.

Where to go next

Converted a .mrpack modpack earlier and now want to move the whole thing to a newer Minecraft version? That's a natural pairing — see Updating a Converted Modpack to a New Minecraft Version.