Check a skin before trying to import it
A Minecraft skin can look like a normal PNG in an image viewer and still fail when it is imported. The dimensions may belong to a legacy or high-definition format, important base pixels may be transparent, or artwork may sit outside every mapped character face. This Minecraft skin checker reads the file in your browser and turns those hidden structural details into a short technical report. It does not require a username, game account, registration, or upload to a public gallery.
Choose a PNG to see its exact width and height, detected format family, likely Classic or Slim arm layout, number of transparent pixels, number of transparent holes in mapped base faces, used overlay pixels, and non-transparent pixels outside recognized UV faces. The checker is diagnostic: it explains what is present in the image without silently resizing, repainting, or replacing the source. Your original file remains unchanged.
What the report checks
The first test is the real decoded image size. A modern standard skin is normally 64 × 64 pixels. A 64 × 32 image is recognized as a legacy layout, while a 128 × 128 image is identified as an HD texture that may be accepted by some servers or tools but is not interchangeable with the standard format. Other dimensions receive an unsupported result. File extensions alone are not enough, so the browser also has to successfully decode the selected file as a PNG.
For a valid 64 × 64 atlas, the checker examines the alpha value of every pixel. Fully transparent pixels are normal in unused areas and in optional outer layers. They become suspicious when they occur in a mapped base face, because a hole in the head, torso, arm, or leg base can render as missing, black, or inconsistent depending on the client and renderer. The report counts these positions instead of claiming that every transparent pixel is an error.
The checker also counts opaque pixels in overlay faces. A nonzero overlay count usually means the skin uses hats, hair volume, jackets, sleeves, or trouser details. An empty overlay is valid; it simply means the appearance is carried by the base texture. Pixels outside all recognized faces are reported separately. Some workflows tolerate unused-atlas data, but those pixels do not normally appear on the character and can indicate that an image was pasted into the wrong position.
Classic and Slim detection is a useful estimate
Classic arms use four-pixel-wide face regions, while Slim arms use three-pixel-wide regions. The PNG does not contain a universal metadata flag that always declares which geometry the artist intended. This checker therefore uses a transparent-column heuristic: if opaque content appears in columns used by Classic arm faces but excluded from Slim faces, the report labels the file as likely Classic. If those evidence columns are transparent, it labels the file as likely Slim.
That result is intentionally described as a likelihood, not a guarantee. A Classic design may leave its outer arm columns transparent, and a damaged Slim file may contain stray pixels in them. Confirm the estimate in a 3D preview and compare it with the model selected in the game. A checker should expose uncertainty instead of presenting a heuristic as authoritative metadata.
Understanding base-layer holes
The base layer contains the essential six faces for the head, torso, both arms, and both legs. The checker builds a UV mask for the detected arm model and counts any mapped base position whose alpha value is zero. One or two holes can be accidental eraser marks. A large count may mean the image is blank, partially exported, using the wrong geometry, or relying on behavior that does not transfer between clients.
Do not automatically fill every reported hole with black or a nearby color. Transparent regions can be deliberate in specialized designs, and an automatic repair cannot know the artist’s intention. The safer workflow is to open the file in the editor, inspect the reported body regions in 2D and 3D, make a visible correction, then run the checker again. This preserves creative control and creates a clear before-and-after process.
Legacy and HD results
A 64 × 32 result is not necessarily a corrupt image. It usually indicates the older layout where the second arm and leg are mirrored rather than stored as independent modern faces. Converting it correctly requires copying and flipping specific UV rectangles into a 64 × 64 document. Stretching the whole image to twice its height produces the wrong mapping, so this checker reports the legacy format but leaves conversion to a dedicated tool.
Likewise, a 128 × 128 result identifies a higher-resolution texture rather than shrinking it automatically. Reducing HD artwork to 64 × 64 needs nearest-neighbor sampling and a review of fine details, transparency, and destination compatibility. The checker keeps the distinction visible so users do not download an altered file without understanding the loss.
Privacy and local processing
The selected image is decoded into temporary browser canvas memory. The active checker does not send its pixels, filename, colors, report, or preview to an image upload endpoint. The preview is drawn locally, and navigating away clears the in-memory result. This is useful for private designs and also reduces the copyright and moderation problems that come with automatically publishing user files.
Local inspection does not bypass the destination platform’s rules. A technically well-formed texture can still be rejected because of account restrictions, game edition differences, server plugins, marketplace requirements, moderation, or content rights. SkinEditor.org is an independent tool and is not an official Minecraft product or service. It is not approved by or associated with Mojang or Microsoft.
Recommended next steps
If the report passes and the model estimate matches your intended geometry, download or keep the original file and follow the import guide for your edition. If base holes or outside-UV pixels are reported, open the Minecraft skin editor and correct those areas without resizing the document. If the format is legacy or HD, use a converter made for that exact input and output pair. After any repair or conversion, check the exported PNG again before importing it.
Frequently asked questions
Does this checker upload my skin?
No. The selected PNG is decoded and inspected locally in the current browser. The tool does not create a public skin page or store the image in an account.
Does a warning mean the skin cannot work?
Not always. A warning identifies a structural condition worth reviewing. Intentional transparency and unused overlay regions can be valid, while platform behavior varies.
Can the checker repair the file automatically?
The current checker is read-only. Automatic filling or resizing could damage intentional artwork. Use the editor or a dedicated converter, review the result, and then check it again.
Why is the arm model only “likely” Classic or Slim?
Standard PNG pixels do not provide a reliable universal model declaration. The tool examines arm columns that differ between the two layouts, so unusual or damaged artwork can remain ambiguous.