Compare Classic and Slim arms
The interactive comparison shows the native front-face grid of a base arm. Classic is four pixels wide and twelve pixels high; Slim is three pixels wide and twelve pixels high. Switch between them to see how one missing horizontal column changes the available artwork area and the character silhouette.
Both models use a complete 64×64 modern skin atlas. Slim does not mean a smaller file, shorter arm, lower resolution, or different head. The distinction is concentrated in arm face widths and their UV placement, including matching sleeve overlay faces.
Classic four-pixel arms
Classic provides four columns across the arm front and back. That extra column is valuable for armor, wide sleeves, strong outlines, robots, broad creatures, stripes, and small sleeve symbols. A one-pixel vertical line occupies one quarter of the visible front width.
The broader silhouette resembles the original default-style arm geometry, but it is not restricted to a default character or any identity. Any design can use Classic. Choose it when the artwork needs the fourth column or an existing source already fills the Classic arm rectangles.
Classic side faces remain four pixels deep. Top and bottom faces are four by four. Each arm base is twelve pixels high, while outer sleeve faces occupy corresponding regions on the second layer. Modern left and right arms remain independent.
Slim three-pixel arms
Slim removes one column from the arm front and back, producing a narrower silhouette. One pixel now occupies one third of the visible width. Detailed borders, gradients, and emblems require stronger simplification. Color contrast and selective outlines can work better than framing both sides with dark pixels.
Slim is useful for narrow sleeves, lightweight characters, compact human designs, and skins already authored for three-pixel geometry. The name describes geometry only and does not determine gender, age, or theme.
Although the front and back are three pixels wide, the arm still needs side, top, bottom, inner, and outer artwork in the correct Slim UV rectangles. A front-only edit remains incomplete.
What happens when the wrong model is selected?
Displaying Classic artwork as Slim can discard or misplace the outer arm column. Sleeve edges, outlines, hands, and logos may be clipped. Displaying Slim artwork as Classic creates an extra visible column that the artist did not design for; it can appear transparent or contain unexpected atlas pixels.
The PNG dimensions cannot always tell an importer which model was intended. Many profile and launcher interfaces therefore ask separately. Select the same model used during editing. If a skin looks correct everywhere except the arms, model mismatch is one of the first things to check.
UV coordinates and why resizing is wrong
Classic-to-Slim conversion is not a whole-image scale operation. Head, torso, legs, and most atlas space must stay fixed. Only arm faces and their overlays need face-aware remapping. Smoothly shrinking the entire 64×64 canvas corrupts every coordinate and blends pixel colors.
A dedicated converter processes each arm face independently. When converting four columns to three, one column must be discarded or merged according to a policy. Good tools report discarded opaque pixels because an automatic choice can remove meaningful detail. Converting Slim to Classic requires deciding how to create the new column, for example by duplicating an edge or leaving transparency.
Choosing a model for a new skin
Start from silhouette. Classic feels broader and supports blocky armor or wide garment shapes. Slim feels narrower and can make arms visually lighter. Then consider artwork capacity. If a repeating sleeve motif requires four columns, Classic avoids unnecessary compression. If the design is mostly solid color with a highlight, Slim may be sufficient.
Preview both with the intended torso and clothing. The arm-to-body relationship matters more than viewing an arm alone. Test at normal gameplay distance, because the one-pixel difference is clearer in silhouette than in a massively enlarged editor.
Outer sleeves and asymmetry
Both models support separate left and right sleeve overlays. Use overlays for cuffs, rolled fabric, bracelets, armor plates, raised stripes, or depth. Leave unused outer pixels transparent rather than duplicating the entire base arm.
Independent limbs permit asymmetric gloves, sleeve badges, scars, mechanical parts, or lighting. Mirroring can accelerate a uniform design, but a UV-aware mirror must respect face orientation. Text and directional symbols deserve special inspection on both arms.
Checking an existing skin
Open the file in a viewer that offers both models. Hide and show outer layers, rotate the arms, and watch the outer vertical edge. The correct model generally produces continuous sleeve faces without an unexplained gap or clipped stripe.
Inspect source dimensions as well. A legacy 64×32 skin uses mirrored limb behavior and may require modernization before a meaningful independent comparison. A correct 64×64 file can still be ambiguous if its arm edges are fully transparent.
Local comparison limitations
The widget is an educational pixel grid, not a file detector. It does not upload or analyze a skin, and it cannot infer intent from transparent columns. Use the skin viewer and model converter for actual files.
SkinEditor.org is independent and not associated with Mojang or Microsoft. Platform labels and import interfaces can change; select geometry according to the current destination.
Frequently asked questions
Is Classic better than Slim?
No. They are different silhouettes and UV widths. The better choice is the one matching the intended design.
Are both files 64×64?
Yes. Modern Classic and Slim skins share the same full canvas dimensions.
Can I switch after finishing?
Yes, but use a model-aware converter and inspect lost or generated arm columns.
Does Slim have shorter arms?
No. Both base arms are twelve pixels high; Slim changes width.