Generating game sprites with AI

How to go from a one-line idea to a game-ready sprite: choosing the artboard size, writing a prompt the model can actually act on, using a reference to lock style, and expanding a single sprite into reskins, a matching set, or an animation. Every result lands on a real pixel grid you can keep editing in the pixel art editor.

Workflows

Generate your first sprite

  1. 1Open the editor and pick a size in Generate → New: 128, 256, 512, or 1024. 128 is the sweet spot for a single character or prop.
  2. 2Describe the subject, then the view, then the style: "side-view knight with a round shield, dark fantasy, limited palette".
  3. 3Leave density on Quality for a small set of clean results; switch to Quantity when you want many rough options to pick from.
  4. 4Generate, then keep the artboard you like and delete the rest before you start editing.

Build a matching set

  1. 1Generate or import one asset you are happy with — that becomes your style anchor.
  2. 2Select it as the reference, then use Variants to produce siblings that share its palette, outline weight, and footprint.
  3. 3For props and icons, keep the same artboard size across the whole set so nothing is drawn at a different pixel resolution.
  4. 4Save the anchor as a component if you plan to reuse its base across several sprites.

Directional and animated sheets

  1. 1Use Directions to turn one facing into a 4 or 8-direction sheet; tell it which way the source is facing and which way you want the result.
  2. 2Use Animate to add frames — frames share one layer stack, so structure stays consistent between them.
  3. 3Name frame ranges as clips (idle, walk, attack) so the export carries them into your engine.

What makes the difference

Don't ask for a pixel size in the prompt

"16x16 pixel sprite" doesn't shrink the output — the artboard size and brush size decide resolution. Pick the artboard size in the panel instead; the editor warns you if a prompt tries to set a size.

Subject → view → style, in that order

Lead with the thing itself, then the camera (side view, top-down, 3/4), then the aesthetic and palette. Long adjective stacks before the subject dilute it and you get generic art.

A reference beats more words

One reference image locks palette, outline weight, and proportions harder than any prompt. Use a real sprite at a reasonable size — a tiny 16px thumbnail gives the model almost nothing to read.

Quality vs Quantity is a budget, not a quality dial

Both modes render the same sheet size. Quality spends the pixels on fewer, larger cells (better for detailed subjects); Quantity divides them across more cells (better for browsing ideas or simple icons).

Small assets need iconic shapes

At 32px there is no room for fine detail. Ask for one clear silhouette and one or two readable features — "a red potion with a cork and a highlight" — instead of a long list of details that will vanish.

Generate the base, animate afterwards

Get one sprite fully right — palette, silhouette, outline — before adding frames or directions. Fixing style across a whole sheet costs far more than fixing one artboard.

Blocked generations aren't wasted words

If the safety filter blocks a prompt, rephrase the subject or swap the reference rather than retrying the same text.