Minecraft Bedrock manifest.json Guide (2026)

A 2026 guide to Minecraft Bedrock manifest.json files: UUIDs, modules, dependencies, pack versions, preview manifest v3 notes, and common import errors.

2026 accuracy note This guide was built from current official documentation checked on May 2026. For preview APIs, always re-check the linked official docs before shipping a public download.

What manifest.json does

`manifest.json` tells Minecraft what the pack is, what type of content it contains, what version it is, and what other packs or script modules it depends on. If this file is wrong, the rest of the addon can be perfect and still fail.

UUID rules

Every pack needs a unique header UUID. Every module inside the pack also needs its own UUID. Do not reuse the same UUID between the Behavior Pack and Resource Pack, and do not reuse old tutorial UUIDs from the internet.

Modules and pack types

A Behavior Pack commonly uses a `data` module. A Resource Pack uses a `resources` module. Scripted Behavior Packs also include a `script` module with an entry file.

Use clear pack names and descriptions because these are player-visible in the Minecraft UI.

Dependencies between packs

If your Behavior Pack expects textures from a Resource Pack, declare the Resource Pack dependency by UUID and version. If your script uses the Script API, declare the `@minecraft/server` dependency as a module dependency.

Example
"dependencies": [
  { "uuid": "RESOURCE_PACK_HEADER_UUID", "version": [1, 0, 0] },
  { "module_name": "@minecraft/server", "version": "2.0.0" }
]

Versions and preview notes

For stable Bedrock packs, manifest version 2 remains the practical baseline for resource packs, behavior packs, and world templates. Microsoft documents manifest version 3 as preview-facing, including optional pack settings screens.

Do not use preview-only manifest features in a public download unless the page clearly says it requires Minecraft Preview or Beta.

Common import errors

`Missing dependency` usually means a UUID/version mismatch or only one half of the addon was installed. `Duplicate pack` usually means the same UUID exists in multiple imported copies. `Unknown pack name` often points to malformed JSON or an invalid manifest structure.

Official sources checked

These are the official or primary references used to keep this tutorial current: