Checked for versions: Java Edition 1.20 to 26.3. Blockbench's Bedrock formats do not work in Java Edition.
In Blockbench
- Use the "Java Block/Item" format. It enforces the rules the game has: every cube must stay within −16 to 32 on each axis (three blocks), and a cube rotates around one axis only, at the 22.5° steps up to 45° that every version accepts.
- Set the display. The Display tab decides how the model sits in the hand, on the head, in a frame and in the inventory. Without it a large model fills the hotbar slot or floats beside the hand.
- Name textures with their pack path. A texture saved as
assets/cube/textures/item/guild_hammer.pngis referenced ascube:item/guild_hammer. Blockbench writes that reference into the model, so the path must already be right when you export. - Export with File → Export → Export Block/Item Model, into
assets/cube/models/item/.
Where the files go
my_pack/
pack.mcmeta
assets/cube/
items/guild_hammer.json (1.21.4+ only)
models/item/guild_hammer.json (exported from Blockbench)
textures/item/guild_hammer.png
Use your own namespace (here cube) instead of minecraft for new files, so they cannot collide with vanilla assets or with another pack.
Hooking it to an item on 1.21.4 and newer
An item definition in items/ says which model to draw:
{
"model": {
"type": "minecraft:model",
"model": "cube:item/guild_hammer"
}
}
The item points to that definition with the item_model component, written the same way on 1.21.4 and 1.21.5 – 26.x:
/give @p minecraft:stick[minecraft:item_model="cube:guild_hammer"] 1
One model can serve several states of the same item (charged, broken, faction colors) through select, range_dispatch or condition in the definition; the item model builder writes those files.
Hooking it on 1.21.3 and older
Older versions have no items/ folder. Instead the vanilla item's model gets an override that switches on CustomModelData, in assets/minecraft/models/item/stick.json:
{
"parent": "minecraft:item/handheld",
"textures": { "layer0": "minecraft:item/stick" },
"overrides": [
{ "predicate": { "custom_model_data": 1 }, "model": "cube:item/guild_hammer" }
]
}
The command then sets the number, with components on 1.20.5 – 1.21.3 or NBT before that:
/give @p minecraft:stick[minecraft:custom_model_data=1] 1
/give @p minecraft:stick{CustomModelData:1} 1
From 1.21.4 overrides are ignored, which is the most common reason a pack that "worked last year" shows only vanilla items.
When it does not show up
- Purple and black checkerboard on the model: the model loaded, the texture did not. Compare the texture reference inside the model JSON with the PNG's real path.
- Purple and black cube instead of the model: the model file was not found or failed to load. Check the path in the item definition or the override, and look at the game log for the file name.
- Huge or misplaced in the hand: the display settings were left at their defaults.
- Nothing changed after editing: press F3+T in game to reload resource packs; restarting is not needed.
- Pack marked as incompatible:
pack.mcmetadeclares a format for another version. The Minecraft Wiki "Pack format" page lists the number for each release.
FAQ
Can one model be used by several items?
Yes. Several item definitions, or several overrides, can point to the same model file.
Can the texture be animated?
Yes, with a vertical strip of frames in the PNG and a .png.mcmeta file next to it that sets the frame time.
Which base item should carry the model?
One whose behaviour fits: a stick or a carrot on a stick for props, a sword or an axe for weapons, paper for documents. The model changes only the look.