Mods and add-ons for Minecraft Bedrock

Mods for Minecraft Java, such as those for Fabric or NeoForge, don’t work on Bedrock. Bedrock has add-ons instead. An add-on is made of a behavior pack, which changes how the game works, and often a resource pack, which changes how it looks. You open the file on your device and turn the add-on on per world.

Below you’ll find how to install an add-on, where to find them and how to put them on your own Bedrock server. Checked in October 2026 with Bedrock 26.52 and Microsoft’s documentation.

Which files make up an add-on?

So if you search for Bedrock mods, what you’re really looking for is add-ons. A .jar file is a Java mod and won’t work on Bedrock. How Java mods work is explained in how to install Minecraft mods.

How do you install an add-on?

1. Open the file. On Windows, double-click the .mcaddon, .mcpack or .mcworld. On a phone or tablet, tap it and open it with Minecraft. Minecraft starts and imports the add-on. If you get a .zip, Microsoft suggests changing the extension to .mcpack or .mcworld.
2. Pick a world. Make a world with Create New World, or choose Edit World on an existing one.
3. Turn the add-on on. Go to Behavior Packs, find the add-on and choose Activate. If the add-on has a resource pack too, do the same under Resource Packs.
4. Turn on experiments if needed. Some add-ons only work with an experiment on, such as Beta APIs. You’ll find them under Experiments. Note: once an experiment is on, you can’t turn it off again in that world. So make a copy or a backup first.

Active behavior packs apply to all players in that world. If you turn on several add-ons that change the same thing, the pack at the top of the list wins.

Where do you find add-ons?

• Marketplace. The official in-game store, where you buy add-ons with Minecoins. According to the Minecraft Wiki, these packs can’t be put on your own server.
• CurseForge. Besides Java mods, CurseForge also has add-ons for Bedrock. How it compares to Modrinth is in CurseForge vs Modrinth.

An add-on is always a .mcaddon, .mcpack or .mcworld, sometimes packed as a .zip. If a site asks you to download an .exe or an installer, that’s not an add-on: skip it.

Add-ons on your own Bedrock server

On a server, you put the packs in place yourself, through the file manager in the game panel or through SFTP. For big worlds SFTP is easiest; how that works is in manage files with SFTP. Stop your server and make a backup first, as in create and restore a backup. There are two ways.

Way 1: upload a world with add-ons (recommended)

This is the easiest way, also for add-ons that need experiments. server.properties has no setting for experiments: you turn them on in the world itself, on your own PC.

1. Make the world on your PC. Turn the add-ons on as above, plus the experiments if needed.
2. Export the world. Choose Edit World on the world, then Export World. You get a .mcworld file. Minecraft also puts the packs you turned on inside it.
3. Unpack it. A .mcworld is just a zip file. Change the extension to .zip and unpack it. The folder holds level.dat and the db folder directly. Give the folder a simple name without special characters, for example Adventure.
4. Upload the folder. Put the whole folder in the worlds folder of your server through SFTP.
5. Choose the world. Open server.properties in the file manager and set level-name to exactly the same name, with the same capitals. Start the server.

Way 2: put separate packs on the server

Already have a world on the server and want to add an add-on? You can do that without uploading it again.

1. Unpack the add-on. Change the extension of the .mcpack or .mcaddon to .zip and unpack it, until you have one folder per pack with a manifest.json file in it.
2. Put the packs on the server. Behavior packs go in the behavior_packs folder, resource packs in resource_packs, both in the main folder of your server. That way every world on the server can use them.
3. Link them to your world. In your world’s folder, inside worlds, create the file world_behavior_packs.json, and world_resource_packs.json for resource packs. For each pack, add the uuid and the version from the header block of its manifest.json, like this: [{"pack_id": "uuid-of-the-pack", "version": [1, 0, 0]}]. For more packs, separate them with a comma.
4. Restart the server. Your world’s folder is the one named at level-name in server.properties.

Players are offered the server’s resource pack when they connect. To make everyone use it, set texturepack-required=true in server.properties. More settings are in edit the settings in server.properties.

Add-on not working on your server?

• The pack isn’t linked. A pack in behavior_packs does nothing until it’s listed in your world’s world_behavior_packs.json.
• The uuid or version is wrong. Copy them exactly from the header block of manifest.json, not from the modules block.
• The add-on needs an experiment. Turn the experiment on in the world on your PC and upload that world with way 1.
• It’s a Marketplace pack. Those don’t work on your own server.
• Wrong edition. A Java mod or .jar doesn’t work on a Bedrock server. For the differences between the two, read Minecraft Java vs Bedrock.