ALL IMAGE TOOLS56
Split GIF into Frames
Split a GIF into Frames — Every Frame as a PNG
Extracts each frame as a numbered PNG and hands them back as a ZIP, in the order they play.
Nothing is enforced, but every frame is held decoded in memory at once, so a long GIF at full size can exhaust the tab before it finishes.
About Split GIF into Frames
This gives you every frame of an animation as a separate picture, numbered in playing order and zero-padded so a two-hundred-frame archive unzips in the right sequence. The frames come out as PNG rather than GIF, and that is deliberate. Decoding an animation composites each frame into a complete picture — most GIF frames store only the rectangle that changed since the last one, so the decoder has to build the whole image before it can hand it over. Writing those complete frames back through a 256-colour palette would throw away what the decode just recovered, for no benefit. PNG keeps them exactly as they were reconstructed. Everything happens in this tab. The animation is decoded frame by frame, worked on, and written back out with gifenc, which this site already carries for its video-to-GIF tool — so nothing is uploaded and no new engine is downloaded. One thing is worth knowing before you start: re-encoding a GIF is not lossless. A GIF can hold at most 256 colours per frame, and rebuilding the file means choosing that palette again. Flat colour, line art and text come through cleanly; fine gradients and photographic frames can band slightly. The original file on your disk is untouched either way.
Questions
Why are the frames PNG and not GIF?
Because decoding an animation composites each frame into a complete picture — most GIF frames store only the rectangle that changed since the last one, so the decoder has to rebuild the whole image before it can hand it over. Writing those complete frames back through a 256-colour palette would throw away exactly what the decode just recovered, for no benefit. PNG keeps them as they were reconstructed.
What order are the files in?
Playing order, numbered from one and zero-padded to the length of the frame count — frame-001.png, frame-002.png and so on. The padding is what makes a two-hundred-frame archive unzip and sort in the right sequence instead of putting frame-10 before frame-2.
Do I get the frame timings as well?
Not as a separate file. Each frame is exported as a picture, and PNG has nowhere to record how long it was displayed. If you need the timings, the speed-changer page reads and shows them; for reassembling an animation, the video-to-GIF tool builds one from frames at a rate you choose.
Is there a limit on how many frames?
Nothing is enforced, but there is a real ceiling: every frame is held decoded in memory at once while the archive is built, and a long animation at full size can exhaust the tab before it finishes. A few hundred frames is comfortable; several thousand at full resolution may not be.
Is my GIF uploaded?
The animation is decoded frame by frame in your tab and written back with gifenc, which this site already carries for its video-to-GIF tool — so nothing is uploaded and no extra engine is downloaded. Two decoders are used depending on your browser: Chrome, Edge and Firefox have a built-in image decoder that returns frames directly, and Safari does not, so a small bundled JavaScript reader handles it there. Both produce the same frames; the difference is only in who does the work.
Is my file uploaded to a server?
No. Transmute processes everything locally in your browser using JavaScript and WebAssembly. Your files never leave your device — there is no server, no upload, no cloud processing.