Skins you upload are read and packaged here in your browser; this page makes no network requests with your files. The only outside call is optional: loading a skin by username contacts the public service mc-heads.net using only the name you type.
Each skin gets a name-tag trigger. In game, rename an armor stand to that exact text and it becomes this skin.
Uses the public mc-heads.net service to fetch the player's current skin.
A named armor stand pack swaps the look of a Minecraft Bedrock armor stand for a custom player skin, triggered by the name you give the stand. Add a name-tag trigger and a skin for each entry, build one resource pack, and load it like any other. It all happens in your browser, so uploaded skins never leave your device and there is no watermark.
The pack overrides the armor stand entity and its render controller. A render controller matches the stand's name with query.is_name_any and, on a match, swaps the stand's model to the standard player geometry and its texture to your skin. Any stand with no name, or a name you did not add, keeps its normal vanilla look, so the pack only changes the stands you choose.
Add each skin by dropping in a 64x64 or legacy 64x32 PNG, or by loading a skin from a Minecraft username. The tool guesses classic or slim arms and lets you switch the model per skin, names the pack with the same section-sign color codes Minecraft uses, and gives you a name list so you and your players know exactly what to type on a name tag.
Import the .mcpack by double-clicking it, then activate the pack on your world or server under Resource Packs. The custom skins only render once the pack is active.
Place an armor stand, then rename it: set a name tag's text on an anvil and use it on the stand, or rename it however your world allows. Use the exact trigger name from your pack and the stand renders as that player skin for everyone who has the pack active, with no command blocks. This is a Bedrock Edition tool; Java uses a different entity system and is out of scope.
Build a resource pack that overrides the armor stand entity. This tool does that: you add a name-tag trigger and a skin for each entry, and it produces a .mcpack. With the pack active, any armor stand renamed to one of your trigger names renders as the matching player skin instead of a plain stand.
Place an armor stand, then rename it. Put a name tag and the armor stand on an anvil or use a name tag on an anvil to set the text, then right-click the stand with the named tag. Use the exact trigger name from your pack and the stand switches to that player skin. Matching is case-insensitive in practice.
Yes, everyone who has the pack active sees them, and no command blocks are needed. The pack changes how the armor stand entity is drawn on each client, so players running the pack all see the named stands as skins. Players without the pack see normal vanilla armor stands.
No, this is a Bedrock Edition tool. It works by overriding the Bedrock armor stand client entity and render controller, which Java Edition does not use. Java handles entity models differently, so a Bedrock pack will not load there. Java support is out of scope for this version.
Upload a standard 64x64 skin PNG, or a legacy 64x32 skin, which is converted automatically. The tool reads the skin's arms to guess classic (Steve, 4px) or slim (Alex, 3px) and you can switch the model per skin. You can also load a skin straight from a Minecraft username.
Yes. Uploaded skins are read and packaged entirely in your browser, so they never leave your device and there is no watermark. The only outside request is optional: loading a skin by username contacts the public mc-heads.net service using only the name you type.
Make a totem next, or browse more Minecraft tools:
