Static backup images are easy to treat as the final export chore. The animated banner gets the timing, easing, ClickTag checks, and creative review; the fallback frame is generated at the end and dropped into the ZIP because the platform asks for it.

That is risky. The backup image may be what a publisher shows in unsupported environments, blocked script contexts, slow preview tools, or conservative QA flows. If it is cropped badly, missing legal copy, too heavy, or different from the approved final frame, the campaign can fail even when the HTML5 animation looks polished.

Define the backup frame before animation starts

The backup image should come from an intentional frame, not whichever moment happens to be visible when the producer exports. For most display campaigns, the best candidate is the final frame: brand, product or offer, CTA, legal line if required, and enough context to make sense without motion.

Write that expectation into the production brief or spec matrix. If the final animated frame is not suitable as a static ad, decide what changes: a clearer product crop, a shorter legal line, a more balanced logo position, or a less motion-dependent visual.

Malabar

Malabar 300 x 600
Choose the backup frame as a creative decision, not an export accident. A tall lifestyle unit can rely on motion to reveal several visual beats. The static backup still needs one complete, approved message that works without that sequence.

Match size, format, and platform expectation

Backup rules vary by platform and publisher. Some expect a JPG, some allow PNG, and some specify a maximum backup weight separately from the HTML5 ZIP. A direct publisher may also expect the image filename to match a naming convention or sit beside index.html inside the package.

Capture these details before packaging:

  • Required image format.
  • Exact pixel dimensions.
  • Maximum backup-image weight.
  • Filename expected by the platform or publisher.
  • Whether the backup needs to be inside the ZIP.
  • Whether the backup should match the animated final frame.

This is especially important when the same creative is exported for several traffic destinations. A backup image that passes one upload tool may fail another if the format, filename, or weight limit changes.

Check readability without motion

Animation helps a banner explain itself over time. A backup image has one frame. That makes hierarchy more important, not less.

Open the exported image at its real size and check the basics: Can the headline be read at 300 x 250? Is the CTA visible? Does the brand appear clearly? Is the product crop meaningful? Is the legal line still legible enough for the campaign requirement? Does the image look like the approved creative, or like a random paused state?

Fusebox

Fusebox 300 x 250
Review the backup image at the actual placement size. A square unit has little room for a lazy fallback. The static frame should preserve the offer, brand, and CTA without needing the animated build-up.

Keep backup images tied to versions

If the HTML5 banner changes, the backup image may need to change too. Updated legal copy, a revised CTA, a new product image, or a different final frame should trigger a backup-image re-export and a package weight recheck.

This is where versioning protects the team. The handoff manifest should list the ZIP filename and the backup-image filename together, with the same version context. If v03 changes the headline, ad ops should not receive a v02 backup image inside the package.

A small manifest row can prevent a lot of confusion:

campaign_market_size_platform_version.zip
backup filename
backup weight
final-frame source
QA status
revision note

The point is not to create paperwork. It is to make sure the static asset and animated asset tell the same story.

QA the image as part of the ZIP

Backup QA should happen after the final package is named and zipped, not only while the source file is open. Producers should unzip the delivery package, confirm the backup image exists, open it, check its weight, and compare it with the approved frame.

For campaign teams, this also gives a clean review path. Instead of asking ad ops to discover issues during upload, the production handoff can say: the HTML5 preview passed, the ClickTag passed, the ZIP weight passed, and the backup image passed.

TMR

TMR 300 x 250
Package QA should include the backup image, not stop at the HTML preview. Simple promotional units still need fallback discipline. If the backup frame is the only version shown, it has to carry the same message as the animated creative.

A practical backup-image checklist

Before a banner ZIP leaves production, confirm:

  • The backup image exists in the expected location.
  • Pixel dimensions match the banner size.
  • File format matches the platform rule.
  • File weight is inside the limit.
  • The frame includes brand, message, CTA, and required legal copy.
  • The image matches the approved creative version.
  • Filename and manifest row match the exported ZIP version.
  • The backup opens cleanly after the ZIP is rebuilt.

Good backup images make HTML5 banner delivery feel more reliable. They reduce platform surprises, give ad ops a clearer package, and protect the campaign when the animated experience is not the version that gets shown.