Skip to main content
The Modrinth launcher lets you create custom modpacks by combining mods, resource packs, shaders, and configurations into a shareable package.

​
Starting a New Modpack

There are several ways to start creating a modpack:
1

Create a new profile

Click Create Profile and select your desired Minecraft version and mod loader.
2

Add mods

Browse and install mods from Modrinth or add them manually.
3

Configure settings

Adjust mod configurations, resource packs, and shader settings as needed.
4

Export as modpack

Right-click the profile and select Export as Modpack.

​
Adding and Removing Mods

​
Adding Mods to Your Modpack

You can add mods from multiple sources:
  1. From Modrinth: Browse the mod library and click Install
  2. From file: Drag and drop .jar files into the mods folder
  3. By version ID: Use the advanced installation option to install specific versions
When you install a mod with dependencies, the launcher automatically adds all required dependencies to your modpack.

​
Removing Mods

To remove mods from your modpack:
  • Right-click a mod in your instance and select Uninstall
  • Or delete the mod file from the mods folder
Removing a mod that other mods depend on may cause crashes. The launcher will warn you if dependencies will be broken.

​
Configuring Mod Settings

Customize your modpack’s behavior through mod configurations:

​
Mod-Specific Configuration

1

Launch the game once

Many mods create configuration files on first launch.
2

Close the game

Exit Minecraft to safely edit configuration files.
3

Edit configs

Navigate to your profile’s config folder and modify the configuration files (usually .toml, .json, or .properties files).
4

Test changes

Launch the game again to verify your configuration changes work as expected.

​
Including Configurations in Export

When exporting your modpack, you can choose which files to include:
  • config/: Mod configuration files
  • resourcepacks/: Custom resource packs
  • shaderpacks/: Shader packs
  • options.txt: Minecraft settings
  • servers.dat: Server list
Include configuration files in your modpack export to ensure players get the intended experience without manual setup.

​
Exporting and Sharing Modpacks

Export your modpack as a .mrpack file to share with others:
1

Open export dialog

Right-click your profile and select Export as Modpack.
2

Configure export options

  • Name: Give your modpack a descriptive name
  • Version: Set the version number (e.g., “1.0.0”)
  • Description: Add a description explaining what your modpack includes
  • Files to include: Select which folders/files to bundle:
    • mods/ (automatically included)
    • config/
    • resourcepacks/
    • shaderpacks/
    • options.txt
    • Other custom files
3

Choose export location

Select where to save the .mrpack file on your computer.
4

Export

Click Export to create the modpack file.

​
Modpack Format

Modrinth uses the .mrpack format:
  • Standards-based: Uses the Modrinth modpack specification
  • Cross-launcher compatible: Can be imported by other launchers supporting the format
  • Metadata included: Contains version info, dependencies, and project links
  • Efficient: Only includes override files; mods are downloaded on install
The .mrpack format doesn’t include the actual mod files (just references to them). This keeps the file size small and ensures users always get the latest compatible versions.

​
Publishing to Modrinth

To share your modpack on Modrinth:
  1. Create a project on modrinth.com
  2. Upload your .mrpack file as a version
  3. Add description, screenshots, and tags
  4. Publish for others to discover and install

​
Importing Existing Modpacks

You can import modpacks from various sources:
  1. Browse modpacks on modrinth.com
  2. Click Install or download the .mrpack file
  3. The launcher will automatically import and set up the modpack

​
Updating Modpacks

Keep your modpack up to date:

​
Updating Individual Mods

  • Click the Update button next to mods with available updates
  • Or use Update All to update all mods at once

​
Versioning Your Modpack

When making changes:
  1. Update the version number (e.g., 1.0.0 → 1.1.0)
  2. Document changes in the description
  3. Export and upload the new version
Use semantic versioning:
  • Major (1.0.0 → 2.0.0): Breaking changes or major overhauls
  • Minor (1.0.0 → 1.1.0): New mods or features
  • Patch (1.0.0 → 1.0.1): Bug fixes or small tweaks

​
Best Practices

Test Thoroughly

Always test your modpack before sharing to ensure:
  • All mods load correctly
  • No conflicts or crashes
  • Performance is acceptable
  • Configurations work as intended

Document Everything

Provide clear documentation:
  • List of included mods
  • System requirements
  • Known issues
  • Installation instructions

Balance Performance

Consider performance impact:
  • Test on minimum spec systems
  • Optimize configuration files
  • Include performance mods if needed
  • Set appropriate memory allocation

Update Regularly

Maintain your modpack:
  • Check for mod updates
  • Fix reported bugs
  • Add new content
  • Communicate changes to users

​
Troubleshooting

​
Export Fails

  • Ensure all mods are from Modrinth or included as overrides
  • Check for corrupted mod files
  • Verify you have write permissions to the export location

​
Large File Size

  • .mrpack files should be small (only overrides)
  • If large, you may be including unnecessary files
  • Check that mod files aren’t being bundled (they should be referenced)

​
Import Issues

  • Verify the .mrpack file isn’t corrupted
  • Check your internet connection for downloading mods
  • Ensure you have sufficient disk space
  • Review the launcher logs for specific errors