One-line distinction: looks vs logic

The simplest way to tell them apart is by what they change:

  • Resource pack = changes looks. Block and item textures, models, sounds, UI, fonts, language files—everything you “see” or “hear.” Install one and the world is still the same world; it’s just wearing a new skin.
  • Behavior pack = changes logic. How entities act, what mobs drop, what you can craft, how the game rules work—everything about “how the world runs.” This is what actually changes gameplay.

For example: re-texturing a zombie to look the way you drew it is a resource pack; making zombies drop diamonds or run faster is a behavior pack. The two often come in pairs—a lot of add-on content ships a behavior pack to change the logic plus a matching resource pack for the look, bundled into a single .mcaddon you install together. To learn about that packaging format, see What are .mcpack and .mcaddon.

They are separate from the world file

Behavior packs and resource packs are both Bedrock mechanics, and they’re content packs that are independent of the world save:

  • They’re stored and distributed separately from .mcworld, and must be enabled individually in-game to take effect.
  • One world can enable several packs; the same pack can be reused across different worlds.
  • Because they’re separate, diagnosing or repairing a world file never touches your packs, and vice versa. To first understand what the world file itself is and what’s inside it, see What is a .mcworld file.

This is also why importing a world and installing a pack are two different things: opening a .mcworld imports the world itself, while packs have to be loaded separately.

How packs are handled when converting from Java to Bedrock

Java Edition’s equivalent concepts are called data packs and resource packs, but they don’t work the same way as Bedrock’s behavior packs/resource packs. So when TopoBlocks converts a Java world to Bedrock, our handling is honest:

  • Java data packs/resource packs usually aren’t auto-applied to the converted world. Instead they’re listed in a separate item-by-item report, for you to handle on the Bedrock side using the matching approach.
  • Conversion is one-way, Java Edition → Bedrock, charged per run, with automatic refunds on failure; prices are shown in-app.
  • We never overwrite your source files—the original Java world, along with its hash, is preserved and traceable; conversion only generates new files.

For the details here—and which content goes into the report rather than being migrated automatically—see How data packs/resource packs are handled when converting to Bedrock. We don’t promise “100% lossless,” but we give you a compatibility score before you pay and an item-by-item change report afterward, so you can see clearly before deciding.