VS

Spritesheet Generator vs Aseprite

Aseprite is the better place to draw pixel art, and its sheet export is good. This tool is for the step after: frames from other sources, sheets you did not author, and engine files Aseprite does not write.

Overview

A pixel art editor and a sheet packer

If you draw your own sprites, you probably want Aseprite, and you may not need this tool at all. Its Export Sprite Sheet dialog covers a lot. The gaps are narrower than most comparison pages admit: frames that never lived in an .aseprite file, a shipped sheet with no source project, and a few engine formats the dialog does not write.

In detail
01Chapter 01

What Aseprite does well

Aseprite is a pixel art editor first. Timeline with layers and cels, onion skinning, tilemap mode, palette tools with shading modes, and a brush engine designed for placing single pixels. The pixel editor here does not compete with it.

The Export Sprite Sheet dialog is also better than people assume. It lays frames out as a horizontal or vertical strip, by rows, by columns, or packed. It handles padding, trim, and merging duplicate frames, and it writes a JSON data file in hash or array form with your tags included. There is a command line interface for build scripts and a Lua scripting API, and people have written exporters on top of both.

At the time of writing, Aseprite costs about $20 on Steam and itch.io and runs on Windows, macOS, and Linux. The source is on GitHub under a license that lets you compile it yourself for personal use.

02Chapter 02

Where it stops

The dialog exports the document you have open. That is the right design for an editor. It just means anything that is not already an Aseprite document needs importing first.

Cases this tool handles directly

  • A folder of PNGs from another artist or another editor, with no .aseprite file behind them.
  • A finished sheet in the repo that needs one frame changed. Drop it in the splitter, cut it by grid, by detected sprite islands, or by the rectangles in its JSON or XML atlas, then fix and repack.
  • An animated GIF that needs to become a sheet. GIF frame extraction relies on the ImageDecoder browser API, so it does not work in every browser.

Aseprite can import a sheet or a GIF too, so none of this is impossible there. It is just more steps when you never meant to open the file in an editor.

The other gap is output. Phaser and PixiJS read Aseprite JSON fine. Godot SpriteFrames resources, Tiled .tsj tilesets, Sparrow XML for FNF mods, and CSS sprites are not in the dialog. Lua scripts can fill some of that, but you have to find or write one.

03Chapter 03

Using both

A setup that works

Draw in Aseprite. Export frames as individual PNGs (File, Export with a frame number in the file name, or the CLI), drop the folder here, set columns and padding, check the timing in the preview, and export the format your engine wants.

If your engine already reads the JSON Aseprite writes, keep exporting straight from Aseprite. A second tool in a pipeline that works is just one more thing to maintain.

Pick Aseprite when

You draw the art yourself, want one tool from first pixel to final sheet, and your engine reads Aseprite JSON or slices a plain grid. The price is low for what it does, and it pays its developers.

Pick Spritesheet Generator when

The frames already exist and came from elsewhere, you need to take apart a sheet you did not author, or your engine wants a SpriteFrames .tres, a Tiled tileset, or Sparrow XML.

Feature comparison
FeatureUsAseprite
Free to use Aseprite is about $20 at the time of writing, or compile the source yourself
Runs in the browser Aseprite is a desktop app for Windows, macOS, and Linux
Import loose PNG frames Aseprite imports numbered file sequences as frames
Grid layout export
Packed atlas layout
JSON atlas export
GIF export
Godot .tres, Tiled .tsj, Sparrow XML Possible in Aseprite with third-party Lua scripts
Split a sheet using its atlas file Aseprite imports sheets by grid
Animation preview
Layers
Onion skinning
Pixel editor Ours is for frame fixes; Aseprite is a full editor
Tilemap mode and shading tools
Tags for several animations in one file
Command-line export
Where this helps

No source document needed

Frames from Krita, Photoshop, an old export folder, or a client GIF all go straight in. Nothing has to become a project file first.

Godot, Tiled, and Sparrow output

A SpriteFrames .tres with regions already set, a .tsj tileset, or Sparrow XML with a frame prefix you choose. No hand-converting Aseprite JSON.

Hand-off

From Aseprite to a packed sheet

  1. 1

    Export frames or a sheet

    Individual PNGs give the most freedom. An exported sheet plus its JSON also works: attach the JSON in the splitter and the frames are cut on the exact rectangles from the file.

  2. 2

    One sheet per tag

    Aseprite tags name several animations inside one file. The Godot export here writes a single animation called default, so export each tag on its own if you want them separate.

  3. 3

    Set the layout

    Cell size, padding, and column count for a grid, or MaxRects packing for a tight atlas. Packed mode exports a PNG with TexturePacker-style JSON; the Godot, Tiled, Sparrow, and CSS exports use the grid.

  4. 4

    Export what Aseprite does not write

    A Godot SpriteFrames .tres, a Tiled tileset, CSS sprites, or Sparrow XML. If you want plain Aseprite-style JSON back, there is an export for that too.

FAQ

More questions? See the full FAQ.

Pack what you drew

Export your frames from Aseprite, drop the folder here, pick your engine format.