Live
Manifest Generator
Build a valid manifest.json from scratch — UUIDs, versions, and script modules handled for you.
Minecraft Bedrock · Free tool
Minecraft Bedrock manifest.json Validator
Paste or upload an existing manifest.json and get a field-by-field check against Bedrock's rules — required fields, UUID format, integer versions, modules, and dependencies.
Validate your manifest
Results Pending
Paste a manifest.json (or upload one) to see validation results.
How it works
How to use the manifest validator
Paste or upload your manifest
Copy your manifest.json into the box, or upload the file directly from your pack folder. Validation starts as soon as there is JSON to read.
Read the results
Errors are rules Minecraft relies on to load the pack — fix these first. Warnings flag unrecognized fields (usually typos) or preview-only formats. Each finding shows the exact field path, like header.uuid.
Fix and re-check
Edit the JSON in place — results refresh live. When the summary turns green, your manifest satisfies the checked rules.
Import the pack
Save the corrected manifest.json in the pack's root folder, zip it, and import into Minecraft. Use the Manifest Generator to build a fresh one if the file is beyond repair.
Questions
Manifest validator FAQ
What does the manifest validator check?
It checks the required fields (format_version, header, modules), UUID format, integer version arrays, min_engine_version for resource and behavior packs, script module requirements, dependencies, capabilities, metadata, and flags unrecognized fields that are usually typos.
Is my manifest uploaded anywhere?
No. The validator runs entirely in your browser — your manifest.json never leaves your device, and there is no server involved.
What is the difference between an error and a warning?
Errors are rules Minecraft relies on to load the pack, such as a malformed UUID or missing min_engine_version. Warnings flag suspicious or unstable content, like unrecognized fields (possible typos) or preview-only format_version 3.
Why does it say min_engine_version is missing?
min_engine_version is required for resource and behavior packs so Minecraft knows the oldest game version the pack supports. World templates and skin packs do not need it.
Can I validate format_version 1 or 3 manifests?
Yes. Format 1 (skin packs) is accepted, and format 3 is flagged with a warning because it is still preview-only and expects semver strings instead of version arrays.
What do I do after fixing the issues?
Save the corrected manifest.json into your pack's root folder, re-zip, and import the pack. The validator updates live as you type, so you can fix issues immediately.