Skins and capes

Change Skin and Change Cape, on the accounts page, change what your accounts wear. Upload one skin file and it goes on every Java and Bedrock account you ticked, or pick a cape and every Java account that owns it puts it on, without signing in to each account yourself.

On a Java account, MinecraftAFK makes each change on the account's own Minecraft profile, signed in as that account, so it's the skin and cape the account really has, not a setting of ours, and nothing about either is stored on MinecraftAFK. A Bedrock account has no such profile, so its skin works another way: see Bedrock accounts. Both work on every plan.

Which accounts

A Java account can change its skin and its cape, and a Bedrock account its skin. An offline (cracked) account can change neither, since it has no Minecraft profile behind it. In the accounts list, the Java accounts are the rows with a grass block, and the Bedrock accounts the rows with a bedrock block.

• An offline account's ⋮ menu has no Change skin or Change cape, and a Bedrock account's has Change skin only.
• If you tick a mix, each dialog changes the accounts it can and says what it leaves out, such as "2 of the selected accounts are offline accounts, so they keep their skins."
• Change Skin is greyed out if nothing you ticked is a Java or Bedrock account, and Change Cape if nothing you ticked is a Java account. Hover one, or tap it on a phone or tablet, to see why.

Bedrock accounts

Bedrock keeps no skin on the account for anyone to change: each time a Bedrock player joins a server, their game sends the skin it's wearing. A bot does the same, and until you pick a skin it sends one of Minecraft's default skins, chosen for that account. So for a Bedrock account, MinecraftAFK keeps the skin file you upload, and the bot sends it each time it joins.

• The bot wears the new skin from its next connect. A bot that's online keeps the skin it has until it reconnects.
• Only the bot wears it. When you play the account yourself on a phone, console or PC, you wear the skin you have there, and nothing you pick here changes it.
• The dashboard doesn't show it: see When the new skin shows.
• The skin file stays on MinecraftAFK until you reset the skin or delete the account.

The dialog says which of the accounts are Bedrock ones, such as "These are Bedrock accounts, so only their bots wear this skin, from their next connect."

Change the skin

1. Visit minecraftafk.com/dashboard/accounts/.
2. Tick the accounts to change. The box at the top of that column ticks every account the list shows.
3. Click Change Skin, at the top beside Delete 3 Selected (for three accounts).
4. Drop the skin file on the box, or click the box to pick one.
5. Check the preview and the Arms, then click Change 3 skins.

For one account, pick Change skin in its row's ⋮ menu instead. A right-click on the row opens the same menu.

Once the file is in, the dialog shows its name, whether it's 64x64 or 64x32, the old layout, and the skin from the front and the back. Choose another file swaps it. Each Java account gets the file exactly as it is, and the preview only shows how the game will draw it. A Bedrock bot is sent the skin as the preview shows it.

When every account has the new skin, the dialog closes and a message says so, such as "Changed the skin on 3 accounts". If any of them are Bedrock accounts, the message adds "Bedrock bots change at their next connect."

The skin file

A skin is a PNG of 64x64 pixels, or 64x32 in the old layout, and no more than 64 KB. The dialog checks the file as soon as you pick it, and if something is wrong it says what under the box:

The preview draws the skin the way the game does. See-through pixels on the skin's base layer are drawn solid, as they are in game, and an old 64x32 skin, which has no left arm or leg of its own, wears mirrored copies of the right ones.

For a Java account, Mojang has the last word on a skin. If it refuses one, its reason is listed beside each account it refused: see If an account fails.

Classic or Slim

Arms sets how wide the arms are: Classic, wide arms like Steve, or Slim, thin arms like Alex. Minecraft keeps the arm width beside the skin rather than in the file, so pick the one the skin was drawn for. The preview changes with it.

The dialog starts on a guess from the file: a skin with see-through pixels where only a wide arm draws was made for slim arms, and any other for classic. It's only a starting point, so check it. An old 64x32 skin only has classic arms, so Arms stays on Classic.

Reset to the default skin

Reset to default skin, at the bottom left of the skin dialog, puts every account in it back on its default skin: the one Minecraft picks for that account, such as Steve or Alex. A Bedrock bot goes back to the default skin it wore before you picked one, from its next connect. It needs no file, and it starts as soon as you click it, without asking again. The line under the dialog's title names the accounts it's for.

Change the cape

An account can only wear capes it owns, and which capes those are differs from one account to the next. So the cape dialog checks first.

1. Visit minecraftafk.com/dashboard/accounts/.
2. Tick the accounts to change, and click Change Cape, beside Change Skin. For one account, pick Change cape in its row's ⋮ menu.
3. Wait while the dialog checks which capes the accounts own: Checking which capes they own: 2 of 5.
4. Pick a cape, or No cape to take capes off.
5. Click the button, which says what it will do, such as Wear Migrator on 3 accounts or Remove 2 capes.

No cape comes first, then every cape at least one of the accounts owns, the most owned first. Each tile shows the cape and how many of the accounts own it, All 5 own it or 3 of 5 own it, or for a single account whether it's Worn now or just Owned. If none of the accounts own a cape, No cape is the only choice.

Capes are matched by name, so picking Migrator puts every account that owns a Migrator cape in its own. Once you pick, a note says which accounts the pick leaves alone, so the count on the button adds up:

• An account that already wears it is skipped, and nothing is sent for it.
• An account that doesn't own it keeps what it wears now.

Taking a cape off doesn't give it up. The account still owns it, and the dialog offers it again next time.

An account whose capes can't be checked, such as one whose sign-in has to be renewed, is left out of the change rather than guessed at. A warning lists each one with the reason, under a title such as "1 account could not be checked and is left out". To check again, close the dialog and open it once more.

When it's done, the dialog closes and a message such as "3 accounts wear Migrator" says how it went.

While it runs

Each account is its own request, made as that account, and the dialog sends them four at a time. A progress bar counts them: Changing skins 6 of 10, Resetting skins 6 of 10 or Changing capes 6 of 10. The dialog can't be closed until every account has an answer.

Your ticks stay as they were, so you can open Change Cape for the same accounts straight after changing their skins.

If an account fails

One account failing never stops the rest. When some aren't changed, the dialog stays open and lists each one with its own reason, under a title such as "2 of 10 accounts were not changed". Reasons you may see:

• The account's sign-in has to be renewed. Its Account Access reads Access Lost: Re-authenticate. Close the dialog, re-authenticate it, and change it again.
• Mojang's rate limit. Wait a little, then press Try again.
• Mojang refused the skin, with its own reason why.

Try again sends the same change to just the accounts that failed. Close leaves them as they are.

When the new skin shows

In the browser you made the change from, every head on the dashboard shows the new skin as soon as the change is done, and still does after a reload. So do the bot's own hand and body in the POV, though the POV draws them with Classic arms even for a Slim skin.

Other browsers and devices keep the head they had already loaded, so there the new skin can take up to a day to show.

A skin you pick for a Bedrock account doesn't show on the dashboard at all, because heads and the bot in the POV are drawn from Java profiles. The players on the server see it once the bot has reconnected.

A head shows a default skin, Steve or Alex, while its real one is still being fetched, as it can for an account you've just added. The browser keeps that default for five minutes at most, so a page loaded after that asks again.

A cape shows nowhere else on the dashboard: heads have none, and the POV doesn't draw capes.