Custom Item Textures in Minecraft: The Server Owner's Guide (2026)
Custom item textures are what make a server's items feel real: a katana that actually looks like a katana instead of a renamed iron sword. The good news — you don't need mods, and since Minecraft 1.20.5+ you don't even need to host a resource pack yourself.
Here's how the whole system works, and the fastest path for each server version.
Quick Answer
Custom item textures on a Minecraft server work in two parts:
- The item carries a texture reference —
CustomModelData(1.13 – 1.21.3) or item model components (1.21.4+). - A resource pack maps that reference to your texture file, and the server sends the pack to players when they join.
No client mods required. Plugins like ExecutableItems assign the reference for you, and from 1.20.5+ can even host the resource pack automatically via a config URL — plus 60+ included 3D weapon textures on 1.21.4+ if you don't want to draw anything.
How Custom Item Textures Actually Work
Minecraft clients render items from the resource pack they have loaded. A server resource pack is downloaded and applied automatically when a player joins (they accept it once). Your pack contains:
- the texture (a PNG, usually 16×16 or 32×32),
- a model (JSON describing how the texture wraps the item — flat, handheld, or full 3D),
- a mapping that says "when this item has reference X, use this model".
The item side is where a plugin comes in: it creates the item and stamps the right reference on it, so the client picks up your model instead of the vanilla one.
CustomModelData vs. item models (the 1.21.4 change)
| Server version | System | How it works |
|---|---|---|
| 1.13 – 1.21.3 | CustomModelData | A number on the item; the pack's overrides array maps numbers to models |
| 1.21.4+ | Item model components | A direct model reference on the item — cleaner, no override juggling |
If you're on 1.21.4+, follow the 1.21.4+ texture guide; for older versions the step-by-step CustomModelData guide walks through building the pack from scratch, including animated textures and per-state textures (bows that change while drawn, for example — see the bow texture guide).
The Three Paths, From Easiest to Most Custom
1. Use included textures (zero work)
ExecutableItems Premium ships 60+ ready-made 3D weapon textures on 1.21.4+. Pick one in the item editor, done — no pack building, no hosting.
2. Auto-hosted resource pack (bring your textures, skip the hosting)
From Minecraft 1.20.5+, ExecutableItems can serve its own resource pack through a config URL. Drop your textures in, and the plugin handles packaging and delivery to players. See uploading a texture pack for the hosted-pack workflow on older versions.
3. Full custom resource pack (total control)
Build the pack yourself: textures, models, mappings, then host it and set it in server.properties. This is the right path when custom items are one part of a larger visual overhaul (custom GUIs, fonts, sounds). The general items guide covers the full 11-step process.
Mixing With Other Texture Plugins
Already using ItemsAdder or Nexo for cosmetics? They coexist fine with ExecutableItems: EI can reference third-party items in its conditions and abilities, so ItemsAdder handles the visuals while EI powers the behavior. See the compatible plugins list and our custom items plugin comparison for how they split the work.
Common Pitfalls
- Texture shows as the vanilla item — the reference on the item and the mapping in the pack don't match, or the player rejected the server pack.
- Purple/black checkerboard — the model JSON points to a texture path that doesn't exist in the pack (case-sensitive!).
- Works in 1.21.3, breaks in 1.21.4 — you upgraded across the item-model change; re-map using item model components.
- Players on old clients — via ViaVersion, older clients may not render newer model features; keep a fallback texture if you support a wide version range.
Frequently Asked Questions
Do custom item textures require mods? No. Server resource packs work on vanilla clients — players accept the pack on join.
How do I give an item a custom texture? Assign a texture reference to the item (CustomModelData or item model component, depending on version) and map it in a resource pack. With ExecutableItems both steps are handled in the item editor.
What if I can't draw textures? Use the 60+ included 3D weapon textures (EI Premium, 1.21.4+), or grab free community textures and map them yourself.
Can textures be animated? Yes — see the animated textures guide.