How it works
Build a Bedrock skin pack with capes
A cape pack is a specialized Bedrock skin pack. Each entry references a player skin PNG, a classic or slim player geometry, and an optional 64 by 32 cape PNG. MC Toolbox writes those relationships into skins.json, creates unique manifest UUIDs, adds the display names, and packages the result as a .mcpack.
The gallery is organized from the cape records documented by Minecraft Wiki. Its texture files are hosted locally by MC Toolbox, so opening this page does not hotlink images from Minecraft Wiki or NameMC. The designs remain Minecraft assets owned by Mojang Studios and Microsoft; the gallery is provided for identification and personal testing.
What this tool can and cannot do
Microsoft documents skin packs and validates 64 by 32 cape textures, but its current validation rules also mark creator-only skin properties. That means the generated structure is real, while acceptance can still differ by Bedrock version, platform, account, and installation method. Test it on your own device. This tool does not grant ownership of Minecon, staff, event, or account capes.
How to use the Cape Pack Builder
- Name the pack. Choose a short name and a useful description.
- Add skins. Upload valid skin PNGs, load a Java username, or try a public Bedrock gamertag lookup.
- Choose capes. Use the local gallery or upload your own 64x32 design.
- Create pairs. Make one entry for every skin and cape combination you want.
- Import and test. Open the .mcpack with Bedrock, or use the manual Windows ZIP if automatic import fails.
Minecraft cape pack FAQ
Does this give my Minecraft account an official cape?
No. It builds a personal Bedrock skin pack that pairs a skin texture with a cape texture. It does not add an account entitlement, unlock an official cape, or make the cape available on Java Edition.
What size should a Minecraft cape texture be?
Use a 64 by 32 pixel PNG. The builder keeps gallery textures at that size and scales uploaded cape PNGs to 64 by 32 before packaging.
Will the cape work on every Bedrock device?
No guarantee is possible. The cape field exists in the Bedrock skin-pack format, but current validation also reserves some cape capabilities for approved creator accounts. Windows personal skin packs are the main target; mobile, console, servers, and future versions may behave differently.
Are my uploaded skins sent to a server?
No. PNG inspection, pairing, resizing, and ZIP creation run in your browser. Java username lookup requests a public Java profile. Optional Bedrock gamertag lookup uses public mccompanion.net and GeyserMC services.
Should I download the .mcpack or the ZIP?
Use the .mcpack first. It follows Microsoft’s documented double-click import workflow. The ZIP contains the same pack inside a named folder for manual installation in a Windows skin_packs directory.
Why is each skin and cape combination a separate entry?
Bedrock skin packs attach a cape file to a skin entry in skins.json. A separate entry lets the Dressing Room show each combination as its own selectable look.
Can other players see this custom cape?
Visibility depends on the Bedrock client, server skin settings, platform, and account restrictions. Treat this as a personal cosmetic pack, not as a method for granting a globally visible account cape.