Choose the format requested by the destination, media team, or delivery specification. HTML packages and rendered media files solve different problems, and a successful export does not guarantee that a platform accepts that format.
Compare the outputs
| Format | Use it when | Output and constraints |
|---|---|---|
| HTML | The destination needs an interactive HTML creative, a platform-specific ZIP, responsive layouts, or custom-hosted code | Choose the exact platform output because click handling, metadata, SDKs, manifests, and package structure can differ |
| Animated GIF | The destination explicitly accepts an animated GIF | Supports lossless or lossy compression and one-time or infinite playback; advanced palette settings can affect the result |
| MP4 | The destination needs an H.264 MP4 video or the export needs an optional audio track | Export using Chrome or the Figma desktop app |
| WebM | The destination explicitly accepts a WebM video | Export using Chrome or the Figma desktop app |
| Animated PNG (APNG) | The destination explicitly accepts an APNG image | Export using Chrome or the Figma desktop app |
| Animated WebP | The destination explicitly accepts an animated WebP image | Export using Chrome or the Figma desktop app |
Choose by requirement
You need ad-platform packaging or click handling
Choose HTML, then select the exact destination under Bannerify HTML platform outputs. Named outputs can add their own click wrapper, metadata, SDK, manifest, and ZIP structure.
You need several responsive layouts in one HTML output
Choose the responsive HTML option that matches the destination. Bannerify selects between the supplied Figma layouts; it does not generate missing sizes, breakpoints, or orientations.
You need a rendered file instead of code
Choose GIF, MP4, WebM, APNG, or animated WebP only after confirming that the destination accepts it. These exports render frames from the Bannerify timeline into the selected media format.
You need audio
Use MP4. Bannerify can add an MP3 file or use audio from an embedded video in the MP4 export workflow.
The HTML upload also needs a static fallback
Enable backup.jpg for a 1x JPG fallback. You can hide selected layers from that fallback and set a target size for the file.
Plan for file size and rendering time
- Higher frame rates take longer to render and produce more frames, which can increase media file size.
- The HTML maximum file-size target compresses image assets toward the requested threshold, but a low target may still be exceeded when the creative contains many or large assets.
- Animated GIFs embedded inside an HTML banner are not included in Bannerify's HTML file-size target.
- Higher HTML image scales can produce sharper JPG and PNG assets, but also increase their file sizes.
Validate the deliverable
- Confirm the required format, dimensions, duration, file-size limit, and playback behavior with the recipient.
- Export a representative banner using the exact destination settings.
- Preview the unzipped result. If a local HTML preview appears frozen, test without an ad blocker or privacy extension before re-exporting.
- Validate or upload the package in the destination platform before producing the full campaign.