Spritesheet Generator vs Piskel
Both tools are free and run in a browser. Piskel is built for drawing animated sprites. This one is built for assembling, splitting, and exporting sheets with the data files engines read.
Same price, different jobs
Since both are free and browser-based, cost and install do not decide anything here. What decides it is where you are in the work. Drawing frames from nothing: Piskel. Frames already drawn and the engine wants a data file alongside the PNG: this.
Piskel is a drawing tool that can export a sheet
Piskel is open source and has always been free. Open a tab and you have a frame list, layers, onion skinning, and a live animation preview in the corner. For learning pixel animation it is hard to beat, mostly because there is so little to learn before you start drawing. Its interface is also simpler than the editor here.
It can also import images. Give it a sheet and a frame size and it slices the sheet into frames, so splitting is not something only one of these tools can do.
The weak point is maintenance. The last tagged release is several years old and the repository has been quiet since. Being a static web app, it keeps working, but new export options are not coming.
The export end
Piskel exports a PNG sheet, an animated GIF, a ZIP of individual frames, and its own .piskel project file. It does not write an atlas data file, so an engine that needs frame rectangles either slices by grid or you write the data by hand.
Data files this writes that Piskel does not
- TexturePacker-style JSON for Phaser and PixiJS.
- A SpriteFrames .tres for Godot 4 with the regions already set.
- A .tsj tileset for Tiled.
- Sparrow XML for FNF mods and Starling.
- CSS sprite rules for web pages.
Layout is the other difference. Piskel exports the grid its canvas implies, which is right for a drawing tool. Here you set columns, cell size, padding, and per-sprite offsets inside a cell, align frames to an edge or center, or switch to MaxRects packing for a tight atlas.
Pick Piskel when
You are drawing frames from scratch and want the simplest canvas, timeline, and onion skin you can get. If your engine slices a plain grid PNG, its export is all you need.
Pick Spritesheet Generator when
Your frames already exist or came from several places, or your engine wants a JSON atlas, a Godot .tres, a Tiled tileset, or Sparrow XML next to the image.
| Feature | UsUs | Piskel |
|---|---|---|
| Free to use | ||
| Runs in the browser | ||
| Import images as frames | ||
| Split a sheet into frames Both slice by frame size; this one can also auto-detect sprites or read an atlas file | ||
| PNG sheet export | ||
| GIF export | ||
| ZIP of frames | ||
| JSON atlas export | ||
| Godot .tres, Tiled .tsj, Sparrow XML | ||
| Packed atlas layout | ||
| Pixel editor | ||
| Layers | ||
| Onion skinning | ||
| Animation preview |
Layout you choose
Columns, cell size, padding, offsets, and alignment, or a packed atlas. Piskel exports whatever grid the canvas implies.
Splitter that reads atlas files
Cut a sheet by grid, by detected sprite islands, or by the rectangles in a TexturePacker JSON, Sparrow XML, or Cocos2d plist file.
From Piskel to a packed sheet
- 1
Export loose frames from Piskel
Use the ZIP export to get one PNG per frame rather than the assembled strip, so the layout is not stuck with the Piskel canvas grid.
- 2
Check frame order
Frames are added in the order the browser hands the files over, with no natural sort. If the names run frame1 to frame12 without zero padding, check the order and drag frames into place.
- 3
Set the layout
Columns, cell size, and padding for a grid, or MaxRects packing when the loader reads an atlas. The Godot, Tiled, Sparrow, and CSS exports use the grid; packed mode gives PNG plus JSON.
- 4
Export the data file
JSON atlas, Godot .tres, Tiled .tsj, Sparrow XML, or CSS. This is the step with no Piskel equivalent, and the only good reason to add a second tool.
More questions? See the full FAQ.
Take it past the PNG
Import your Piskel frames and export the data file your engine reads.