Minecraft Mods vs Add-ons: What's the Difference?

Mods (Java Edition)

True game modifications — compiled code loaded by a mod loader (Fabric, NeoForge, Forge, Quilt). They can:

• Add entirely new systems: dimensions, machines, magic, worldgen
• Rewrite rendering and physics (Sodium, Iris, physics mods)
• Chain into modpacks of hundreds of mods (skyblock, kitchen-sink packs)
• Cost: free; source: Modrinth, CurseForge; risk: version lock-in — mods must match your game version, and big updates break them

Limits: Java only, and they can’t run on consoles or vanilla servers without the server also being modded — see make a server.

Add-ons (Bedrock Edition)

Official, Mojang-supported content packs:

• Behavior packs — new entities, items, recipes, loot, scripting API logic
• Resource packs — textures, models, sounds, UI
• Installed per world (or globally for resource packs); file formats .mcaddon/.mcpack
• Two sources: community sites (free) and the Marketplace (partner-made, Minecoins, the only route onto consoles)
• Realms supports add-ons — a Bedrock Realm can run pack content for every invited friend

Limits: the API can’t touch core engine behavior the way Java mods can — no new dimensions, no renderer changes, and experimental features sit behind world toggles.

Side-by-side

Which should you use?

Playing on Java and want real transformation → mods. Playing on Bedrock or with console friends → add-ons. Playing both → this is the real split between editions — our Java vs Bedrock guide covers the rest of it.

What to read next

• How to Install Mods — loaders, folders, safety
• Install Shaders — the graphics side of modding
• Multiplayer Guide — playing pack content with friends