isometric sprite generator

Isometric Sprite Generator

Generate isometric sprite sheets with diamond tiles and aligned anchors, then export a PNG atlas and a manifest.json with frame rectangles and fps.

2:1 isometric grid · baseline locked
▶ Iso Mech 2:1 · 8F
Pack workbenchFree preview · 2:1 tiles · JSON manifest

Build an isometric sprite sheet

Diamond tiles into an aligned atlas plus manifest.json.

  • Diamond tiles with consistent anchors
  • Eight-direction character frames
  • Manifest with per-frame 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 UploadingRobot · 13 frames · 12 FPS
Robot live animation preview
Packed Alpha Sheet (3302×460 px · 254×460 cell)
Robot packed sprite sheet
Open the pack workbenchAccepts PNG · WebP · JPG · GIF · MP4 · MOV · WebM

Step by step

How it works..

Step 011
RAW2:1 iso mech frames

Choose the tile

Set a 2:1 diamond tile size for your isometric grid.

Step 022
DIAMOND BASE ANCHOR

Add tiles or frames

Load tiles or character frames and align their anchors.

Step 033
iso-mech.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 Isometric Art Needs

Isometric art sits on a diamond grid. Tiles are drawn as rhombi that tile edge to edge at a 2:1 width-to-height ratio, so the floor repeats cleanly in every direction. Characters follow the same grid, and their anchor point must sit at the base of the diamond so they stand correctly on the floor.

If anchors drift, a character floats above or sinks into the tile. Consistent anchoring is the whole game in isometric scenes, and it is invisible until something looks wrong, at which point the cause can be hard to find across a large map. A manifest records each tile and frame rectangle plus its anchor, so the engine places them precisely.

Getting the ratio right early saves rework. Changing the diamond after the art is drawn means re-aligning every anchor and sprite, which can take days on a large tileset. A consistent unit is what lets a floor tile, a wall, and a character all agree on where the ground is.

Isometric also depends on draw order, so tall objects must be sorted by depth as the camera moves. Precise rectangles and consistent anchors make that sorting reliable, because the engine knows exactly where each sprite's base sits on the grid.

Building the Iso Sheet

Pick a tile size first, usually a 2:1 diamond like 64 by 32. Every tile and character shares that unit, so they interlock on the grid without per-asset scaling. Give each sprite the same padding so a tall character or a raised object does not clip a neighbour, since padding keeps tall art from colliding with the tiles above it.

Align anchors at the tile base. Preview a small map to confirm tiles meet without gaps or overlaps before you commit to a full sheet and discover a systematic offset. For walking characters, keep eight directions if you need diagonal movement, and record fps per direction so speed stays even across the compass.

Keep outlines consistent between tiles and characters. A darker or thicker outline on one type makes the scene look assembled from mismatched parts rather than one world. Consistent line weight and palette across a tileset is what makes an isometric scene read as a place rather than a collage.

Draw a small test map before a large one. It exposes anchor mistakes early, while fixing them is still cheap and no art has been built on top of them. A four-tile patch with one character is enough to reveal a wrong anchor or a ratio that does not tile.

Why the Manifest Beats a Uniform Grid

Isometric tiles vary in height: a flat floor tile, a wall, and a character are all different sizes. A uniform grid clips them and breaks the illusion of a real space. Exact rectangles keep each tile and frame intact, and the engine draws the true box with the anchor at the base of the diamond so everything sits where it should.

The manifest also stores fps and loop flags for character states, so walk cycles are documented per direction instead of guessed from a single global default. That makes a generated or hand-built iso sheet import with no special handling, across any engine that reads rectangles, from a bespoke renderer to a full engine.

It also keeps tall props and short tiles in one file without one clipping the other, which is hard to do with a rigid grid and a fixed cell height. A manifest lets a tall statue and a flat floor tile coexist and still anchor correctly to the same ground plane.

And because the data is plain JSON, a map editor can read the same material a runtime does. That means the tool used to place tiles and the engine that draws them agree on every rectangle and anchor, which removes a whole class of visual mismatch.

Workflow Tips for Isometric Games

Lock the tile ratio before you draw. Changing it later means re-aligning every anchor and sprite, which is days of avoidable rework on a large project. Use whole-pixel scaling for pixel-art iso, and keep filtering off so edges stay sharp, since fractional scale makes diamond edges shimmer when the camera moves.

Packing and preview are free in the browser. Only AI generation spends credits, and failed runs are refunded automatically, so experimenting with a tileset is cheap. Draw a small test map before a large one, because it exposes anchor mistakes early while fixing them is still cheap.

Re-export from the originals after edits. Hand-patching the atlas desynchronizes it from the manifest and is overwritten on the next pack, so keep the source files intact. Keep the manifest and the tile PNG together in version control so a fresh checkout rebuilds the same grid.

Document the tile ratio and anchor convention beside the manifest. A short note stops a contributor from exporting at a slightly different diamond, which is the kind of mismatch that only appears once a full map is assembled and is painful to correct after the fact.

Depth sorting is the hidden problem in isometric scenes. As a character walks behind a tall tile, the engine must draw the tile after or before the character depending on their base positions. Precise anchors make that comparison reliable, because the sort uses the base of each diamond rather than the image bounds. Test a character walking behind a wall to confirm the order flips at the right moment. Keep tall props on the same anchor convention as characters so sorting works across the whole scene. A manifest that records the anchor turns a fragile guess into a fixed rule you can trust.

FAQ

Frequently asked questions.

What tile ratio should I use?+
Most isometric games use a 2:1 diamond, such as 64 by 32 pixels. Pick one ratio and keep every tile and character on it.
How many directions should characters have?+
Four directions suit simple games; eight allow diagonal movement. The manifest records fps per direction.
Is previewing free?+
Yes. Packing, slicing, and preview are free in the browser. Only optional AI generation uses credits.
How do I keep characters on the floor?+
Anchor every sprite at the base of the diamond and keep that anchor consistent. The manifest stores the anchor with each frame.
Can I mix tiles of different heights?+
Yes. Exact rectangles in the manifest let flat tiles, walls, and characters coexist without clipping.
Do my tiles get uploaded?+
No. Packing and export run locally. Files reach a server only if you request an AI step.
Can I use the tiles commercially?+
You keep rights to your own art. For AI output, confirm your use complies with the applicable license before shipping.