Sprite Sheet Editor
Lay frames out as an even grid or a packed atlas, then tune cell size, padding and layers until the sheet matches what your engine expects.
Layout control, not just stitching
Getting frames into one image is the easy part. What decides whether the sheet imports cleanly is the layout: how many columns, how big each cell is, how much space sits between cells, and whether frames sit in an even grid at all. This page covers those controls. If you are starting from a folder of loose PNGs, the PNG to Sprite Sheet page covers the import side.
Grid or packed
Grid mode gives every frame an equal cell. Packed mode runs a MaxRects packer and shows how much of the atlas is actually used.
Columns and Force Size
Cells follow the largest frame unless you force a width and height. Columns decide how many frames sit on one row.
Cell padding
Empty pixels added inside each cell on every side, horizontal and vertical set separately, so neighbours do not bleed into each other when the engine filters the texture.
Trim Transparent
Cuts empty borders off each frame so cells shrink to the largest real content. The trim offsets are written into the JSON and XML exports.
Layers
Hide, lock, rename, reorder and duplicate layers. Visible layers are stacked cell by cell when you export.
Frame tools
Reverse, ping-pong, duplicate the run, remove empty frames, reset offsets. One click each in the sidebar.
Pixel cleanup
Remove a solid background, harden soft edges, add a 1px outline, or scale every frame 2x or 0.5x. Applies to the whole layer, or right-click one frame.
Grid layout versus packed layout
A uniform grid puts every frame in an identical cell, so the engine needs only the cell width, cell height and a frame index to find any frame. Unity slicing by cell size, Godot AnimatedSprite2D and CSS background-position all expect this. The cost is wasted space when frames differ in size, because every cell has to fit the largest one.
Packed mode drops the uniform cell. The MaxRects packer places each sprite of the active layer wherever it fits, with 1 pixel of padding on every side, and picks the smallest power-of-two size that holds them all (512, 1024 and so on, or a half-height variant when that is cheaper). You can force an exact atlas size instead, and drag sprites by hand if you want one somewhere specific. The result downloads as packed-atlas.zip: atlas.png plus atlas.json with one rectangle per frame, keyed by the original file name.
Which to pick
Use the grid when your target slices by cell, and the packed atlas when your loader reads frame rectangles from JSON. Switching modes does not touch your frames, so you can try both. The engine presets under Format (Godot, Tiled, Sparrow XML and the rest) always write grid data.
Cell size, padding and trim
Cell size is the number that touches everything else. By default it follows the largest frame across all layers. Turn on Force Size and type the size the art was drawn at, and every frame is held to that cell. A cell one pixel too tall pushes each row a pixel further down than the last, which is the most common reason a sheet slices wrong on import.
Padding adds empty pixels inside each cell, on every side, so the exported grid has a cell size that includes the padding and no extra spacing between cells. It matters when the engine draws the sheet at a non-integer scale or with filtering on, because the GPU then samples a little past the edge of a frame and picks up the neighbour. Trim Transparent goes the other way: it measures the real content of each frame and shrinks the cells to the largest of those, which can cut a sheet of loosely cropped frames down a lot. Force Size and trim are mutually exclusive, since one fixes the cell and the other measures it.
Some older mobile GPUs and WebGL contexts refuse textures above 2048 or 4096 pixels on a side. If a sheet gets near that, splitting it by animation is usually better than shrinking the art.
Layers keep parts apart until export
A character body on one layer, a weapon on another, hit sparks on a third. Hide a layer and the canvas shows the sheet without it. On export, every visible layer is drawn into the same cell in stack order, so the weapon on frame 4 lands on the body of frame 4. Hidden layers are left out of the file entirely.
Lock what is finished
Once the body frames are aligned, lock that layer. A stray drag then does nothing instead of nudging a frame two pixels sideways. Layer names matter for one export: the Sparrow XML dialog uses the active layer name as the default animation name, so a layer called run gives frames run0000, run0001 and onward.
From empty canvas to engine-ready file
A typical build
- 1Drag in your frames and check the column count first. Four columns for a four-frame cycle per row, or one long row if your loader wants a horizontal strip.
- 2Set the cell size. Leave it automatic if all frames share a size, or use Force Size with the size the art was drawn at. Then use the align buttons to line the active layer up: bottom for anything that stands on ground, middle for projectiles and effects.
- 3Add padding if the engine filters or scales the texture. Play the preview once and step through any frame that jumps.
- 4Export: plain PNG if the engine slices by cell, Format for a preset that writes the data file, or Packed Atlas if you switched to packed mode. Save the project JSON too, so changing one frame later does not mean rebuilding the layout.
More questions? See the full FAQ.
Build a sprite sheet
Grid or packed, your call. The layout stays editable until you export.
Open the editor