gamemaker sprite sheet maker

GameMaker Sprite Sheet Maker

Produce GameMaker-friendly sprite sheets: an aligned PNG atlas and a manifest.json of frame rectangles, origins, and fps. Import cleanly without hand-slicing.

live sprite · 8f @ 12 fps
▶ Slime Bounce · 8F
Pack workbenchFree · alpha kept · origin-friendly

Pack a GameMaker-ready atlas

PNG frames into an aligned atlas plus manifest.json for GameMaker.

  • Exact frame rectangles for GameMaker frames
  • Consistent origins and baselines across states
  • Manifest records fps and loop flags

Drop files here to jump straight into the workbench

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

Instant Demo — Try Without UploadingSlime · 16 frames · 12 FPS
Slime live animation preview
Packed Alpha Sheet (8736×340 px · 546×340 cell)
Slime 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

Drop PNG frames or a folder; ordering follows the filenames.

Step 022
SAFE PADDING + RECT

Align the cells

Set one cell size and padding so origins line up.

Step 033
sheet.pngmanifest.json

Export for GameMaker

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

GameMaker Studio Strip Import & GML Snippet

Download free sample PNG + manifest.json →

Import horizontal strips via Sprite Editor -> Import Strip Image, or load and align a baseline-locked strip dynamically in GML:

obj_character_Create_0.gmlgml
/// @description Load a SpritesGen horizontal strip with bottom-center foot pivot
var _frames = 20;
var _cell_w = 404;
var _cell_h = 460;

spr_walk = sprite_add_strip(
    working_directory + "slime.png",
    _frames,
    0, 0,
    _cell_w, _cell_h
);

// Lock origin to bottom-center so foot baseline matches floor collisions
sprite_set_offset(spr_walk, _cell_w div 2, _cell_h);
sprite_set_speed(spr_walk, 12, spritespeed_framespersecond);

sprite_index = spr_walk;
image_speed = 1;
Setting the Y origin to cell_height locks the character's feet to your tilemap collision mask.

What a GameMaker Sprite Sheet Needs

GameMaker slices an imported sprite into frames by columns and rows, and each frame shares the same size inside one sprite resource. That is fine for uniform art, where every pose occupies an identical box. It gets awkward when poses differ in size, because GameMaker frames cannot vary within one sprite.

A wide attack and a narrow idle cannot share one uniform grid cleanly without wasting space or clipping art. A manifest helps in two ways: it tells you the exact frame rectangles, and it documents where each state starts and ends. You plan around the real bounds instead of forcing every pose into one guess.

For mixed-size art you can split into a few uniform sprites, or pad to one cell. The manifest keeps the mapping clear either way, so nothing is ambiguous when someone else opens the project. It also records fps and loop flags, so playback timing is written down instead of being rediscovered per animation.

Origins matter as much as rectangles in GameMaker. A consistent origin, usually bottom-center, keeps the character standing on the ground. The manifest documents the intended baseline so an importer or a teammate can set the same origin for every frame and avoid the classic bounce between poses.

Importing the Atlas into GameMaker

Import the PNG as a sprite and set the frame size, or the columns and rows, to match the sheet. The importer then cuts frames on that grid, so the numbers must agree with the manifest you packed. Set a consistent origin, usually bottom-center, so characters stand on the ground rather than bouncing between frames.

Use image_speed and image_index to drive playback. Set image_speed from the manifest fps divided by the room speed, and remember that looping is the default for sprites. Keep padding between cells so texture filtering never bleeds neighbouring frames at the edges, which otherwise shows as a thin coloured line in motion.

Prefer one character per texture group so frames draw together and batching stays efficient. Mixing unrelated art into one page hurts draw performance more than it saves in file count. If the sheet is large, split by state or by character so the texture pages stay a manageable size.

Match image_speed to the manifest fps so the game plays the cycle as previewed, and check the loop seam in a test room rather than only in the sprite editor. Timing changes under load, and a seam that looks fine in the editor can pop during play.

Why a Manifest Beats a Uniform Grid

A uniform grid assumes one frame size, which is safe only when the art truly is uniform. A single taller boss frame breaks the assumption and clips at the cell edge, losing the top of the character. Exact rectangles tell you the truth about each frame, so you build sprites that respect the real bounding boxes instead of guessing a cell.

The manifest also stores fps and loop flags, so timing is documented rather than rediscovered per animation. That saves time on every new state and keeps speed consistent across a character's moves. When art changes you re-pack and read the new rectangles, so the sprite and its data stay consistent and silent cropping bugs are rare.

It also helps when several people work on one project, because the manifest is a shared reference everyone can read without opening the engine. Questions about layout get answered in seconds, and a new teammate can map frames to states without a screen-share. That documentation value compounds as a project grows.

Finally, the manifest keeps the sheet portable. Another engine can read the same rectangles and play the same frames, so an asset built for GameMaker is not trapped there. That flexibility is useful when a prototype later moves to a different engine or a web build.

Workflow Tips for GameMaker Teams

Match image_speed to the manifest fps so the game plays the cycle as previewed, and check the loop seam in a test room rather than only in the sprite editor. Keep origins consistent across every state of a character, because that single habit prevents the most common jitter bug in 2D character animation.

Packing and preview are free in the browser, and only AI generation spends credits with failed generations refunded automatically, so trying a new character is inexpensive. Canvas a baseline guide into your art source so feet land at the same height each frame, which the packer can respect but cannot invent.

Re-export from the originals after edits, because hand-patching the atlas desynchronizes it from the manifest and the next export overwrites your changes. Keep the manifest with the PNG in the project so the import is reproducible for anyone who opens the repository later.

If a sprite looks wrong, inspect the origin and the cell size first, before touching the art. Most GameMaker animation glitches come from a mismatched frame grid or a drifting origin, not from the drawing itself, so check the data before redrawing anything.

Keep a note of the room speed next to the manifest, because image_speed depends on both the manifest fps and the room speed. Without that note a speed that looks right in one room can drift in another, and a walk suddenly looks either sluggish or frantic depending on the scene. Document it once and every animation stays consistent across rooms, and record it in the manifest notes so the value travels with the asset.

FAQ

Frequently asked questions.

Is this an official GameMaker tool?+
No. spritesgen is independent and not affiliated with GameMaker or YoYo Games. It exports a PNG and JSON that you import yourself.
Can GameMaker use mixed frame sizes?+
One sprite resource has uniform frames. For mixed art, split into a few sprites or pad to a common cell. The manifest lists the real rectangles.
Is packing free?+
Yes. Pack, slice, and export are free in the browser with no signup. Only optional AI generation costs credits.
How do I stop sprites from bouncing?+
Set one consistent origin for every frame, usually bottom-center. A drifting origin is the usual cause of vertical jitter.
Do my frames get uploaded?+
No. Packing and export run locally. Frames reach a server only if you explicitly choose an AI step.
Can I read the manifest in GML?+
Yes. It is plain JSON, so you can load and parse it with GameMaker's JSON functions to place frames or drive custom logic.
Can I use the sheet commercially?+
You keep the rights to your own art. For AI output, confirm your use complies with the applicable license before shipping.