Guides

Short, specific write-ups on the asset problems that come up between drawing a sprite and shipping it in a game.

Find the right grid, extract every frame as a PNG and import the result into your engine.

Nearest neighbour, whole scale factors, and the import settings that undo your work.

Cell size, frame order, padding and the settings each engine needs to read the sheet.

Grid, per-frame timing, transparency — and the limits of the format before you commit to it.

Slice it with AnimatedSprite2D, kill the blur, and know when Godot's slicer gives up.

Sprite Mode, the Sprite Editor's three slice modes, and the import settings that quietly ruin pixel art.

spritesheet vs atlas, frameWidth in pixels, generateFrameNumbers — and why nothing loads over file://.

Four shades, the one setting that decides whether the picture still reads, and where extra colours creep back in.

Four numbers hold the corners still — and the default stretch mode undoes them in all three engines.

It is off by one. Here is what shifts it, how to find where, and the four other failures worth knowing.

Diagnose it in greyscale first. Then the outline colour that is not black, and the three fixes that are not an outline.

Compare the first frame with the last. Whether the error grows tells you which of four things is wrong.

Three causes, one symptom. Whether the seam flickers when the camera moves tells you which.