How to make your own Minecraft modpack
Making a modpack takes more than dumping a few dozen mods into one folder. You have to pick mods that work well together, configure crafting recipes, test stability and optimize performance. This guide walks you through the whole process, from choosing your tools to publishing the finished pack.
Tools for making modpacks
To make a modpack you need a tool that helps you manage the mod list, mod versions and configuration. These are the three most popular approaches:
Prism Launcher: the simplest approach for beginners. You create a new instance with the mod loader of your choice (Fabric or NeoForge), add mods through the built-in Modrinth/CurseForge search, and once the pack is ready, you export it as a .mrpack file (Modrinth) or a .zip file (CurseForge). The whole process happens in a graphical interface without touching the terminal.
packwiz: a command-line tool for advanced creators. The modpack is defined as a set of TOML files in a Git repository, so you can track every change and collaborate with other people. Commands like packwiz modrinth add sodium automatically fetch the mod's metadata and update the pack manifest. Exporting to .mrpack or CurseForge format takes a single command.
MultiMC / ATLauncher export: both launchers let you export an existing instance as a modpack. It is a less elegant method than packwiz, but it works well when you already have a configured instance and simply want to share it with your friends.
Choosing mods
Rule number one: all mods must be for the same Minecraft version and the same mod loader. Mixing Fabric mods with NeoForge mods will not work. Pick one loader and stick with it.
Start with the foundations. Every modpack should include optimization mods: Sodium, Lithium and FerriteCore on Fabric, or their equivalents on NeoForge. Also add quality-of-life mods: Mod Menu (mod list), Roughly Enough Items (recipe browser) and JourneyMap (map). These mods give you a solid base to build the rest on.
Then add themed mods in batches. If you are planning a tech pack, start with one big mod (for example Create or Mekanism), test it, and only then add more. Avoid installing 200 mods at once: when something breaks, you will not know which mod is to blame.
Check mod licenses. Most mods on Modrinth allow you to include them in modpacks, but some mods on CurseForge have restrictive terms. Always read the "License" section on the mod's page.
Compatibility testing
Testing is the most important and most time-consuming stage of making a modpack. Here is a proven method:
- Add mods in batches of 10-15: after each batch, start the game and check that it does not crash. Join a world, fly through a few chunks, open your inventory and test basic interactions.
- Read crash logs: when the game crashes, open the file in
.minecraft/crash-reports/. The "Caused by" line points to the problematic mod. Paste the log on mclo.gs to get an automatic analysis. - Test interactions between mods: some mods work fine on their own but conflict with each other. For example, two mods that change terrain generation can cause strange artifacts. Pay special attention to mods that modify the same game systems.
- Play for a few hours: some problems only show up after a longer play session, for example memory leaks or FPS drops in later stages of the game when you have lots of machines running.
Configuration and recipes
Most mods generate config files in the config/ folder on first launch. It is worth going through them and adjusting them. Typical changes include disabling duplicate blocks (when two mods both add copper), adjusting mob difficulty and changing resource generation rates.
To change crafting recipes, use mods like KubeJS (Fabric and NeoForge) or CraftTweaker (NeoForge). They let you remove, modify and add recipes without editing the mods' source code. For example, you can make players progress through Create before they get access to Mekanism: just change the recipes so that the advanced machines require components from the earlier mod.
A quest system (for example FTB Quests) lets you guide players through your modpack. Quests can reward items, unlock new stages of progression and explain the mechanics of complex mods. A well-designed quest system turns a random collection of mods into a coherent experience.
Performance optimization
Modpacks with hundreds of mods can eat up 8-12 GB of RAM and stutter even on powerful computers. Here is how to prevent that:
- Optimization mods: Sodium, Lithium, FerriteCore, ModernFix and LazyDFU should be in every modpack. Together they can double your FPS and cut RAM usage by 30-40%.
- JVM arguments: set the Java flags in the modpack's default settings. The recommended Aikar's flags (
-XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200) noticeably improve memory management. - Limit world generation: if your modpack adds dozens of new biomes and structures, consider disabling the less important ones. Every extra piece of world generation slows down chunk loading.
- Test on weaker hardware: if the modpack runs smoothly on a computer with 16 GB of RAM and an RTX 4070, that does not mean it will run for players with 8 GB of RAM and integrated graphics. Test it in a virtual machine or ask someone with weaker hardware for feedback.
Publishing your modpack
Once the modpack is stable and tested, it is time to publish it. The two main platforms are Modrinth and CurseForge. Modrinth is newer, faster and shows no ads. CurseForge has a bigger user base and a payout program for creators. It is worth publishing on both platforms.
Before publishing, prepare:
- A name and description: a unique name, a catchy description and a list of the main mods. Explain what makes your modpack stand out and who it is for.
- Screenshots: at least 3-5 screenshots showing the most interesting parts of the modpack. The first screenshot matters most, because it appears in search results.
- An icon: a square 512x512 px image that makes your modpack stand out in the list.
- A changelog: a list of changes in every version. Players want to know what changed before they update.
- Hardware requirements: list the minimum and recommended RAM, so players know whether their computer can handle it.
To export from Prism Launcher, right-click the instance and choose "Export Instance". With packwiz, use the packwiz modrinth export command. You then upload the resulting .mrpack file to Modrinth or CurseForge.
Summary
Making a modpack is an iterative process: you add mods, test, configure and repeat. Take your time and do not try to build a pack with 300 mods right away. Start with 20-30 mods, get them stable, then expand step by step. Check out our list of the best modpacks of 2026 for inspiration, and if you need the modding basics, start with our guide to installing mods.