Minecraft has two editions, and they do not share resource packs. A pack made for Java Edition will not load on Bedrock (phones, consoles, Windows), and the other way around. The textures are often the same PNG files, so it is tempting to think you can just rename a folder. You can get surprisingly far that way, but not all the way.
This post compares the two formats and shows how to do the conversion in the browser with JavaScript. It is the same idea behind the Java to Bedrock pack converter on MCPlayerTools, cut down to the basics.
The two formats
A Java resource pack looks like this:
pack.mcmeta
pack.png
assets/minecraft/
textures/block/stone.png
textures/item/diamond_sword.png
sounds/...
models/...
pack.mcmeta is small:
{
"pack": {
"pack_format": 34,
"description": "My pack"
}
}
A Bedrock resource pack looks like this:
manifest.json
pack_icon.png
textures/blocks/stone.png
textures/items/diamond_sword.png
sounds/...
And manifest.json has more in it:
{
"format_version": 2,
"header": {
"name": "My pack",
"description": "My pack",
"uuid": "8f6c4a1e-...",
"version": [1, 0, 0],
"min_engine_version": [1, 20, 0]
},
"modules": [
{ "type": "resources", "uuid": "2b9d0e77-...", "version": [1, 0, 0] }
]
}
The two UUIDs have to be unique and different from each other. Bedrock uses the header UUID to tell packs apart, so if you reuse one from another pack, one of them will not load.
What maps cleanly
-
Metadata:
pack.mcmetabecomesmanifest.jsonwith two fresh UUIDs.crypto.randomUUID()is available in every modern browser. -
Icon:
pack.pngbecomespack_icon.png. -
Folders:
assets/minecraft/textures/block/becomestextures/blocks/anditem/becomesitems/. Note the plural. Java renamed these folders to singular in 1.13, Bedrock never did. - Many textures: a lot of block and item PNGs keep the same file name in both editions.
What does not map
This is the part to be honest about with users:
- File names differ for many textures. Some blocks have different names on Bedrock, and some textures are split or combined differently.
- Models use different formats. Java uses JSON block and item models. Bedrock uses its own geometry format. There is no simple conversion.
- Animations, particles and sounds are defined differently. Sound files can be copied, but the event names that point to them are not the same.
So a converter can give you a pack that installs and loads, with the textures that match by name. It cannot give you a perfect copy. The tool says this on the page, which saves a lot of confused messages.
Doing it in the browser
There is no reason to upload a pack to a server for this. Everything happens on zip files, and JSZip can read and write them in the browser.
import JSZip from "jszip";
const FOLDERS = [
["assets/minecraft/textures/block/", "textures/blocks/"],
["assets/minecraft/textures/item/", "textures/items/"],
["assets/minecraft/textures/", "textures/"],
["assets/minecraft/sounds/", "sounds/"],
];
async function javaToBedrock(file) {
const src = await JSZip.loadAsync(file);
const out = new JSZip();
const report = { moved: [], skipped: [] };
const meta = JSON.parse(await src.file("pack.mcmeta").async("string"));
const desc = typeof meta.pack.description === "string" ? meta.pack.description : "Converted pack";
out.file("manifest.json", JSON.stringify({
format_version: 2,
header: {
name: file.name.replace(/\.zip$/i, ""),
description: desc,
uuid: crypto.randomUUID(),
version: [1, 0, 0],
min_engine_version: [1, 20, 0],
},
modules: [{ type: "resources", uuid: crypto.randomUUID(), version: [1, 0, 0] }],
}, null, 2));
const icon = src.file("pack.png");
if (icon) out.file("pack_icon.png", await icon.async("uint8array"));
for (const [path, entry] of Object.entries(src.files)) {
if (entry.dir) continue;
const rule = FOLDERS.find(([from]) => path.startsWith(from));
if (!rule || path.endsWith(".mcmeta")) { report.skipped.push(path); continue; }
const target = rule[1] + path.slice(rule[0].length);
out.file(target, await entry.async("uint8array"));
report.moved.push(`${path} -> ${target}`);
}
const blob = await out.generateAsync({ type: "blob" });
return { blob, report };
}
A few details that matter:
-
Order of the folder rules. The specific
block/anditem/rules come before the generaltextures/rule, sofind()picks the right one. -
The description in
pack.mcmetacan be a text component (an object or array) instead of a string, so check the type. -
Skip
.mcmetafiles inside the textures folder. Java uses them for animated textures, Bedrock does not read them. - Return a report. Telling the user which files moved and which were skipped is the most useful part of the whole tool. It shows them exactly what to fix by hand.
To let the user download the result:
const { blob } = await javaToBedrock(input.files[0]);
const a = document.createElement("a");
a.href = URL.createObjectURL(blob);
a.download = "converted.mcpack";
a.click();
URL.revokeObjectURL(a.href);
An .mcpack file is just a zip with a different extension. On most devices, opening it imports the pack straight into Minecraft.
Why client-side
Packs can be large and some are people's own unreleased work. Doing it in the browser means nothing is uploaded, there is no server cost, and it works offline once the page has loaded. The trade-off is memory: a very large pack is held in memory while it converts, so a phone can struggle with a 200 MB pack. For normal packs it is fast.
Try it
The full version, which also converts the other way (Bedrock to Java), is the pack converter on MCPlayerTools. If you want to combine several packs first, there is also a texture pack merger. Both are part of a set of free Minecraft tools that all run in the browser, along with creation tools like a banner maker and a player head generator.
Top comments (0)