A Minecraft modpack you make yourself is really just a modded instance, a loader, a Minecraft version, and a mod list, packaged so someone else's client can rebuild it exactly. The CurseForge app and the Modrinth App both handle that packaging, so making your own modpack comes down to three steps: create an instance, add mods to it, then export the result. This guide covers building a personal pack for single-player or a small friend group. Already have a pack you want to install instead of build? See how to install a Minecraft modpack.
Pick a loader and Minecraft version before you add any mods
Every mod added has to match two things, the mod loader and the Minecraft version, so decide both before installing a single mod. Fabric is the lightest loader and usually the first to get new mod updates. Forge has the oldest and largest mod library. NeoForge is a modern fork of Forge that split away around Minecraft 1.20.1 and does not run Forge-only mods despite the shared history. Quilt is a fork of Fabric built for extra loader hooks, and it runs most Fabric mods, but not every Fabric mod is tested against it, so treat Quilt compatibility as likely rather than guaranteed. Changing the loader or the version later usually means checking every mod's compatibility again from the start.
- Fabric, lightweight and modern, needs the separate Fabric API library for many mods
- Forge, the oldest and largest mod ecosystem, still the safest bet for older or niche mods
- NeoForge, a modern fork of Forge for newer versions, incompatible with Forge-only mods
- Quilt, a Fabric fork with extra hooks, runs most Fabric mods but isn't a guaranteed match for every one
Build your modpack with the CurseForge app
In the CurseForge app, building a pack starts with a new profile rather than a new mod.
- 1.Open the Minecraft tab and click Create.
- 2.Name the profile, choose a Minecraft version, then choose the mod loader and loader version.
- 3.Click Create and let the app download that version and loader.
- 4.Open the new profile and click Add More Content to search for mods; CurseForge only shows mods that match the version and loader already set.
- 5.Launch the profile once with Play to confirm everything starts clean before adding more mods.
Build your modpack with the Modrinth App
The Modrinth App follows the same shape, instance first, mods second.
- 1.Click the plus icon in the app's Library sidebar to start a new instance.
- 2.Enter a name, pick a loader (Vanilla, Fabric, Forge, Quilt, or NeoForge), and pick the Minecraft version.
- 3.Click Create; the app downloads the matching Minecraft version and loader automatically, including Java if it's needed.
- 4.Open the instance and click Add Content to search Modrinth for mods; results are filtered to the loader and version already set.
- 5.Launch once to confirm everything loads before adding more.
Check mod compatibility before you add more
A mod built for the wrong loader or the wrong Minecraft version making it into the mod list is the single biggest reason a homemade modpack won't launch. Both apps filter search results to compatible mods, but that protection disappears the moment a mod is added manually or downloaded from a site that doesn't check loader and version for you. Before adding a mod from outside the app's own search, confirm its listed loader and Minecraft version match the instance exactly, and check whether it needs a separate library mod, most commonly Fabric API for Fabric mods, or another dependency named on its own page. The Fabric loader guide covers the loader-versus-API mix-up that trips up fresh Fabric setups, and the Forge and NeoForge guide covers the equivalent setup for those two loaders. More mods added this way is more surface for something to conflict; a ten-mod personal pack rarely breaks, while a pack pushing past a couple hundred mods almost always needs some troubleshooting before it settles.
Export and share your modpack
Export from the CurseForge app
Open the profile, click the three-dot menu next to Play, and choose Share Profile. Pick which folders to include (mods and config cover a normal pack; add worlds only when the save should go too), then choose Export as .zip or Generate Code. A generated code is tied to a CurseForge account and expires after seven days, so the .zip is the more durable option for anything meant to keep being shared.
Export from the Modrinth App
Right-click the instance in the library and choose Export. The app packages everything into a single .mrpack file, Modrinth's own modpack format. Send that file through any file host, or publish it as a project on Modrinth's website to make it publicly discoverable; a public project goes through Modrinth's moderation review before it's live.
Either format is enough for a friend to load the exact same pack on their own client. A .zip goes back into the CurseForge app through its Import button, and a .mrpack opens directly in the Modrinth App. Neither export includes a game world by default unless that folder was specifically checked, and putting the pack on a dedicated server is a separate job outside what either app's export button does.
Fix a modpack that won't launch
Work through the usual suspects in order before reinstalling anything.
- A mod built for the wrong loader or the wrong Minecraft version snuck into the list
- Two mods edit the same game system and conflict; the crash log usually names one of them
- A required library mod, most often Fabric API, is missing
- Not enough RAM is allocated for a pack with a lot of mods
Removing the last mod added and relaunching narrows this down fastest. If the pack still won't start with everything removed, the loader and Minecraft version pairing itself is the problem, not any single mod. The beginner troubleshooting checklist covers RAM allocation and the other common Minecraft crash causes in more depth.
Frequently asked questions
How do I create a modpack in Minecraft?
Open the CurseForge app or the Modrinth App, create a new profile or instance, and choose a Minecraft version and a mod loader together. Add mods through the app's own search so only compatible ones show up, launch once to confirm it works, then use the app's export option to package the mod list, configs, and loader details into a single file to share.
How do I make my own CurseForge modpack?
In the CurseForge app, open the Minecraft tab, click Create, name the profile, and choose a Minecraft version and mod loader. Open the new profile and use Add More Content to install mods; CurseForge only shows mods that match the chosen version and loader. When it's ready, use the profile's Share Profile option to export it as a .zip or a seven-day profile code.
Can I make a modpack without CurseForge?
Yes. The Modrinth App builds and exports modpacks the same way, using its own .mrpack format instead of a CurseForge zip. Create an instance, pick a loader and Minecraft version, add mods through the app's search, then export. A .mrpack file opens in the Modrinth App or in Prism Launcher, so it needs no CurseForge account at all.
Why won't my custom modpack launch?
The most common cause is a mod built for a different loader or Minecraft version than the rest of the pack, followed by a missing required library mod like Fabric API. Check the crash log for the mod it names, remove mods one at a time starting with the most recently added, and confirm every mod's listed loader and version actually match the instance.
