AI Sprite Sheet Generator

An AI sprite sheet maker removes the slowest part of 2D character work: drawing and hand-placing every frame. With spritesgen you describe the character — class, silhouette, palette, weapon, and view angle — and the model returns a coherent set of poses. The pipeline then nudges each frame onto a shared cell so the feet, hips, and shoulders stay locked to one baseline. That single-cell alignment is what stops the jitter you get when frames are cropped and re-centred by eye.

Because every frame is generated against one reference, outfit details, outline weight, and colour ramps stay consistent from the first pose to the last. You get an idle, a walk, or a four-direction set without the costume quietly changing between sheets. When a pose drifts, you regenerate just that frame instead of the whole set, which keeps credits and review time down.

The result is not a flat image you then have to cut apart. You receive a packed alpha PNG atlas plus a manifest that records every frame as an absolute rectangle. Drop it into your project and the sprite already animates at the frame rate you chose.

Text to sprite sheet used to mean generating a strip, exporting it, opening a second tool, and dragging grid lines until the cells finally lined up. spritesgen folds those steps into one run. You type what you want — for example, a 32×32 slime with two bounce frames on a transparent background — and the system returns a sheet whose cell size, padding, and row layout match that request.

Frame count is a parameter, not a guess. Ask for 4, 8, or 32 frames and the generator distributes the motion across exactly that many cells, so the animation speed stays predictable once it is in-engine. You can also pin pixels-per-unit and an anchor so a 32-pixel character occupies the same world height as the rest of your art.

If you already have a look you like, seed the run with a single image and let the generator expand it into a pose set. That keeps the style fixed while you request the animation you are missing, and it avoids the drift that happens when each frame is prompted from scratch.

Most AI sprite generators stop at a pretty image. spritesgen is built for the import step. The manifest lists every frame as an absolute rectangle — x, y, width, height — with the name, fps, and loop flag for each state. Your importer reads those rectangles instead of assuming a uniform grid, so uneven padding or a multi-row atlas never breaks the animation.

In Unity you slice from the manifest or drive a SpriteRenderer through an animation clip built from the frame list. In Godot, AtlasTexture regions map one-to-one to the rectangles. In GameMaker you import the strip and let the manifest define image_number and per-frame timing. The same sheet loads in Phaser and PixiJS without a custom parser.

Because the atlas and the descriptor ship together, there is no re-cutting when you tweak a frame. Regenerate a pose, and the manifest updates its rectangle; the engine picks up the change on the next import. That keeps the art pipeline and the runtime in sync instead of letting them drift apart.

A uniform grid is a convenient lie. It works until a taller pose, a weapon swing, or a non-square cell breaks the assumption, and then the artist re-cuts the sheet by hand. A manifest makes the layout explicit: each frame declares its own rectangle, so a wide attack frame and a narrow idle frame can share one atlas without special cases.

The manifest also carries the data a grid cannot express — per-state fps, whether an animation loops, and the anchor that keeps a character grounded. Those are the values that decide whether a walk cycle reads correctly in game. Exporting them alongside the pixels is what turns a sprite sheet from an image into an asset.