mcbepacks
Guide · 17 November 2026 · by IcyNutella

How to convert a texture pack between Java and Bedrock

Turn a Java resource pack into a Bedrock .mcpack, or a Bedrock pack into a Java one, with the free converter on mcbepacks. What converts, what doesn't, and how to use the new pack.

How to convert a texture pack between Java and Bedrock

Java and Bedrock packs do the same job, but they're built differently. A Java pack has a pack.mcmeta file and an assets folder. A Bedrock pack has a manifest.json file and a textures folder. Many textures have different names on the two editions, and some are laid out differently, so renaming a Java pack to .mcpack doesn't work. The pack has to be converted.

The mcbepacks converter does that for you, both ways, for free.

Convert a pack

  1. Open the converter.
  2. Choose the pack: a Java pack's .zip file, or a Bedrock .mcpack or .mcaddon file. On a computer you can drop it on the page instead.
  3. Wait while it converts. The progress bar shows how many textures are done.
  4. Press Download for Bedrock or Download for Java to save the new pack.

The converter works on your own device, so the pack isn't uploaded anywhere. It handles packs up to 500 MB, and once the page has loaded it even works without a connection.

Use the converted pack

  • On Bedrock: open the downloaded file and Minecraft adds the pack. Then turn it on in Settings, under Global Resources.
  • On Java: in Minecraft, open Options, then Resource Packs, then Open Pack Folder, and put the downloaded file there. Then choose the pack in the list. The converted pack is made for Java 1.21 and newer.

What converts

  • Blocks and items
  • Armour, chests and most mobs
  • Hearts, hunger, armour, the crosshair and the hotbar
  • Potions and tipped arrows
  • The glint on enchanted items
  • Animated blocks, like water, lava and fire
  • Grass, leaves and water, which the two editions colour differently
  • The pack's name, description, icon and credit files

Old PvP packs made for Java 1.8 convert well, since most of what they change is swords, armour, blocks and the HUD.

What doesn't

  • 3D models. Java and Bedrock use different kinds of block and item models.
  • Menus and inventory screens. Each edition draws its screens in its own way.
  • Custom skies and other OptiFine features. Java needs OptiFine for custom skies and connected textures, and Bedrock doesn't have OptiFine.
  • Fonts and sounds. Fonts are laid out differently on each edition, and sounds aren't converted yet.
  • Particles, most paintings and shaders.
  • The part of an add-on that changes how the game plays. Only resource packs can be converted.

When it's finished, the converter lists everything it left out and why, file by file, so you know exactly what you're getting.

If it doesn't work

  • "That's a data pack" or "That's a behaviour pack": these change how the game plays, not how it looks, so there's nothing to convert.
  • "That pack is locked": its creator has protected the files, so it can't be converted.
  • The zip can't be opened: some zips use an unusual kind of compression. Unzip the pack, zip it again the ordinary way and try once more.
  • Your device ran out of memory: big packs can be too much for a phone. Try it on a computer.

Only convert packs you're allowed to

Convert your own packs, or packs whose creator is happy for you to convert them. The converted pack keeps the original's name, description, icon and credit files, so the credit stays with the person who made it. If you share a converted pack, say where it came from and who made it.

Consoles

Converting doesn't make packs work on Xbox, PlayStation or Switch, because consoles can't open pack files. The console guide explains the ways console players can still play with custom packs.

The converter's list of matching texture names comes from GeyserMC's open-source PackConverter.

More news and guides