How to Install Add-ons

Bedrock doesn’t support Java-style plugins or mods. The equivalent is Add-ons — behavior packs (change gameplay/logic) and resource packs (change textures, models, and sounds), often bundled together as a single .mcaddon.

Note

Add-ons bought from the in-game Marketplace are tied to the account that purchased them and won’t install this way. This is for free, community-made add-ons — sites like MCPEDL have large libraries of them.

Using the Addon Manager

AtomicHost has a dedicated tool for this, rather than needing to hand-edit files — go to More → Addons in the sidebar. It only appears on servers the panel detects as Bedrock.

Click the upload area and pick a .mcaddon, .mcpack, or plain .zip (up to 256MB)
It’s scanned for every valid pack inside, however it’s laid out — nested folders, behavior-only or resource-only packs, and .mcpack files still zipped inside a .mcaddon are all handled automatically
Valid packs are unpacked into behavior_packs/ or resource_packs/ and registered so Bedrock actually loads them, staying in sync with valid_known_packs.json and your active world’s pack files behind the scenes — no manual JSON editing needed

You’ll get a green “Deployed 1 pack to server” confirmation, and the pack appears under Installed Addons with an Active badge and a Load order: 1 · 1 pack(s) line underneath its name.

Note

If you get “no manifest.json could be found,” the archive genuinely doesn’t contain a valid pack — it isn’t a size or format limit on the tool’s end.

Managing Installed Addons

Each installed addon has three actions:

Enable / Disable — toggles whether Bedrock loads the pack, without deleting anything. Confirmed instantly (“Addon disabled. Files are kept on disk - re-enable any time, or use Remove to delete them for good.”), and safe to flip back and forth.
Remove — permanently deletes the pack’s files from the server. Only use this if you actually want it gone for good.
Untrack — stops the Addon Manager from managing it, without touching its files or registration on the server at all.

Warning

As of this writing, Remove and Untrack don’t reliably work — clicking either can silently do nothing. If you need a pack gone, go to Files → behavior_packs/ or resource_packs/ and delete its folder directly (it’s named <load-order>_<PackName>_<id>, e.g. 01_MyPack_8f3a1c2e) — that’s confirmed to work. The Addon Manager may still list it afterward as a stale entry pointing at now-deleted files; that’s cosmetic only.

Tip

Packs that were already on your server before you first opened this page — uploaded by hand, or left over from a reinstall — show up labeled (found on server). If one of those isn’t something you want this page managing, Untrack it rather than Remove (bug above notwithstanding) — the intent is that nothing on the actual server gets touched.

Load Order

If two installed addons modify the same asset — a texture, a UI file — whichever loads last wins. Drag a pack by its handle to reorder the list; the bottom of the list wins conflicts. If something looks wrong after installing multiple overlapping addons, this is usually why.