Feature

Sprite Sheet Splitter

Cut an existing sprite sheet back into individual frames. Slice on a grid, read the atlas file that came with it, or let auto-detection find the sprites.

One sprite sheet cut back into 24 individual sprites, with grid, auto-detect and atlas-file slicing modes
Overview

Extract sprites from any sheet

Drop a single image on the editor and the sprite sheet splitter opens with a preview of the frames it would cut. Even grid takes a cell size or a column and row count. Detect sprites looks for islands of non-transparent pixels. Atlas reads the exact rectangles from the data file that shipped with the sheet. Nothing is cut until you confirm, and the frames then land in the editor ready to reorder, fix or repack.

What it does

Even grid

Cell width and height in pixels, or a column and row count. The editor shows how many cells that gives before you commit.

Detect sprites

Finds sprites by the transparent space around them. Sensitivity, diagonal connection and merging of nearby pieces are adjustable.

Atlas file

Attach the .json, .xml or .plist that came with the sheet. TexturePacker, Sparrow and Cocos2d layouts are read, rotated frames included.

Skip empty cells

Grid and detect modes can drop cells with no visible pixels, so the last half-empty row does not turn into blank frames.

Keep cell padding

Keep each frame at full cell size, or crop it to its content while remembering where it sat in the cell.

Use as single sprite

If the image you dropped is one sprite and not a sheet, skip the split and put it on the canvas as is.

In practice
01Chapter 01

Why you end up needing to unpack a sheet

Packing is the easy direction. Unpacking comes up when you inherit work from someone else: an asset pack that arrived as one PNG with no data file, a sheet laid out wrong for your engine, a project where the only surviving copy of a character is the exported atlas, or a 16 pixel sheet that has to move to a 32 pixel grid.

The pixels are all there and the arrangement is the problem. Splitting the sheet turns a fixed asset back into separate sprites you can reorder, trim, recolor or repack.

02Chapter 02

Three ways to find the frame boundaries

Pick the mode by what you have

  • Even grid is for sheets on a uniform cell, which is most of them. Enter the cell size in pixels, or switch to columns and rows when you know the count but not the size. Leftover pixels at the right or bottom edge that do not fill a whole cell are ignored. If the preview frames are cut through the middle of a sprite, the numbers are wrong and nothing has been cut yet.
  • Detect sprites is for sheets that were never on a grid. It boxes each island of non-transparent pixels. Raise the sensitivity for fewer, larger sprites, turn on Merge nearby sprites when a sword or a spark gets split off from its body, and Connect diagonal pixels when thin pixel art lines touch only at corners. It needs real transparency between sprites, so a sheet on a solid background is a grid job.
  • Atlas is the exact one. If the sheet came with its data file, attach it and the rectangles are read instead of guessed: TexturePacker JSON (hash or array), Sparrow and Starling XML, or a Cocos2d plist. Frames the packer rotated to save space come back upright at their original size.

An animated GIF dropped on the editor gets a fourth option, GIF frames, with one sprite per frame. The GIF to Sprite Sheet page covers what to do with those.

03Chapter 03

Trimmed frames and alignment

Many packers crop the transparent margin off each frame to save space, and record the original size and offset in the data file. Grid mode with Keep cell padding off does something similar: each frame is cropped to its content, but its position inside the cell is kept, so the frames still line up when they land in the editor.

Detect mode has no cell to remember. Every sprite comes out tight to its own pixels, which is exactly what makes an animation wobble. After a detect split, set a common cell size and use the align buttons (bottom for characters standing on ground) to give the frames a shared baseline again.

04Chapter 04

Tilesets split differently from characters

A tileset sits on a strict grid, usually 8, 16 or 32 pixels, and tiles touch each other with no transparent gap. That makes Even grid the only sensible mode: Detect sprites sees a grass tile touching a dirt tile as one island.

Find the tile size by looking at where the pattern repeats, not by dividing the image size. A 320 by 320 image could be 20 tiles of 16 pixels or 10 of 32, and only the artwork tells you which.

Gaps between tiles

Some tools put a 1 or 2 pixel gap between tiles to stop bleeding. Grid mode has no separate gap setting. If the gap also runs along the right and bottom edge, use tile size plus gap as the cell size and each frame carries its strip of gap with it. If the tiles have transparent gaps but no edge gap, Detect sprites usually does better.

05Chapter 05

What to do with the frames once they are out

The frames land in the editor, not in your downloads folder. Repack them at another cell size for a different engine, delete the animation you are not using, or move frames onto separate layers to split one big sheet into several.

From there: fix a pixel in the pixel editor, make a colour variant on the recolor tab, play the preview to check the order survived, or export a ZIP of single PNGs if another tool needs them as files. Your original image file is never changed, so a bad split only costs another try with better numbers.

Frequently Asked

More questions? See the full FAQ.

Related

Split a sprite sheet now

Drop the sheet, check the preview, get every frame back.

Open the editor