Most campaign teams do not start every banner set from zero.
They reuse the creative that already worked.
The real job is to refresh it: new offer, new date, new CTA, maybe a new product shot or seasonal visual hook, but the same basic size family and performance logic that already proved itself.
That sounds efficient until the refresh touches twenty sizes, three ad platforms, two fallback formats, and one rushed approval cycle that somehow turns “just update the sale” into a full production sprint.
Bannerify is useful here because it turns those Figma updates back into production-ready HTML, GIF, MP4, and ad-platform outputs without forcing the team to rebuild each size by hand.
This topic is deliberately different from Spreadsheet-Driven Banner Variant Workflow, Multi-Offer Banner Test Matrix Workflow, and Banner Variant Review Workflow for Campaign Teams. Those focus on variant generation, offer testing, or review structure. This one is about refreshing a proven evergreen campaign set when the team wants new creative energy without resetting the whole production system.
Refresh work fails when the team edits the outputs instead of the system
The usual bad pattern looks like this:
- export last quarter’s winning set
- open individual sizes
- change the date or price one by one
- patch layouts where the new line breaks differently
- forget one old CTA or landing URL
- discover late that the seasonal visual only works in half the sizes
That is not a refresh workflow. It is a manual rewrite of a system that already existed.
The cleaner approach is to go back to the master Figma structure, define what is changing, and treat the refresh as a controlled update to a banner family.
Decide what stays evergreen and what changes this round
Before touching the design, sort the campaign into two buckets.
Stable:
- size set
- motion structure
- primary layout logic
- placement-specific constraints
- known file-format requirements
Refreshable:
- offer or discount
- dates and urgency language
- imagery or seasonal art treatment
- CTA language
- landing URL
- disclaimer details when relevant
That distinction keeps the team from accidentally redesigning the whole campaign while pretending it is a quick refresh.
It also surfaces whether the new concept really fits the old system. If the refreshed message needs totally different hierarchy, that is a redesign, not a refresh.
Stress-test the smallest size first
The fastest way to know whether the refresh is real or fake is to test the least forgiving size.
If the new offer, date, or CTA breaks the smallest placement, the rest of the set is probably at risk too.
Check the hard cases first:
- longest promo line
- biggest percentage or currency treatment
- densest disclaimer
- most seasonal visual treatment
- smallest or most crowded size
This keeps the team from approving a desktop-friendly concept that quietly fails across the actual banner family.
If file-size pressure is part of the refresh, HTML5 Banner File Size Reduction Checklist is the right supporting article to pair with this step.
Keep the refresh source organized around campaign intent
A simple production structure helps a lot:
- one master page for the approved evergreen family
- one clearly labeled refresh pass for the new offer cycle
- one note on what changed and what must not change
That makes reviews much easier because stakeholders can compare:
- original high-performing concept
- refreshed campaign direction
- exact places where the new round differs
It also makes future refreshes cheaper. The team is building a lineage, not improvising from exported remnants.
Use preview and approval as part of the refresh, not only the end
Refresh work often gets underestimated because people think the banner “already exists.”
In reality, fresh offers introduce fresh risk:
- the new CTA may overpromise
- the destination URL may have changed
- the refreshed visual hook may feel off-brand
- disclaimers may need re-checking
- animation pacing may feel wrong with the new copy rhythm
That is why preview matters.
Bannerify is especially helpful when the team needs to present the refreshed family as real outputs instead of static mockups. If the approval loop is part of the bottleneck, Banner Preview Link Workflow for Approvals is the best companion article.
Do one refresh-focused QA pass before the final export
The QA pass for a refresh is different from the QA pass for a brand-new concept.
You are looking for drift between the old reliable system and the new campaign details.
Check:
- every size reflects the new offer and dates
- stale copy from the previous round is gone
- landing URLs match the refreshed campaign
- disclaimer updates are consistent
- animation still supports the revised message
- fallback outputs match the refreshed family
That last point matters. A refresh often updates the HTML5 banners correctly while the MP4, GIF, or preview fallback still carries old messaging because nobody checked the whole export set.
A practical refresh checklist
Before shipping the refreshed campaign, confirm:
- the team updated the master banner system, not only individual outputs
- the smallest size survived the longest realistic copy
- stable campaign rules stayed stable across the refresh
- approvals reviewed the refreshed output, not assumptions based on the old winner
- stale URLs, offers, and disclaimers were fully removed
- the fallback and platform-specific exports match the new round
If your team also runs more aggressive experimentation across offers or messaging, Multi-Offer Banner Test Matrix Workflow is the better adjacent piece. This article is for the common case where one proven banner family needs a fast but disciplined new campaign pass.
Where Bannerify helps most
Bannerify is valuable here because growth teams win by reusing what already performs, but they still need each new campaign round to feel intentional and production-ready.
That means the refresh workflow has to preserve the system while updating the message.
If your team keeps turning “just refresh the banners” into a manual rebuild exercise, move the process back into Figma, refresh the master family deliberately, and let Bannerify handle the real output generation. That is how a proven evergreen system stays fast instead of becoming technical debt in creative form.
Read as Markdown Related resource index Site index for AI agents
Pro Bundle