Cape Support

Capes are cosmetic items on a Minecraft player's back. They do not affect the game.

How capes work in Minecraft

Capes come from:

Account events: Migration capes and the Vanilla cape for linked Bedrock and Java accounts
Events: Minecraft Live, MINECON, and social media campaigns
Staff or volunteer work: Mojang employees, translators, and moderators
Personal awards: Capes for specific Java Edition players
Pan Cape: The only cape given automatically to all players

You cannot create a custom cape or move a cape to another account. Each cape belongs to a Mojang or Microsoft account.

How SkinsRestorer handles capes

When you use /skin <playerName>, SkinsRestorer gets the complete skin data from Mojang. The data contains:

The skin texture
The cape texture (if the player has one equipped)
Mojang's cryptographic signature

If the source player has an equipped cape, your character also shows it.

Example

/skin Dinnerbone

If Dinnerbone equips a Mojang employee cape, your character shows the same skin and cape.

Limitations

What SkinsRestorer can do

Copy skins from players who have capes (cape included)
Display the cape that comes with the copied skin data

What SkinsRestorer cannot do

Create custom capes: Capes need Mojang's signature and belong to specific accounts.
Add capes to URL skins: /skin url creates only a skin texture.
Remove a cape from copied data: Copied skin data includes the skin and its cape.
Create other capes: Mojang does not provide an API for new capes.

MineSkin creates only skin textures for /skin url. It cannot create capes because capes require Mojang account verification.

Finding players with capes

To copy a cape, find a player who has equipped one.

Players with capes include:

Mojang employees (Mojang cape)
MINECON attendees (various years)
Minecraft Live participants
Content creators with personal capes

SkinsRestorer copies the cape that the source player equips. Cached data can show the old cape until you refresh it.

Refreshing cape data

If the source player changes their cape, refresh the cached data:

/skin update

You can also clear and apply the skin again:

/skin clear
/skin <playerName>

Technical details

Cape data is part of Mojang's signed skin property. The Base64-encoded texture data contains URLs for the skin and cape:

{
  "textures": {
    "SKIN": {
      "url": "http://textures.minecraft.net/texture/..."
    },
    "CAPE": {
      "url": "http://textures.minecraft.net/texture/..."
    }
  }
}

The cape URL exists only when the player equips a cape. Mojang signs the complete data. Therefore, SkinsRestorer cannot create custom capes.

Cape Support

On this page