Your packs and images never leave your device. Reading the zips, fitting overrides, merging everything and building the final pack all happen here in your browser; this page makes no network requests with your files.
Drag in resource pack .zip files you already made (painting, totem, HUD, sky, glint, mob and more). They merge into this one project, with a priority order and a conflict report.
Pick any item, block, painting or mob, upload an image, and it is fitted and added at the correct texture path. No file structure to learn.
Java resource packs only (.zip). Add as many as you like, then order them below. The top pack wins on conflicts.
Replace any single texture without learning the pack folder structure. Pick a target, upload an image, and it is fitted to the right place.
One unified pack.png and pack.mcmeta are written for the whole pack. The imported packs' own name and icon are dropped in favor of these.
A resource pack creator that does more than one job. Build your entire resource pack in one place: combine the packs you made with our other tools and add your own texture overrides for items, blocks, paintings and mobs, then download one clean pack. Most pack tools do a single thing; the studio is where you assemble all of them under one pack identity. It runs in your browser, so nothing uploads and there is no watermark.
There are two ways to fill a project. The first is to import packs: drag in resource pack .zip files you already made, set the priority order, and the studio stacks them so the top pack overrides the others on any file conflict, with a full report of which paths collided and which source won. The second is quick overrides: a universal picker that spans items, blocks, paintings and mobs. Search for a target, upload an image, and it is fitted to the vanilla texture size with nearest-neighbour scaling and written to the correct path inside the pack.
When you build, every imported file and every override is flattened into one .zip with a single fresh pack.mcmeta and one optional pack.png. The imported packs' own names and icons are dropped in favor of the unified identity you set, so the result looks and loads like a single pack you authored.
Importing is ideal for combining finished work. If you made a custom painting pack, a totem pack and a HUD pack with our other tools, importing all three into the studio gives you one pack instead of a cluttered resource pack list. The priority order decides which import wins when two of them touch the same file, the same way Minecraft applies packs from top to bottom.
Quick overrides are for the small, deliberate changes you want without opening an image editor's folder browser. Pick the exact texture from the picker, and the studio knows the right in-pack path and size for it, so a 16x16 item or block texture stays crisp and a painting or mob texture is saved at the size you provide. Overrides always take priority over imported packs, because they are your most explicit choices.
The project view keeps a live count of every file grouped by category, so you always know exactly what is in the pack before you download. Remove any import or override at any time and the counts update. The whole process is local to your browser and makes no network calls with your packs or images.
Open the studio and fill your pack two ways. Import any resource pack .zip files you already have, and add quick overrides by picking an item, block, painting or mob and uploading an image. The tool merges everything, writes a fresh pack.mcmeta, and gives you one .zip you can drop straight into Minecraft's resource pack folder. You never have to build the folder structure by hand.
Yes, that is what the studio is built for. Drag in the .zip packs you made with our painting maker, totem maker, HUD customizer, sky maker, glint maker, mob skin maker or any other Java resource pack. They merge into one project under a single pack name and icon, so instead of activating five separate packs in game you ship one combined pack.
The studio resolves conflicts by priority, exactly like stacking packs in Minecraft. Quick overrides you add by hand win first, then imported packs in the order you set, with the top import beating the ones below it. The project view lists every conflicting path and names which source was kept, so nothing is silent and you can confirm the result before you build.
No. Reading the zip files, fitting your override images on a canvas, merging everything and building the final .zip all happen in your browser. The page makes no network requests with your files, so your packs and images never leave your device and there is no watermark.
Version one builds Java Edition resource packs, which are .zip archives with an assets folder and a pack.mcmeta. Bedrock packs use a different layout (.mcpack with a manifest.json), so they are not combined here yet. Keep Bedrock packs separate for now; Bedrock support is planned for a later update.
The built pack carries the highest pack format found across your imported packs plus a wide supported_formats range, so it loads without the incompatible warning across many versions. Quick overrides are plain textures placed at standard paths, so they behave the same way the vanilla textures do on any supported version.
Just need to stack a few packs, or want more tools?
