rpg character sprite sheet generator

RPG Character Sprite Sheet Maker

Create RPG character sprite sheets in a four-direction walk layout, then export an aligned PNG atlas and a manifest.json with frame rectangles and fps.

live sprite · 8f @ 12 fps
▶ Arcane Mage Cast · 8F
Pack workbenchFree · 4-direction layout · JSON manifest

Pack an RPG character sheet

Frames into a four-direction layout with manifest.json.

  • Order frames by direction and step
  • Align a shared baseline for walking
  • Manifest with per-state rects and fps

Drop files here to jump straight into the workbench

Accepts PNG · WebP · JPG · GIF · MP4 · MOV · WebM · no signup required

Instant Demo — Try Without UploadingMage · 20 frames · 12 FPS
Mage live animation preview
Packed Alpha Sheet (6680×420 px · 334×420 cell)
Mage packed sprite sheet
Open the pack workbenchAccepts PNG · WebP · JPG · GIF · MP4 · MOV · WebM

Step by step

How it works..

Step 011
RAWframes/*.png

Add frames

Load your down, up, left, and right walk frames.

Step 022
FOOT BASELINE LOCK

Order by direction

Group frames into the four directions and their steps.

Step 033
atlas.pngmanifest.json

Export the sheet

Download the atlas and manifest.json with exact 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.

What an RPG Character Sheet Needs

RPG characters usually walk in four directions: down, up, left, and right. Each direction has its own short step cycle with a few frames, and together they let a character move believably around a map. The layout must be consistent, or the character faces the wrong way or jitters at each step.

Classic engines like RPG Maker expect a fixed layout, often eight characters with four directions and a few frames each. Matching that layout saves fiddling and avoids a custom importer. A manifest records where each direction and step sits, so any loader can map frames without guessing.

Consistency across characters matters too. If every sprite shares a grid, party members line up on screen without per-character offsets, and swapping actors never shifts the camera. That shared structure is what makes a cast feel like it belongs to one game rather than a set of separate assets.

A baseline shared by all directions keeps the character grounded. Feet should meet the ground at the same height whether the character faces down, up, left, or right, because a direction that sits a few pixels higher reads as a different character entirely.

Building the Layout

Name frames by direction and step, then order them consistently. Filename order drives the default packing order, so clear names do a lot of work and save manual sorting later. Use one cell size per character so every direction shares a baseline, and feet meet the ground at the same height in all four directions.

Group directions into rows if the engine expects it, or keep them in a single packed atlas and let the manifest describe them precisely for a custom loader. Preview a walk in each direction and confirm the step rhythm before you export, because a direction that reads differently stands out immediately in play.

Keep padding between cells so filtering never bleeds one direction into the next. Bleed is most visible on high-contrast outlines, which RPG sprites often use to stand out against a busy map. A small pad between cells prevents a thin coloured line from appearing when the sprite is scaled.

Draw one direction first and finalize its proportions before doing the other three. It saves redoing all four if the scale changes after a review, and it keeps the cast consistent when several artists contribute characters to the same project over time.

Why the Manifest Beats a Uniform Grid

RPG frames can differ in width, especially attack or idle poses mixed into a set. A uniform grid clips them at the cell edge and loses detail exactly where the pose is widest. Exact rectangles keep every direction and step intact, so the engine draws the true box and no pose loses a limb or an extended weapon.

The manifest also stores fps and loop flags per state, so walking speed is documented per direction instead of guessed from a global default. When you add a new character, the same structure repeats and the manifest keeps every sheet consistent across the cast, so party members behave the same way.

It also makes the layout portable. Another engine can read the same rectangles and play the same walk without a bespoke conversion or a re-authored asset. That portability matters when a project starts in one engine and later ships a web demo or a different port.

The data also documents intent. Seeing that the down-walk uses four frames and the left-walk uses three tells a reader exactly how each direction was authored, which is hard to reconstruct from the image alone once the original artist has moved on.

Workflow Tips for RPG Projects

Pick a target layout early: RPG Maker, LPC, or a custom engine. That choice fixes the direction order and cell size before art is drawn, and changing it later is expensive. Keep every character on the same grid so party members line up on screen and share the same collision footprint.

Packing and preview are free in the browser. Only AI generation spends credits, and failed runs are refunded automatically, so trying a new character is inexpensive. Draw one direction first and finalize its proportions before doing the other three, which saves redoing all four if the scale changes after a review.

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 PNG together in version control so a fresh checkout rebuilds the same layout without anyone recounting directions by hand.

Document the direction order and frame count beside the manifest. A short note stops a contributor from exporting at a different step count, which is the kind of mismatch that only surfaces after integration and takes a day to trace back to a naming difference.

Check the cell math against your target engine before drawing a full cast. If the engine expects a fixed character block, build one character first and confirm it walks in all four directions before scaling up. Test each direction on a real map, not only in the editor, because a wrong row order is obvious once the player turns a corner. Keep a reference sheet of the direction order so a new contributor does not guess. If a direction reads oddly, suspect the step order before redrawing the art, since a swapped frame is the usual cause. One quick map test with a single character saves redoing a whole cast.

FAQ

Frequently asked questions.

Does it support four directions?+
Yes. You order frames by direction and step, and the manifest records where each one sits for any loader.
Is it compatible with RPG Maker?+
It can produce a compatible layout if you set the cell size and direction order to match. It is not official RPG Maker software.
Is packing free?+
Yes. Packing, slicing, and export are free in the browser with no account. Only optional AI generation uses credits.
How many frames per direction?+
Three or four steps per direction is common. Set the count to match your target engine's expectations.
How do I keep walk cycles aligned?+
Use one cell size and a shared baseline for every direction. That keeps feet on the ground and stops vertical drift.
Do my frames upload anywhere?+
No. Packing and export run locally. Frames reach a server only if you request an AI step.
Can I use the sheet in a commercial RPG?+
You keep rights to your own art. For AI output, confirm your use complies with the applicable license before shipping.