A sprite sheet can look perfectly aligned while exporting the wrong frames. The common causes are a mistaken row count, a border around the sheet, spacing between cells, or an assumed animation order. Start by confirming the grid, then inspect the extracted files before importing them into a game or animation project.

Check that the sheet is actually a regular grid

The sprite sheet splitter accepts one JPG, PNG, or WebP image and creates numbered PNG frames in a ZIP. It is intended for known, regular rows and columns. A texture atlas with irregular rectangles, rotated sprites, or separate packing metadata needs an atlas-aware workflow instead.

Prefer the original PNG or an appropriate WebP source when transparency matters. A JPEG has no alpha channel, and saving it as PNG afterward cannot reconstruct a transparent background. Keep the original sheet and any animation metadata together; splitting the image does not recover timing or pivots that were never encoded in its pixels.

Work out frame size before splitting

A clean grid with ten frames
Sheet:       960 × 384 pixels
Columns:     5
Rows:        2
Frame width: 960 ÷ 5 = 192 pixels
Frame height:384 ÷ 2 = 192 pixels
Frame count: 5 × 2 = 10

This calculation assumes no outer border and no gaps between cells.

If the sheet has two-pixel gaps, simply dividing the whole width by the column count gives the wrong answer. Obtain a correctly prepared sheet or use an editor that can remove the documented margins and spacing. Do not assume the splitter detects gutters or irregular packing automatically.

When the dimensions do not divide evenly, investigate before exporting. The source might have a border, the grid may be different, or the image may have been resized. A one-pixel error repeated across columns can cut into neighboring frames.

Export a small set and inspect it

  1. Select the source image and set the known column and row counts.
  2. Run the split and download the ZIP. Keep it separate from the original image.
  3. Extract the archive into a new folder. Check the number of files and the pixel dimensions of a frame.
  4. Open the first frame, a frame at a row boundary, and the last frame. Check edges, transparency, and whether neighboring artwork leaks into a cell.
  5. Review the full sequence. The tool follows grid order; it cannot infer which frames belong to walking, jumping, or idle animations.

The example above should produce ten 192 × 192 frames. That is a calculated expectation for this grid, not a benchmark or a guarantee that an arbitrary source is valid. A sheet containing eight useful cells and two empty cells still has ten grid positions.

Set animation meaning in the destination

In the target engine, confirm frame order, frame rate, loop behavior, scale, filtering, and origin or pivot. Equal-sized frames can still appear to jump if the character is not consistently positioned within each cell. Cropping away different transparent margins can also change apparent alignment unless the destination has matching offset metadata.

For example, Godot’s sprite-animation documentation shows both separate-frame and sheet-based animation workflows. Use the documentation for your actual engine and version. Aftermath exports images, not an engine-specific animation resource or a reconstructed atlas manifest.

Fix the symptom closest to its cause

  • Every frame includes part of its neighbor: recheck grid counts, margins, and gaps.
  • The animation runs in the wrong order: inspect the numbered files and map them to the intended animation sequence in the destination.
  • Edges look blurred: inspect the original at native pixels and check import filtering. Splitting cannot restore pixels already softened by resizing or JPEG compression.
  • The tab becomes slow: use a smaller source or process the sheet on a device with more available memory. Encoded file size is not the same as decoded pixel memory.

The selected image is processed in the browser and not sent to an Aftermath processing service. The ZIP you choose to download remains a separate copy that you control. Site analytics and later sharing have their own boundaries, described in the privacy policy.