Sprite Sheet Generator Guide: Godot, Unity and Phaser Formats

A sprite sheet is an interface between art and runtime code. The engine needs to know where each frame begins, how large it is, which direction it faces and how long it should display. A beautiful sheet with inconsistent frame bounds is not ready for a game. Generate the art first, then enforce a frame contract before import.

Choose a frame contract

Write down frame width, frame height, columns, rows, padding, spacing, pivot and animation order. For example: 64x64 cells, one pixel spacing, four columns, idle frames left to right, pivot at the bottom center. Never infer frame geometry from a PNG by eye once the sheet enters production.

Engine	Typical import path	What to verify
Godot	AtlasTexture or SpriteFrames	Hframes/Vframes, region, centered pivot and animation FPS
Unity	Sprite import mode Multiple, then Sprite Editor	Cell slicing, pivot, pixels per unit and filter mode
Phaser	Sprite sheet config or JSON atlas	Frame dimensions, key, frame rate and loader path

Godot

For a regular sheet, Godot can use horizontal and vertical frame counts. For irregular atlases, define regions with AtlasTexture resources or use an imported atlas workflow. Set filtering according to the art style: nearest for crisp pixel art, linear only when the project expects smooth scaling. Check the imported resource in the actual animation player rather than trusting the source image.

Godot's animation concepts and asset import documentation are the useful references here: 2D sprite animation.

Unity

Set Sprite Mode to Multiple, open Sprite Editor and slice by cell size when the sheet is regular. Set Pixels Per Unit consistently across the project. The pivot is not cosmetic: a bottom-center pivot keeps feet planted while the sprite changes pose. Disable filtering and unwanted compression when the game needs exact pixel edges.

For sheets with uneven padding or different frame sizes, use a JSON atlas or carefully named slices instead of asking Unity to guess. Automated slicing is fast until one frame has a transparent edge that changes the bounding box.

Phaser

Phaser can load regular sprite sheets by specifying frame width and height, or use a JSON atlas when the packer has created named frames. The key and path must match the loader entry exactly. After loading, create an animation with an explicit frame sequence and rate. Phaser's references cover the animation system and loader.

What AI sprite generators tend to break

• Frame count is visually implied but not exact.
• Character drifts horizontally between frames.
• Feet change scale or ground position.
• Background pixels appear between frames.
• Weapon or effect leaves the declared cell.
• Facing direction changes without a naming convention.

Sprixen's sprite generator and animation workflow are useful for producing a consistent batch, but always run a technical pass: crop or pad to exact cells, remove background correctly, align the pivot and inspect the loop at runtime. If the sheet is for pixel art, do not let a browser rescale it with smoothing during QA.

Export checklist

1. Confirm every frame has the same canvas dimensions.
2. Confirm the animation order in a written manifest.
3. Use transparent PNG when the runtime expects alpha.
4. Record intended FPS and whether the animation loops.
5. Set a stable pivot and pixels-per-unit convention.
6. Import into the real engine and test at target resolution.

The best sprite sheet generator is not the one that produces the most frames. It is the one that gives you a repeatable frame contract, consistent visual alignment and an export you can load without repairing every animation by hand.