MCPACK to Java converts a Bedrock .mcpack resource pack into a Minecraft Java Edition texture pack you can drop straight into .minecraft/resourcepacks. It works right in your browser — choose your .mcpack, pick your Minecraft version, and download a ready Java .zip.

📱➜🖥️
Drag & drop your .mcpack file here or click to choose a Bedrock resource pack

Runs entirely in your browser — nothing is uploaded. This is a best-effort converter: it builds a valid Java pack (pack.mcmeta + pack.png), remaps the Bedrock folder layout, and renames the common block/item textures whose Bedrock and Java names differ. Textures with no Java equivalent keep their original name and may need manual fixing; block models/states are not converted.

How to convert a .mcpack to Java

  1. Click the box above, or drag your Bedrock .mcpack onto it.
  2. Pick the Minecraft Java version you play (this sets the pack format).
  3. Press Convert & download. The tool rebuilds the pack in Java’s layout and downloads a .zip.
  4. Put the .zip in .minecraft/resourcepacks and enable it in Options → Resource Packs.

What this converter does (and what it can’t)

It builds a valid Java pack — a pack.mcmeta and pack.png — then remaps the Bedrock folder layout to Java’s (for example textures/blocks → assets/minecraft/textures/block) and renames the common block and item textures whose Bedrock and Java names differ (wood types, the 16 colours, and well-known blocks like stone bricks and mossy cobblestone).

Because Bedrock and Java name many textures differently and use different block models, a .mcpack can never map perfectly to Java. Textures with no Java equivalent are copied with their original name and may not show in-game, and block models/states are not converted. This is a best-effort tool — the same limitation applies to every Bedrock-to-Java texture converter.

Why are Bedrock and Java texture packs different?

Java Edition stores textures under assets/minecraft/textures/ and identifies them by the block/item ID. Bedrock uses a textures/blocks and textures/items layout with its own naming and JSON files (terrain_texture.json, item_texture.json). The two editions were built separately, so the file names and the model systems don’t line up one-to-one. That is why a converter can move and rename the obvious textures, but some always need a manual touch.

Frequently asked questions

Is this mcpack to Java converter free?

Yes — free, unlimited, no account, and your file is never uploaded (it is processed in your browser).

Will every texture work after converting?

The pack structure, icon and common block/item textures will. Less-common textures whose Bedrock name has no Java match keep their original name and may not display — that part is best-effort.

Does it convert Bedrock addons or behaviour packs?

No. This tool is for resource / texture packs (.mcpack). Add-ons and behaviour packs use entirely different systems that Java doesn’t support.

My pack uses .tga files — what happens?

Java only reads PNG, so TGA textures are skipped and counted. Convert them to PNG first if you need them.

Which Minecraft version should I pick?

Pick the version closest to the one you play. The version only sets the pack_format; if it is slightly off, Minecraft just shows an “outdated/incompatible” note and still loads the pack.