Minecraft Player Lookup

Minecraft Player Lookup: usernames to UUIDs and back, with skins and capes

Paste Minecraft Java usernames and you get each player's UUID in both forms, with their skin, cape and arm model; paste UUIDs and you get the current usernames back. Every row is looked up from Mojang when you run it, so a name is the one the account holds today. What it cannot give you is name history: Mojang withdrew it in 2022, and there is no nameHistory field here pretending otherwise.

🔍 What Minecraft Player Lookup does

Usernames come back in the account's real capitalisation, so philza returns the spelling the player chose. Names are looked up ten at a time and UUIDs one by one, so a long UUID list runs slower than the same number of names. If you can choose the direction, run names.

Duplicates collapse before anything is looked up, and across both lists: a username in one box and the same player's UUID in the other make one row, charged once. Several names on one line are fine if commas or spaces split them, since a Minecraft name can contain neither.

The skin lookup is a second step for every player. Switch it off when all you need is a name-to-UUID map for a whitelist or a plugin config, and the run finishes in a fraction of the time.

skinTextureId is the hash at the end of the skin URL. Two accounts wearing the same skin share it, which is how you group them. Mojang serves the texture URLs over plain http, and they are passed through unchanged.

Close to its time limit, a run stops looking things up. Players it had found but not yet fetched skins for arrive without them, free of charge, instead of the run being killed mid-list.

📥 What you give it

{
  "usernames": ["jeb_", "Dinnerbone", "Dream"],
  "uuids": ["069a79f4-44e9-4726-a5be-fca90e38aaf5"],
  "includeTextures": true,
  "maxItems": 100
}

📤 What you get back

A real row from a real run on 30 September 2026:

{
  "ok": true,
  "username": "jeb_",
  "uuid": "853c80ef3c3749fdaa49938b674adae6",
  "uuidDashed": "853c80ef-3c37-49fd-aa49-938b674adae6",
  "hasCustomSkin": true,
  "skinUrl": "http://textures.minecraft.net/texture/7fd9ba42a7c81eeea22f1524271ae85a8e045ce0af5a6ae16c6406ae917e68b5",
  "skinTextureId": "7fd9ba42a7c81eeea22f1524271ae85a8e045ce0af5a6ae16c6406ae917e68b5",
  "skinModel": "classic",
  "hasCape": true,
  "capeUrl": "http://textures.minecraft.net/texture/9e507afc56359978a3eb3e32367042b853cddd0995d17d0da995662913fb00f7",
  "capeTextureId": "9e507afc56359978a3eb3e32367042b853cddd0995d17d0da995662913fb00f7",
  "texturesStatus": "ok",
  "texturesTimestamp": "2026-09-30T02:31:10.009Z",
  "textureSignature": null,
  "queriedBy": "username",
  "queriedValue": "jeb_",
  "scrapedAt": "2026-09-30T02:31:10.104Z"
}

🧾 Reading the output

ok is not the filter it looks like. Real rows say ok: true, but so does the free sample row, and so do the rows where the skin lookup failed.

After 50 problem rows, the rest roll into one summary row per code, so your real results are not buried. A 300-name test list with 272 unknown names came back as 79 rows: 28 players, 50 problem rows and one summary.

To keep only real players, drop every row carrying _sample or _diagnostic.

▶️ How to run it

1. Open Minecraft Player Lookup and click Try for free. 2. Paste usernames into Usernames, UUIDs into UUIDs, or both. 3. Untick Look up skin and cape if names and UUIDs are all you need. 4. Set Maximum players. 5. Click Start, then download the dataset as JSON, CSV or Excel, or read it from the API.

💰 How much does it cost?

$0.40 per 1,000 players, flat on every Apify plan, with or without skins.

Not charged: the sample row, every problem row (invalid input, unknown names, lookups Mojang did not answer) and a player whose skin you asked for but did not get. A player you listed twice, by name and by UUID, is charged once.

💡 What people use it for

• Turning the names in a server whitelist or a plugin config into UUIDs, with the skin lookup off.
• Refreshing the names on a leaderboard that stores players by UUID. Names change; UUIDs do not.
• Pulling skin and cape URLs to draw player heads on a website or in a Discord bot.
• Finding every account on a list that wears the same skin, by grouping on skinTextureId.

🚧 What it does not do

• No name history. Mojang withdrew it in 2022 and nothing replaced it.
• Java accounts only. A Bedrock gamertag is looked up as if it were a Java name, so if a Java

player happens to hold the same name, you get that Java player, not the Bedrock one.

• No offline-mode UUIDs. A server in offline mode makes up its own ids. Mojang has never heard of

them, so they come back as a free UUID_NOT_FOUND.

• No server data. It looks up players, not servers.
• No skin images. You get the URL and the texture id; download the PNG yourself.
• No ban or account status. Mojang does not publish it.
• No promise that a huge list comes back whole. A very long list can return some RATE_LIMITED

rows. Re-run just those, or split the list across runs.

🧭 Which gaming scraper do you need?

❓ Questions people ask

How do I get a Minecraft UUID from a username? Put the name in Usernames and run it. uuid is the undashed form and uuidDashed the standard one; every row has both.

Can I get a username from a UUID? Yes. Put it in UUIDs, with or without dashes.

Can I get a player's old usernames? No. Mojang removed name history in September 2022, so Mojang no longer gives it to anyone.

How do I tell an Alex skin from a Steve skin? skinModel is slim for three-pixel arms and classic for four. When hasCustomSkin is false, the account never uploaded one and the game picks a default.

Do I need a Mojang API key or a Minecraft account? No. There is nothing to sign up for.

Is the data live? Yes. Every row is looked up from Mojang at run time.

🆘 If something breaks

Open the Issues tab on the actor page. Send the run ID and a few of the names or UUIDs that went wrong, with their errorCode.