Recombine two aligned skin layer files
This Minecraft skin layer merger takes two complete 64 × 64 PNG files and produces one combined atlas. The first input supplies pixels for mapped base faces. The second supplies pixels for mapped outer faces such as the hat, jacket, sleeves, and trouser layers. The tool keeps those regions at their standard coordinates, applies an optional opacity multiplier to visible overlay pixels, and exports a real 64 × 64 PNG.
The operation happens locally in the browser. Neither source file, its name, its pixels, the selected arm model, the opacity value, nor the merged output is transmitted. A first-party example is loaded immediately so every control and the download can be tested without providing personal artwork.
How this merger differs from ordinary image compositing
A skin atlas places base and outer geometry in different UV rectangles. Merging the layers does not mean drawing the second image directly over the first at the same x and y coordinates. That kind of flat alpha composite would be appropriate for two screenshots, but it would destroy the atlas relationship expected by a character renderer.
Instead, this tool selects the mapped base rectangles from the base file and the mapped overlay rectangles from the overlay file. Both files remain aligned to the same 64 × 64 coordinate system. A hat pixel stays in the hat region; it is not flattened onto the head face. A sleeve stays in the sleeve region rather than replacing arm artwork. Unmapped pixels are cleared in the result.
This behavior is designed to reverse the working-file separation produced by the Minecraft skin layer splitter. It is also useful when two independently edited full-atlas files already follow the same mapping.
How to merge a base and overlay
Choose Upload base PNG and select the file that contains essential head, torso, arm, and leg surfaces. Choose Upload overlay PNG for the aligned outer-layer file. Both inputs must be PNG images exactly 64 × 64 pixels. The three previews show the selected base, selected overlay, and combined output.
Select Classic or Slim arms before download. The model affects which arm pixels count as mapped faces. Classic arms use four-pixel front and back widths; Slim arms use three-pixel widths. Head, torso, and leg regions remain in their modern positions. If the model is uncertain, inspect the source with the Minecraft skin model detector.
Move the overlay opacity control only when you intentionally want to scale alpha. At 100 percent, original alpha values are preserved. At 50 percent, an overlay pixel with alpha 200 becomes approximately 100. RGB colors remain unchanged. At zero, overlay pixels are fully transparent even though their mapped positions remain part of the output.
What should go in the base file
The base file should hold the required character surface. The skin ought to remain coherent when the outer layer is disabled: the face should exist, limbs should be covered intentionally, and clothing colors should not depend entirely on a jacket or sleeve. Transparent holes in mapped base faces can produce missing-looking geometry or inconsistent results.
Use the Minecraft skin checker to find base-layer holes before merging. The merger does not invent colors or fill gaps because doing so would modify artwork without a reliable intent. It copies mapped values from the chosen input.
The base source may be a full combined skin rather than a base-only file. That is acceptable because the tool ignores its overlay rectangles. Likewise, any visible pixels outside the selected UV map are not carried into the combined output.
What should go in the overlay file
The overlay file should contain optional depth details: hair volume, glasses, hat elements, helmet pieces, jacket edges, pockets, sleeves, cuffs, belts, trouser panels, or shoe accents. Large transparent areas are expected. The overlay is a second surface around the model, not a complete character by itself.
The overlay source may also be a full combined skin. Only its mapped outer regions are selected, so base pixels in that file do not replace the chosen base source. This makes it possible to take the underlying design from one aligned skin and outer details from another, provided you have permission to use both.
If a file contains visible color in unused atlas space, run the Minecraft illegal pixel checker or skin background cleaner to inspect it. The merger clears unused space automatically, but a diagnostic report is useful when you need exact coordinates.
Opacity and renderer differences
Partial alpha can look different across clients, renderers, thumbnails, and export pipelines. Some workflows preserve translucent outer pixels; others may reject, quantize, or display them differently. The opacity slider changes PNG alpha values but cannot guarantee how every target environment interprets them.
For the most conservative result, leave opacity at 100 percent when recombining a previously split skin. Change it only when the overlay was designed for that adjustment. Always inspect the downloaded PNG in a 3D skin viewer and in the final application.
A careful layer workflow
Keep an untouched combined master. Split it into aligned base and overlay working files. Edit each file without changing dimensions or moving UV rectangles. Verify the arm model. Run structural checks. Merge at full opacity, inspect the combined output from several angles, and save it under a new filename. This creates a reversible audit trail and avoids repeatedly degrading a single file.
The merger reports the number of mapped base pixels copied and the number of visible overlay pixels written. These counts help confirm that the result is not empty, but they do not measure artistic quality. A sparse overlay can be completely intentional.
Privacy, copyright, and independence
The page has no registration, cloud storage, database, gallery, or image-upload API. Browser canvas APIs decode and create the files. Closing the tab discards the active state unless the PNG was downloaded.
Only combine designs you own or have permission to adapt. Technical alignment does not grant a license to copy another artist’s work, fictional character, brand, or paid asset. SkinEditor.org is independent and is not associated with or approved by Mojang or Microsoft.
Frequently asked questions
Are the two inputs flattened together?
No. Base and overlay UV regions remain separate in the atlas so a 3D renderer can display them as separate surfaces.
Must both files be layer-only exports?
No. They can be full aligned skins; the merger selects only the appropriate mapped regions from each input.
Why does the arm model matter?
Classic and Slim arm faces have different effective widths, so the selection must match the intended geometry.
Can I undo a merge?
Keep the source files. You can also split the merged result again, but retaining the originals is the safest reversible workflow.