Minecraft mob renderer

12 mobs, a body or a head, every pose and every variant, from one URL. The same renderer as the skin API, pointed at something other than a player.

creeper

zombie

skeleton

spider

The URL

A mob has no UUID and no profile, so there is nothing to look up: the name in the path is the whole subject, and the image is produced from the address alone.

https://skinrender.dev/render/mob/creeper/body
https://skinrender.dev/render/mob/creeper/head

The second segment is the render type. There are two: body, the whole model, and head, the head alone as a square for icons and lists. Either may end in .png where a URL has to look like an image file, and /render/mob/creeper on its own redirects to the body render, the same shorthand a player render has.

Everything after the ? is the parameter set from the skin renderer, unchanged: size, bg, yaw, pitch, fov, zoom, crop, margin, shading, shadow, download and the rest all mean here what they mean there. The mob endpoint reference has the full list with the two that are specific to mobs.

Every mob

12 mobs are in the renderer today, each with a page of live renders of every pose and every variant, and the URL that produced each image.

• 
  Creeper

  The one that hisses. Four stubby legs, no arms, and that face.

• 
  Zombie

  Arms out, knees stiff and the shirt still on: the mob everyone meets first.

• 
  Skeleton

  Bare bones on two thin legs, standing as if the bow were still in its hands.

• 
  Spider

  Eight legs, eight eyes and a body low enough to fit under a slab.

• 
  Enderman

  Nearly three blocks of black limbs with two eyes burning at the top.

• 
  Slime

  A cube of translucent green jelly with a smaller, sadder cube set inside it.

• 
  Pig

  Snout, four trotters and an optional saddle. The friendliest render on the site.

• 
  Cow

  Patched hide, stubby horns and a heavy walk. The mooshroom variant comes with spots.

• 
  Sheep

  A fleece on four legs, dyed or freshly sheared, with a face poking out of the wool.

• 
  Chicken

  Orange beak, red wattle and two wings that never quite get it off the ground.

• 
  Wolf

  Grey fur, white muzzle and a tail that tells you exactly how the meeting is going.

• 
  Villager

  Brown robe, folded arms and the biggest nose in the game. Hmm.

The gallery is the same list without the surrounding prose. New mobs appear there the moment they are added to the renderer; nothing on this page is written by hand per mob.

Poses and variants

Two parameters belong to the mob rather than to the API, because their accepted values depend on which mob you are rendering.

pose= is the whole posing interface. Every mob answers to default and walk, so a URL written for one works when you point it at another, and beyond those two the names are the mob's own — creeper takes default, walk, hiss, look. There are no per-joint parameters as there are for players: a player rig is always the same six joints, while mobs have four legs, or wings, or neither.

https://skinrender.dev/render/mob/creeper/body?pose=hiss

variant= picks a colour or breed of the same model, and the first in a mob's list is what you get without it — creeper has normal and charged. A mob with one look has no variants at all, and asking for one then is an error rather than a silent fallback, because a picture that looks right and is wrong is worse than a 400.

https://skinrender.dev/render/mob/creeper/body?variant=charged

The cycling poses — the walk, and whatever else a given mob animates — take frame=0..1 to pick the phase, with fit=false so the camera does not rescale between frames. Animation covers turning that into something that moves.

Side profile and angles

The camera is the player renderer's camera. Each mob has a three-quarter view it defaults to, and yaw and pitch move it anywhere else: yaw=90&pitch=0 is a flat side profile, yaw=0 the front, yaw=180 the back, and every angle combines with every pose and variant.

https://skinrender.dev/render/mob/creeper/body?yaw=90&pitch=0

Each mob's own page has its side, front and back views, and a table of the model's dimensions — the whole mob and every part, in pixels and in blocks — measured from the same geometry the renderer draws.

Size, background and crop

size is the height in pixels, from 8 to 1024. The width follows the mob's own proportions — a tall mob and a wide one do not share an aspect ratio — so size=512 on one is not the same canvas as on another. Pass width and height together when you need a fixed box, and the mob is centred in it.

The background is transparent unless you set bg, which takes a hex colour with an optional alpha (bg=1e1e2e, bg=00000080). crop=true trims the transparent border so the PNG is exactly as big as the model, which is what you want in a tight layout; margin sets how much room is left around it when you do not crop.

https://skinrender.dev/render/mob/creeper/head?size=128
https://skinrender.dev/render/mob/creeper/body?crop=true
https://skinrender.dev/render/mob/creeper/body?size=256&bg=1e1e2e&shadow=true

Putting one on a page

It is an <img> tag. Give it the width and height you asked for so the layout does not shift while it loads, and let the browser cache do the rest.

<img src="https://skinrender.dev/render/mob/creeper/head?size=128"
     width="128" height="128" alt="A Minecraft creeper"
     loading="lazy" decoding="async">

const mobs = ["creeper","zombie","skeleton","spider","enderman","slime","pig","cow","sheep","chicken","wolf","villager"];
list.innerHTML = mobs.map((mob) =>
  `<img src="https://skinrender.dev/render/mob/${mob}/head?size=64" width="64" height="64" alt="${mob}" loading="lazy">`
).join("");

Every response carries Access-Control-Allow-Origin: *, so fetching one into a canvas or a bot works from any origin, and Cache-Control: public, max-age=31536000, immutable, because a mob render depends on nothing but its URL and can never go stale. Store the URL rather than the file.

When the name is wrong

An unknown mob is a 404 whose body lists every mob that does exist, so a typo tells you what you meant. A pose or a variant the mob does not have is a 400 naming the ones it does. Errors are plain text with a real status code, never a PNG of an error message.

There is no fallback and there should not be one: a player render draws Steve rather than break an <img> because a missing skin is normal, whereas a mob name is either in the renderer or misspelt. The endpoint reference has the exact wording.