How SkinsRestorer works
Understand how SkinsRestorer requests and applies skin data.
Read the storage page first. It explains the skin data used on this page.
This page explains how SkinsRestorer gets and applies skins.
Recap
SkinsRestorer gets signed player skin data from Mojang. The Minecraft client accepts only skin data that Mojang signed.
This rule also keeps official capes linked to approved accounts.
Signed-skin restrictions apply to players, not Minecraft heads. Citizens NPCs also use the player skin rules.
SkinsRestorer gets skins in two ways:
- It gets the signed skin data of a Minecraft player.
- It sends a custom PNG to an account service that gets signed skin data.
SkinsRestorer uses MineSkin for the second method.
Paid MineSkin plans above Lite include higher limits and more features. Visit the
MineSkin API keys page
and use coupon code SKINSRESTORER10.
The code gives you 10% off the first three months.
SkinsRestorer does not receive a commission.
Skin request flow
This diagram shows a skin request by player name:
SkinsRestorer API endpoints
SkinsRestorer uses these endpoints to cache and distribute skin data:
eclipse.skinsrestorer.net- Handles UUID lookups and profile dataaxolotl.skinsrestorer.net- Handles MineSkin URL decryptioncool-skins.skinsrestorer.net- Provides recommended/featured skins
These endpoints provide a cache between your server and Mojang. The cache reduces Mojang API requests and rate-limit errors.
It can also provide cached skin data when Mojang is slow or unavailable.
How is this guide?
Last updated on