Extract the frames of a GIF (or animated WebP/APNG) as PNG, JPG or WebP, with each frame's timing, right in the browser.
An animated GIF is, internally, a sequence of frames shown in a loop, each with its own display time. Splitting those frames into individual images opens several options: picking the best frame to become a thumbnail, editing the animation frame by frame, studying the motion of a sequence, or building a sprite sheet for a game. This tool ships a GIF decoder written from scratch in plain JavaScript, so it works in every browser, including Firefox, which does not implement the ImageDecoder API most tools of this kind rely on. Decoding the GIF ourselves also exposes what that API hides: each frame's real delay and its disposal method, which is what makes it possible to correctly rebuild animations where every frame only stores what changed. You pick the output format (PNG, JPG or WebP) and the frame range, export a .zip with a frames.json carrying the timings, or generate a sprite sheet. Animated WebP and APNG are accepted too, through ImageDecoder, when the browser offers it. Everything runs locally: the file is never sent to a server.
GIF compresses each frame with LZW and, to save space, almost always stores only the region that changed since the previous frame. Extracting the frames properly means decompressing the LZW, applying the colour palette and compositing the result onto the previous frame, honouring the disposal method declared in the file (keep, clear the region, or restore the previous frame). That is what this tool does, and it is why the frames come out whole rather than as disconnected patches.
Because decoding happens in plain JavaScript, there is no dependency on the ImageDecoder API (WebCodecs), which Firefox does not implement. For animated WebP and APNG we do use ImageDecoder when it is available, since there is no reasonable pure-JS path for those formats.
The most common use is picking a frame to serve as a cover or thumbnail: instead of accepting the first frame (sometimes blank), you split them all and take the best. Another is editing: to tweak a GIF you need the frames separated, edited, then reassembled, and the exported frames.json keeps the original timings so the cadence is not lost.
For games and web animation, the sprite sheet lays the extracted frames onto a single grid image, the format engines and CSS consume directly. And for motion study, laying the frames side by side with their delays reveals an animation's real cadence, valuable in pixel art and motion work.
By default the tool extracts up to 300 frames and tells you, with the exact number, when the animation has more than that, offering a button to extract all of them anyway. The cap exists because every frame becomes an encoded image: an 800-frame animation at 800×600 produces hundreds of megabytes.
Extraction yields control back to the browser between frames, so the tab keeps responding and the cancel button genuinely works throughout. Thumbnails load only as they scroll into view, and frames are streamed into the .zip one at a time instead of all being held in memory.
Paste the code into your HTML and the tool shows up on your page, without J-Kit's navigation and ads. It still runs in the browser of whoever visits your site.
<iframe
src="https://jkit.tools/embed/en-US/extract-gif-frames"
width="100%"
height="600"
style="border:0"
loading="lazy"
title="Extract GIF Frames"
></iframe>Your choice: PNG (lossless, preserves the transparency common in GIFs), JPG (smaller files, no transparency) or WebP. Each frame becomes a file numbered by its order in the animation and prefixed with the source file's name, all gathered into a single .zip.
Extraction happens entirely in your browser. No file is sent to any server.