Crafatar also provides support for 3D renders of Minecraft skins.
Please note that this feature is currently beta!
The head render type returns a render of the skin's head.<%= domain %>/renders/head/uuidThe body render returns a render of the entire skin.<%= domain %>/renders/body/uuid
You can also get the full skin file of a player.
The user's skin is returned, or the default image is served.
You can use the default parameter here as well.<%= domain %>/skins/uuid
A cape endpoint is also available to get the active cape of a user.
The user's cape is returned, otherwise a 404 is returned.
Crafatar supports CORS so you can make AJAX request from within the browser!
Responses come with these HTTP headers, useful for debugging.
Please note that these headers are cached by CloudFlare (CF-Cache-Status: HIT).
The time, in milliseconds, it took Crafatar to process the request.
Details about how the requested image was stored on the server
The internal ID assigned to this request.
If you think something is wrong with your request, please contact us and provide this ID.
We strongly advise you to use UUIDs instead of usernames! UUIDs never change while usernames do.
Looking up players by username has officially been deprecated by Mojang ever since UUIDs were introduced.
@@ -306,19 +306,19 @@
UUIDs may use the blank or dashed format.
Malformed UUIDs are rejected.
Crafatar caches skins for <%= config.caching.local / 60 %> minutes before checking for skin changes.
Images are cached in your browser for <%= config.caching.browser / 60 %> minutes until a new request to Crafatar is made.
When you changed your skin you can try clearing your browser cache to see the change faster.