You have one offer, one landing page, and two very different production choices. In a responsive display ad, you supply images, logos, headlines, descriptions, and a call to action; Google assembles eligible combinations for different placements. In an uploaded ad, you deliver the finished composition—or, with responsive HTML5, the rules that govern how that composition adapts.
The practical answer is simple: use responsive display ads when your message is modular and reach matters more than a fixed hierarchy; use uploaded ads when the idea depends on exact copy order, cropping, line breaks, qualification, timing, or interaction. Many campaigns need both. The mistake is treating “responsive” and “uploaded” as opposite file types rather than different levels of authoring control.
A current platform note matters before production begins. As checked on September 9, 2026, Google says Display campaigns are moving into Google Display Network inventory within Demand Gen. Its migration table lists responsive display ads and uploaded static image ads as supported, while uploaded HTML5 is marked “coming soon” and planned for late 2026; Google also says those timelines can change. Confirm the campaign workflow and format availability in the account before commissioning an HTML5 build. See Google’s Demand Gen migration notice.
The choice is about who assembles the ad
“Responsive” is used for two production systems that should not be confused. A Responsive Display Ad is asset-based: the platform combines the parts. A responsive uploaded HTML5 ad is designer-authored: the file contains fluid rules and breakpoints. A fixed uploaded image locks one composition for one size.
| Format | Who assembles the impression? | What may vary | Production burden | Best fit |
|---|---|---|---|---|
| Responsive Display Ad | Google assembles supplied assets | Asset pairing, text presence, crop, format, and layout | One modular asset pool, then combination QA | Broad coverage, rapid iteration, messages that survive recombination |
| Uploaded static image or GIF | Designer locks each final file | The platform may still choose among eligible sizes and placements | A separate, checked composition for every size | Exact hierarchy, precise typography, tightly coupled claim and visual |
| Responsive uploaded HTML5 | Designer defines fluid behavior and media rules | The layout changes only according to authored rules | Shared code plus breakpoint, interaction, and browser QA | Controlled adaptation, animation, or interaction across viewports |
Google’s own guidance reflects this division. Its Responsive Display Ad creation page says Google automatically generates ads from uploaded assets and that potential ads can appear in thousands of layouts. Its uploaded-ad overview says uploaded ads are built outside Google Ads and give the advertiser control over how the creative appears. That control is valuable, but it is not free: Google also warns that uploaded ads cannot run in every part of Display inventory available to responsive display ads.
Responsive display ads trade fixed hierarchy for flexible coverage
A responsive display ad is not a master banner that the platform merely scales. It is a pool of components. Google can select a headline, a description, a logo, and an image, then arrange or omit elements to fit an eligible treatment. The consequence is more important than any individual specification: every supplied asset must remain useful when separated from the arrangement in which you first imagined it.
Current Google guidance recommends marketing images in horizontal 1.91:1, square 1:1, and vertical 9:16 ratios, with recommended dimensions of 1200×628, 1200×1200, and 900×1600 respectively. Images can be resized for different layouts. Google also advises against baking logos, promotional copy, or button graphics into marketing images, partly because those elements can become repetitive or unreadable when the system adds its own text and controls. The dimensions and image guidance are documented in Google’s Responsive Display Ad best-practices guide.
The text pool has constraints too. Google’s creation instructions allow up to five short headlines of 30 characters or fewer and one long headline of 90 characters or fewer. The current official pages disagree on description length: the best-practices page says 80 characters, while the advanced-format specification table says 90. A conservative production brief should keep descriptions at 80 characters or fewer and verify the live input field before launch rather than choosing the more generous number by assumption.
What you still control in a responsive asset system
You control the truth and quality of the pool. That includes the offer, the focal subject, the available aspect ratios, the business name, and whether each line makes sense beside each image. You can also review advanced-format options before saving the ad.
That last check deserves attention. Google’s advanced options can include smart cropping, text or logo overlays, image expansion, resolution changes, animated images, backgrounds, font selection, and keyword highlighting. The same documentation says descriptions may occasionally be dropped and logo margins may be cropped. These are not reasons to reject the format; they are reasons not to design a concept whose meaning collapses when one description disappears or the crop becomes tighter.
A robust responsive message therefore behaves like a set of complete atoms:
- Each short headline communicates a useful idea without requiring a particular description.
- Each description supports more than one headline without changing the claim.
- Each marketing image has one obvious subject and enough crop tolerance for another treatment.
- Price, discount, product identity, and landing-page promise stay consistent across the pool.
- No crucial qualifier exists only in a line the platform may omit.
Treat the Google preview as a sampling tool, not a guarantee of the exact impression every user will see. Use it to hunt for bad combinations and weak crops. Do not approve the system merely because the most attractive preview looks right.
Uploaded ads lock the file, not the whole impression
An uploaded 300×250 image can preserve the placement of the logo, the line break in “20% off Arc One,” the product crop, the price, and the call-to-action button. That is real layout control. It does not mean the advertiser controls the page surrounding the ad, the device, the eligible slot selected for an impression, or whether another supplied size serves instead.
This distinction prevents two common planning errors. First, a team may assume one beautiful uploaded rectangle covers the whole campaign. It does not. Google’s current uploaded display specifications list many supported dimensions and explicitly suggest also using responsive assets for spaces a custom ad does not fit. Second, a team may export the same composition at several dimensions and call the set complete. A 728×90 leaderboard has radically less vertical room than a 300×600 half-page unit; preserving the idea usually requires reauthoring, not proportional shrinking.
For static and animated image uploads, Google currently accepts GIF, JPG, and PNG files up to 150 KB. The 300×250, 728×90, and 300×600 sizes used in the original example below are all listed in the current specification. Those limits are upload requirements, not evidence that a file has been approved or will serve.
Uploaded HTML5 adds interaction and authored animation, but it introduces another layer of constraints. Google’s current specification caps the ZIP at 600 KB, limits it to no more than 40 files, requires local or specifically permitted references, and gates HTML5 access by account eligibility. Editing an existing uploaded HTML5 ad also requires re-uploading it as a new ad with its own reporting, according to Google’s uploaded-ad overview. Verify these conditions before promising a production route.
Responsive uploaded HTML5 is the middle path
A responsive HTML5 upload can adapt without surrendering assembly to an asset-combination system. In Google Web Designer, a responsive document can use 100% page dimensions, percentage-based positions, and media rules. Those rules can change an element’s position, size, source, visibility, animation, text, or component properties at specific viewport sizes or ranges. See Google Web Designer’s responsive layout overview and media-rule documentation.
The difference is authorship. With a Responsive Display Ad, Google chooses among supplied parts. With responsive uploaded HTML5, the designer decides that, for example, a wide viewport uses a horizontal product crop and one-line headline, while a tall viewport moves the copy below the product and preserves a two-line price block. The file may be fluid, but its behavior is specified.
That middle path is valuable when a concept needs controlled transitions or interaction across multiple dimensions. It also demands more QA: every breakpoint, click area, animation state, asset reference, and permitted environment behavior must be checked. Google Web Designer says static image ads cannot themselves be responsive, though a multi-size workflow can export several fixed sizes from one document; it also says responsive features are not supported in AMPHTML ads. And during the current Demand Gen transition, uploaded HTML5 availability must be verified in the actual account and campaign route.
One fictional offer, built both ways
To make the trade-off concrete, the package for this article uses an original fictional brand, LumaNest, and one offer: the Arc One desk lamp, regularly $100, discounted 20%, for a sample sale price of $80. The example is a teaching artifact—not a Google preview, a live campaign, an approval result, or a performance claim.
Open the interactive layout-control teaching demo to switch among four illustrative responsive arrangements and the three finished uploaded versions. The responsive arrangements were created for explanation; they do not reproduce or predict Google’s serving layouts. The exact copy, dimensions, and asset status are recorded in the example asset manifest.
The responsive asset set
The responsive branch supplies three text-free marketing images and two separate logo files. The subject remains recognizable in each crop, but the composition is not identical: the vertical image gives the lamp and plant more height, while the wide image retains room around the workspace.
| Asset role | File | Dimensions | Deliberate production choice |
|---|---|---|---|
| Horizontal marketing image | HB59_rda_landscape_1200x628_v1.png | 1200×628 | Broad desk context with the lamp as the focal object |
| Square marketing image | HB59_rda_square_1200x1200_v1.png | 1200×1200 | Reframed scene rather than a blind center crop |
| Vertical marketing image | HB59_rda_vertical_900x1600_v1.png | 900×1600 | Tall subject relationship for portrait treatments |
| Landscape logo | HB59_rda_logo_landscape_1200x300_v1.png | 1200×300 | Separate 4:1 brand asset with transparent space |
| Square logo | HB59_rda_logo_square_1200x1200_v1.png | 1200×1200 | Separate compact mark for square placements |
The five short headlines are intentionally independent:
| Short headline | Characters | What it contributes |
|---|---|---|
| Save 20% on Arc One | 19 | Offer plus product identity |
| A calmer desk starts here | 25 | Emotional benefit |
| Focused light, softer room | 26 | Product effect without an unsupported technical claim |
| Meet the Arc One lamp | 21 | Straight product introduction |
| Upgrade your work light | 23 | Action-oriented use case |
The long headline is 68 characters, and all five descriptions in the manifest are 76 characters or fewer. More important than passing a counter, every line remains compatible with the same product, price, discount, and landing-page promise. The marketing images contain no overlaid headline, separate logo, or imitation button, so Google’s own treatment does not duplicate those elements.
The uploaded versions
The uploaded branch uses the same offer but does not merely resize one master:
- 300×250: A vertical split gives the offer, price, and call to action a stable reading column while the product occupies the right side.
- 728×90: The small height forces a much shorter hierarchy. A compact product crop sits between the message and price/CTA block; brand, offer, and one support line remain readable at actual size.
- 300×600: The large portrait crop becomes the visual opening, followed by the offer, benefit, price, and a full-width call to action.
The three original PNGs are 300×250, 728×90, and 300×600. Each file is well below Google’s current 150 KB limit, but none has been uploaded to Google Ads or tested for approval or serving. Their purpose is to show what size-specific authorship buys: predictable internal hierarchy at the cost of more files and narrower inventory coverage.
Use a control test, not a format preference
Do not choose a format because the team “likes control” or “likes automation.” Ask what must remain invariant for the idea to stay truthful and legible.
| Decision question | Responsive Display Ad is viable when… | Prefer an uploaded format when… |
|---|---|---|
| Can the assets be recombined? | Every headline, description, image, and logo pairing remains true | A particular line only makes sense with one image or preceding line |
| Must a qualifier stay next to a claim? | The claim remains complete without fragile adjacency | Legal, price, or eligibility language must be visibly coupled |
| Does the crop carry meaning? | The subject survives resizing and tighter crops | A reveal, comparison, diagram, or before/after relationship must stay framed |
| Are line breaks and typography part of the idea? | Reflow does not change comprehension | Exact lineation, scale contrast, or reading order carries the concept |
| Is interaction or authored motion required? | Static modular assets can communicate the offer | A controlled HTML5 sequence or interaction is essential and currently supported |
| Is broad placement coverage the priority? | The team accepts variable layouts for wider eligibility | The campaign deliberately prioritizes a smaller set of controlled placements |
| How much production can the team maintain? | One quality asset pool is realistic | The team can reauthor, review, and refresh every important size |
Here is the filled decision for LumaNest. The discount claim is simple, the product remains recognizable across ratios, no legal qualifier must remain adjacent, and broad coverage is useful, so a responsive asset set is valid. But the team also wants a high-control visual hierarchy in three priority sizes. The resulting recommendation is a hybrid: responsive assets for flexible coverage, plus uploaded 300×250, 728×90, and 300×600 files for placements where the authored hierarchy earns its production cost.
A different concept would produce a different answer. Imagine a two-panel “glare before / soft light after” comparison where reversing or separating the frames would invert the meaning. That is not a good asset-pool concept without redesign. Put it in an uploaded composition whose relationship is fixed, or simplify the message until each responsive asset can stand alone.
Build a hybrid campaign without creating a measurement fiction
A practical hybrid workflow starts with one message contract, not two unrelated creative briefs. Write down the product name, offer arithmetic, approved benefit language, prohibited implications, landing-page destination, and expiration terms. Then branch production:
- Build the responsive pool as independent atoms: ratio-specific images, separate logos, short headlines, long headline, and concise descriptions.
- Identify the few placements where exact hierarchy adds enough value to justify custom work. Reauthor those sizes; do not scale one layout mechanically.
- Review the responsive branch by testing hostile combinations and aggressive crops. Review uploaded files at their actual pixel dimensions, not only enlarged on a design canvas.
- Verify current campaign-type support, upload limits, account eligibility, click behavior, and policy status before launch.
- Keep offer, destination, audience intent, and naming consistent enough to compare results responsibly.
Do not describe the result as a pure format A/B test unless delivery conditions are genuinely equivalent. Uploaded ads and responsive ads can reach different slices of inventory, and the responsive system can generate many layouts. Performance differences may therefore reflect placement mix, dimensions, or serving behavior as well as the creative format. Break reporting down by format and placement where available, and frame conclusions around the traffic actually delivered.
Preflight the amount of control you chose
For a Responsive Display Ad, confirm that every text asset can stand alone, all image ratios have a purposeful crop, the focal object remains clear at small sizes, and no crucial term is trapped in a description that may disappear. Review the advanced-format choices, inspect more than the favorite preview, and make sure the landing page supports every surviving combination.
For an uploaded image set, inspect each file at 100% size, confirm that minimum readable text has not been sacrificed to preserve a desktop layout, and check dimensions, format, and file size against the current specification. Confirm that each important slot actually has a designed version. For uploaded HTML5, add breakpoint, interaction, animation, click, local-reference, ZIP, file-count, eligibility, and campaign-availability checks.
For both branches, recompute the offer. In the teaching example, 20% of $100 is $20, so the advertised sample price is $80. Check that exact arithmetic, product identity, dates, exclusions, and destination persist in every file and every asset. Layout freedom never excuses claim drift.
Choose the smallest amount of control the idea actually needs
Responsive Display Ads are strongest when the creative idea is modular by design, not when a rigid banner is chopped into platform inputs. Uploaded ads are strongest when an authored relationship—between words, images, timing, or interaction—is the idea. Responsive uploaded HTML5 occupies the useful middle, where adaptation is needed but the designer still writes the rules.
Start by identifying what cannot change without breaking truth or comprehension. Lock only those relationships. Leave the rest flexible. That produces a more useful answer than asking which format is universally better: buy the reach of recombination where the message can survive it, and pay the production cost of control only where control protects the idea.
Sources
- Create a responsive display ad — Google Ads Help.
- Best practices guide for responsive display ads — Google Ads Help.
- About advanced format options for responsive display ads — Google Ads Help.
- About uploading your own display ads — Google Ads Help.
- Uploaded display ads specifications — Google Ads Help.
- Google Display Ads campaigns have a new home in Demand Gen — Google Ads Help.
- Responsive layout overview — Google Web Designer Help.
- Manage media rules and overrides — Google Web Designer Help.
