You resize a banner ad to all display sizes by building one campaign in Display Format Builder: add your artwork once, adapt the layout to each IAB size, animate it, preview the set together and export exact-size images, GIFs or video. The whole process runs locally in the browser, so your files never leave your device and there are no file-size caps.
If you have ever exported a 300x250, then a 728x90, then a 160x600, then a 300x600, then a 320x50, you already know why this matters. A campaign is rarely one banner. It is a set, and every size has its own aspect ratio, safe area and reading distance. This guide shows how to produce the full set from one build instead of rebuilding the same idea six times.
What are the standard display ad sizes?
The IAB defines the sizes buyers and ad servers expect. You do not need every one of them for every campaign, but you do need the common core.
| Size | Name | Typical placement |
|---|---|---|
| 300x250 | Medium rectangle | In-content, sidebar |
| 336x280 | Large rectangle | In-content |
| 728x90 | Leaderboard | Top of page |
| 970x250 | Billboard | Premium top of page |
| 160x600 | Wide skyscraper | Sidebar |
| 300x600 | Half page | Sidebar, in-content |
| 320x50 | Mobile banner | Mobile anchor |
| 300x100 | Mobile large | Mobile in-content |
| 1200x628 | Landscape (social/display) | Feeds, native |
| 1080x1080 | Square | Social, native |
A practical campaign set is usually four to eight of these. Start with the medium rectangle and the leaderboard, add the half page and mobile banner, then fill in the rest if the placement plan calls for them.
How to resize a banner ad to all display sizes
1. Open Display Format Builder and add your file
Go to Display Format Builder. The page opens with a drop zone labelled 'Drag & drop or browse' under the line 'Processed locally — your files never leave your device'. Drag your artwork onto the drop zone, or browse to it on your own machine. Nothing is uploaded anywhere; the file is opened in the page and the work happens there.
If you are starting from a screenshot or a product shot rather than finished artwork, it can help to place it in a device frame first with Mockup Generator so the source image already looks like a real ad.
2. Choose the sizes you need
Select the display sizes for your campaign. You are building one campaign across every size, not one file per size. Display Format Builder takes several files at once, so you can also batch a set of source images through the same build if you are producing variants for different products or markets.
On free plans, a batch processes up to 3 files without an account or 5 with one, and each batch counts as a single run. The free daily allowance is 5 runs, or 15 with a free account; Pro unlocks unlimited daily use. See /pricing if you need it.
3. Adapt the layout for each size
This is the part that separates a real campaign set from lazy resizing. A 728x90 leaderboard is a horizontal strip: headline left, call to action right, logo small in a corner. A 300x600 half page is vertical: headline, supporting line, button, logo stacked. A 320x50 mobile banner is a thumbnail: one short line and a button, nothing else.
For each size, adjust:
- Headline length. Shorten it for small sizes. 'Save 40% on running shoes this week' becomes 'Save 40% this week' at 320x50.
- Hierarchy. Decide what the single most important element is at that size and make everything else smaller or remove it.
- Safe area. Keep text and logos away from the edges. Some placements crop or overlay controls.
- Logo size. It should be legible but never the loudest element unless the campaign is a brand awareness push.
- Call to action. At small sizes the button may be the only text that survives. Make it count.
4. Animate the set
Animation works differently per size. A 970x250 billboard can hold a three-step sequence. A 320x50 banner can hold one transition and nothing more. Build the motion so the first frame already communicates the offer, because many placements only show a moment of it.
If your campaign also needs a GIF or a short video, this is where you produce it: Display Format Builder exports exact-size images, GIFs or video from the same build, so the animated and static versions stay consistent.
5. Preview them all together
Preview the full set side by side before you export. This is the step people skip, and it is the step that catches the mistakes: a headline that fits at 300x250 but overflows at 300x100, a logo that disappears against a dark placement, a button that is unreadable at mobile size. Seeing the set together shows you the campaign, not just the files.
6. Export exact-size images, GIFs or video
Export the set. Every file comes out at the exact pixel dimensions the placement expects, which means no last-minute resizing in another app and no soft, upscaled text. Because the work happens locally, there is no queue and no waiting for a server to finish.
7. Reuse the build for the next campaign
Once a campaign set exists, the next one is mostly layout work. Keep the size list and the layout logic, swap the artwork and copy, and you have a new set without redoing the structural decisions.
Why local, in-browser processing beats upload-based banner makers
Most online banner ad makers ask you to upload your creative to their server, process it there and send it back. That has three costs.
Privacy. Your unreleased campaign artwork is a business asset. Sending it to a third-party server means it leaves your control, and you are trusting whatever retention policy that service has. Display Format Builder runs in the page: your files never leave your device, and nothing is uploaded.
Speed. Local processing has no upload time and no download time. A large source image that would take a while to push over a hotel or office connection opens instantly because it is already on your machine.
No file-size caps. Because nothing is being transferred to a server, there is no file-size limit imposed to protect someone else's bandwidth. You can work with the full-resolution source rather than a compressed version.
There is also a practical workflow benefit: no account is required to start, so you can produce a set before deciding whether the tool earns a place in your process.
Common mistakes when building a multi-size banner set
- Scaling one design to every size. A 970x250 shrunk to 320x50 is unreadable. Adapt the layout per size instead.
- Ignoring the smallest size until the end. Design the 320x50 first and the rest gets easier, because you have already decided what the single most important message is.
- Text too close to the edge. Leave a margin. Placement environments are not as tidy as your canvas.
- Too many fonts and weights. Two weights of one typeface is usually enough across a whole set.
- Animation that carries the message. If the offer only appears in frame three, most viewers never see it.
- Forgetting the static fallback. Some placements will not run your animated version. Export stills from the same build.
- One call to action for every size. At small sizes, shorten it. 'Shop the summer sale' becomes 'Shop now'.
Pro tips for campaign banner sets
- Build the size list once and reuse it. Most campaigns use the same core sizes every time.
- Keep a master headline and a short headline. Write both at the start, then choose per size.
- Check the logo at 100% zoom, not zoomed out. Legibility is decided at actual size.
- Batch variants, not sizes. Use the multi-file batch to run several products or markets through the same build, since a batch counts as one run.
- Export stills alongside GIFs. You will be asked for a static version eventually.
- If the campaign also needs social sizes, Social Pack Exporter handles that set in one pack, and Podcast Artwork Pack does the equivalent job for cover art sizes if audio is part of the same launch.
A campaign set is not a pile of exports. It is one idea, translated honestly into each size it will appear in, with the hierarchy rebuilt rather than scaled. Doing that work inside the browser — locally, without uploads, without a queue and without a file-size cap — turns a task that used to take an afternoon of repetitive exporting into a single build you can preview as a whole and reuse for the next launch.