Display campaigns moving to Demand Gen: which images to prepare
Google is folding Display campaigns into Demand Gen. Prepare the image set Demand Gen uses, then generate each ratio with one Sume image request per size.

If you run Display campaigns, the practical step is to build the image set a Demand Gen campaign asks for, not only the banner sizes Display used. Google's announcement says Display advertisers will manage the Google Display Network inside Demand Gen, with a migration tool coming (read 2026-10-02). Sume cannot run the migration, but it can produce the new ratios from one source image.
What Google says changed
Google's post, dated May 26, 2026, frames this as a move of Display management into Demand Gen. Advertisers keep the option to serve only on the Google Display Network or to widen to other Demand Gen surfaces (read 2026-10-02).
| Item | What the page says |
|---|---|
| Reach of the Display Network | 2 million sites, videos and apps |
| Surfaces in Demand Gen | YouTube, Discover, Gmail, Google Maps and the Display Network |
| Migration | Google will provide updates and a migration tool |
| Display-only option | Still possible: serve only on the Display Network |
Why the creative set is different
Display campaigns lived on banner sizes. Demand Gen places ads on YouTube, Discover and Gmail too, so a set limited to one landscape banner leaves feeds without a native shape. The existing size guides on this blog list the ratios: landscape 1.91:1, square and 9:16 for Shorts.
What Sume does about it
The Image API takes a prompt plus reference images, and lets you set aspect_ratio or, on models that accept custom pixels, image_size. ChatGPT Image 2.5 on Sume requires both edges to be multiples of 16, a maximum edge of 3840 and an aspect ratio of at most 3:1, so check the catalog for the model you pick before asking for an exact pixel size.
Run one request per ratio from the same reference so the product and logo stay the same. The one-reference, four-ratios post shows that flow.
- Pick the reference image once and keep it fixed across ratios.
- Ask for each ratio in its own request instead of cropping a single output.
- Review every output for text and logo errors before upload.
What Sume does not do
Sume does not connect to Google Ads, move campaigns, or read your Display performance history. It returns image files you upload yourself. Read Google's own migration guidance in the Help Center before you move a live campaign.
Sources
Related posts
More in Use cases
- Local Services Ads photos: 640x640, 10 MB, no phone numbers
Local Services Ads business photos need 640 x 640 px or more, up to 10 MB and 100 images per account, with no phone numbers shown. Plan a compliant set.
- Merchant Center: AI product images must keep AI metadata
Google Merchant Center says generative-AI images must contain metadata marking them AI-generated. Check your exported file with exiftool before uploading.
- GPT Image 2.5 ad headline text: quote the copy, test medium vs high
For an ad still with a headline, quote the exact words, state position and type style, and render at medium and high to compare. A Sume script and its cost.
- Ad still from a packshot: tell GPT Image 2.5 what must not move
Turn a product packshot into an ad still with GPT Image 2.5 by listing what must not move: shape, colour, label text. A Sume request and a checklist.
Written by Sume