Check a skin’s dimensions
The analyzer above classifies pixel width and height without reading or uploading a file. Enter the decoded dimensions reported by your image editor, operating system, or skin checker. It distinguishes the standard modern 64×64 atlas, the older 64×32 layout, square HD-style multiples, and sizes that do not match common skin structures.
Dimensions describe the source PNG, not how large the character appears on screen. A 64×64 skin can be displayed across hundreds of screen pixels because the renderer magnifies individual texture pixels. Increasing the file to 128×128 does not automatically create better art or universal compatibility.
Modern 64×64 dimensions
The modern standard canvas is 64 pixels wide and 64 pixels high. It contains independent base faces for the head, torso, left and right arms, and left and right legs. It also provides a complete second layer for hats, jackets, sleeves, and trouser overlays.
Each body surface occupies a small rectangle inside the atlas. The head front is 8×8; the torso front is 8×12; Classic arm fronts are 4×12; Slim arm fronts are 3×12; and leg fronts are 4×12. Those are surface dimensions, not the full file size. The remaining rectangles store sides, backs, tops, bottoms, other limbs, and overlays.
Use 64×64 when starting a new conventional skin. It provides the clearest broad modern compatibility and supports asymmetrical limbs. Keep unused atlas space transparent and preserve alpha in PNG export.
Legacy 64×32 dimensions
Older skins use a 64-pixel-wide by 32-pixel-high atlas. The layout predates independent left limbs and the complete modern overlay system. Renderers mirror right-arm and right-leg artwork to the left side. That is why old characters often have identical gloves and shoes.
A legacy file can still be meaningful, but modern editing usually benefits from conversion to 64×64. A proper converter preserves the upper source and maps mirrored arm and leg faces into the new independent left-side UV regions. Simply adding 32 transparent rows creates the correct outer dimensions but does not populate the new limb faces.
If a 64×32 file is rejected, conversion may be required by the target flow. If it imports but looks mirrored, that behavior is inherent to the legacy structure rather than a random rendering bug.
128×128 and HD-style dimensions
Some third-party launchers, servers, mods, and skin systems accept square atlases that scale every coordinate by an integer factor. A 128×128 atlas doubles each source dimension, so a standard 8×8 head front becomes 16×16. Larger multiples may also exist.
Support is not universal. A platform expecting exactly 64×64 may reject, resize, or mishandle the file. Before investing in HD details, verify the destination’s current requirements. Resizing a finished 64×64 skin to 128×128 with nearest-neighbor produces larger pixel blocks but no new information. Actual HD work requires drawing new detail within the expanded faces.
Invalid and misleading sizes
Common mistakes include 32×32 icons, 64×64 screenshots with margins, 512×512 avatar portraits, rectangular crops, and images whose file extension says PNG even though the encoded content is another format. A square image is not automatically a skin atlas. It must contain the expected UV rectangles at exact coordinates.
Web previews can mislead because CSS display dimensions differ from decoded bitmap dimensions. Download the original file and inspect its pixel properties. File size in kilobytes also says nothing reliable about canvas width and height.
Classic and Slim do not change the full size
Both Classic and Slim modern skins remain 64×64. Only arm face widths and associated coordinates differ. A three-pixel Slim arm does not require a narrower file. Import screens often ask for arm geometry separately because the PNG dimensions alone cannot resolve intent reliably.
Do not crop a Classic atlas to make it Slim. Use a model-aware converter or edit arm UV faces in place. Head, torso, and leg coordinates must remain unchanged.
Transparency and color channels
Dimensions are only one validity condition. A correct skin should normally be PNG with RGBA transparency. Mandatory base faces should not contain accidental alpha holes. Optional outer-layer and unused atlas regions can remain transparent.
JPEG may decode to 64×64 but still be unsuitable because it removes transparency and blends colors. Renaming a JPG extension to PNG does not convert the internal format. Re-export from an image editor or browser tool.
Diagnosing import failures by dimensions
Start by confirming decoded width and height. For modern work, correct anything other than 64×64 unless the destination explicitly supports another size. Convert 64×32 legacy files rather than stretching them. Avoid smooth scaling and preserve exact coordinates.
Then confirm the format, alpha, arm-model selection, and base-face coverage. If all local checks pass, the cause may be an account restriction, service outage, launcher behavior, or changing platform policy that a dimension analyzer cannot observe.
Local analyzer limitations
The inputs remain in the browser and are not stored. Because this widget accepts numbers rather than a file, it cannot verify actual encoding, transparency, corrupt bytes, or UV artwork. Use a file checker for a deeper inspection.
SkinEditor.org is independent and not associated with Mojang or Microsoft. Compatibility statements describe common atlas structures, while import requirements should be confirmed for the exact platform and version you use.
Frequently asked questions
What is the best Minecraft skin size?
For a conventional modern skin, use 64×64 PNG unless your target explicitly documents another format.
Is 64×32 still a skin?
Yes, it is the legacy mirrored-limb layout. Convert it to 64×64 for independent modern limbs and layers.
Is 128×128 always supported?
No. HD-style support depends on the launcher, server, mod, or platform.
Do Slim skins have different full dimensions?
No. Classic and Slim modern files are both 64×64.