Citizens, Custom NPC Skins Guide

Making NPCs Look Unique

Default Citizens NPCs spawn with a Steve or Alex skin, which looks generic and breaks immersion. Applying citizens custom npc skins transforms your server's feel instantly. Quest givers, shopkeepers, guards, and tutorial NPCs each get a distinct visual identity that players remember. This guide covers every method Citizens supports for skin assignment.

If you have not set up Citizens yet, start with our Citizens NPC tutorial which covers installation, basic NPC creation, and click actions. This guide assumes Citizens is already running on your server.

Method 1: Using a Player Name

The simplest way to skin an NPC is to copy a real Minecraft player's skin:

/npc skin PlayerName

Citizens fetches the skin data from Mojang's session servers and applies it to your NPC. The skin persists even if the original player changes their skin later, because Citizens caches the texture data at the time of the command. To update the cached skin, run the command again.

This method works well when you want to use your own alt account's skin or a well-known community member. For completely custom designs, read on.

Method 2: Custom Skin from URL

For citizens custom npc skins that do not belong to any real player, upload your skin to a site like mineskin.org. The site generates a texture value and signature that Citizens can use directly:

/npc skin --url https://textures.minecraft.net/texture/abc123...

Alternatively, use the full Mineskin workflow:

1. Design your skin in a skin editor (NameMC, PMC Skin Editor, or Blockbench for 3D preview).
2. Upload the PNG to mineskin.org.
3. Copy the skin URL from the result page.
4. Apply it with /npc skin --url <url>.

The URL method is the most reliable approach for citizens custom npc skins because the texture is stored permanently on Mojang's CDN. It will never expire or break.

Method 3: Texture Value and Signature

For advanced setups or when scripting NPC creation through the Citizens API, you can set the raw texture data:

/npc skin -t <texture_value> -s <signature>

You can get these values from mineskin.org's API response or from Mojang's session server. This method is most useful when you are programmatically creating NPCs through a script or a companion plugin.

Skin Caching and Performance

Citizens caches skin data locally so it does not hit Mojang's API every time a player loads a chunk with NPCs. The cache lives in plugins/Citizens/skins/. On a server with dozens of NPCs, this cache prevents rate limiting from Mojang, which throttles requests after about 200 per minute.

If you notice NPCs loading with default skins temporarily before their custom skin appears, that is the client-side texture download. Players with slower connections see this brief flicker. There is no server-side fix for this; it is how Minecraft's skin system works.

Skin for Non-Player Entity Types

Citizens custom npc skins only apply to PLAYER-type NPCs. If your NPC is a villager, zombie, or other mob type, you cannot apply a player skin to it. You can, however, change mob-type NPC variants:

/npc type VILLAGER
/npc profession LIBRARIAN

For completely custom mob appearances, consider using Oraxen or ItemsAdder for custom model entities. Our Oraxen tutorial covers the resource pack pipeline you would need.

Organizing Skins for Large Servers

If you run a server with 50+ NPCs, maintain a spreadsheet or internal wiki mapping each NPC ID to its skin source. When a skin breaks (rare, but it happens when Mojang rotates texture servers), you need to know where each skin came from so you can re-apply it. Use descriptive NPC names to make maintenance easier:

/npc rename &6Master Blacksmith
/npc skin --url https://textures.minecraft.net/texture/...

Pair your skinned NPCs with the pathing and waypoints guide to make them walk around your world, and connect them to ShopGUI+ or ChestShop for interactive vendor NPCs that look the part.

See these configs live: Astroworld MC, IP play.astroworldmc.com, Java + Bedrock.