Expand three-pixel arms to four-pixel arms
This Slim to Classic skin converter transforms the arm UV regions of a modern 64×64 Minecraft skin from three-pixel-wide Slim faces to four-pixel-wide Classic faces. Select a local PNG, choose how the new face column should be created, compare the source and result on their intended models, and download a separate Classic PNG.
The converter does not resize the complete canvas. Both input and output remain 64×64. It changes mapped arm pixels because Classic geometry requires one more horizontal column on the front and back arm faces. The source file remains unchanged and no image upload API is used.
Why a real conversion is necessary
Switching a model selector in a viewer changes preview geometry only. It does not rearrange atlas pixels. A Slim sleeve shown on Classic arms can expose an undefined column, stretch the visual rhythm, or place side pixels where a new front or back edge is expected.
The converter performs an explicit UV transformation. It moves mapped pixels into the Classic layout and creates the additional columns according to the selected expansion strategy. This makes the operation reviewable rather than hiding an assumption.
Duplicate-edge strategy
The default expansion strategy duplicates a neighboring edge column into the new Classic column. This generally produces a continuous color boundary and is useful for flat sleeves, skin tones, gloves, and simple shading.
Duplication is an approximation. A logo, stripe, asymmetric highlight, letter, or detailed hand may not make artistic sense when one edge is repeated. Inspect all base and outer arm faces and repair the result manually when necessary.
Transparent-column strategy
The alternative leaves the generated column transparent. This clearly exposes where new artwork is needed and avoids inventing an opaque color. It can be useful when you plan to paint the Classic result immediately.
Transparent pixels on an arm base layer may create visible holes, so this strategy is not a finished safe output by itself. Open the result in the editor and intentionally fill required base pixels. Transparency on unused overlay areas can be valid.
Choosing the changed edge
You can choose whether the first or last face edge supplies the duplicated column. The better choice depends on the artwork. A sleeve whose seam sits on one side may look more natural when the opposite edge is expanded. A highlight running along the outer arm may need a different decision than a uniform fabric color.
Compare both settings before download. The conversion always recalculates from the preserved source pixels, so changing the option does not repeatedly transform an already transformed result.
Before-and-after previews
The source preview uses Slim arms and the result preview uses Classic arms. Rotate both to matching front, back, left, and right views. Check shoulders, sleeves, hands, inner arms, top and bottom faces, and the outer layer.
Pay particular attention to one-pixel lines that cross from front to side faces. An expanded front may shift the perceived seam even when the operation is technically consistent. The report counts generated opaque edge pixels so the scope of the approximation is visible.
Input requirements
The converter requires an exact 64×64 PNG. Legacy 64×32 skins need the legacy converter first. A 128×128 HD texture needs a deliberate size workflow before this standard model converter can process it.
Confirm that the source is actually Slim. Transparent Classic edge columns can sometimes resemble a Slim file to automatic detectors. Use the model viewer, inspect the arm regions, and rely on known design intent rather than treating heuristic detection as authoritative metadata.
Review after conversion
Download under a new filename and preserve the original. Open the result in the 2D editor to refine the generated column. Then run the checker for base-layer holes, visible pixels outside mapped faces, model likelihood, overlay use, and format compatibility.
Test the result in the intended game workflow. A local UV conversion cannot control launcher state, account permissions, server behavior, moderation, or every client rendering detail.
Local-first privacy
The PNG is validated, decoded, transformed, previewed, and exported in the browser. SkinEditor.org has no account, public gallery, cloud project database, subscription, or credit balance. Browser state is not backup storage, so keep the original and converted files.
Only convert artwork you own or have permission to adapt. SkinEditor.org is independent and is not affiliated with Mojang or Microsoft.
A dependable workflow
Preserve the Slim source, verify its dimensions and model, select the file, compare duplicate and transparent strategies, choose the edge that best matches the design, and rotate both previews under identical settings. Download the Classic result, repair generated areas, run the checker, and test in the destination client.
Frequently asked questions
Does this make the entire image wider?
No. The atlas stays 64×64; only mapped arm UV regions are rearranged and expanded.
Is duplicating an edge lossless?
No. The new Classic column did not exist in the Slim source. Duplication is a visible, reviewable approximation.
Can I leave the new column transparent?
Yes, but transparent base-arm pixels may create holes and should be intentionally repaired before use.
Can I convert back to Slim?
Yes, use the direction selector or the Classic-to-Slim page. Narrowing may discard opaque edge pixels, so preserve both source files.