Minecraft Resource Pack Format Versions (pack_format)

Q: Can I convert a Java pack to Bedrock?

You can export a Bedrock .mcpack from a Java zip with a converter, but not every Java asset maps 1:1. Always test on Bedrock after export.

Every Java Edition resource pack declares a pack_format in pack.mcmeta. That integer tells the game which asset layout and features the pack expects. Loading a pack with the wrong format can show a warning, break textures, or refuse to load.

Convert in the browser — use the free Resource Pack Converter to retarget Java versions, convert ItemsAdder / Nexo / Oraxen / CraftEngine / MythicCrucible packs, or export a Bedrock 1.19+ .mcpack. Larger packs convert on-device; there is also a public /api/pack-convert for smaller zips.

Section 01

What pack_format is

pack.mcmeta typically looks like:

{
  "pack": {
    "pack_format": 34,
    "description": "My server pack"
  }
}

As Minecraft updates, Mojang bumps pack_format when the resource layout or required metadata changes. A pack built for an older format may still open with a compatibility warning, but renamed textures, models, or atlases can silently break.

Section 02

Convert between Java versions

Zip your pack so pack.mcmeta sits at the root of the archive (not nested in an extra folder).
Open the Resource Pack Converter and choose your source and target Java versions.
Download the converted zip, install it under resource packs, and verify textures / models in-game.

Converters rewrite format metadata and known asset renames between versions. You can also convert ItemsAdder, Nexo, Oraxen, CraftEngine, and MythicCrucible zips to a vanilla resource pack (or the other way around). Custom, heavily scripted, or shader-dependent packs still need manual testing after conversion.

Section 03

Bedrock 1.19+ .mcpack export

Bedrock uses a different pack structure. From 1.19 onward the converter writes a manifest.json with a matching min_engine_version, remaps Java flattened texture names (for example oak_planks → planks_oak), and copies block, item, entity, and other texture folders into a .mcpack.

Exporting from a Java zip is useful for cross-play branding packs, but not every Java asset maps 1:1 (models, CTM, OptiFine features, and some GUI assets differ). After export, import on Bedrock and check the pack appears under Settings → Global Resources (or the world’s resource packs list).

Section 04

Tips and pitfalls

Keep a clean source zip for each major Minecraft version you support.
Validate that assets/minecraft/… paths match the target version’s naming.
Server resource packs must be served over HTTPS with a matching SHA-1 in server.properties when forced.
For automated pipelines, the converter API accepts JSON with base64 zip payloads for packs up to ~4MB; larger packs should stay in-browser.

FAQ

Frequently asked questions

What is pack_format?

pack_format is the integer in pack.mcmeta that tells Minecraft which asset layout your resource pack expects. Wrong values can break textures or prevent the pack from loading.

Can I convert a Java pack to Bedrock?

You can export a Bedrock 1.19+ .mcpack from a Java zip with a converter. Texture filenames are remapped, but not every Java asset maps 1:1. Always test on Bedrock after export.