How to merge Minecraft texture packs
Minecraft can already stack texture packs: turn several on, and the one higher in the list wins wherever two change the same texture. Merging builds one pack from several, with that same order baked in. It is handy for a server or a Realm that takes a single pack, for sharing your favourite combination, or for keeping your pack list short. The free Merge Texture Packs tool does it in your browser.
Step by step
- Put them in order by dragging, or with the arrow buttons. The pack at the top wins wherever two packs change the same file.
- Name the merged pack and pick its icon. For Java, pick the version you play.
- Click Merge and check the list of conflicts.
- Download the merged pack, or open it in the editor to keep working on it.
Which pack wins?
The same rule Minecraft uses: for every file, the pack highest in the list wins. A texture and its animation file always travel together, so a lower pack’s animation is never attached to a higher pack’s picture.
Some files are combined instead of replaced, so nothing useful is lost:
- Java: language files (key by key),
sounds.json(sound by sound), texture atlases and fonts. - Bedrock:
terrain_texture.json,item_texture.json,flipbook_textures.json,blocks.json, sound definitions and language files.
The result lists every conflict, such as “block/stone.png from Pack A, overriding Pack B”, and how many files each pack added.
Packs for different versions
Java packs made for different versions can be merged: pick the version you play and older packs are renamed to its texture names first (the same renames the converter uses), so a 1.12 pack and a 26.3 pack fit together. Java and Bedrock packs cannot be merged directly: convert one of them first.
Merging packs by hand
- Unzip every pack into its own folder.
- Make a new folder and copy in the lowest-priority pack first, then each higher pack on top, replacing files when asked.
- Merge the files that should be combined (
sounds.json, language files, atlases) by hand, or the last copy wins. - Keep one
pack.mcmeta(Java) or write a newmanifest.jsonwith new IDs (Bedrock), then zip the contents.
The tool does all of this, including the combined files and the right pack format, so manual merging is only worth it for unusual packs.
Questions
How many packs can I merge?
Two to eight at a time. To combine more, merge the result again with the next packs.
Can I merge shader packs?
No. Iris and OptiFine shader packs only run one at a time. Vanilla shader resource packs can be merged like any resource pack, but two packs that change the same shader file will not combine their effects.
Can I use a merged pack as a server resource pack?
Yes. Upload the merged .zip wherever you host server packs and set it in server.properties like any other pack.
Are my packs uploaded?
No. The packs are merged in your browser and stay on your device.