Split one skin atlas into two usable layer files
A modern Minecraft skin stores the essential character texture and optional raised details inside one 64 × 64 PNG. This Minecraft skin layer splitter reads that combined atlas and creates two separate, full-size PNG outputs. The base result keeps the mapped head, torso, arm, and leg faces from the base layer. The overlay result keeps the hat, jacket, sleeve, and trouser-layer faces. Every other pixel is transparent, so each download remains aligned to the original atlas instead of becoming an arbitrary crop.
The workspace loads a first-party example immediately. It is a real generated 64 × 64 texture with colored body regions and partially transparent overlay marks, not a decorative screenshot. Use the download buttons to inspect both example outputs, or upload your own PNG. Processing happens in browser memory and does not send the image, filename, model choice, or resulting layers to a server.
How to use the layer splitter
Choose Upload 64 × 64 PNG and select a modern skin file. The source preview displays the combined texture. Choose Classic arms when the design uses four-pixel arm fronts, or Slim arms when it uses three-pixel arm fronts. The two output previews update immediately. Download the base PNG, the overlay PNG, or both.
The files remain 64 × 64 because atlas coordinates matter. A separate layer is not useful if its rectangles are packed into a smaller image and lose their original positions. Keeping the canvas size and coordinates means the output can be examined, edited, compared, or recombined using tools that understand standard skin UV placement.
The model selector changes only arm-region interpretation. Head, torso, and leg regions use the same modern coordinates, while Classic and Slim arms have different effective face widths. If the source model is uncertain, inspect it with the Minecraft skin model detector before treating the split output as authoritative.
What belongs in the base output
The base layer is the required visual surface of the character. It contains six mapped faces for the head, torso, right arm, left arm, right leg, and left leg. A robust skin should normally remain recognizable and structurally complete when only this layer is visible. Hair volume, jackets, helmets, and cuffs may disappear, but important facial, clothing, and limb coverage should not depend on an optional overlay.
Splitting is therefore a useful diagnostic step. Open the base download in an image editor and look for transparent holes, abruptly missing seams, or details that were accidentally painted only on an outer surface. The splitter does not repair those issues. It preserves mapped pixels exactly and makes the separation visible. Use the Minecraft skin checker when you need numeric transparency warnings or the skin fixer when you want explicit, reviewable repair choices.
What belongs in the overlay output
The overlay output contains the second texture surface for every supported body part. On the model, those pixels are rendered slightly outside the base geometry. Designers use them for a hat layer, loose hair, glasses, helmet details, jacket edges, sleeves, pockets, belts, trouser panels, and shoe depth.
Large transparent areas are normal in an overlay-only file. Transparency is not evidence that the export failed. Only pixels that were present in mapped outer-layer rectangles are retained. Unused atlas space is cleared, and base faces are transparent by design. Preview the original skin with the Minecraft skin layer viewer to compare the complete character with the outer surface toggled on and off.
Partial alpha is preserved. If an overlay pixel was translucent, the output keeps its RGBA value instead of forcing it opaque. Different clients and renderers may treat partial transparency differently, so validate the result in the environment where it will be used.
Classic and Slim arm mapping
Both arm models use a 64 × 64 canvas, but their arm faces do not occupy identical effective widths. Classic arms use four-pixel front and back faces. Slim arms use three-pixel front and back faces while side faces retain their mapped depth. Selecting the wrong model can move a narrow column into the wrong conceptual category or leave an unexpected transparent strip.
The splitter never guesses or converts the model. It follows the selection you make. This avoids a destructive surprise: separating layers should not invent pixels, crop the source, or silently transform Classic artwork into Slim artwork. If conversion is the actual goal, use the dedicated Classic-to-Slim converter or Slim-to-Classic converter, then split the converted file.
Practical uses for separate layer PNGs
Layer files are useful for auditing commissioned artwork, teaching atlas structure, comparing two revisions, rebuilding a damaged overlay, or isolating garment details before recoloring. A creator can duplicate the original, split it, edit the overlay file without touching base pixels, and preserve both downloads as a clear review record.
They are also useful as masks. The alpha channel of the overlay output identifies mapped pixels that contribute raised details. The base output identifies the essential surface. Advanced desktop editors can load both as aligned layers because they share the same dimensions and coordinate system.
Do not assume a game client accepts the separated files directly. Standard skins normally expect one combined atlas. These downloads are intermediate working assets. Keep the original combined PNG, and use a deliberate merge workflow before importing a modified result.
Privacy, ownership, and safe workflow
The selected file is decoded with browser image and canvas APIs. There is no account, upload endpoint, cloud project, public gallery, subscription, or database record. Closing the page discards the active processing state unless you separately save the downloaded PNG files.
Only split artwork you own or have permission to modify. Separating a texture does not grant rights to another creator’s design, character, logo, or branded costume. SkinEditor.org is an independent tool and is not affiliated with Mojang or Microsoft.
A careful workflow is: keep an untouched source copy, verify that it is 64 × 64, choose the correct arm model, download both outputs, inspect transparency, make edits under new filenames, and compare the final combined skin from several model angles.
Frequently asked questions
Does splitting damage the original PNG?
No. The source file is read locally and is not overwritten. The tool creates new canvas outputs.
Why are both downloads still 64 × 64?
They preserve standard UV coordinates, which makes later editing, comparison, and merging predictable.
Can I import the overlay-only PNG as a complete skin?
Usually not. It is an intermediate asset with the base deliberately removed.
Does the tool merge the layers again?
Not on this page. It focuses on accurate, auditable separation and leaves the original combined source unchanged.