Minecraft Skin Viewer
Enter a Minecraft Java Edition username to view their skin renders. Shows full body, head, and avatar using the Crafatar rendering service.
Embed This Tool
Put the skin viewer on your own site or server wiki.
<iframe src="https://tools.astroworldmc.com/embed/skin-viewer" width="700" height="600" frameborder="0" style="border:none;border-radius:12px;" loading="lazy" title="Skin Viewer"></iframe>
How to view a Minecraft skin
Enter the username
A Java Edition name, which is resolved to the account UUID before anything is rendered.
Read the renders
Full body, head and avatar are drawn through the Crafatar service, with the hat layer included.
Download the file
The download hands you the skin file itself, at the size the game stores it in.
Mind a name change
The renders follow the UUID, so an old name returns nothing once the account is wearing a new one.
How It Works
View any player skin in 3D from any angle.
Skins drawn by crafatar.com from the Mojang UUIDPage updated
How to Use the Minecraft Skin Viewer
Enter any Minecraft Java Edition username in the search field and click "View Skin" or press Enter. The tool looks up the player UUID through the official Mojang API and then fetches skin renders from Crafatar, a free and open-source Minecraft avatar service. You will see three different render styles: a full body 3D render showing the entire skin, an isometric head render for profile pictures, and a flat face avatar commonly used for forums and chat plugins.
The UUID displayed below the username is the unique identifier Mojang assigns to every Minecraft account. This UUID stays the same even when a player changes their username. Server administrators often need UUIDs for whitelist files, permission plugins, and ban lists. The tool formats the UUID with dashes in the standard 8-4-4-4-12 pattern that most plugins expect. That is the same UUID a whitelist entry needs, so a whole list of names can go through the whitelist manager and come back as whitelist.json.
Click "Download Skin File" to get the raw 64x64 PNG skin texture. This file can be uploaded to the Minecraft launcher to apply the skin to your own account, or used in resource packs and server plugins. All skin renders include the overlay layer, showing hats, jackets, and other second-layer details that players often customize.
Common Use Cases
Server owners use skin viewers to verify player identities and check for inappropriate skins before granting whitelist access. Content creators grab skin renders for thumbnails, video overlays, and social media posts. Developers building Minecraft-related websites integrate skin renders into their user profiles and leaderboards using the same Crafatar API endpoints this tool uses.
The viewer is also useful for finding your own UUID when setting up a new server, troubleshooting skin display issues, or simply checking what another player looks like before joining their server. Since Crafatar caches skins, recently changed skins may take a few minutes to update in the renders. The UUID under a skin is the one the UUID lookup resolves from a name, and it is also the key LuckPerms files a player under, which the permissions calculator writes the nodes for.
The Same Three Renders As Links
Every image on this page is an address you can use yourself. Crafatar serves the body under /renders/body/, the isometric head under /renders/head/, the flat avatar under /avatars/ and the raw texture under /skins/, each one taking the UUID with the dashes stripped out rather than the 8-4-4-4-12 form a plugin expects. The overlay flag keeps the hat and jacket layer on, and scale or size decides how large the image comes back. Point an image tag at one of those and it stays current on its own, because the render is drawn when the request lands.
The Same Face On A Block
A player head in game carries a profile rather than a picture, which is why a head placed years ago still shows the face its owner wears today. Handing one out is a give command with that profile attached, the kind the command generator assembles, and it is worth knowing the difference: a head tied to a profile follows the account, while a head that stores the texture itself is frozen at the moment it was made.
How a Minecraft skin file is built
| Size | 64 by 64 pixels since Java 1.8. The old 64 by 32 layout only held one arm and one leg and mirrored them. |
|---|---|
| Two models | Classic has 4 pixel wide arms, slim has 3. The model is a property of the account, not of the image, so the same file looks different on each. |
| Two layers | An inner body layer and an outer overlay for hats, jackets and sleeves. Only the overlay is meant to carry transparency. |
| Cape | A separate texture that is not part of the skin file and cannot be uploaded, only granted. |
| Where it comes from | The skin is fetched from the account profile, so this viewer shows whatever the player is wearing right now. |
| Head | The 8 by 8 face used for avatars is one square of the same file, which is why an avatar and the model can never disagree. |
Two outside services do the work: Mojang turns the name into a UUID, and crafatar.com draws the body, the head and the avatar from the skin belonging to that UUID. Nothing about the player is kept on our side.
Frequently Asked Questions
Questions about skins
How do I tell classic from slim?
Count the pixels across the arm. Four is classic, three is slim. If a skin drawn for one model is worn on the other the arms come out too wide or a column of the sleeve goes missing.
Why is part of my skin invisible?
Transparent pixels in the inner layer. Transparency belongs in the outer overlay, and where the inner layer is empty the model has nothing to draw.
Why does the viewer still show my old skin?
Profile textures are cached on Mojang's side and again by the client. A change can take a few minutes to travel, and reloading this page sooner just fetches the same cached answer.
Can I view a Bedrock player's skin?
No. Bedrock accounts are not in the Mojang profile system this viewer reads, and their skins are not served from a public texture URL.
