Image layout · browser local

Split a sprite sheet into individual frames.

Enter the frame columns and rows, then download each source-pixel frame in a local ZIP for game or animation work.

Illustration of arranging several images into a new layout

What this workspace does

A numbered local ZIP of sprite frames.

Use it accurately

Use a regular grid for predictable results. Auto-detecting animation boundaries is deliberately not assumed.

Private browser processing

Selected files are processed in the current browser session. Aftermath has no account, cloud file storage, or server-side file-processing job.

How to use this tool

Split a local sprite sheet into numbered frames using the selected grid, then download the resulting frame set as a ZIP. The source image remains unchanged in the browser session while the tool makes the frame boundaries explicit for review. Check padding, grid alignment, order, and the target engine's import requirements before using the output.

What to choose and what you get

What to choose

  • one supported local image

Result

  • a ZIP containing numbered sprite-sheet frames

Before you start

  • Does not parse irregular or rotated texture-atlas packing, infer animation timing, or reconstruct missing engine-specific metadata.

Supported formats

  • Accepted formats: JPG, PNG, WebP.
  • Output formats: ZIP, PNG.

Browser support and permissions

  • Modern browser with JavaScript, a supported image decoder, and enough memory for the selected image.
  • No camera, microphone, or screen permission is needed.

Worked example

A 1024 × 512 sprite sheet contains eight frames in a four-column by two-row grid that need numbered files.

Starting facts

  • The grid dimensions are known and regular.
  • Frame order follows rows and columns rather than semantic animation timing.

Observed operation: Set four columns and two rows, split the decoded canvas and package eight numbered raster frames in a ZIP.

Review the result: Check frame dimensions, row-major order, transparency and edge boundaries before importing the animation assets.

Boundary: The route cannot detect irregular packing, trim transparent bounds, infer animation timing or reconstruct missing metadata.

Check your result

  • Does not parse irregular or rotated texture-atlas packing, infer animation timing, or reconstruct missing engine-specific metadata.

Things to know

  • Review the result on the intended device before relying on it.

Privacy boundary

The selected image stays in the current browser session and is not sent to an Aftermath processing service. How local processing is verified.

What this tool verifies

Checks the displayed limits and reports or creates a ZIP containing numbered sprite-sheet frames from one supported local image.

Check before sharing

A local measurement or export does not guarantee acceptance by an external destination.

How it works · Privacy · Terms of use · Contact

More to explore