Find transparent holes where a body surface should exist
This transparent pixel fixer examines the mapped base faces of a modern 64 × 64 Minecraft skin. It reports every coordinate whose alpha value is zero inside the selected Classic or Slim body map, then lets you fill the reported coordinates with one opaque color. The original and result remain visible side by side, so the change is explicit rather than hidden behind an automatic “repair” claim.
The image, filename, selected model, coordinates, fill color, and output stay in browser memory. There is no upload endpoint, account, cloud project, or database. A first-party skin with six deliberate holes loads when the page opens, making the diagnosis and download testable without personal artwork.
What a transparent base-layer hole means
A modern skin atlas contains base faces for the head, torso, arms, and legs, plus optional outer faces. A base pixel represents the essential body surface. When its alpha is zero, a renderer may show a missing patch, black area, unexpected fallback, or inconsistent transparency depending on edition and context.
Transparency is normal in unused atlas space and on optional outer layers. This tool does not fill every transparent pixel in the PNG. It uses the selected UV map and targets only transparency inside mapped base rectangles. For visible color outside mapped rectangles, use the Minecraft illegal pixel checker. The two checks describe opposite structural conditions.
How to use the fixer
Upload an exact 64 × 64 PNG or keep the first-party example. Select Classic for four-pixel arms or Slim for three-pixel arms. The hole count and coordinate list update when the model changes because arm-face widths differ.
Choose a fill color, review the coordinate list, and select Fill reported holes. The result preview changes while the source remains untouched. Reset returns the preview to the selected source. Download creates a separate 64 × 64 RGBA PNG.
The color is intentionally one uniform opaque value. This is useful for repairing known solid-color surfaces or creating a safe temporary marker. It cannot reconstruct missing eyes, clothing seams, gradients, shading, or texture. For mixed artwork, use the coordinates as a guide and continue in the Minecraft skin editor instead of accepting a flat fill.
Why the model selector matters
Classic and Slim skins have the same outer dimensions but different effective arm widths. A coordinate can be part of a Classic arm face yet outside the corresponding Slim face. Selecting the wrong model can therefore change the reported set.
If the intended model is unknown, run the Minecraft skin model detector and examine its evidence. Model detection is heuristic when arm columns are transparent or sparse, so the source of the file and an actual 3D preview remain important.
Alpha, hidden RGB, and partial transparency
The checker defines a hole as alpha exactly zero. Hidden RGB values under alpha zero do not make a pixel visible and do not prevent a report. Partial alpha greater than zero is not counted as a complete hole, although translucent base pixels can behave differently across clients.
The fill action writes the selected RGB values with alpha 255. It does not adjust nearby colors, sample neighbors, blur edges, or modify mapped pixels that were already visible. This narrow rule keeps the operation measurable.
Run the broader Minecraft skin checker when partial transparency, dimensions, overlay use, or outside-UV pixels also need review. A clean hole count does not guarantee complete game compatibility.
Safe repair workflow
Keep an untouched master file. Run the diagnosis with the intended arm model. Inspect every coordinate at pixel zoom. If all holes belong to one solid surface, apply a matching color and download under a new filename. Compare source and result in the 3D skin viewer, especially around face edges and limb seams.
If holes cross several colors, do not use a single flat fill. Open the source in the editor, repair individual pixels, then run this checker again. A zero count should be a verification step, not a substitute for visual review.
The dedicated Minecraft skin fixer combines base-hole filling with outside-UV cleanup and undo/redo. Use this focused page when the search task is specifically transparent base pixels and a compact coordinate-first workflow is preferable.
What the fixer does not promise
The tool does not validate an account, game version, server, launcher, skin pack, marketplace, or moderation result. It cannot determine artistic intent or copyright. Some transparent regions may be deliberate for a particular custom renderer, while standard workflows may display them unexpectedly.
It also does not repair a corrupt PNG container, resize HD artwork, convert a legacy layout, or change Classic into Slim. Use a dedicated converter when the input dimensions or geometry are the real problem.
Privacy and ownership
Browser image and canvas APIs decode and export the file locally. Closing the page clears the active state unless the result was downloaded. Only repair artwork you own or have permission to modify. Technical correction does not grant rights to another creator’s design.
SkinEditor.org is independent and is not associated with or approved by Mojang or Microsoft.
Frequently asked questions
Does the tool fill transparent outer-layer pixels?
No. Empty outer layers are normal. It targets only transparent coordinates inside selected base faces.
Can it restore the original missing artwork?
No. It applies one chosen color. Detailed reconstruction requires manual editing or a trusted source copy.
Why did the count change after selecting Slim?
Classic and Slim arm-face widths differ, so their mapped coordinate sets are not identical.
Is a zero hole count a compatibility guarantee?
No. Dimensions, outside-UV pixels, metadata, target software, and other conditions can still affect use.