How to convert a Java texture pack to Bedrock
A Java texture pack does not work on Bedrock, and renaming the .zip to .mcpack does not help: the two editions use different folders, file names and description files. To convert a pack, every texture has to be moved to Bedrock’s folder, renamed to Bedrock’s file name and given a manifest.json. The free Texture Pack Converter does this in your browser in a few seconds, and works the other way too.
Step by step
- Open the Texture Pack Converter and choose your pack: a Java
.zip, a Bedrock.mcpackor PNG textures. - Pick what to convert it to: Bedrock Edition, or Java Edition and a version.
- Click Convert. Your browser loads the target edition’s texture list and converts every texture it can.
- Read the report: how many textures were converted, and which were skipped and why.
- Download the converted pack, or open it in the editor to repaint the skipped textures first.
What converts, and what does not
The converter knows which Java texture plays the same part as which Bedrock texture, worked out from the game files of both editions. Most textures have the same picture on both, so they can be copied as they are.
| Converts | Does not convert |
|---|---|
| Most block and item textures (around four in five) | Textures that exist in only one edition |
| Many mob and environment textures (sun, moon, clouds) | Textures laid out differently: chests, many mob skins, banners, the menus and particles |
| Animated textures: .png.mcmeta becomes a flipbook entry | Models, sounds, fonts, splash texts and shaders |
| The pack icon, name and description | OptiFine extras such as connected textures and custom item textures |
Anything skipped is listed in the report with the reason, so you know exactly what to repaint. Open the converted pack in the Texture Pack Maker to fix those textures on their 3D models before you download it.
Convert a Bedrock pack to Java
Choose a Bedrock .mcpack (or .mcaddon) and pick Java Edition and the version you play. Textures go to Java’s folders and names, .tga images become PNG, flipbook animations become .png.mcmeta files and the pack gets the right pack.mcmeta for that version.
Update an old Java pack to a new version
The same converter updates Java packs between versions. Many textures were renamed over the years, most of all in 1.13, when textures/blocks became textures/block and hundreds of files got new names. Choose the old pack, pick Java and your version, and every renamed texture moves to its new name. Texture names inside the pack’s own models are updated too.
It works backwards as well, for example to make a 26.3 pack for 1.8.9.
Install the converted pack
- Bedrock: open the
.mcpack(double-click on Windows, Open with Minecraft on phones), then activate it under Settings > Global Resources. - Java: put the
.zipin theresourcepacksfolder and move it to Selected.
More detail in How to install texture packs. If something looks wrong, see Texture pack not working.
Questions
Is the converter free?
Yes, with no account and no limits. The pack is converted in your browser and never uploaded.
Will the pack look the same on Bedrock?
Converted textures look the same. Textures that are skipped fall back to Bedrock’s own, and Bedrock’s lighting and Vibrant Visuals can make colours look a little different.
Can I convert a Java shader pack to Bedrock?
No. Bedrock does not load custom shader code. Use a Vibrant Visuals pack instead, which you can make with the Shader Maker.
Can I turn PNG files into an .mcpack?
Yes. Choose a PNG, or a zip of PNGs, named like the game’s textures (for example stone.png), and convert it to Bedrock.
Can I use the converted pack on a console?
Consoles cannot import files. Add the pack to a world on a PC or phone and join that world, or use a Realm or server that has it.