resourcepack.ai
DOCS

Building

Items

An Item is the flat picture Minecraft draws for an item: in your hand, in the hotbar, in an inventory and in an item frame. It's pixel art, like a Block, and Studio calls the picture a sprite. Use it to redraw a vanilla item (every diamond sword looks like yours) or to make a special item for your server (a quest key, a coin).

Item sprites made in Studio, in an inventory

Want depth? Pick 3D

Choosing 3D under Shape makes a 3D item out of cubes instead of a flat sprite, edited in the model editor. See Models.

Which kind do you need?#

A resource pack can't add a brand new item to the game, so every sprite is attached to an item that already exists. How it's attached decides who sees it:

KindWhat changesTrade-off
Reskin (Applies to: Base Item)Every copy of that vanilla item, for everyone with the packThe vanilla look is gone. One reskin per item, per pack
Variant (Applies to: Custom)Only copies handed out with this variant's tag. Ordinary ones look normalNeeds Minecraft 1.21.4 or newer, and a command to hand one out
Custom item (item: Custom)Nothing vanilla. A new-looking item carried on paperNeeds a give command, like any carried model

Use a reskin for a texture pack: every iron sword in the world looks like yours. Use a variant or a custom item on a server: your quest item looks special and everyone else's sword stays a sword.

The "tag" a variant uses is custom_model_data, a value stored on an item stack that the pack reads to decide which picture to draw. Studio sets it up for you and puts it in the give command.

Making one#

Open a pack, press Add asset and pick Item. Choose the Item to reskin (or Custom for a custom item), then how it Applies to, and keep Shape on 2D.

Then either:

  • Generate: describe it, for example "a rune-etched iron key, cold blue glow along the teeth". See Generating with AI.
  • Blank: draw it yourself in the pixel editor.
  • Upload: bring a PNG you already have, or a model (.json or .bbmodel) for a 3D item. Once Studio knows which vanilla item a file is for, its row asks whether it changes Every one of that item (a reskin) or Custom model data only (a variant), the same choice as Applies to.
SizeNotes
16×16Vanilla's resolution
32×32The default for a generated sprite
64×64Higher-resolution packs
128×128HD packs: the most detail, still with the pixel-art outline
CustomBlank only: any size up to 256

A generated sprite comes in those four sizes only. For any other size, draw it from blank or upload it.

On the item's page, Regenerate tries the same prompt again and Edit with AI changes one thing about the sprite you have, which is usually what you want when only a detail is wrong.

Choosing from 4 versions#

Every 2D Item you generate is drawn 4 times, and Studio picks the best one to start you off. On Creator, Studio or a Team, the Versions card on its page shows all 4: hover over one to preview it, and click it to use it instead. Switching is free, and the one it replaces stays in the 2D Item's AI history, so you can always switch back. On the free plan, the card shows that 4 were drawn.

With a reference picture of the thing itself, 2 of the 4 are redrawn from your picture and 2 are drawn from a description of it, in no particular order, so you can pick whichever came out best.

How it's held#

A flat item is held like paper unless you say otherwise: flat and upright. That's wrong for a staff, a wand or a flag. A variant or a custom item has a Held like card on its page:

ChoiceHeld like
ItemPaper: flat and upright. The default
ToolA sword: at an angle, the bottom left of the picture in the hand
RodA fishing rod: the tool angle turned the other way

For Tool, draw the handle in the bottom left and the tip in the top right, as vanilla's swords are. Sync to see the change in game; it's in every export too. A reskin is held the way its vanilla item is, so it has no card.

Drawing a good sprite#

Click a sprite to open it in the pixel editor, the same one Blocks use. Two habits help:

  • Keep the outline dark and unbroken. An item is seen small, against both a light inventory and a dark hotbar, and the outline stops it disappearing into either.
  • Leave a little room at the edges. The stack count is drawn over the bottom-right corner, and art that runs to the very edge looks clipped.

Seeing it in game#

On a server running RP Engine, our free plugin, press Sync: Studio sends the pack straight to you in game. A reskin needs nothing else, since every copy of that item already shows it. Without a plugin, export the pack and add it like any resource pack.

For a variant or a custom item, the item's page has the give command and a Give in-game button that hands you one directly. A variant's command looks like this:

/give @p iron_sword[minecraft:custom_model_data={strings:["quest_blade"]},minecraft:item_name="Quest Blade"]

That string is what makes the item look like yours, so a shop, crate or menu plugin can show it too: give that plugin the vanilla item and the same custom_model_data string. An Item is art, not a plugin item: to give it behaviour, an ID or a permission in RP Engine, define it in a content pack and point its texture: at this picture.

The string in custom_model_data is made from the item's name, so it can come out long. To pick a shorter one, press the pencil on the item's page and change Custom Model Data. Copies handed out before the change stop showing the item, so give them again after you Sync.

States: a bow that draws back#

A variant is the vanilla item underneath, so a variant of a bow shoots like a bow and a variant of a shield blocks like one. What you give it is how it looks while it does: the item's page has a States card for every item the game draws in more than one way.

Variant ofStates
BowThree drawing stages (from the start, after 0.65 seconds, fully drawn at 0.9)
CrossbowThree loading stages, Loaded, and Loaded with a rocket
TridentRaised to throw
ShieldBlocking
Fishing rodCast
Goat hornPlaying
BrushThree brushing stages

Each state switches at the same moment vanilla's does. Leave one empty and it shows the state before it, so a single drawn look is enough for a bow. On a 2D item each state is a picture you upload, fitted to the item's size; on a 3D item each state is another model in the pack. States need Minecraft 1.21.4 or newer, like the variant itself.

A reskin (Base Item) has states too. A 3D reskin works like a variant. A 2D reskin of a bow, crossbow or fishing rod replaces vanilla's own drawing pictures, so it works on every version, and an empty state shows vanilla's picture. A 2D reskin of a trident, shield, goat horn or brush has no pictures of its own to replace; make it 3D to give it states.

A custom item is carried on paper, which has no states. To make your own bow, make a variant of a bow.

A crossbow (or bow) from another pack. Importing a pack whose crossbow has several models gives you each model as a separate 3D Model on paper, which can't be turned into a crossbow afterwards. Instead, add the main look as an Item: Item to reskin set to Crossbow, Shape 3D, and Upload its model (.json or .bbmodel), as a Custom variant or a reskin. Its page then has the States card, where each state picks another model in the pack: the pulling and loaded models you imported. Needs Minecraft 1.21.4 or newer.

Several versions of one item#

There's no variant switch on a single item. Make each version its own Item: right-click it on the pack page, Duplicate, then change the copy with Edit with AI (a Christmas version, another colour) or in the editor. Each copy has its own custom_model_data and give command. A reskin is one per item, so extra versions of a reskinned item have to be variants.

What's in the exported pack#

In the exported .zip, a sprite is a PNG at assets/minecraft/textures/item/<name>.png, which is where vanilla looks. For a reskin that's all there is.

Variants and custom items also get an item definition under assets/minecraft/items/, which maps the custom_model_data tag to the sprite. They need the pack and a command: the sprite alone changes nothing until something hands out a tagged item.

If you edit an exported pack by hand

textures/item/ and textures/block/ are different folders to the game. A sprite in the wrong one does nothing at all, with no error. Studio files them correctly for you.

On Bedrock#

Reskins carry over to the Bedrock .mcpack, renamed where Bedrock uses a different name (golden_apple is apple_golden, wooden_sword is wood_sword). Variants don't: custom_model_data is Java-only. A custom item comes across as its sprite (or its model's icon) on a server with Geyser; see Bedrock and Geyser.