Why Your Minecraft Skin Looks Wrong

A stripe down the arms, or squashed sleeves

This is the wrong model, and it is by far the most common skin problem.

If you see an unpainted or oddly coloured column running down the outside of each arm, you have uploaded a Slim skin onto the Classic model. The skin paints three pixels of arm width; the model is four wide; the fourth column was never painted.

If instead the sleeves look compressed and the hand colour bleeds into the wrong place, it is the reverse — a Classic skin on the Slim model, with four pixels of texture squeezed into three.

The fix is to re-upload and choose the other model. Nothing about the file needs to change. Each skin page in our library states which model it was built for, so you can check rather than guess.

Black patches where you expected transparency

Transparency only works on the second layer. On the base layer it does not.

If you erase pixels on the base body, head or legs expecting to see through them, Minecraft renders those pixels as solid — usually black. The base layer is the character's actual surface and is always opaque by design.

So anything that needs a see-through region has to live on the overlay: hair with gaps in it, glasses with clear lenses, a jacket that stops partway down the arm. If you have painted an accessory onto the base layer and cut holes in it, the accessory needs moving to the overlay rather than fixing in place.

The other version of this problem is a skin saved as JPEG at some point in its life. JPEG has no transparency at all, so every previously clear pixel becomes opaque, usually with coloured fringing around the edges. There is no repair for that beyond going back to a PNG original.

The upload is refused

Three checks, in order.

Dimensions. The file must be exactly 64x64, or 64x32 for a legacy skin. Not 63x64, not 128x128. An HD skin at 128x128 will be refused by vanilla no matter which platform you are on — it needs a client mod, as covered in the format guide.

Format. It must be a real PNG. A file renamed from .jpg to .png is still a JPEG internally and will be rejected.

Source. A screenshot of a skin is not a skin. Images saved from a preview render, a search result thumbnail or a 3D viewer are pictures of a character, not the texture map, and will either fail or upload as unrecognisable noise. Always download the actual skin file.

You see the new skin, but other players do not

This is a caching problem and not a fault in your file.

Servers cache the skins of connected players, and so do other players' clients. When you change your skin mid-session, everyone already loaded keeps the old texture until something forces a refresh. Leaving and rejoining the server usually clears it; occasionally the other player needs to reconnect too.

Give it a few minutes before treating it as broken. Mojang's skin service also takes a short while to propagate a newly uploaded file, so a change that appears instantly for you can lag for everyone else.

The diagnostic that settles it: check your own character in third person. If your client shows the new skin, the upload succeeded and everything else is cache.

A thin line where two faces meet

If a faint seam runs down the character's side or around a limb, the edge pixels of two adjoining faces do not match.

Each face of each body part is a separate rectangle on the texture map, and they are not adjacent in the image the way they are on the model. The right edge of the front of the leg and the left edge of the side of the leg sit in different places on the PNG, so it is easy to paint one and forget the other.

Fix it by matching the colours along both edges. This is much easier in an editor with a 3D preview, where you can rotate until the seam is visible and paint straight onto the model. The skin-making guide goes into the workflow.