Skin Converter

Turn an old 64×32 Minecraft skin into the modern 64×64 layout. The left arm and leg get filled in, you see the result on the player model in 3D, and the PNG downloads. Runs in your browser.

Your skin file

Drop a skin PNG here or click to choose a file — 64×32 (old) or 64×64 (current)

What you loaded

No file chosen yet.

Converted sheet

Nothing converted yet.

What the conversion actually does

A 64×32 sheet stores one arm and one leg. The game draws the other side by mirroring them, so the old layout has no box of its own for the left arm or the left leg. The 64×64 layout added those two boxes at (32,48) and (16,48) — paste an old sheet in without filling them and the left limbs come out blank.

So the converter copies your sheet unchanged, then rebuilds the two new boxes face by face from horizontally flipped copies of the right arm and right leg. Nothing is resampled: every pixel is moved, never blended, so the result is the same image the game was already drawing — just stored where a modern client looks for it. From there the two limbs are separate, and you can paint them differently in a skin editor.

Your file is read with canvas in this page. It is never uploaded.

Also works on a 128×64 HD sheet, which comes out as 128×128. Vanilla Java only accepts 64×64 on upload; HD skins need a mod.

Quick guides

How to use this tool, and the questions players ask most.

Slim or classic is decided by 24 pixels, and you can see exactly which onesA skin is slim if fewer than 6 of the 24 pixels at (46,20)–(47,31) are opaque. Plus the full UV map, and why legacy 64×32 skins get mirrored.

What is the difference between a 64×32 and a 64×64

skin?

The old 64x32 sheet holds one arm and one leg, and the game mirrors them onto the other side. The 64x64 sheet introduced in 1.8 gave the left arm and left leg their own boxes, and added a second overlay layer for every body part instead of only the head.

Why does my old skin have an invisible left arm after resizing it?

Resizing the canvas to 64x64 in an image editor leaves the two new boxes at (32,48) and (16,48) empty, and empty means fully transparent. Those boxes have to be filled with mirrored copies of the right arm and right leg, face by face, which is what this converter does.

Does converting a skin lose any

image quality?

No. Every pixel is copied at a one-to-one scale with smoothing switched off, so no pixel is ever blended or resampled. The converted file renders exactly like the original did in game — the pixels are simply stored where a modern client reads them.

Why do both arms look identical on the converted

skin?

Because the old format never stored a second arm, so there is nothing else to fill the new box with. Once converted the two limbs are independent, so a skin editor can repaint the left arm and left leg without touching the right side.

Can I upload a 64×32 skin to Minecraft

Java today?

Java clients still render the legacy layout, but the current launcher and nearly every skin tool, resource pack and server plugin are written for 64x64. Converting first avoids the whole class of problems, and it is the only way to use the per-limb overlay layers.