Engine support

One sheet.Nine engines.

Which export each engine reads, and the settings to type in on the other side. Pick yours, or read the full import guide.

Frame data included
Metadata export

These engines read a frame data file, so the export carries every frame rectangle and you never retype a grid.

Slice in-engine
Grid workflow

These engines slice the image themselves. The export is a uniform PNG with touching cells, and you give the engine the cell size.

Side by side

What each engine reads, and what bites

The export on the left, the field you type into on the right, and the mistake that costs the most time in each one.

EngineYou exportImport pathWhere it goes wrong
UnityPNG grid plus a TextureImporter .metaPNG and .meta into the same Assets folderThe .meta pairs with the PNG by file name: spritesheet.png.meta next to spritesheet.png. Rename one without the other and Unity ignores the slices.
GodotSpriteFrames resourceAnimatedSprite2D > Sprite FramesThe .tres points at res://spritesheet.png in the project root, so moving or renaming the PNG breaks the resource.
PhaserJSON atlasthis.load.atlas(key, png, json)Frame names are zero-padded to three digits, so generateFrameNames needs zeroPad: 3 or it finds nothing.
PixiJSJSON atlasawait Assets.load("spritesheet.json")animationSpeed counts frames per 1/60 of a second, so 12 frames per second is 0.2, not 12.
GameMakerUniform PNG strip or gridImage Editor > Image > Convert to FramesFrame Width in Convert to Frames is the full cell, including any editor Padding, not the size of the art.
Construct 3Uniform PNG strip, zero gutterImport frames > From sprite stripThe strip importer counts cells, so the image width must divide evenly by the horizontal count or every frame is clipped.
DefoldTile SourcePNG at the project root, .tilesource anywhereThe generated .tilesource points at /spritesheet.png in the project root, so moving the PNG means editing that one line.
TiledJSON tilesetMap > Add External TilesetThe .tsj records image size and tile count, so a sheet re-exported at different dimensions needs a new .tsj too.
FNF & SparrowSparrow TextureAtlasname + four digit index (idle0000)Prefixes are case sensitive and matched from the start of the name, so singLEFT also picks up frames named singLEFTmiss.
Same thing, different name

The vocabulary engines disagree on

Ten terms that turn up in import dialogs under different labels. Knowing which is which turns most import problems into a one-field fix.

Atlas

A data file listing every frame rectangle in a sheet by name. An engine that reads an atlas needs no grid, because each frame carries its own coordinates. TexturePacker JSON, Sparrow XML, Godot SpriteFrames, and a Tiled tileset are all atlases with different syntax around the same numbers.

Cell size and pitch

Cell size is one frame. Pitch is cell size plus the gutter, which is the distance from the start of one cell to the start of the next. Import dialogs disagree about which one they want, and typing the pitch where the cell size belongs is the most common cause of frames drifting across a row.

Gutter, margin, separation

Names for empty space between cells. Unity calls it Padding, GameMaker separation, Defold Tile Spacing, Phaser and Tiled spacing. Sheets from this editor have none, so the value is 0 in every engine. The editor Padding setting is something else: it adds transparent pixels inside each cell, and they count toward the cell size.

Bleeding and extrusion

When a sprite is drawn at a fractional size or position, the sampler reads slightly outside the frame and picks up the neighbour. Extrusion duplicates each frame edge pixel outward so the sampler finds more of the same colour. Defold (Extrude Borders) and GameMaker (texture group borders) can add space at build time, so the source sheet does not need it.

Trimming

Cropping the transparent margin off a frame so the rectangle is only as large as the art. It saves texture space and destroys alignment unless the atlas also records the original size and the offset of the crop. Grid workflows cannot trim, because a grid needs every cell to be identical.

Pivot and origin

The point a sprite is positioned, rotated, and scaled around. Unity and Godot default to the centre of the frame and GameMaker to the top left, and neither suits a character that should be placed by its feet. Set it once per sprite at import rather than compensating in code.

Nearest versus linear filtering

Linear filtering blends neighbouring pixels, which suits photographs and destroys pixel art. Nearest, also called point, picks the closest pixel and keeps edges hard. Linear is the usual default, which makes this the setting most likely to make a correct sheet look wrong.

Texture page and batching

GPUs draw fastest when many sprites share one bound texture. Engines therefore repack art onto large pages at build time. So how tightly you pack matters less than you would think. What matters is that sprites drawn together end up on the same page.

Frame rate versus frame duration

A sheet has no timing in it. Some engines take one frame rate for a whole animation, others store a duration per frame, and a few take a total length. Uniform rates are easier to set and per-frame durations animate better, because good animation holds on its extremes.

Frame naming

Atlas formats address frames by name, so the naming scheme is part of the contract. Zero padded indices sort correctly as text, which is why frame_007 is safe and frame_7 is not. Sparrow goes further and derives the animation name from the frame name prefix.

True everywhere

Three settings, every engine

Filtering off

Point, nearest, or no filter. Linear is the usual default, fine for photos and wrong for pixels.

Exact frame size

Cell width and height, including any padding. One pixel off and every frame after the first drifts sideways.

Pivot and padding

Set the origin once per sprite. If frames bleed when scaled, add a pixel of Padding so each one has a transparent border.

Ship the sheet.

Pack it, preview it, export the format your engine reads.