Check the rendered display ad rather than the uncropped source image

Verify the current format and available transformations

Google describes responsive display ads as combining uploaded assets and provides guidance on image quality, logo cropping and text readability. The guidance checked on November 7, 2026 also notes movement of eligible Display campaigns into Demand Gen. Check the account's actual format and migration state before using a legacy specification.

Record which images, logos, text and supported enhancements can participate in the ad. Treat the source file as input rather than the final composition. An approval for a large promotional tile does not automatically cover a cropped image beside a separately supplied headline. Identify the transformations that could change meaning and build the acceptance cases around those risks.

Review crops for commercial accuracy as well as aesthetics

Inspect representative aspect ratios and small rendered sizes. Check that the product remains recognizable, included components are not confused with props and a crop does not remove the feature that distinguishes the advertised variant. A technically sharp image can still imply a different offer after its surrounding context disappears.

Prefer an asset whose important subject survives the required layouts rather than forcing one crowded composition into every shape. Where necessary, supply separately approved images for different proportions under the supported format. Keep the chosen crop and source version together so a later replacement does not accidentally restore a failed composition. Do not treat automatic focal-point selection as an editorial guarantee.

Test branding and text as separately assembled parts

Preview the logo on light, dark and busy representative backgrounds where supported. Check legibility at realistic size and ensure its proportions have not been distorted. A detailed lockup that works on a presentation slide may become an unreadable block in an ad. Keep essential brand identification in an appropriate usable asset rather than relying on tiny text embedded in a photograph.

Combine images with different eligible headlines and descriptions. Look for duplicated logos, contradictory product variants, repeated text and claims that depend on an optional description. Avoid decorative buttons that suggest an interaction the rendered image cannot provide. If a required qualification cannot be reliably communicated in the format, simplify the claim or choose a suitable approved creative route with the qualified reviewer.

Accept a tested asset set with explicit coverage limits

Record the reviewed layouts, devices or preview modes and the defects resolved. State what was not observable in the available tools. A sample of previews supports a bounded acceptance decision; it does not establish that every possible publisher rendering has been seen.

After launch, inspect available rendered examples and asset evidence for unexpected crops or combinations. Recheck when the format, enhancement settings, image set or campaign migration changes. Keep performance evaluation separate from visual acceptance: a more frequently served image is not automatically more accurate or causally better. The deliverable is a maintainable set that remains understandable under the tested transformations, with an owner for reported exceptions.

Make the reasoning concrete.

A fictional outdoor brand supplies a wide image of a jacket beside a backpack. A narrow crop centers the backpack, while the assembled headline promises the jacket’s waterproof specification and the tiny logo becomes unreadable.

The team accepts the tested asset set rather than the original canvas alone. It records preview limitations and repeats checks when format or enhancement behavior changes.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Transformations

   Which crops, layouts and supported enhancements can affect this asset?

2. Subject

   Does every reviewed crop still identify the advertised offer?

3. Brand

   Is the logo readable and correctly proportioned at realistic size?

4. Combination

   Do image and text remain accurate when assembled differently?

5. Coverage

   Which renderings were checked and which remain unobserved?

Watch for the wrong conclusion.

• Approving only the uncropped source artwork.
• Embedding essential qualifications in tiny image text.
• Treating preview coverage as exhaustive or frequency as proof of quality.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not Google implementation instructions or measured business results. Sources support only the specifically attributed platform facts. Platform controls and eligibility can change; verify current account guidance before implementation.

• Google Ads: Manage your responsive display ads →Primary platform documentation · Supports: Supports asset-based assembly, careful logo cropping and readability concerns for image text. Rendered-meaning checks are original editorial analysis.
• Google Ads: Best practices guide for responsive display ads →Primary platform documentation · Supports: Supports reviewing assets across combinations and checking current Display-to-Demand-Gen migration context. No universal migration date is inferred.