How Minecraft pack merging works
Resource packs override files by path. If two packs both contain the same texture, model, or metadata file, only one can win. This merger uses the same mental model as Minecraft's pack stack: the pack at the top has the highest priority and replaces duplicate files from packs below it.
Review duplicate paths instead of merging them blindly
Two files with the same path cannot be combined automatically just because both are JSON or PNG. A block model may depend on textures from one pack, while a language or sound file may contain entries worth preserving from both. Use the conflict list and MERGE_NOTES.txt to decide whether priority is enough or whether a specific file needs a manual semantic merge.
Validate the merged pack in the target edition and version
Java and Bedrock use different archive layouts and metadata, so choose one output edition and skip incompatible source packs. After export, open Minecraft's resource-pack screen, check for a compatibility warning, and test representative blocks, items, sounds, and menus. Keep the original packs until the merged result has been verified in game.
Upload
Add Java .zip packs or Bedrock .mcpack files. The tool detects pack.mcmeta and manifest.json automatically.
Reorder
Move packs up or down until your preferred textures have the highest priority. Duplicate paths are detected before export.
Export
A fresh manifest.json or pack.mcmeta is generated, optional icon is applied, and the merged file downloads locally.
Pack Merger FAQ
What happens when two packs use the same file?
The pack higher in the priority stack wins. The output also includes MERGE_NOTES.txt so you can review overrides and skipped packs.
Can I merge Java and Bedrock packs together?
The output must be either Java or Bedrock. Packs with the wrong source format are skipped because mixing both structures into one archive would create a broken pack.
Is this private?
Yes. The files are read and merged in your browser with JSZip. They are not uploaded to MC Toolbox.