Spritix dev notes

Look at the sprite at 1x before you export the big sheet

The biggest sprite sheet I can export from my own tool has cells of several hundred pixels each. In a case study on the site, one walk cycle is a 5×5 grid at 960 px per cell: a 4,800 px square PNG for one animation of one character.

That character will be about fifty pixels tall in most games that use it.

I build Spritix, an AI Sprite Sheet Generator. I mention the big numbers because they are seductive. A larger export feels safer, as if you are keeping the option to have more detail. You are not, really. The detail that matters is the detail that survives at the size the player sees.

The 1x test

Before exporting anything, take a single frame and scale it down to its real in-game size. Not a nice preview size, the actual size. Then look at three things:

  • Is the head still distinct from the body?
  • Can you see where the feet are?
  • Is the held item (sword, staff, lantern) still there?

If any of these disappear, a bigger sheet will not bring them back. The engine will scale the big texture down to the same fifty pixels, and the same detail will be lost, only after costing more memory.

The cell is not the character

One thing is easy to get confused about. In the Sprite Sheet Maker every frame sits in a uniform square cell. The cell includes the transparent space around the pose. A jumping character needs room above its head; an attack needs room for the weapon to swing out.

So the visible character is often much smaller than the cell. When sizing a sprite for a game, measure the character, not the cell, and then pick a frame size that leaves the character at the height you want after scaling.

The tool also does not make the visible character the same height in every frame. That is deliberate: a crouch should be lower than a standing pose. But it means you should compare heads and feet across frames, not cell edges.

Silhouette first

When something fails the 1x test, the fix is almost always in the shape, not the pixels:

  • An arm overlapping the torso reads as a blob. A small gap between arm and body reads as an arm.
  • A thin weapon held vertically against the body vanishes. The same weapon held at an angle stays visible.
  • A dark outfit on a dark background disappears no matter how detailed it is. Check the frame on the actual level background, both light and dark areas.

These are old pixel-art lessons. Generating the animation does not make them go away; it just makes it faster to get to the point where you need them.

So what size should you export?

The smallest frame size that passes the 1x test with a little headroom, so the engine scales down slightly rather than up. Frame count is a separate decision: a short idle often needs fewer distinct poses than a fast attack, and more frames do not guarantee better motion.

If the game is pixel art, one more check: decide whether the sprite will be scaled by whole numbers with nearest-neighbour filtering. A frame that looks crisp at 2x can turn soft and uneven at 1.5x. That is a camera and import setting, not something the export can fix, but it changes which frame size makes sense.

Big sheets are useful for some things: a character portrait screen, a promotional GIF, cleaning frames by hand in a pixel editor. For the sprite that walks around the level, the question is not how big you can export. It is how small you can go and still read.


Drafted with AI assistance; reviewed and edited by the author, who builds Spritix.