Separate the base from the outer layer
This Minecraft skin layer viewer helps you inspect how a local PNG uses its base texture and optional outer overlay. Load a supported file, rotate the model, turn the outer layer on or off, hide individual body parts, switch Classic or Slim arms, and compare the result without changing source pixels.
Minecraft skins can store two visual surfaces in one atlas. The base layer defines the essential head, torso, arms, and legs. The outer layer sits slightly above it and can represent hair, hats, helmets, jackets, sleeves, trouser overlays, and decorative depth. Good inspection asks whether each detail is on the intended surface.
Why layer inspection matters
An outer layer can hide an unfinished base. The complete model may look acceptable until the overlay is disabled, revealing a transparent face, missing torso pixels, or holes in an arm. Those gaps may display unexpectedly in clients or when users disable accessories.
The opposite issue also occurs: opaque outer pixels may cover carefully drawn base details, create bulky shapes, or connect regions that should remain separate. Toggle repeatedly while rotating the model to identify the exact source.
Read-only visibility controls
Layer and body-part switches affect only the preview. They do not erase, clear, merge, or rewrite pixels in the selected PNG. This makes the viewer safe for diagnosis before deciding whether a modification is needed.
If the outer layer needs correction, open the editor. If the base contains transparent holes, use the checker and consider only explicit repairs reported by the fixer. Do not fill every transparent pixel because most unused atlas space and many overlay regions are supposed to remain transparent.
Inspect by body part
Hide the head to examine the top of the torso and shoulders. Hide one arm to expose the torso side. Hide the torso when inner arm surfaces overlap it. Hide one leg to inspect the inner face of the other.
Body isolation is useful for seams and hidden surfaces, but it does not represent the finished silhouette. Restore all parts and the outer layer for the final review.
Head and hat layer
The head base should contain the complete face, sides, back, top, and bottom required by the design. The hat layer may add hair, a visor, helmet, ears, glasses, or other depth. Check it against multiple camera angles.
Transparent overlay pixels are normal. Fully opaque blocks over the entire face may be intentional for a helmet, but they can also hide an incomplete base. Compare both states.
Torso, sleeves, and trousers
Jacket and shirt overlays should meet their neighboring faces cleanly. Inspect front-to-side and side-to-back edges. Sleeve overlays need the correct Classic or Slim arm width; a model mismatch can expose columns or clip details.
Trouser overlays can add cuffs, belts, pockets, or layered shoes. Check the waist transition and inner legs. A detail that exists only on the front rectangle may end abruptly when the character turns.
Classic and Slim layer geometry
Both models use the same overall modern canvas size, but arm face widths differ. Layer artwork follows those mapped arm regions. Switch geometry to diagnose the file, but remember that preview switching does not convert the atlas.
Use the model detector only as a clue and the converter for an intentional output transformation. After conversion, return to the layer viewer and inspect base and overlay arms separately.
Texture and background checks
The flat texture view helps locate the rectangles responsible for a model detail. Background controls help expose partial-alpha fringes and pale matte colors around overlay edges. Compare checker, light, and dark backgrounds.
The viewer does not produce a numeric alpha report. Use the checker when you need counts, dimensions, or mapped-region warnings.
When you need aligned working files instead of a read-only preview, the Minecraft skin layer splitter exports separate 64 × 64 base and overlay PNGs without changing their UV coordinates. If the atlas contains visible matte pixels in unused gaps, the Minecraft skin background cleaner can clear only those unmapped positions.
Local-first workflow
Selected files are decoded in the browser and are not published. There is no login, gallery, cloud project database, subscription, or credit balance. Downloaded source and revisions remain under your control.
A practical sequence is to preserve the source, load it, inspect all layers and body parts, identify one suspect atlas area, edit one change, export under a new name, and review again. This keeps repairs auditable.
Only use artwork you own or have permission to inspect and adapt. SkinEditor.org is independent and is not affiliated with Mojang or Microsoft.
Frequently asked questions
Does hiding the outer layer delete it?
No. Visibility is read-only and the selected PNG remains unchanged.
Should the outer layer be fully opaque?
Usually only where extra detail is intended. Transparent overlay space is normal and often necessary.
Can the viewer merge or split layer files?
No. It focuses on visual inspection of a standard combined skin atlas.
Why does a sleeve look wrong only on Slim?
The file may use Classic arm mapping. Compare models, inspect arm columns, and use the converter only when a real transformation is intended.