Banner Studio
Designers make the master.
Agents make each size.
HTML5 banners and social visuals in every size from one Figma master, each checked against its network’s rules.
Six formats, in sync with the 300 × 600. Drop a component on it and I carry it to the other five.
Instagram · 1440 × 1800Last check just now · 6 formats
One master, every size. Hand edits stay yours.
-
Social visuals too. The image a LinkedIn, Instagram or Facebook post carries, made from the same master as the display sizes.
One Lumo creation on the canvas, a section per platform: the 4:5 master and the LinkedIn post image, Instagram's feed post and story, Facebook's square post, and the Google Ads display sizes 300 × 600, 300 × 250 and 728 × 90. -
Own edits. Edit one size by hand, and the agent leaves it alone when the master changes.
Petra rewrites the headline of the 300 × 250 banner by hand and it gets Own edits; then the master's headline changes, the Animator adapts the sizes that follow the master, and the 300 × 250 keeps Petra's line. -
One ZIP per network. Every size and network becomes its own ZIP with a backup image. A pair that fails stays out.
The export of the summer set: sizes by network, Google Ads, Sklik and MAFRA; each checked pair is its own ZIP with a backup image, and one MAFRA pair with a finding is not exported. -
The agent watches it play. The agent plays each size in a real browser, sees what went wrong and fixes it before you look.
The Animator agent plays Lumo's 300 × 600 banner in a real browser and lays out five frames; at 2.4 seconds the headline is clipped, so it edits the file, looks again, and every frame is clean.
The campaign plans it. The studio builds it.
-
From the campaign’s plan. Brief, landing page, networks and run dates come from the campaign, so a set starts where the plan left off.
Lumo's summer campaign board: the Launch phase, 8–21 June, holds the summer banner set; the set's settings carry the campaign's brief, the landing page, the networks Google Ads, Sklik and MAFRA, and the run dates from the Launch phase.
Ready for the networksyou buy from.
-
Every network’s rules. Google Ads, Sklik, CM360, Amazon DSP and Czech publishers, each checked its own way.
-
Rich media. Expandables and interstitials, both states rendered and checked.
-
Smallest package. Every ZIP ships the smallest files that still pass.
-
Agency ZIPs. Upload an agency’s package and get its full check back.
-
Approve the set. A person approves the set for its run dates.
-
Brand check in the studio. Every text in every format checked against your brand’s rules.
Agents
The agents behind your banners and visuals. A person approves what they make.
-
Visual agent
Fills a template family with copy and a background for every format.
-
Animator
Codes HTML5 banners, watches them play and checks each network.
Questions about HTML5 banners
What are HTML5 banners in Monobase?
HTML5 banners in Monobase are animated display ads that the Animator agent writes as files from your designer’s master. It adapts the master to every size you pick, plays each one in a real browser and checks it against the networks of the set. A person on your team approves the set.
Does Banner Studio make social visuals?
Yes. Besides HTML5 banners it makes the image a LinkedIn, Instagram or Facebook post carries: every network’s format from one master, exported as PNG or ZIP to Media, or opened straight from a post with Edit visual.
Can it make versions for different audiences?
Yes. Give the agent a brief and it proposes audiences with their source. Once you confirm them, each audience gets its own master and formats, so two audiences in three formats make six visuals.
Does Banner Studio read the campaign’s plan?
HTML5 banner sets do: a set made from a campaign format takes the campaign’s brief, landing page and phase, and runs on the phase’s dates. Social visuals that read the campaign’s brief and phases are coming soon.
What is the studio built from?
From your designers’ masters and your brand: layout, fonts, colours and logos come from the brand’s display profile, so the agent fills the slots and keeps the design.
Which ad networks are supported?
Google Ads, Sklik and Seznam (Seznam RTB too), Google Ad Manager with Campaign Manager 360 and DV360, CM360 Studio for rich media, Adform, Amazon DSP, IAB-standard ad servers, MRAID for in-app ads, and the Czech publishers MAFRA, Publico and CNC. Each is checked its own way: size, file weight, files and folders, click-through, animation length and calls out of the banner.
Does Monobase upload the banners to the networks?
No. Monobase exports one ZIP per size and network, with that network’s click-through and a backup image, and you upload it in the network’s own tool. A size that fails a network’s check is not exported for that network.
What happens to a size we edited when the master changes?
A size you edit by hand gets its own edits, and the agent leaves it alone. When the master changes, the agent updates every other size and checks it again.
Can we bring banners an agency made?
Yes. Upload the agency’s ZIP to a size and it becomes a new revision with its full check: the network’s rules and a render in a real browser.
Do you support rich media and video?
CM360 Studio expandables and MRAID interstitials, with both states rendered and checked. A video file can ride in the package for CM360 Studio, MRAID and CNC. Monobase doesn’t make VAST or VPAID video ads.
Does approving a set publish it?
No. Approval records that a person signed off this creative for its run dates. It publishes nothing, uploads nothing and doesn’t block the export.