png to sprite sheet

PNG to Sprite Sheet

Turn PNG frames into a packed sprite sheet, then export an aligned PNG atlas and a manifest.json with frame rectangles, fps, and loop flags.

live sprite · 8f @ 12 fps
▶ Dungeon Bat · 8F
Pack workbenchFree · alpha kept · no watermark

Pack PNG frames into a sheet

PNG images into an aligned atlas plus manifest.json.

  • Order PNG frames by filename
  • Pad and align for a clean atlas
  • Manifest with rects, fps, and loop flags

Drop files here to jump straight into the workbench

Accepts PNG · no signup required

Instant Demo — Try Without UploadingBat · 12 frames · 12 FPS
Bat live animation preview
Packed Alpha Sheet (6168×460 px · 514×460 cell)
Bat packed sprite sheet

Step by step

How it works..

Step 011
RAWframes/*.png

Add PNG frames

Drag in PNG images or a folder; they sort by filename.

Step 022
FOOT BASELINE LOCK

Set the cell

Choose cell size and padding so frames share a baseline.

Step 033
atlas.pngmanifest.json

Export the sheet

Download the PNG atlas and manifest.json with rectangles.

Supported Inputs

MP4, MOV, WebM (≤15s 1080p) · Animated GIF · PNG, WebP, JPG (≤240 frames)

Native Engine Exports

PNG Atlas + manifest.json · Godot 4 .tres · Phaser 3 JSON · Unity .meta · Aseprite · FNF XML

Anti-Jitter Alignment

Bottom-Baseline Foot Lock · BBox Center Anchor · Chroma Key & Edge De-Spill

100% Client-Side Privacy

Runs locally in your browser via Canvas 2D — zero server upload, no signup, no watermark.

Standard manifest.json Frame Layout Schema

Download free sample PNG + manifest.json →

Every export includes a clean PNG atlas plus a machine-readable manifest.json (alongside one-click Godot .tres, Phaser 3 JSON, Unity .meta, Aseprite JSON, and FNF XML):

character.manifest.jsonjson
{
  "characterId": "knight",
  "sprite_sheet_alpha": "knight.png",
  "cell": { "width": 387, "height": 460, "safe_margin_x": 6, "safe_margin_y": 6 },
  "animation": {
    "cellWidth": 387,
    "cellHeight": 460,
    "columns": 25,
    "rows": {
      "walk": { "row": 0, "frames": 25, "fps": 12, "loop": true }
    }
  },
  "frame_layout": {
    "sheetWidth": 9675,
    "sheetHeight": 460,
    "cellWidth": 387,
    "cellHeight": 460,
    "rows": {
      "walk": [
        { "x": 0, "y": 0, "w": 387, "h": 460 },
        { "x": 387, "y": 0, "w": 387, "h": 460 }
      ]
    }
  }
}
All coordinates are integer pixel rectangles from the top-left corner of the PNG atlas — zero floating-point UV rounding drift.

Why Start From PNG

PNG is the most common format for sprite art. It supports transparent backgrounds and lossless pixels, which suits hard-edged game art and keeps outlines crisp. If your frames are already PNG, you are close to a finished sheet, and you only need to pack and describe them, not redraw anything.

Packing combines many PNGs into one atlas. That cuts draw calls and file count in the engine, which matters on mobile and low-end hardware where every draw is expensive. A manifest then records where each frame sits, so the engine maps animation states without guesswork about columns and rows.

The whole process runs in the browser, so your frames stay private and you avoid upload waits for large sets or slow connections on a shared network. That local-first approach also means the tool works offline once loaded, which is handy when you are iterating on art away from a reliable connection.

PNG's lossless nature matters for pixel art in particular, because lossy formats smear hard edges and introduce artefacts that no amount of filtering can recover. Starting from PNG keeps the crisp look the artist intended all the way into the atlas.

Packing PNG Frames

Drop single PNGs or a folder. Files are ordered by name, so name frames by state and step for a predictable order you do not have to fix by hand. Set one cell size and add padding, and a shared cell keeps frames aligned and prevents edge bleeding when filtering samples near a border.

Keep the transparent background. Export preserves alpha, which matters for characters composited over any scene and avoids a coloured halo around edges. Write the manifest from the same grid so every rectangle matches the packed atlas exactly, and the data describes the real layout with nothing inferred.

If a frame is much larger than the rest, consider whether it needs a bigger cell or a separate state. Consistency keeps the atlas tidy and the import simple, and a single oversized frame can force the whole atlas to scale up if you are not careful about the cell size.

Keep source PNGs organized by state in folders, so the filename order matches the state order automatically. That small habit means packing needs no manual sorting, and a new frame drop into the right folder lands in the right place in the sequence.

Why the Manifest Beats a Uniform Grid

A uniform grid assumes frames share one size. Mixed art, like a wide attack, then clips at the cell edge and loses detail exactly where the pose is most dramatic. Exact rectangles keep each frame intact, so the engine draws the true box for every state and nothing is cut at import.

The manifest also stores fps and loop flags, so timing travels with the file instead of living in scattered config that drifts over time. Adding a frame later is easy: re-pack and the rectangles update together, so the atlas and its data stay in step and a late addition does not break earlier work.

It also makes the sheet portable, since any rectangle-based loader can read the same manifest across engines without a custom importer. That means a PNG set packed for one project can move to another runtime without re-exporting, which saves time when prototypes migrate to production.

Finally, the manifest is auditable. When a frame looks wrong, you can compare its rectangle to the source PNG and see whether the packer or the filter caused the issue, which is far faster than guessing from the atlas alone.

Workflow Tips

Use one cell size across a character's states so baselines stay aligned. Consistency beats clever per-state packing and saves debugging later in the engine. Preview the loop in the animator and set fps before exporting, since what you see in the preview is what imports.

Packing and preview are free in the browser. Only AI generation spends credits, and failed runs are refunded automatically, so the free path covers most needs. Keep source PNGs organized by state in folders so the filename order matches the state order automatically.

Re-export from the originals after edits, because hand-patching the atlas desynchronizes it from the manifest and is overwritten on the next pack. Keep the manifest and the PNG together in version control so a fresh checkout rebuilds the same atlas without re-measuring frames by hand.

Name frames with a zero-padded index so ten frames sort correctly instead of placing frame 10 before frame 2. Small naming details prevent an out-of-order animation that is annoying to spot and easy to avoid with a consistent scheme.

Keep one folder per state, so a batch pack produces the right order without manual work. If a frame lands out of order, check the zero-padding before re-packing, since frame two before frame ten is almost always a naming issue rather than a packing bug. Pack the whole character in one pass so every state shares a cell size, then export the manifest and keep it beside the PNG. A consistent folder structure also lets a script re-pack the set later without a person remembering which files belong together, which matters once a project has dozens of characters and states to maintain. A short README in the folder listing each state and its frame count saves every future contributor from opening the atlas to work out the layout, and it keeps a growing cast consistent as new artists join.

FAQ

Frequently asked questions.

Which formats can I upload?+
PNG is the focus here, and the packer also accepts WebP and JPG frames. Keep a transparent PNG background for clean edges.
Is packing free?+
Yes. Packing, slicing, and export are free in the browser with no account and no watermark. Only optional AI generation uses credits.
Is transparency preserved?+
Yes. The alpha channel is kept in the exported atlas, so characters composite cleanly over any background.
How are frames ordered?+
By filename by default. Name frames by state and step, or reorder them in the list before packing.
Do my PNGs upload anywhere?+
No. Packing and export run locally in your browser. Files reach a server only if you request an AI step.
Can I control the grid and padding?+
Yes. Set rows, columns, cell size, and padding. The manifest is written from those values for exact rectangles.
Can I use the sheet commercially?+
You keep rights to your own art. For AI output, confirm your use complies with the applicable license before shipping.