Export a Modpack

[Meta] Please note that this page is missing images. They will be added at a later date.

You can export a modpack from CurseForge to share it with others. When you export a modpack, CurseForge creates a .zip file that contains all of the information required to make a copy of your modpack.

Understanding Import/Export Function

When you export a modpack, CurseForge will create a .zip file. At a bare minimum, this .zip file will simply include a single manifest.json file. This file is a structured list of every mod in your modpack. When your modpack is imported, the manifest.json list will be used to download all of the correct versions of the mods you had when you exported the modpack. At a bare minimum, an exported modpack will have this file.

Beyond the manifest.json, the .zip file may include an overrides folder. As the name implies, the contents of this folder will override any files generated by the modpack when the players runs the pack. If you have changed mod config files and want those changes to be present when someone imports your modpack, you would have to put these changes in the overrides folder.

The structure of the overrides folder matches that of the modpack itself. For example, if there is a config folder present in the overrides folder, then its contents will override whatever is generated when someone import's your modpack and runs it.

Step 1: Right-click a modpack, then click ExportShare Profile

Right-click any modpack to open its options menu. Click ~~Export~~Share Profile.

Step 2: Click "Export as .zip file"

Two options will appear when you click Share Profile. Select the one on the left that says "Export as .zip file."

Step 3: Select what to export

After clicking Export ~~Profile,~~as .zip file, a window should appear. You will see a list of items each with a checkbox to their left. These items are files and folders within your modpack's folder.

Non-empty folders will have an arrow to the left of their checkbox. Clicking this arrow will show that folder's contents along with a new column of checkboxes for those sub-items.

At a bare minimum, you need to have each mod's .jar file selected. Beyond that, there isn't any correct list of things to select because it all depends on your own preference.

Verify only mods are selected within mods folder

Open the mods folder to see all of the mod files. Ensure that only the .jar files are selected and that any etra files or folder are not selected. If you need extra files to be present in the mods folder, then you can select them, but this is rarely ever required.

Select any changed config files

It is generally a bad idea to have the entire config folder selected. Instead, you should select the individual files where you've made changes.

If you have pre-configured any config files and want these modified files to be present when someone imports your modpack, you will need to select them. Make sure that the config folder is unchecked, then open it to see its contents. Select the individual files or folders that you want to be present when your modpack is exported. Whatever you select here will overwrite whatever is generated naturally when someone runs your modpack.

Select any other files you'd like to have when your modpack is imported

Beyond each mod's .jar file and any of your changed config files, everything else is up to you. You should deselect everything else unless you have a specific reason for wanting it to be present when your pack is imported. For example, you could select the server.dat file so that when your modpack is imported the server list will look yours when you exported the modpack.

Step 3:4: Click Export

Once you have everything selected, click the orange Export button at the bottom-right of the window. A File Explorer window will open where you can select where you want the .zip file to be saved.