When this tool is useful
Inspecting individual animation states, selecting source frames, building a contact sheet, or moving frames into an editor with explicit timing notes.
How local processing works
GIF disposal and transparency are resolved into full-canvas RGBA frames by the GIF decoder. For animated WebP, the tool requires a compatible browser ImageDecoder and reads its decoded frames and durations. Each frame becomes PNG and a JSON manifest records order, dimensions and available timing.
How to use it
- Prepare the source and limits: Keep an unchanged source and review the accepted format, dimensions, frame or page budget, and output choices. Inspecting individual animation states, selecting source frames, building a contact sheet, or moving frames into an editor with explicit timing notes.
- Process locally: Run the documented bounded operation in this browser and stop when the decoder reports an unsupported structure. GIF disposal and transparency are resolved into full-canvas RGBA frames by the GIF decoder. For animated WebP, the tool requires a compatible browser ImageDecoder and reads its decoded frames and durations. Each frame becomes PNG and a JSON manifest records order, dimensions and available timing.
- Download and verify: Compare manifest frame count, order and duration with playback in the source viewer, inspect every PNG around disposal and transparency transitions, and verify WebP-derived timing in the exact browser used for extraction.
Important limitations
GIF is the core supported animation path. Animated WebP extraction depends on browser ImageDecoder availability and codec behavior and can be unavailable even when ordinary WebP images display. PNG frames do not remain animated, compressed frame rectangles become full canvases, timing precision can differ by decoder, and metadata and original compression are not retained.
Verify the downloaded result
Compare manifest frame count, order and duration with playback in the source viewer, inspect every PNG around disposal and transparency transitions, and verify WebP-derived timing in the exact browser used for extraction.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
When is this workflow useful?
Inspecting individual animation states, selecting source frames, building a contact sheet, or moving frames into an editor with explicit timing notes.
What does local processing do?
GIF disposal and transparency are resolved into full-canvas RGBA frames by the GIF decoder. For animated WebP, the tool requires a compatible browser ImageDecoder and reads its decoded frames and durations. Each frame becomes PNG and a JSON manifest records order, dimensions and available timing.
Which format limits matter?
GIF is the core supported animation path. Animated WebP extraction depends on browser ImageDecoder availability and codec behavior and can be unavailable even when ordinary WebP images display. PNG frames do not remain animated, compressed frame rectangles become full canvases, timing precision can differ by decoder, and metadata and original compression are not retained.
How should I verify the download?
Compare manifest frame count, order and duration with playback in the source viewer, inspect every PNG around disposal and transparency transitions, and verify WebP-derived timing in the exact browser used for extraction.