What file formats can Aseprite import and export?
Aseprite can open or save a PNG image sequence, create and save animated GIF files, export sprite sheets as .png and .json, and create a texture atlas that stores several animations in one file. These are the formats documented on aseprite.org for moving pixel-art and animation work into game engines, web projects, or an asset pipeline. If your target engine expects a single packed image plus a data file, the sprite sheet and texture atlas paths are the relevant ones; if you need a simple shareable animation, GIF is the direct option.
Import and export formats at a glance
| Format | Direction | What it is used for |
|---|---|---|
| PNG image sequence | Open or save | A series of numbered PNG frames, useful when another tool or engine consumes frames individually |
| Animated GIF | Create and save | A single self-contained animation file, convenient for previews and sharing |
| Sprite sheet (.png + .json) | Export | Packed frames in one PNG with a JSON file describing frame positions |
| Texture atlas | Create | Several animations stored together in one atlas |
How each format fits a project
PNG image sequence
Aseprite can open or save a sequence of images. This matters when your pipeline already works frame-by-frame — for example, when a build script or engine importer expects frame_0001.png, frame_0002.png, and so on. You are not locked into a packed layout, and each frame stays independently editable outside Aseprite.
Animated GIF
You can create animations and save them as .gif files. This is the simplest way to get a moving result out of Aseprite without a companion data file. The trade-off is that GIF is a display format, not a game-asset format: it does not carry the layer or tag structure your project may need later.
Sprite sheet with JSON
Aseprite exports your work to sprite sheets in .png and .json files. The PNG holds the packed frames; the JSON describes where each frame sits. This pairing is what most 2D engines and web runtimes need to slice a sheet back into individual frames at load time. If your engine asks for "a sheet plus a data file," this is the export to use.
Texture atlas
Aseprite can store several animations in one texture atlas. Instead of one sheet per animation, you consolidate multiple animations into a single atlas — useful when you want fewer texture swaps or a tidier asset bundle. The site lists this as a creation capability, so treat it as the packing step for multi-animation projects rather than a separate file extension.
Choosing between them
- Sharing a quick preview or posting an animation: animated GIF.
- Feeding a 2D engine or web runtime that slices frames: sprite sheet
.png+.json. - Combining many animations into one packed image: texture atlas.
- Working with a frame-by-frame pipeline or external compositing: PNG image sequence.
Related capabilities worth knowing
Aseprite also documents a command-line interface (CLI) for integrating the tool into an assets pipeline and automating image conversions. If you are exporting the same formats repeatedly as part of a build, the CLI is the mechanism the site points to for that automation, rather than doing each export by hand.
Data recovery is also listed, so a crash does not necessarily mean losing the sprite you were working on.
Practical notes
- The site describes these import/export paths but does not publish per-format limitations here, so verify frame counts and sheet dimensions against your target engine's own limits.
- Pricing and licensing are handled separately on the site's Buy page; nothing in the format documentation implies the software is free. A trial version is referenced on the site.