When this tool is useful
Inspecting animation transitions, editing individual displayed frames, building contact sheets, or recovering a reviewed still-frame sequence.
How local processing works
After strict chunk and sequence validation, each frame rectangle is decoded, blended onto the canvas, captured at display time, and disposed correctly before the next frame. Captures receive zero-padded names in one ZIP.
How to use it
- Prepare and preserve the source: Keep the unchanged source, review the intended destination, and begin with conservative limits. Inspecting animation transitions, editing individual displayed frames, building contact sheets, or recovering a reviewed still-frame sequence.
- Run the bounded local operation: Process only in this browser and stop on unsupported, malformed, or ambiguous input. After strict chunk and sequence validation, each frame rectangle is decoded, blended onto the canvas, captured at display time, and disposed correctly before the next frame. Captures receive zero-padded names in one ZIP.
- Inspect the result: Open the first, transition, disposal-sensitive, and last PNG, compare them with paused APNG playback, confirm frame count and ordering, and retain the animation plus report.
Important limitations
Exports are fully composited canvases rather than the original delta rectangles. Timing, loop metadata, source chunks, profiles, and edit history are reported but not embedded into each PNG.
Verify the downloaded result
Open the first, transition, disposal-sensitive, and last PNG, compare them with paused APNG playback, confirm frame count and ordering, and retain the animation plus report.
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 tool useful?
Inspecting animation transitions, editing individual displayed frames, building contact sheets, or recovering a reviewed still-frame sequence.
What does the local operation do?
After strict chunk and sequence validation, each frame rectangle is decoded, blended onto the canvas, captured at display time, and disposed correctly before the next frame. Captures receive zero-padded names in one ZIP.
Which limitations matter?
Exports are fully composited canvases rather than the original delta rectangles. Timing, loop metadata, source chunks, profiles, and edit history are reported but not embedded into each PNG.
How should I verify the result?
Open the first, transition, disposal-sensitive, and last PNG, compare them with paused APNG playback, confirm frame count and ordering, and retain the animation plus report.