Add 3D armor layers and 2D inventory icons. Choose the armor material to replace and upload your files.
Add textures that replace vanilla items. For example, enter diamond_sword and upload your icon.
Add textures that replace vanilla blocks. For example, crafting_table_top.
This page is most useful when you already know the item, block, or armor slot you want to replace, but you do not want to hand-build the folder structure, rewrite JSON over and over, or package the ZIP manually every time. It keeps the boring parts predictable so you can spend your energy on the actual look and behavior of the content.
If you are making custom props for an RP server, a themed survival pack, or a small event item set, the generator is good at turning scattered PNGs into a pack that is already structured well enough to open in Minecraft. It works especially well when you need to move quickly between texture ideas, model hooks, and in-game preview.
You do not need to choose between “I use a pack tool” and “I do everything by hand”. Many creators sketch icons in the texture painter, refine skins or sprites elsewhere, then come back here to attach the right vanilla item, block face, or armor layer and export a clean archive.
Modern Minecraft content is less forgiving than older tutorials make it seem. Once item syntax, model definitions, and resource-pack paths start diverging from old examples, a browser workflow that keeps the pieces aligned becomes a lot more valuable than another half-broken copy-paste guide.
If you are not sure in which order to touch things, this sequence keeps the project tidy and reduces the chance of exporting a pack that technically builds but is hard to debug later.
Use a pack name that still makes sense two weeks later. If you plan to reuse the pack for a server season, guild event, or prop library, pick the final name now. That sounds small, but it saves a surprising amount of confusion once you have multiple ZIPs on disk.
Decide early which vanilla item or texture name is going to carry the custom look. A lot of pack problems are not rendering bugs at all; they come from changing the replacement target halfway through and forgetting to update related commands or documentation.
The texture atlas slicer is strongest when you already know where your faces live. If the atlas is still moving around every few minutes, slice later. Otherwise you end up debugging selection rectangles instead of the pack itself.
A fast 3D preview catches the embarrassing mistakes: upside-down block tops, wrong side faces, missing transparency, or an item that reads well in the atlas but collapses visually in the hand. Export only after the silhouette still feels right in preview.
Once the pack looks right, export and test the exact ZIP in Minecraft. That is the thing your players, teammates, or event build process will actually use. It is the only state that fully matters.
Item icons want readability at a glance. Block textures want repetition that does not look noisy when tiled. If you draw both with the same habits, one of them usually suffers. The generator helps by keeping those pipelines separate from the start.
“final-final-real-use-this-one.png” is funny until you have five of them. Clean target names and predictable slots matter because they spill into your pack structure, your command notes, and your own future memory.
Many creators build the pack first and only later realize they still need a clean item command, villager trade, or reward flow. If the pack is for gameplay and not just screenshots, it helps to think about the command side at the same time. That is why this tool works best together with the Custom Item Builder, Villager Trades, and Potions pages.
Yes. The workflow is light enough for a single icon replacement, but it is also useful when you are building a whole little family of props and want the ZIP structure to stay coherent.
No. If you only need texture replacement or simple pack assembly, you can stay here. If you are doing more involved 3D work, Blockbench still pairs well with this generator.
Usually yes. It is easier to draw or revise art in the texture tools first, then bring final PNGs here when you are ready to bind them to vanilla targets and export the pack.
Open the wiki guide for pack structure if you want the folder logic explained, or jump into the Custom Item Builder, Villager Trades, and Custom Potions tools if the pack is only one part of a larger gameplay setup.
