New Banner Ads

Official boundaries for banner formats, flexible sizing and accessibility

Google Ads publishes uploaded display-ad specifications for its network, including supported image, AMPHTML and HTML5 configurations, file limits, dimensions and campaign-dependent eligibility. Google also notes that some sizes can be regionally available. These are Google product requirements, not universal banner standards or performance promises. IAB's New Ad Portfolio describes flexible ad-size guidance intended for varied screens and devices; it does not prove that every publisher or network accepts each format. WCAG 2.2 is a W3C Recommendation covering web-content accessibility across devices, while acknowledging that the guidelines do not address every user need. Use each source for its stated purpose: confirm the receiving platform's current asset rules, use flexible-size guidance only where supported, and test the rendered ad and destination against relevant accessibility criteria. Do not convert specifications into claims about attention, click rate, viewability or conversion.

• Uploaded display specifications from Google Ads - Google-specific formats, sizes, files and eligibility, not a universal inventory standard
• IAB New Ad Portfolio creative guidelines - industry flexible-size guidance whose acceptance must be checked with each seller
• W3C Web Content Accessibility Guidelines 2.2 - web accessibility recommendations across devices, not a guarantee that all user needs are met

Write the banner decision brief

State which business decision the new banner must inform. Name the audience hypothesis, placement family, campaign stage, destination, accepted outcome and review owner. Define the largest release the test may authorize before creative discussion begins.

Distinguish a design refresh from a message test, offer test or placement test. If several variables change together, say so and treat the result as a package comparison. A visual preference vote cannot substitute for evidence from the intended campaign job.

Inventory the receiving placements

List the networks, publishers, page positions, apps and responsive containers expected to receive the assets. Obtain current specifications from each receiving system. Do not assume that an industry format name means identical rendering or eligibility everywhere.

Record fixed, fluid, responsive or assembled behavior, plus device and regional limits. Identify unsupported combinations before production. A large file library is not coverage when many files cannot enter the planned inventory or lose the message after cropping.

Build a claim hierarchy

Give the banner a recognizable source, one main supported claim, any qualification needed to understand it and one clear action. The first frame or static fallback should preserve the essential meaning without requiring animation.

Remove competing headlines and decorative labels that create false hierarchy. A viewer may see the asset briefly or at a small size. Clarity means the offer and condition remain understandable, not that every campaign detail is compressed into the banner.

Substantiate before designing

Create a claim record containing the exact wording, evidence owner, source, market, product scope, approval date and review trigger. Include comparative, environmental, price, savings and performance statements. Design should not outrun the evidence.

If support applies only to one model, customer group or period, carry that boundary into the creative and destination. Do not hide a material limitation in an unreadable line. Revise or remove claims that cannot be supported under the planned placement conditions.

Choose a layout family deliberately

Select a layout based on available area and message order: image-led, product-led, typographic, offer-led or another documented pattern. Define how logo, headline, evidence cue, qualification and action adapt across aspect ratios.

Avoid stretching one composition into every shape. Create related layouts that preserve semantic order while moving elements. Store the mapping between source copy and each rendition so a correction can be applied across the family without leaving an outdated size live.

Plan responsive assembly

For systems that combine uploaded assets, document which headlines, descriptions, logos and images may appear together. Preview supported combinations and remove assets that produce contradictory, repetitive or incomplete messages.

Do not judge only the hand-picked best preview. Automated assembly can create combinations that no designer arranged manually. Retain the asset set, campaign settings and preview date so a delivered result can be traced to the eligible components.

Verify fixed-size files

Check dimensions, aspect ratio, file type, byte limit, animation behavior, border treatment and click destination against the live platform rules. Validate the exported file, not only the editable design document.

Use a consistent naming and version convention. Reject files with hidden overflow, unreadable text, unexpected transparency or outdated claims. Platform acceptance confirms technical eligibility, not that the banner is accessible, truthful or commercially useful.

Treat animation as optional communication

Put the core proposition in the opening state and ensure the final state retains identity and action. Use motion to clarify sequence or draw limited attention, not to make a disclosure appear briefly and disappear.

Test timing, loops, flashing, motion sensitivity and static fallback under the receiving system. If animation is blocked or unsupported, the remaining frame must still make sense. Do not claim that an animated asset will outperform a static one without a controlled result.

Design a clear action

Use action text that describes the next step, such as compare options or view eligibility, when accurate. Make the control visually distinct without mimicking browser, device or publisher interface.

Align the action with the landing state. A banner promising details should not open an unrelated sign-up gate. Record the destination and deep-link behavior for every creative ID, including fallback when an app or page state is unavailable.

Keep qualifications readable

Place material conditions where they can be perceived in the rendered asset or use a claim that remains accurate without hidden context. Test text size, contrast, duration and cropping in each planned container.

A disclosure cannot repair a misleading headline when it contradicts the main impression. Review the complete creative and destination together. Escalate uncertainty rather than shrinking a crucial condition until it technically exists but cannot be understood.

Check contrast and non-text meaning

Test text and important graphical objects against their actual backgrounds, including imagery and animation frames. Preserve meaning without relying only on color. Supply alternatives where the delivery system permits them.

WCAG provides web-content criteria, but the banner's host and format may expose different technical controls. Use the relevant criteria as a review framework and test the complete destination. Do not announce universal accessibility from a single automated score.

Protect touch and close behavior

On mobile placements, inspect the action area relative to edges, publisher controls and any close button. Avoid accidental activation caused by overlapping or shifting elements. Check orientation and zoom behavior where applicable.

Separate tap rate from usable destination entry. Sudden increases can come from layout or placement changes rather than greater interest. Review rapid returns and duplicate interactions before rewarding a new design for volume alone.

Use imagery with an assigned job

Choose imagery that identifies the product, demonstrates a relevant state or supports recognition. Document rights, crop rules and alt or accessible labeling where the format provides it. Decorative imagery should not displace the claim.

Test focal points in every ratio and at realistic rendered sizes. Avoid visual evidence that implies an unsupported result, interface or endorsement. A stock photograph cannot prove customer experience or substitute for substantiation of the written offer.

Preserve brand recognition without clutter

Define the minimum recognizable brand treatment for light, dark and image backgrounds. Confirm logo clear space and contrast in the smallest approved rendition. Keep partner marks only when permission and relationship wording are current.

Do not let repeated logos, badges and labels crowd out the message. Brand consistency concerns source recognition and meaning, not identical pixel placement across every shape. Record approved exceptions for narrow or flexible containers.

Connect banner and landing message

Carry the main claim, qualification, visual cue and action into the first useful destination state. Test redirects, parameters, consent layers, page readiness and confirmation. The journey should explain any detail that could not fit in the asset.

Version the landing page with the banner. If the destination changes during a test, mark a new observation period. Do not attribute a decline to the creative when a form, price, stock state or mobile layout changed underneath it.

Create a production quality gate

Require claim approval, spelling review, export validation, destination check, accessibility review and rendering evidence before release. Use a checklist tied to creative IDs and named owners instead of relying on memory.

Keep source files, final assets and approvals together. A fast correction is possible only when the live version can be identified. Block release when a material condition, link or format rule remains unresolved.

Run a fair creative test

Hold audience, placement, offer, destination, schedule and accepted outcome stable while comparing the intended creative change. Use an allocation rule that prevents one variant from receiving only the easiest inventory.

Predefine the primary outcome, observation window and stop rule. Mark exploratory breakdowns. If the delivered source mix differs materially, narrow the conclusion or rerun rather than declaring one banner universally stronger.

Diagnose the response path

Report eligible requests, served impressions, rendered or viewable evidence where available, interactions, usable visits, accepted actions and reversals as distinct stages. Keep provider definitions beside each number.

Look for the first material loss by variant and placement. A banner can fail at rendering, message comprehension, destination continuity or qualification. Changing the artwork again without locating the loss may repeat the same problem in a new style.

Account for full creative cost

Include concept, copy, design, resizing, animation, localization, approvals, trafficking, verification and maintenance. Track the burden created by many variants and repeated corrections.

Compare complete cost with accepted value and learning value. A cheap asset that cannot enter useful inventory or needs constant repair may be less economical than a smaller, well-governed family. Keep currency and accounting period aligned.

Retire and archive safely

Set expiration and review triggers for price, feature, inventory, policy and seasonal claims. Remove superseded files from active libraries and campaigns. Confirm that old destinations and dynamic feeds cannot restore obsolete messaging.

Archive the creative ID, files, claim record, placements, dates, results and reason for retirement. A reliable archive prevents an apparent winner from being reused outside the conditions that produced it and makes corrections traceable.

Close with a banner release record

Document the decision brief, platform rules, claim evidence, layout family, asset map, rendered checks, campaign cells, response path, accepted outcomes and complete cost. Link the record to the live creative IDs.

Choose release, revise, retest or retire. State the next exposure, owner and rollback condition. A new banner is ready when its meaning, technical fit and evidence survive the actual placement, not when the design file receives approval.

Create a placement exception register

List placements where the standard asset family cannot preserve message order, qualification or action. Record the specific container behavior, affected campaign, temporary treatment and owner. An exception should explain why a dedicated rendition or exclusion is safer than forcing the default file into an unsuitable slot.

Review exceptions after platform or publisher changes and retire workarounds that are no longer needed. Keep delivery from unknown containers in an observation state until rendered evidence exists. A general banner approval should never override a documented placement failure simply because the same creative performed correctly elsewhere.

Coordinate creative and trafficking versions

Connect every approved export to a campaign asset ID, destination, start date and responsible trafficker. Record substitutions made inside the receiving platform. The creative library and campaign interface must agree on which version is live before results can be attributed to a design decision.

After replacement, verify that cached previews, copied campaigns and scheduled groups do not retain the superseded file. Start a new evidence period when an asset or destination changes. Without that boundary, results from two materially different banners can be merged under one friendly name.

Review flexible banners at extreme ratios

For flexible or responsive placements, test the narrowest, widest, smallest and image-limited combinations that the receiving product can produce. Check source recognition, claim continuity, qualification, cropping and action text. A comfortable middle preview does not establish acceptable behavior at the edges.

Remove components that create broken combinations and document the tradeoff between coverage and message control. If a product does not reveal every possible assembly, state that uncertainty and monitor delivered examples. Do not promise pixel-identical presentation from a format designed to adapt.

New banner ad release matrix

Each banner moves forward only when claim, format, rendering, journey and outcome evidence are present.

Retained banner advertising resources

Existing banner-design links, graphics and campaign routes remain below in their established order. They support further review but do not verify present platform eligibility, file limits, placements, viewability, interaction quality or business results for a new asset.

New banner ad questions