Accept the composed animation, not its isolated frame images

Define the output canvas before listing frames

The PNG Specification, Third Edition, checked 7 November 2026, defines APNG frame controls for disposal and blending. A frame’s visible result therefore depends on more than its isolated image data. This lesson scopes the technical model to APNG; it does not assume every image viewer supports animation or handles an unsupported file in the same way.

Draw the intended complete canvas at several meaningful moments in the campaign sequence. Identify which elements should remain, which should disappear and which should be replaced. A product badge that persists for the whole sequence has a different role from a temporary price callout. Obtain the content owner’s intended sequence before inspecting implementation details, so the technical review has a clear visual result to reproduce.

Trace a small region through successive updates

Use an original synthetic canvas divided into four named areas. Start with a neutral background and a permanent blue marker in the upper-left area. The next intended picture adds an orange marker at the lower right; the following picture removes orange while leaving blue. Write these complete expected pictures first, without choosing how to encode them. This separates the visual contract from a particular optimization method.

Ask the implementer to show each supplied frame’s affected rectangle and controls, then reconstruct the displayed canvas after each step. Keep the previous canvas, affected region, operation and resulting canvas in separate columns. Compare the reconstructed result with the expected complete picture. A frame image showing only an orange square is not wrong by itself; the important question is what the receiver combines it with and what remains afterward.

Exercise retained pixels and the loop seam

Include a candidate that leaves the orange marker behind after it should disappear. Mark the first output canvas that differs rather than simply describing the animation as glitchy. Also inspect a candidate with an unintended cleared region. These observations give the implementer a concrete state mismatch to explain without assuming that the same repair fixes both cases. Preserve the earlier canvas needed to reproduce the issue.

Run the sequence across its return to the beginning in an approved supplied preview. Compare the first picture after wraparound with the intended opening picture, not merely with the last frame’s isolated data. Check temporary labels near the seam and any region that never receives a full redraw in the proposed implementation. Do not infer an infinite loop or a particular playback duration from the creative brief; confirm the intended behavior with its owner.

Accept the composed delivery rather than extracted pictures

Review the final artifact in the actual receiving route and compare it with the canvas trace. A successful frame extraction establishes neither correct composition nor correct delivery support. Keep the accepted output captures linked to the exact file. If a receiver cannot present the intended animation, route the need for a separately approved fallback to the creative owner rather than claiming the same file is universally suitable.

Retain the expected pictures and trace with the production handoff so later file-size optimization can be evaluated against the same visual contract. Optimizing a partial update should not change which offer text survives into the next moment. This exercise does not create or publish a live campaign, and it does not establish flashing-content safety or accessibility. Those reviews concern the delivered sequence through their own qualified process.

Make the reasoning concrete.

A fictional service ad animates two colored markers around a fixed logo. The supplied frame previews look correct individually, but an orange marker remains beneath the final call to action and reappears at the loop boundary.

The producer holds the optimized animation until its composed pictures match the intended sequence. No live file is replaced.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Canvas

   What complete picture should the viewer see at each meaningful moment?

2. Region

   Which part of the canvas does each supplied frame affect?

3. History

   What previous picture must be retained to explain the next result?

4. Mismatch

   Where does an unwanted retained or cleared area first appear?

5. Loop

   Does the delivered return to the opening reproduce the intended first picture?

Watch for the wrong conclusion.

• Approving isolated frame images instead of displayed canvases.
• Ignoring regions that receive only partial updates.
• Treating a clean first pass as proof of a clean loop seam.

Sources & scope

Workflows, fixtures, worksheets and examples are original editorial analysis. Sources support the narrow attributed statements, not measured business results. Platform guidance is scoped to the documented implementation and date checked. Synthetic offline planning only; no external account, file publication, permissions or production configuration is changed.

• Portable Network Graphics (PNG) Specification (Third Edition) →Primary platform documentation or published technical standard · Supports: Supports APNG disposal and blending as composition controls; the marker fixture and acceptance trace are original.