Minecraft Skin Pack Not Showing or Not Importing? Fixes
Why is my Minecraft skin pack not showing?
The most common cause is Only Allow Trusted Skins being enabled. Turn it off in Settings → General. Other causes: an extra folder inside the zip (manifest.json must be at the root), the file is still a .zip instead of .mcpack, the two UUIDs in manifest.json are the same, or the PNG is in a subfolder instead of the pack root.
You downloaded a .mcpack, double-clicked it, and… nothing. Or the pack imported but the skin is missing, the name is a jumble of code, or the arms look cut off. This guide walks through every common reason a Minecraft Bedrock skin pack fails to show up, and how to fix it.
Work through the sections in order. Most problems are solved in the first two.
Quick checks first
Before digging into the details, run through this five-point checklist. It catches the vast majority of "skin pack not showing" problems:
- Is "Only Allow Trusted Skins" off? Settings → General → toggle it off. This is the number-one cause on every platform.
- Is
manifest.jsonat the root of the zip? Open the.mcpack(rename to.zip) and confirm the file is at the top level, not inside a wrapper folder. - Are the two UUIDs different? The header UUID and the module UUID in
manifest.jsonmust be two separate values. Reusing one UUID for both breaks the import. - Is the PNG in the pack root? Skin images must sit next to
manifest.json, not in a subfolder. - Is the file actually a
.mcpack? A plain.zipwill not auto-import. Rename the extension to.mcpack.
If all five check out and the pack still will not appear, keep reading. The problem is usually in the JSON or the image itself.
Import failed or nothing happens
If double-clicking the .mcpack does not launch Minecraft, or the import message says it failed, the cause is almost always one of these:
- Extra folder inside the zip. The zip must contain
manifest.json,skins.json, the PNG files, and thetexts/folder directly at its root. If you see a folder likeMyPack/manifest.json, that is the problem. Re-zip the contents, not the folder itself. - File is still a
.zip. Minecraft only auto-imports the.mcpackextension. Right-click the file → Rename → change.zipto.mcpack. On Windows you may need to show file extensions first (View → File name extensions). - File association is wrong. If double-clicking opens a zip viewer instead of Minecraft, right-click the
.mcpack→ Open with → Minecraft. On Android, long-press the file in your file manager and choose "Open with Minecraft".
If you are editing an existing pack and re-importing it, make sure you have not accidentally kept the old UUIDs. Two packs with the same UUID will conflict. Generate two new UUIDs from a free generator such as uuidgenerator.net.
Stuck? Grab one of my free skin pack templates and compare your file structure against it side by side. The official Microsoft sample pack is another good reference.
Imported but not in the Dressing Room
The import message said "success" but you cannot find the skin. Here is where to look:
- From the main menu, click the Dressing Room button.
- Go to Classic Skins. On some game versions you need to click the green clothes-hanger Featured Skins button first, then your pack will be listed there.
- If it is still missing, fully close and restart Minecraft. The
development_skin_packsfolder does not work reliably: packs must be inskin_packs, and the game sometimes needs a restart to pick them up.
Custom packs appear under Classic Skins, not under Character Creator. If you are looking in the Character Creator tab, that is why you cannot see them.
Broken JSON and duplicate UUIDs
A single missing comma or a mismatched quote in manifest.json or skins.json will silently break the pack. Minecraft does not always show a clear error.
How to check: open each JSON file in a text editor, copy the contents, and paste them into any free online JSON validator. Fix every error it reports, then save and re-import.
The most common JSON mistakes in skin packs:
- Trailing comma after the last item in an array or object.
- Single quotes instead of double quotes around keys or string values.
- Same UUID in header and module. They must be two different values. A minimal valid
manifest.jsonlooks like this:
{
"format_version": 2,
"header": {
"name": "My Skin Pack",
"uuid": "AAAA1111-2222-4333-8444-555566667777",
"version": [1, 0, 0]
},
"modules": [
{
"type": "skin_pack",
"uuid": "BBBB1111-2222-4333-8444-555566667777",
"version": [1, 0, 0]
}
]
}(Replace both UUIDs with your own generated values.)
In skins.json, the geometry field is case-sensitive and must be exactly geometry.humanoid.custom (Classic / wide arms) or geometry.humanoid.customSlim (Slim / narrow arms). A typo here makes the skin render as a blank or broken model.
Need a hand building the JSON from scratch? My Skin Pack Creator tool generates valid manifest.json and skins.json for you in the browser. No typing UUIDs by hand.
Image problems: size, format, and model type
The skin PNG itself can cause the pack to fail or look wrong:
- Wrong file format. Only PNG is supported. If your image is a JPG, BMP, or WebP, re-save it as PNG first.
- Unsupported size. On Windows and mobile, imported custom skins accept 64×32, 64×64, or 128×128 pixels. 64×64 is the standard and what the official Microsoft sample uses. If your image is a different size, resize it before adding it to the pack.
- Wrong model type. A Classic (4-pixel arm) skin set to
geometry.humanoid.customSlimwill show a visible gap or stripe on the arms, and vice versa. Match the geometry value to your skin:geometry.humanoid.customfor Steve-style wide arms,geometry.humanoid.customSlimfor Alex-style slim arms. - Transparency. In Bedrock, pixels with an opacity of 25/255 or lower are invisible; anything above that is visible. If your skin has a semi-transparent background, flatten it to full transparency before saving.
If you see the error "That's not a Minecraft skin, silly." when importing a single PNG, the file is not a valid skin image. Re-export it as a plain 64×64 PNG and try again.
Skin names show as codes or are blank
If the skin appears in the Dressing Room but the name reads something like skin.MyPack.FoxClassic instead of a friendly label, your language file keys do not match the localization_name values in skins.json.
The file texts/en_US.lang uses this pattern:
skinpack.MySkins=My Skin Pack
skinpack.MySkins.by=YourName
skin.MySkins.FoxClassic=Fox (Classic)
skin.MySkins.FoxSlim=Fox (Slim)Every key must line up exactly with the localization_name in skins.json. If your skins.json says "localization_name": "FoxClassic", the lang key must be skin.MySkins.FoxClassic: same capitalisation, same spelling.
The pack will still load even if the names are wrong. You will just see raw key strings or blank labels in the skin picker. Fixing the lang file and re-importing resolves it.
Only Allow Trusted Skins
This is the single most common reason a custom skin pack imports successfully but the skin simply does not appear in the list.
- From the main menu, click Settings.
- Go to the General tab.
- Find Only Allow Trusted Skins and toggle it off.
Go back to the Dressing Room and your custom skin should now be visible. This setting is on by default in some game versions, and it silently hides any pack that is not from the Marketplace.
On Xbox, PlayStation or Switch?
Custom skin import (both .mcpack files and single PNG uploads) is not officially supported on Xbox One, Xbox Series X|S, PlayStation 4/5, or Nintendo Switch. This is a platform policy, not a bug.
On consoles your official options are:
- Marketplace skin packs: buy or unlock them with Minecoins in the in-game Marketplace.
- Character Creator: build a character piece by piece (body, hair, clothing, accessories) using free and paid items.
What about the "set it on PC first" trick? Some Xbox players report that a skin imported on Windows or mobile with the same Microsoft account appears on the console. This worked inconsistently in the past and is reported broken in recent 1.21.x versions (the game shows "Local skin could not be loaded" and falls back to a default). We found no reliable reports of it working on PlayStation or Switch. It is harmless to try, but do not count on it.
Servers and Realms can provide their own skin packs to every player who joins, including console players, but that is the server's skin, not your own, and it only applies on that server.
DNS tricks, third-party connection apps, and modified consoles carry real risks (account security, scams, terms-of-service violations). We do not recommend them.
Marketplace purchases follow your Microsoft account, so a pack you buy on your phone will also appear on your console once you sign in with the same account.
For full details per platform, see the Xbox guide, the PlayStation guide, or the Nintendo Switch guide.
FAQ
Why does my updated pack not replace the old one?
If you want the new version to update the existing pack, keep the same UUIDs and raise the version number in manifest.json. If you want a completely separate pack, generate two new UUIDs.
Can I use a .zip file directly?
No. Minecraft only auto-imports the .mcpack extension. Rename the file from .zip to .mcpack and double-click it.
Do custom skins sync between my phone and my PC?
No. Custom imported skins are stored on the device you import them to. You will need to import the .mcpack separately on each device. Marketplace purchases, on the other hand, follow your Microsoft account.
I see "Invalid or corrupt skin!" when joining a multiplayer server. What does that mean?
Your PNG is likely an unsupported size or format. Re-export it as a plain 64×64 PNG and re-import.
Can I add custom geometry or models to a skin pack?
No. Custom geometry is not supported in skin packs. The geometry is fixed to the built-in Classic or Slim humanoid model.
Where can I make my own skin pack without editing JSON by hand?
Try my free Skin Pack Creator. It runs in your browser, lets you add skins, preview them in 3D, and downloads a ready-to-use .mcpack. You can also start from one of my free skin pack templates and swap in your own images.
Related guides
Sources
- Microsoft Learn: Packaging a Skin Pack
- Microsoft Learn: Change Your Look: An Introduction To Skin Packs
- Microsoft sample skin pack
- Minecraft Wiki: Skin
- Minecraft Wiki: Skin pack
- Minecraft Wiki: Marketplace
- Mojang bedrock-samples: en_US.lang
- Bedrock Wiki: Skin Packs
Join the Discord for update announcements, help and sneak peeks.
Join Discord