VS

Spritesheet Generator vs TexturePacker

TexturePacker is a desktop build tool for texture atlases, with a free mode and a paid Pro license. This is a hand tool in a browser tab: it packs one sheet at a time and adds an editor, a splitter, and a preview.

Overview

A build tool and a hand tool

TexturePacker is built to sit in an asset pipeline and repack automatically. This tool is for packing a sheet by hand when you need one. If your project repacks often or ships large atlas sets, TexturePacker is the better tool and this page will not argue otherwise. If you pack a sheet every few weeks, the question is whether you need a pipeline at all.

In detail
01Chapter 01

What TexturePacker is for

TexturePacker, made by CodeAndWeb, runs on Windows, macOS, and Linux. You point it at folders and it packs them, and it can do that again every time the folder changes. The command line tool and the .tps project file are what a pipeline uses; the GUI configures them.

What that buys you

  • Polygon packing fits sprites by outline instead of bounding box, which saves texture memory on sheets of irregular shapes.
  • Rotation and multipack: sprites turn to fit, and a set too large for one texture is split across several with consistent data.
  • Exporters for dozens of engines and frameworks, plus scaling variants that generate several resolutions in one run.

It has a free Essential mode for basic packing; the features above sit in the paid Pro license. Pricing changes, so check codeandweb.com for the current figure.

02Chapter 02

What you give up here

The specific gaps

  • Packing is MaxRects on axis-aligned rectangles with no rotation, so irregular or mixed-aspect sprites leave more empty space than TexturePacker would.
  • No multipack. A set that does not fit one sheet has to be split by hand.
  • No CLI and no watch folder, so nothing here can run unattended in CI.
  • Packed mode exports a PNG with TexturePacker-style JSON. The Godot, Tiled, Sparrow, and CSS exports use the grid layout instead.

There is no fixed size cap, but everything is decoded in the tab, so very large sheets run into browser canvas and memory limits. Studio-scale atlas sets are not what this is for.

03Chapter 03

What you get back

A pixel editor, so a stray pixel gets fixed without a round trip to another program. A splitter, so an existing sheet becomes frames again, cut by grid, by detected sprites, or by the rectangles in its JSON or XML. An animation preview with an fps control, so timing gets checked before the engine sees it.

And it runs in a browser, which matters for a contributor on a locked-down work laptop or a Chromebook who needs to fix one frame and will not install anything to do it.

Pick TexturePacker when

Packing is a repeated build step, you need polygon packing, rotation, or multipack, you ship at several resolutions, or a CI job must produce atlases with nobody watching.

Pick Spritesheet Generator when

You pack by hand now and then, the sheet fits in one texture, and you want to fix a frame, check the timing, and export a Godot .tres in the same tab.

Feature comparison
FeatureUsTexturePacker
All features free TexturePacker has a free Essential mode; Pro features need a license
Runs in the browser TexturePacker is a desktop app for Windows, macOS, and Linux
Trim transparent pixels
JSON atlas export
Engine-specific formats TexturePacker supports far more
GIF export
Animation preview
Pixel editor
Split a sheet back into frames
Polygon packing
Sprite rotation when packing
Multipack across several sheets
Scaling variants
Command-line interface Needed for CI and automated repacking
Where this helps

Splitter

Take a published sheet apart using its atlas file, fix a frame, and repack. TexturePacker is built to go the other way, frames to sheet.

Editor in the same tab

Pencil, eraser, fill, line, shapes, and a color picker for frame-level fixes, with onion skinning to check them against neighbouring frames.

Hand-off

From TexturePacker to a packed sheet

  1. 1

    Start from frames, not the .tps

    TexturePacker project files are not read here. Use the source frames, or split the published sheet with its JSON or Sparrow XML attached so the rectangles come back exactly. Rotated frames in the data file are handled.

  2. 2

    Rebuild the layout once

    Set cell size and padding for a grid, or pack tight with MaxRects.

  3. 3

    Export the same atlas format

    Phaser and PixiJS loaders that read TexturePacker JSON read the JSON from here too. Sparrow XML for Starling works the same way.

  4. 4

    Keep TexturePacker for automation

    A licensed CLI in CI and a browser tool for one-off sheets is a reasonable split, since both can write the same JSON shape.

FAQ

More questions? See the full FAQ.

Pack it in a tab

No license key, no installer, no project file. Drop frames in and export.