Live
Manifest Generator
Build a valid manifest.json from scratch — UUIDs, versions, and script modules handled for you.
Minecraft Bedrock · Free tool
Minecraft Bedrock Pack Version Generator
Pick the correct next version for your pack — with sane bumping rules and a consistency check for every version in your manifest.
Bump your pack version
Next version
[1, 0, 1]Patch — bug fixes and tweaks. Existing imports update cleanly.
Paste this version into header.version and every module — same triple everywhere.
Check versions across the manifest
Results Pending
Paste labeled versions, one per line (e.g. header = 1.0.0), to check consistency.
How it works
How to use the pack version generator
Enter the current version
The triple from header.version in your manifest. Bedrock compares these numerically, so 1.10.0 is a bigger version than 1.9.9 — bumping any part moves the pack forward.
Pick the bump type
Patch for fixes, minor for features, major for breaking changes. The tool warns if a part would pass 255 and handles the rollover for you.
Put the same version everywhere
Copy the result into header.version and every modules[].version. The consistency check below catches any field you missed.
Check the whole manifest
Paste your labeled versions, one per line. The checker reports drift between header and modules, duplicate labels with conflicting values, and lines that do not parse.
Questions
Pack version generator FAQ
How do pack versions work in Bedrock?
Every pack manifest is an integer version triple like [1, 2, 0] in header.version and in the same. When comparing packs with the same UUID, Minecraft treats the higher version as a newer import and replaces the older copy.
Which bump should I choose?
Patch for bug fixes and small tweaks, minor for new features or content, and major for major changes or large rewrites. Bump header.version and every module version at the same time.
Must module versions match the header version?
Yes, by convention — the header and each module should carry the same version so the pack updates as one unit. The consistency check on this page flags any drift.
What happens at the 255 limit?
Each version part must stay between 0 and 255. If a bump would push a part past 255, the tool tells you to bump the next level up, for example [255, 0, 255] → [255, 1, 0].
How is min_engine_version different from the pack version?
min_engine_version is the oldest game version your pack supports; the pack version tracks your releases. Engine-version lines are exempted from the equality rule so they never cause false warnings.
Why are versions arrays instead of 1.2.3 strings?
format_version 2 manifests use integer arrays like [1, 2, 0]. String versions belong to the preview-only format_version 3, which this tool does not target.