Compare one PNG with three skin workflows
This Minecraft skin compatibility checker reads a local PNG, detects whether its dimensions match a modern 64 × 64, legacy 64 × 32, supported HD 128 × 128, or unsupported layout, and compares that format with three common targets: a Java standard upload, a Bedrock classic-skin workflow, and the original legacy 64 × 32 layout.
The result is practical format guidance, not official certification. A structurally compatible PNG can still fail because of game version, account settings, launcher behavior, server policy, skin-pack geometry metadata, marketplace requirements, moderation, or a damaged file. The tool answers a narrower question: does this image’s size and inspected atlas structure fit, need review, require conversion, or fall outside the supported formats?
Processing is local. The selected image, filename, pixels, and report are not uploaded. The page includes modern, legacy, and HD first-party examples so the status matrix can be explored immediately.
How to use the checker
Upload a PNG or select one of the example buttons. The preview displays the decoded file and the status line reports its dimensions and detected category. Three result cards then explain the expected workflow for Java, Bedrock, and legacy use. Download the JSON when you need to save the machine-readable result for a project note or support conversation.
For supported 64 × 64 and 64 × 32 files, the checker examines pixel structure as well as dimensions. It can identify base-layer holes or visible pixels outside mapped faces and change a modern format from a clean compatible result to a review state. For 128 × 128, it identifies an HD layout that needs nearest-neighbor conversion before the standard 64 × 64 workflow.
An arbitrary image such as 300 × 300 is displayed for visual confirmation but classified as unsupported. The tool does not read a full large-pixel report for unsupported dimensions, which keeps the scope focused on known skin layouts.
Modern 64 × 64 results
A modern 64 × 64 PNG is the standard atlas shape for independent left and right limbs plus body outer layers. When no structural warning is found, the Java target is marked compatible. The Bedrock classic-skin target is also format-compatible with the standard atlas, although an actual skin pack may still require separate manifest and geometry metadata.
The legacy target is not marked natively compatible because the original 64 × 32 layout lacks the modern lower-half regions. If a legacy export is required, use the 64x64 to 64x32 converter and review its discarded-pixel count. Unique left limbs and modern-only overlays cannot be retained in that smaller canvas.
When the modern checker sees transparent holes in required base faces or visible pixels outside the selected map, Java and Bedrock results move to review. The dimensions are still recognized, but the file deserves inspection with the full Minecraft skin checker.
Legacy 64 × 32 results
A 64 × 32 PNG matches the original mirrored-limb layout. The legacy target is therefore marked compatible. Java workflows may encounter old Classic textures, but conversion is recommended when you need independent limbs and modern outer layers. Bedrock standard workflows should convert the file to a modern atlas.
Use the 64x32 to 64x64 skin converter for that operation. It copies the old regions and mirrors right arm and right leg faces into the modern left-limb positions. Conversion cannot invent truly independent artwork, but it produces a modern coordinate structure that can be edited afterward.
Legacy dimensions alone do not prove a design will display correctly. The artwork may have incorrect face orientation, unexpected transparency, or a nonstandard arrangement. Preview the output rather than relying only on the green status badge.
HD 128 × 128 results
The checker recognizes an exact 128 × 128 image as the supported two-times HD form of a modern atlas. Standard Java and Bedrock skin uploads generally use 64 × 64, so the report requires conversion first. The legacy target also needs a different layout, not merely a crop.
Use the 128x128 to 64x64 skin converter to downsample with nearest-neighbor mapping and review the reported color loss. HD artwork may contain details that collapse when four source pixels become one destination pixel. Nearest-neighbor avoids blur but cannot preserve every pattern.
After resizing, run the resulting 64 × 64 file through the checker again. Compatibility is a pipeline: verify the source category, perform a deliberate conversion, then verify the actual output.
Bedrock compatibility requires context
“Bedrock compatible” on this page refers to the standard 64 × 64 classic-skin atlas used by common import workflows. A Bedrock skin pack is a package, not just a PNG. It can require manifest files, skin definitions, localization text, and geometry identifiers. Use the Bedrock skin pack maker when packaging is the goal.
Marketplace, persona, and custom geometry content are outside this checker’s scope. A valid PNG cannot satisfy rules that live in metadata or a publishing system. The status explanation deliberately separates atlas compatibility from complete product acceptance.
Reading the four statuses
Compatible means the inspected format matches the target’s expected atlas workflow. Review means dimensions match but structural pixel warnings deserve attention. Convert first means a recognized source format needs a deliberate layout or size transformation. Unsupported means the dimensions do not match the standard, legacy, or supported HD input categories.
These labels help choose the next tool; they are not legal, moderation, or official platform decisions. Downloaded JSON preserves the detected format, dimensions, overall structural status, warnings, and target-specific reasons.
Privacy and responsible use
There is no account, database, cloud draft, public gallery, or image upload API. Browser image and canvas APIs perform the check. Closing the page clears the active report unless it was downloaded.
Only inspect and convert artwork you own or have permission to modify. Technical compatibility does not grant rights to another creator’s design or branded character. SkinEditor.org is independent and is not associated with or approved by Mojang or Microsoft.
Frequently asked questions
Can the checker guarantee that my skin will upload?
No. It checks supported dimensions and selected structural signals; external account, client, metadata, and policy conditions remain.
Why is a 64 × 64 file marked Review?
Recognized dimensions can still contain transparent base holes or visible pixels outside mapped UV faces.
Is 128 × 128 invalid?
It is recognized as an HD source, but it must be deliberately converted for the standard 64 × 64 workflow.
What is the JSON report for?
It provides a portable record of the detected format and target-specific reasons for debugging, documentation, or handoff.