GIF to Sprite Sheet
Turn an animated GIF into a sprite sheet. Every frame comes out in order, ready to clean up and export as a grid your engine can slice.
Drop the GIF, get the frames
Drop one animated GIF on the editor and the splitter opens in GIF frames mode, with one sprite per frame. Confirm, and the frames land on the canvas like any other sprites. A GIF almost always carries frames a sprite sheet does not need, so the useful work happens next: finding repeats, cutting the empty margin, and checking the loop.
Full frames, not patches
Each frame is decoded at full canvas size, as it looks at that moment in playback, even when the GIF only stores the pixels that changed.
Duplicate detection
Identical frames are flagged in a banner with a count. One click removes the extras.
Trim the margin
GIF frames carry the full canvas. Trim Transparent shrinks every cell to the real content of the animation.
Order tools
Reverse a run that plays backwards, delete half of a ping-pong loop, drag single frames into place.
Engine exports
PNG sheet, JSON atlas, Godot SpriteFrames, Sparrow XML, Tiled tileset or a ZIP of single frames.
How a GIF stores an animation
A GIF is a stack of images, each with a delay and a disposal rule that says what to do with the previous image before drawing the next. Many encoders store only the rectangle that changed, so one frame inside the file can be a small patch rather than a full picture.
Frames are decoded with the browser built-in ImageDecoder, which composes each patch onto what came before. What you get is the full picture at that point in playback. Chrome and Edge support ImageDecoder; in a browser without it, the GIF produces no frames, so try one of those if the splitter comes back empty.
Why GIFs have frames you do not want
GIF delays are stored in hundredths of a second, and many viewers treat very short delays as a tenth of a second. To slow a moment down, some encoders repeat a frame several times instead of setting a longer delay. In a GIF that is invisible. In a sheet each repeat is a cell that costs texture memory and makes the frame count lie.
After extraction, the editor hashes every frame and shows a banner when it finds exact copies. Open Details to see which frames match, or hit Remove to keep one of each. Long holds belong in your engine as per-frame durations, not as copies in the texture.
Check for ping-pong loops
Many GIFs play forward then backward, so the second half is the first half reversed. Those frames are not exact neighbours, so the duplicate check will not catch them all. Delete the reversed half and let the engine play the animation ping-pong instead.
What GIF colour limits mean for your sheet
A GIF frame holds at most 256 colours, and one of them can be marked transparent. There is no partial alpha, so any soft edge in the original art was hardened or dithered against a background before the GIF was written. The conversion keeps every pixel, but it cannot bring back what the GIF never stored.
Pixel art usually comes through clean, because it had hard edges and a small palette to begin with. Smoother art tends to arrive with a fringe of odd pixels around the outline. When the fringe is close to the old background colour, Remove background with a higher tolerance clears it along with the background. Per-colour recolor can replace a fringe colour across the whole layer, and the pixel editor handles the spots both miss.
Deciding which frames survive the trip
A GIF made for a web page and a sheet made for a game want different frame counts. On the web, extra frames cost only bandwidth. In a sheet they stay in texture memory for as long as the sprite exists, so a 24-frame idle is a poor trade when 8 frames read the same in motion.
The cleanup pass
- 1Remove the exact duplicates the banner finds.
- 2Delete the reversed half of any ping-pong loop.
- 3Turn on Trim Transparent so cells shrink to the animation, not the GIF canvas.
- 4Play the preview and hide frames one at a time. If the motion still reads, delete them.
More questions? See the full FAQ.