Setting a maximum file size target for each banner in your HTML exports

Some ad platforms have a size limit per banner (for example, 150kb), so you can use this HTML export setting to try and automatically fit each banner under that size threshold.

Enable Maximum file size target for each banner and enter your size limit in KB. Bannerify adjusts image compression to fit the target while preserving as much detail as possible. Targets use 1 KB = 1,000 bytes. If you leave the limit blank, it defaults to 150 KB.

New export settings use Slower (Smaller Size, Default) compression. This spends more time compressing images to aim for smaller files. Choose Faster when export speed matters more. Existing saved compression choices are preserved.

A low target or lots of large images can require more compression, especially at 1.5x or 2x scale. With the target enabled, Bannerify checks the finished creative and shows an error if it is still too large.

Large SVG files can use most of the size budget before photos are compressed. If the photos look blurry but the banner still exceeds its target, first export with the target disabled and inspect the files in the banner's images folder. For a small logo with a large SVG file, try a PNG format override with Retina 2x enabled, then compare the appearance and final banner size. Confirm the required size limit and whether it applies to the ZIP or unpacked files with your ad platform.

When targeting unpacked files for individual non-responsive banners, the image budget accounts for the code, localized media and included backups already written to the creative, then reserves space for SVGs and GIFs. Repeated images sharing the same output filename count once. The final size check uses the actual exported files, including any changes made while rendering GIFs.

Bannerify automatically applies lossless ZIP compression to HTML export downloads, including individual banner and section ZIPs. This reduces the packaged size without changing image quality or the extracted files. Image compression can reduce image quality. You can export with the target disabled first to check whether the original images already fit.

Target the individual ZIP size ​

For HTML/JS (CSS @keyframes), HTML/JS (GSAP/Greensock) or DoubleClick (DCM) exports, enable Include individual .zip files for each banner and Maximum file size target for each banner. Bannerify automatically applies the target to each finished individual ZIP; no extra setting is needed. Enter the limit required by your ad platform.

Bannerify checks the complete individual ZIP while choosing image quality, so space saved by ZIP compression can be used for more image detail. If space remains, Bannerify tries higher quality for individual images without lowering the quality of the others. For JPG and PNG output, it also tries restoring the original exported image bytes when they fit. Every candidate is checked against the complete ZIP, and the final archive is checked again before download. Some space can remain when no further quality upgrade fits.

Repeated images sharing the same output file count once. Code, SVGs, GIFs, and any included backup or other assets all count toward the ZIP limit. Only the raster image quality is adjusted during this check; animated GIFs are not recompressed to fit.

Export may take longer. If the banner cannot fit at the lowest supported image quality, Bannerify shows an error instead of downloading an oversized individual ZIP. Reduce the assets or use a larger permitted limit and try again. The limit applies to each individual ZIP, not the outer download containing all banners and previews. If banners have different limits, export them in groups with the appropriate target.

Target the unpacked files ​

Other ad-platform formats, responsive exports, section exports and multiple-platform exports use the total size of the underlying files. For HTML/GSAP or DoubleClick (DCM) exports with an unpacked-file limit, turn off Include individual .zip files for each banner.

Bannerify checks each finished banner separately, including its code, images, GIFs, packaged media, manifests and any included backup. Responsive creatives and section packages are checked as a complete group, with shared files counted once. AppLovin exports are checked after the assets are embedded in the final HTML.

If the creative fits with space left, Bannerify tries higher quality for its JPG, PNG and WebP images without lowering another image's selected quality. It checks the complete file total as it raises quality, then tries individual image upgrades to use smaller amounts of remaining space. For JPG and PNG output, it also keeps the original exported image bytes where they fit.

This can take longer. Some space can remain when images reach their maximum supported quality or higher quality settings do not fit. Bannerify leaves that space unused and checks the final total again before download.

If the total exceeds the target, Bannerify stops before downloading or uploading the preview. Reduce the assets or use a larger permitted target and try again. The overall download and preview page are not treated as one banner. Externally hosted assets that are not included in the creative's files are not counted; confirm your platform's requirements separately.

Exporting WebP images instead of JPG/PNG. Choose Use WebP Format from the compression menu to convert JPG/PNG images to WebP. Confirm that your ad platform accepts WebP and check browser support before using it.

Animated GIFs count toward both ZIP and unpacked-file limits, but Bannerify does not reduce their quality to meet the target. Large GIFs or other fixed assets may need to be reduced separately.