Minecraft PBR Resource Pack Builder
Upload loose textures, ZIP, or MCPACK; preserve supported texture folders; generate missing material maps; repair the package structure; and export a pack Minecraft can import directly.
Free workflow: local processing and 256px or 512px export are included after sign-in. Mapper+ unlocks output above 512px.
Start the browser workflow
Privacy: image decoding, archive inspection, channel processing, and package creation run in the browser.
What makes a Bedrock PBR resource pack installable?
An installable Vibrant Visuals pack is a ZIP-compatible MCPACK whose manifest.json sits at archive root, declares a resources module, uses different valid UUIDs, includes the pbr capability, and requires Bedrock 1.21.120 or newer. Each texture_set JSON chooses normal or heightmap and chooses MER or MERS without declaring both alternatives.
Bedrock PBR packaging choices
| Choice | Use it when | Export contract |
|---|---|---|
| MER | Metalness, emission, and roughness are sufficient. | RGB plus metalness_emissive_roughness. |
| MERS | Subsurface scattering is also needed. | RGBA plus the MERS property and overlap resolution. |
| Normal | Broad compatibility and authored tangent detail are needed. | Generated normals use DirectX style; supplied tangent normals are preserved for review. |
| Height | Block relief should be height-derived. | 8-bit single-channel grayscale PNG; heightmap declared and normal omitted. |
How to use Minecraft PBR Resource Pack Builder
Upload loose maps or an existing pack
ZIP and MCPACK are CRC-checked locally; wrapper roots, manifests, texture sets, references, duplicate basenames, and supported blocks/items/entity/particle folders are inspected.
Confirm material grouping and roles
Assign base color, normal, height, scalar maps, packed MER/MERS, and optional subsurface sources.
Choose one valid material contract
Select MER or MERS, select normal or height, and generate absent derived maps only when needed.
Download and install MCPACK
The builder writes manifest.json at root, adds pbr capability, preserves or creates UUIDs, increments imported pack versions, and includes install notes plus a build report.
Minecraft PBR Resource Pack Builder FAQ
Can I upload an existing ZIP or MCPACK?
Yes. The builder audits it locally and reconstructs a safe, root-correct pack from decoded texture inputs.
What Bedrock version does the pack require?
The generated manifest requires Bedrock 1.21.120 or newer and declares the pbr capability for Vibrant Visuals.
Should a texture set use normal or height?
Choose one. The builder requires normal for imported item, entity, or particle materials because height output is intended for block materials.
How are imported pack updates handled?
With identity preservation enabled, valid header and module UUIDs are kept and the patch version is incremented. Disable it to create a separate pack identity.
Why does Minecraft show purple and black?
That often means texture-set metadata references a missing or misnamed image. The preflight checks incoming references and generated references exactly match exported stems.