9MinecraftToolsMinecraft Bedrock Pack Validator

Minecraft Bedrock Pack Validator

Drop an .mcaddon, .mcpack or zip and find the reasons it will not import: broken JSON, a reused UUID, a version written as a string, a missing script entry.

← All 137 tools

Part of Bedrock & Pack Tools — all tabs in one tool.

manifest.json

Checks

Common Questions

What is a Minecraft Bedrock manifest json file?

A manifest.json file is a required metadata file located at the root of every Bedrock pack containing format_version: 2, pack descriptions, and two distinct version 4 UUID strings for identification.

How do you make an addon for Minecraft Bedrock?

Create a root folder containing a valid manifest.json alongside either a behavior_packs or resource_packs subfolder, then compress the directory into a .zip archive and rename the extension to .mcaddon.

Why do Minecraft Bedrock manifests require two UUIDs?

Bedrock manifests require two unique UUID values to identify the overall pack in the header section and its functional type in the modules section. Bedrock & Pack Tools generates valid v4 UUIDs automatically.

How do you import an addon into Minecraft Bedrock?

Open the exported .mcaddon or .mcpack file directly to launch Minecraft Bedrock, which automatically installs the contents into the development_behavior_packs or development_resource_packs folder located inside your local com.mojang directory.

What format do Java Edition custom block models use?

Java Edition custom block models use JSON files located in assets/minecraft/models/block/ with coordinate arrays constrained to values between -16.0 and 32.0 on the X, Y, and Z axes.