How to Create a Custom Modpack on CurseForge

Building your own modpack lets you curate the exact Minecraft experience you want, hand-picked mods, balanced configs, and a single download link your friends or community can use. CurseForge is the largest mod distribution platform, and its tooling makes it straightforward to create custom modpack CurseForge projects even if you have never published anything before.

Prerequisites

• The CurseForge App (or the Overwolf-based launcher) installed on your machine.
• A free CurseForge account with author permissions enabled.
• A target Minecraft version, this guide assumes 1.21+ on Forge or NeoForge, but the workflow applies to Fabric packs too.

Step 1, Create a custom profile

Open the CurseForge App and click Create Custom Profile. Pick your Minecraft version and mod loader. Give the profile a clear internal name, this is not the final pack title, just your workspace label. The app generates a fresh .minecraft instance folder with the correct loader already installed.

Choosing between Forge, NeoForge and Fabric

Forge has the largest legacy mod library. NeoForge is the community fork that most new mods for 1.21+ target. Fabric is lighter but has a smaller pool of content mods. If you plan to include tech and magic mods, Forge or NeoForge is usually the safest bet. Check that every mod you want supports the same loader and the same Minecraft version before you start adding them.

Step 2, Add mods

Click Add More Content inside the profile. The CurseForge search pulls from over 100,000 projects. Filter by your Minecraft version and loader to avoid incompatible results. Add mods one at a time and launch the game after every five or so additions to catch conflicts early. Key tips:

• Read the mod description for listed incompatibilities.
• Install required library mods (Architectury, Geckolib, Bookshelf, etc.), CurseForge resolves most dependencies automatically.
• Keep a changelog in a text file so you remember why you added or removed something.

Step 3, Configure and balance

Launch the profile at least once so every mod generates its config files under config/. Then tweak values: ore generation rates, mob difficulty, recipe changes, loot tables. This is where a custom modpack goes from "random collection of mods" to a polished experience. Tools like CraftTweaker or KubeJS let you add or remove recipes via scripts.

If you are building a server pack, test with a local dedicated server too. Some client-side mods crash the server, and some server-side mods have no visible effect on the client. Separate your mod list into client-only and shared categories early.

Step 4, Test thoroughly

Before you publish, play through at least several hours of progression. Check that:

1. The game starts without errors in the log.
2. World generation produces the biomes and structures you expect.
3. Recipes do not conflict (two mods using the same crafting pattern).
4. Performance is acceptable, if TPS drops below 18 in single-player, the pack will struggle on servers. See our guide on using Spark for profiling.

Step 5, Export and publish

In the CurseForge App, right-click your profile and select Export Profile. The app creates a lightweight zip that contains only mod references and your config overrides, not the mod jars themselves. This is the format CurseForge uses to create custom modpack CurseForge listings.

Log in to curseforge.com, go to your author dashboard, and create a new project of type Modpack. Upload the exported zip, write a description with screenshots, and submit for review. Approval usually takes 24-48 hours.

Server-side distribution

If you want to host a server with your pack, export a server pack variant. Most server hosts accept CurseForge pack IDs directly, upload the zip to your panel or paste the project ID. For a deeper walkthrough on server setup, check out how to start a Minecraft server.

Maintaining your modpack

Mods update frequently. When you create custom modpack CurseForge projects, plan on releasing updates every few weeks. Use semantic versioning (1.0.0, 1.1.0, etc.) and include a changelog so players know what changed. Pin mod versions in your manifest if you need stability over bleeding-edge features.

Common mistakes

• Mixing loader versions, a Forge mod will not load on NeoForge unless the author explicitly supports both.
• Ignoring RAM, large packs need 6-8 GB allocated. Set -Xmx8G in JVM arguments.
• Skipping a test world, always generate a fresh world after major mod additions to catch worldgen crashes.

Need hosting that handles custom content? Astroworld Hosting, NVMe SSDs, full panel access, 24/7 support.