Home / Tool group

Convert Minecraft Packs: Java and Bedrock

Convert supported resource assets between Java ZIP and Bedrock MCPACK, inspect omissions and install the output for the matching edition.

Open the tool

Step-by-step workflow

1. Keep an untouched copy of your source pack. Start with sample pack A below if you want a small known input.
2. Choose Java to Bedrock for the Java ZIP sample, then upload it. Use the reverse direction for an existing Bedrock resource MCPACK.
3. Read the matched and skipped entries. A successful download does not mean every source file was translated.
4. Download the converted pack and retain the report. Use the separate model or PBR workflows only when those assets match the compatibility table.
5. Import the MCPACK on a Bedrock device that supports file import; activate it under world Resource Packs. Java ZIP output belongs in the Java resourcepacks folder.
6. Test in a separate world on the declared target version. Check active pack priority before concluding that a texture is missing.

Worked stone-texture example

Sample A is a Java resource pack containing an original stone texture. Its converted Bedrock example retains the same pixel image at the mapped Bedrock path. The comparison below shows actual archive entries, not a gameplay capture.

When content is skipped

Check the report against the compatibility table. Unknown paths, Java mod code and unsupported geometry do not become Bedrock behavior. Renaming a ZIP to MCPACK changes its name, not its contents.

When the pack does not appear

Check the selected edition, target version, import result and activation menu. An experimental block add-on needs both generated resource and behavior packs. Keep the original archive for recovery; website file checks do not establish in-game compatibility.

Java input pack A · Converted Bedrock example

Tool limits and troubleshooting · Merge compatible packs after conversion

{
  "direction": "java-bedrock",
  "mappingCount": 47,
  "matched": [
    {
      "from": "assets/minecraft/textures/block/stone.png",
      "to": "textures/blocks/stone.png"
    }
  ],
  "skipped": [
    {
      "file": "pack.mcmeta",
      "reason": "Not in the static-texture mapping"
    },
    {
      "file": "PACKLAB-README.txt",
      "reason": "Not in the static-texture mapping"
    },
    {
      "file": "EXAMPLE.txt",
      "reason": "Not in the static-texture mapping"
    }
  ]
}

Maintained by MCToolLab · Updated 28 October 2026. How our guidance and examples were made. Game and device validation is still required for pack outputs.