Convert a player skin into a custom totem texture
This Minecraft skin to totem converter creates a compact 16×16 character-shaped item texture from a local 64×64 player skin. Open a PNG, choose Classic or Slim arms, decide whether outer-layer artwork should be composited, and preview the result at enlarged pixel scale. Download the texture by itself or package it inside a Java resource pack ZIP.
The tool does not fetch usernames or transmit the selected file. Image decoding, UV face extraction, resampling, PNG creation, resource-pack assembly, and download happen in the current browser without an account or database.
How the skin is rearranged
A player skin is a 64×64 texture atlas containing many separate body faces. A totem item uses one small flat image. Copying the entire atlas into the item path would display a tiny grid of disconnected faces rather than a recognizable character.
The converter takes the front of the head, torso, arms, and legs and rearranges them into a sixteen-pixel-square silhouette. The head occupies the upper area, the torso is compressed into the center, arms extend down both sides, and two short legs complete the bottom. Nearest-neighbor sampling keeps hard pixel edges.
This is an original practical remapping, not the game’s default totem artwork and not a claim to reproduce an official 3D player model. Some details must be reduced because an ordinary player front is taller and more detailed than a 16×16 item canvas.
Classic and Slim input
Classic skins use four-pixel-wide source arms, while Slim skins use three-pixel arms. The output silhouette reserves the same compact destination width, but selecting the correct source layout ensures the intended columns are sampled.
If the model is unknown, use the Minecraft skin model detector. A wrong selection may include an unused transparent column or omit artwork at an arm edge. The converter never modifies the original skin.
Outer-layer composition
With outer layers enabled, visible hat, jacket, sleeve, and trouser pixels are alpha-composited over their corresponding front base faces before reduction. This can preserve distinctive hair, hood, jacket, cuff, and shoe details.
The item texture is still flat. It does not generate a raised hat, custom 3D item model, animation, emissive material, multiple player variants, or per-user behavior. Turn overlays off for a simpler base-only result. Check layer placement with the Minecraft skin layer viewer if the preview looks unexpectedly busy.
PNG download
The PNG button downloads totem_of_undying.png at 16×16 pixels with transparency around the character silhouette. It can be inspected or edited in any lossless pixel editor. Do not save it as JPEG because JPEG removes transparency and adds compression artifacts around pixel edges.
The standalone PNG is not installed automatically. To use it in a Java resource pack manually, place it at assets/minecraft/textures/item/totem_of_undying.png inside a pack that is correct for the target release.
Keep a backup of any existing file before replacing it. The custom texture changes the appearance of the item; it does not change survival behavior, activation rules, effects, inventory logic, or server authority.
Java resource pack ZIP
The Java pack download contains three files: pack.mcmeta at the archive root, the generated image as pack.png, and the item texture at assets/minecraft/textures/item/totem_of_undying.png. The ZIP uses relative forward-slash paths and can be inspected with an ordinary archive application.
Java resource pack format numbers change between releases. The numeric input is intentionally editable. Enter the value required by the exact Java version in which the pack will be loaded. The default is only a starting value and is not a promise of compatibility with the newest, snapshot, modded, or future release.
If the game reports that a pack was made for another version, verify the required format number and update the field before downloading again. Do not simply remove pack.mcmeta; Java identifies a pack through that root metadata file.
This pack targets the common Java item texture path. It is not an .mcpack and is not presented as a Bedrock pack. Bedrock packaging, manifest metadata, texture definitions, cache behavior, and import workflow differ. Use the Bedrock skin pack maker for player skin packs, while recognizing that a Bedrock skin pack and an item-texture resource pack solve different tasks.
Installing and testing
Keep the ZIP intact unless the target launcher or workflow specifically requires an extracted folder. Add it through the Java resource pack interface or place it in the correct resourcepacks directory for that installation. Exact folder locations depend on operating system, launcher, and profile.
Enable the pack, load a safe test world, and inspect the totem in inventory, first person, third person, dropped-item, and activation contexts. Other packs can override the same texture depending on pack priority. Move this pack above conflicting packs when its item image does not appear.
If the image appears blurred, confirm the source is the generated 16×16 PNG and that no editor resampled it with smoothing. Texture filtering, shaders, mods, or resource-pack enhancements can change presentation. Test in a clean profile before assuming the generated pixels are wrong.
Design tips for a readable totem
The available canvas is extremely small. Strong contrast between face, hair, clothing, and outline works better than subtle gradients. A distinctive eye color or central clothing mark can survive reduction, while one-pixel source details may disappear.
If the generated result is unclear, edit a copy of the skin in the Minecraft skin editor and simplify the front-facing colors. Alternatively download the totem PNG, adjust the sixteen-pixel result directly, and place that corrected file into a pack. Preserve the original character skin separately.
Limitations
This converter creates one static 2D texture. It does not make a 3D player-shaped totem, custom item model, animated texture metadata, name-dependent variants, CustomModelData configuration, server plugin, behavior pack, or marketplace content. It also does not install or enable the ZIP automatically.
The preview displays enlarged pixels for inspection, not the exact lighting, scaling, rotation, or animation used by every game context. Real testing in the target version remains necessary.
Privacy, security, and content rights
The resource archive is constructed locally from a fixed set of safe relative paths. It contains the generated PNG and plain JSON metadata, not executable code. Inspect the archive before use if it will be shared or combined with another project.
Only convert skins you created or have permission to use. A format conversion does not grant rights to another creator’s character, logo, brand, or likeness. Follow the rules of any server, platform, or distribution site where the pack is shared.
SkinEditor.org is independent and is not associated with Mojang or Microsoft. Minecraft names are used descriptively to identify compatible file layouts.
Frequently asked questions
Is the image exactly 16×16?
Yes. The generated item texture is a transparent 16×16 PNG.
Does the ZIP work on Bedrock?
No. It is structured as a Java resource pack ZIP.
Why must I enter a pack format?
Java uses release-dependent metadata numbers to determine resource-pack compatibility.
Does it create a 3D totem?
No. It replaces the ordinary 2D item texture.
Will it change how the totem works?
No. A resource texture changes appearance, not gameplay behavior.
Can another resource pack hide it?
Yes. A higher-priority pack that replaces the same item texture can override it.