Can the splitter detect my sprite grid?

Declare the cell width, cell height, four margins and horizontal/vertical gaps. The tool validates complete cells; it does not detect packed or irregular sprite regions.

How are frame ranges numbered?

Frames use zero-based row-major indices across the whole source sheet. Range endpoints are inclusive. Select at most 32 frames per run; omitted ranges must cover no more than 32 frames.

Which PNG files work?

Choose exactly one static PNG up to 10 MiB. Animated PNGs and corrupt inputs are rejected. Source geometry, output geometry and conservative memory limits apply before export; a small selected range still reserves the full source image.

BROWSER-LOCAL · EXPLICIT GRID

Sprite sheet splitter

Declare a regular PNG grid, check the crop coordinates and download the selected frames. No account or image upload.

Declare cells before exporting

Set the cell width and height, all four outer margins and the gaps between cells. The remaining area must contain complete cells. This tool does not detect a grid, trim transparent borders or read packed-atlas JSON. Incorrect dimensions can produce plausible crops with the wrong boundaries; check the displayed first and last crop coordinates.

Frames run left to right, then top to bottom. An optional range uses zero-based source-sheet indices with both endpoints included: range 2 through 5 exports four frames and keeps those original frame IDs. Choose at most 32 frames. For a larger sheet, enter a range explicitly.

Use the margin and spacing diagnosis to compare aligned and shifted crops, then declare any leftover border explicitly.

Download one frame or the complete result

Each selected cell becomes a named PNG. The ZIP contains the same PNG bytes plus a manifest recording source dimensions, grid geometry, source frame IDs and top-left crop rectangles. Rectangles include their left/top edge and exclude their right/bottom edge. A failed or cancelled run publishes no partial result.

To change the arrangement, load the downloaded PNG frames into the sprite sheet maker. To enlarge the separate frames, use the batch PNG upscaler. These exports do not supply animation duration, tags or engine import resources.

Static PNG and memory boundaries

Choose exactly one static PNG up to 10 MiB. Animated PNGs and corrupt files are rejected. Source and output geometry must fit 16,777,216 pixels and 16,384 pixels per edge, with an additional conservative memory estimate. Even a one-frame range needs the full source sheet decoded; reducing the range does not bypass that source cost.

Processing requires worker image decoding and PNG encoding in your browser. Cancellation stops that worker; a fresh run starts a new job. The tool reports unsupported capabilities instead of moving image work to the page thread.

Browser decoding and canvas encoding can round partially transparent colors or discard invisible RGB and PNG metadata. Keep the original sheet. The transparent-edge guide explains why a crop can preserve the decoded pixels while differing from the source file's hidden color channels.

? QUESTIONS

Can the splitter detect my sprite grid?: Declare the cell width, cell height, four margins and horizontal/vertical gaps. The tool validates complete cells; it does not detect packed or irregular sprite regions.
How are frame ranges numbered?: Frames use zero-based row-major indices across the whole source sheet. Range endpoints are inclusive. Select at most 32 frames per run; omitted ranges must cover no more than 32 frames.
Which PNG files work?: Choose exactly one static PNG up to 10 MiB. Animated PNGs and corrupt inputs are rejected. Source geometry, output geometry and conservative memory limits apply before export; a small selected range still reserves the full source image.