Modshift

For Fabric, Forge, NeoForge and Quilt packs

Know what breaks before you update.

Drop in your mods folder and pick the Minecraft version you want. Modshift checks every mod, flags the ones that hold you back, and points to maintained replacements for the ones that won't make it.

  • No sign-up
  • Files stay on your computer
  • Mod data from Modrinth

Drop your mods folder here

or a Modrinth .mrpack export

Files are hashed in your browser with SHA-512. Only the hashes are sent, never the .jar files.

What you get back

Not a wall of green ticks. A short list of what needs doing, with the problems on top.

Example packFabric · 1.21.1 → 26.3 · 26 mods
2blockers
  • EMINo known migrationNo 26.3 build yet
  • SAMPLE Legacy LightsReplacement found→ SAMPLE Modern Lights
    ✓ Handheld light sources✓ Light from entitiesVerified successor
  • Iris ShadersUpdate available1.8.1 → 1.9.0
  • SodiumReady
  • + 22 more ready

  1. Blockers first

    Mods that stop the upgrade sit at the top. The ones that already work stay out of your way.

  2. Replacements that were checked

    When a mod is abandoned, you see its maintained fork or successor and which features carry over.

  3. A plan, not a verdict

    Update these, swap those, wait on the rest. Your mods folder is never touched.

Most checkers stop at a red cross.

Modrinth tells you whether a release exists. Modshift helps when it doesn't.

A typical compatibility check
SAMPLE Legacy Lights✕ No compatible version

That's it. You go looking on your own.

Modshift
SAMPLE Legacy Lights✕ No 26.3 build
SAMPLE Modern Lights✓ Fabric 26.3

Covers handheld and entity lights. Listed as a verified successor.

How it works

  1. 1

    Pick your pack

    A mods folder, a few .jar files, or a Modrinth .mrpack export.

  2. 2

    Fingerprint it locally

    Your browser hashes each file and looks the hash up on Modrinth. The files stay where they are.

  3. 3

    Choose where you're going

    Pick a Minecraft version and loader. You get what's ready, what needs an update, and what to replace.

What leaves your computer

Modshift reads metadata. It never uploads, edits, or deletes your files. Read the full privacy policy.

Sent

  • A SHA-512 hash of each mod file
  • The Minecraft version and loader you pick
  • Anonymous usage events, like how many files were scanned
  • Feedback and reports, only when you press send. An unknown file’s name is included only if you report it.

Never sent

  • Your .jar files
  • Worlds, configs, and saves
  • Who you are. There's no account.

What it checks, and what it can't

Modshift plans a Minecraft modpack upgrade from published metadata. Treat it as a map, not an autopilot.

Checks

  • Which version of each mod you have, matched by file hash on Modrinth
  • Whether a release exists for your target Minecraft version and loader
  • Maintained forks, ports, and successors for abandoned mods
  • Which features a replacement keeps and which it drops

Can't guarantee

  • That every mod works together at runtime. Mixin and config conflicts still happen.
  • That your worlds convert cleanly to the new version
  • Anything about files that aren't on Modrinth. They show up as Unknown.
  • That a replacement matches every option of the original

Before switching, back up the instance and its worlds, apply changes to a copy, and load a test world first.

Questions

Are my .jar files uploaded?

No. SHA-512 hashes are calculated locally in your browser. The mod files themselves stay on your device.

Does Modshift modify my mods folder?

No. Modshift only analyzes metadata and provides a migration plan.

Can Modshift guarantee that my modpack will launch?

No. It checks published metadata compatibility. Runtime conflicts can still exist between mods.

Which loaders are supported?

Fabric, Forge, NeoForge, Quilt, and any other loader Modrinth lists. The list is refreshed from Modrinth.

What does Unknown mean?

The file could not be identified from Modrinth metadata.

Where does mod information come from?

Mod metadata comes from Modrinth. Replacement relationships are curated and verified separately.

A mod has no replacement. Now what?

Press "Request a migration path" next to it. Requests are counted, and the most-requested mods are researched first. You can also send a note through Feedback.