Google Ads Display Size Guide for 2026

You’re staring at a Google Ads asset screen with a familiar problem: which display sizes should you build? The list includes rectangles, leaderboards, skyscrapers, mobile banners, and responsive image ratios. Upload too few, and placements disappear. Upload everything without a plan, and your asset library becomes a collection of designs that rarely serve.

The practical answer is that Google Ads display size planning isn’t a banner checklist anymore. Responsive display ads and uploaded fixed-size ads operate together, each solving a different delivery problem. The strongest campaigns treat images, copy, logos, fixed banners, file limits, and placement reporting as one connected production system.

Why Google Ads Display Size Is a System Problem

Most advertisers begin with a size list. They select a few familiar dimensions, send them to a designer, upload the files, and assume Google will distribute the ads evenly. That workflow misses what happens after launch.

A responsive display ad can assemble the same campaign message into different layouts using supplied images, headlines, descriptions, and logos. An uploaded banner, by contrast, remains locked to the exact dimensions delivered. The campaign may therefore contain a responsive asset system reaching adaptable inventory alongside fixed files competing for specific slots.

Google’s current responsive display specifications center on three core image ratios: 1.91:1 horizontal, 1:1 square, and 9:16 portrait. Recommended examples are 1200 × 628, 1200 × 1200, and 900 × 1600 pixels, with smaller minimums accepted for each ratio, as documented in Google’s responsive display ad specifications.

Plan at campaign level

A size decision affects more than one creative. It determines which devices, publisher layouts, and app environments your campaign can enter. A wide-format image may fit a broad range of placements, while missing square or portrait assets can make other inventory unavailable to the responsive ad.

Use this workflow:

1. Define the message system first. Establish the offer, headline hierarchy, logo treatment, CTA, and landing-page connection before resizing anything.
2. Build responsive ratios as the foundation. Treat horizontal, square, and vertical as distinct compositions, not automatic crops.
3. Add fixed sizes where control matters. Use uploaded banners for exact layouts, known placements, or strict brand requirements.
4. Inspect delivery after launch. Placement and asset reports should determine which files deserve further production effort.

” Practical rule: A size that exists in your design folder has no value until it earns eligibility and delivery in the placements your campaign needs.
The right question, then, isn’t “What’s the best Google Ads display size?” It’s “Which asset mix gives this campaign reach, control, and useful evidence after launch?”

Responsive Display Ad Image Specs at a Glance

Responsive display ads require an asset system, not one universal banner. Google’s current guidance covers 1.91:1 horizontal, 1:1 square, and 9:16 vertical formats. Recommended dimensions are 1200 × 628, 1200 × 1200, and 900 × 1600 pixels. The listed minimums are 600 × 314, 300 × 300, and 600 × 1067 respectively. See Google’s current image asset guidance for the full specification.

Each ratio serves a different placement pattern:

• 1.91:1: The broad horizontal workhorse for desktop-oriented placements and wider native layouts.
• Square, 1:1: A practical fit for in-feed and compact mobile compositions where a wide image can lose the subject.
• Portrait, 9:16: Built for tall mobile slots. It needs a separate composition because a horizontal crop can remove the product, face, or CTA carrying the message.

Google supports 1 to 15 images, with 5 images recommended, in its responsive display documentation. Treat that recommendation as a production baseline, not a quota. One image gives the system little creative variety. A selected set of distinct assets creates more usable combinations without filling the library with near-duplicates.

Minimum size versus production size

Minimum dimensions can make an asset eligible, but they are a weak design target. Recommended dimensions leave more resolution for cropping and rendering when the same source must adapt across placements.

Composition still matters. Keep the subject away from the edges, especially in portrait and square images. As layouts change, Google may reframe the image. A product tight against one border can disappear from the crop even when the original upload looks correct.

File handling also differs between responsive assets and uploaded static banners. The current responsive reference lists image assets up to 5,120 KB. Uploaded display ads commonly use a 150 KB limit, covered in Google’s uploaded display ad requirements. Maintain separate export rules for the two workflows. Responsive assets need adaptable source material, while fixed banners must satisfy stricter file and dimension constraints.

Responsive Ads vs Uploaded Fixed Display Ads

Responsive display ads and uploaded fixed ads solve opposite problems.

With a responsive ad, you provide the ingredients. Google combines images, headlines, descriptions, and logos into layouts that fit available inventory. This is the practical default when you want broad eligibility and don’t need every placement to show an identical pixel-perfect composition.

With an uploaded fixed ad, your team provides the finished unit. A 300 × 250 file remains a 300 × 250 file. Google won’t rearrange the headline, move the CTA, or rebuild the composition for another slot.

Choose based on the control you need

Responsive ads are usually the sensible starting point for a new Display campaign. They reduce the number of finished banners your team must create and let the platform adapt the message to different placements.

Fixed ads still have a place. Use them when a publisher agreement requires a precise unit, when a brand team approves only a specific composition, or when you need to guarantee that a legal line and product arrangement appear exactly as designed. Both formats can run in the same ad group, letting responsive assets cover adaptable inventory while fixed files handle selected placements.

Classic Banner Sizes That Still Drive Placement

A campaign can have strong responsive assets and still miss placements that expect a finished banner. Legacy dimensions remain relevant because many Display Network placements are built around familiar inventory shapes. Google describes 300 × 250 as the single most widely used ad size on the Google Display Network. 320 × 50 remains a standard mobile banner, while 728 × 90 is the familiar desktop leaderboard, as summarized in Google Display banner size guidance.

Treat these dimensions as an asset system, not a checklist of files. Start with the medium rectangle for broad coverage, add the large rectangle or half-page unit when the campaign needs more visual space, then produce mobile and premium desktop formats when placement reporting supports the work.

Desktop anchors

• 300 × 250, medium rectangle: A practical first fixed banner for in-article and sidebar inventory. It usually deserves production before less common sizes.
• 336 × 280, large rectangle: A roomier rectangle for article endings and sidebars. The added space gives the headline, product, and CTA more breathing room.
• 728 × 90, leaderboard: A horizontal desktop unit often placed above content. It can deliver broad access, although its limited height restricts storytelling.
• 300 × 600, half-page: A tall sidebar format with room for a product, benefit, and CTA without forcing the type to become too small.
• 970 × 90, large leaderboard: A wide desktop banner for masthead-style placements. It can reach premium inventory, but delivery may be selective.
• 970 × 250, billboard: A large desktop canvas for high-impact campaigns. Treat it as a placement-specific expansion rather than a default first deliverable.
• 160 × 600, wide skyscraper: A vertical sidebar unit for long-form desktop pages. It is useful when the placement mix includes tall side inventory.

Smaller and less predictable formats

These dimensions can appear in selected inventory, apps, tablets, or regional placements:

• 468 × 60: A classic horizontal banner that still fits older or narrower layouts.
• 250 × 250: A square unit for compact inventory.
• 200 × 200: A smaller square with limited room for creative elements.
• 120 × 600: A narrow skyscraper for specific sidebars.
• 250 × 360: A less common vertical rectangle.
• 580 × 400: A larger custom-style rectangle that may fit selected publisher placements.

Production capacity should determine the sequence. Start with 300 × 250, 728 × 90, 300 × 600, and 320 × 50. Add the less common formats after placement reporting shows a meaningful opportunity. Keep the fixed files alongside responsive assets, since responsive ratios can cover adaptable inventory while these legacy units qualify for placements that require exact dimensions.

Building a Modular Asset Library Instead of One Master Design

A single master design resized into a long list of banners usually fails for a simple reason: aspect ratios change the hierarchy. A composition that works in a wide leaderboard becomes unreadable in a medium rectangle, while a product placed correctly in a rectangle may be pushed out of a skyscraper crop.

A modular library separates the message into reusable parts:

• Headline slot: A short benefit that remains legible in narrow layouts.
• CTA plate: A button or text treatment that can move without covering the subject.
• Product or hero block: The visual proof point, kept flexible enough to scale.
• Logo lockup: A standalone brand element rather than a logo baked into every image.
• Background layer: A color, texture, or image that can expand or contract around the focal content.

Build for recombination

The headline lockup may sit left of the product in a 728 × 90 leaderboard, above the product in a 300 × 250 rectangle, and beside a larger hero block in a 300 × 600 unit. The message stays consistent, but the supporting arrangement changes.

Designers should preserve a safe area around text, logos, and product edges. The plan notes call for a 12 to 15 percent text rule, but that figure isn’t included in the verified Google data supplied here, so treat it as an internal design guideline rather than a platform fact. The practical principle remains clear: keep text concise, high-contrast, and independent from image details that may crop.

Use layered source files, not flattened exports alone. Organize folders by campaign, concept, ratio, and revision. A naming pattern such as campaign_concept_ratio_variant_date makes it easier to identify what changed and prevents old files from returning to production by accident.

Responsive ads benefit from the same component thinking. Google assembles the assets, but your team still controls whether each image, headline, logo, and description belongs to a coherent system. For broader creative research, the Meta Ads Library resource from Excellorix can help teams review how other advertisers structure visual concepts, though the final Google assets still need their own specifications.

Mobile Banner Dimensions and File Size Limits

A mobile slot can reject a creative before performance becomes the issue. Narrow formats leave little room for copy, while heavier files can slow loading and reduce practical delivery opportunities. Build fixed assets alongside responsive images, rather than shrinking one desktop banner for every placement.

The main fixed mobile formats are 320 × 50 and 320 × 100. 300 × 250 and 300 × 600 can also appear on mobile and in apps when the available slot supports greater height. Each dimension needs its own composition, even when the campaign message remains consistent.

Uploaded static display ads commonly have a 150 KB file-size limit, according to Google’s uploaded display ad specifications. File format affects how easily a design meets that limit. Photographic JPGs often compress efficiently, while transparent PNGs with gradients or detailed text can become large quickly.

Export mobile files separately

A desktop asset reduced to mobile scale usually makes the headline too small, weakens product visibility, and leaves the CTA competing with decoration. Give each mobile size a clear job:

• Keep one focal point: Use one product or visual subject instead of a narrow collage.
• Shorten the message: Retain the benefit and CTA, then remove supporting copy.
• Use strong contrast: In-app backgrounds and surrounding content vary widely.
• Compress before upload: Choose JPG for photographic scenes. Use PNG when transparency or sharp graphic detail justifies the larger file.
• Check motion carefully: Animated GIFs have separate technical requirements. Animation does not exempt a file from Google’s upload rules.
• Preview on a real phone: Check type size, contrast, tap-area context, and how the creative sits inside an app.

The limit is a production constraint, not a final checklist item. It pushes the mobile asset toward a simpler composition that communicates before the user scrolls away.

Regional and Market-Specific Display Inventory

A size that performs reliably in one market may be less useful elsewhere. Google’s own uploaded display specifications preserve country-specific formats, including 930 × 180 for Denmark, which demonstrates that the ecosystem has never depended on one universal banner dimension. The regional example appears in Google’s uploaded display ad documentation.

Some formats are also described as limited or regional-use placements. Coverage from ScalixAI’s Google Display size analysis highlights examples such as 240 × 400 and 980 × 120, while noting that inventory and benchmark behavior can differ by format and market.

Audit by country, not only by campaign

If a campaign expands internationally, duplicate the creative audit by geography. Review where impressions serve, which dimensions receive eligibility, and whether the design still works after translation. A longer German headline, a different Spanish CTA, or a right-to-left layout can change the composition enough to require a new asset rather than a copy edit.

Don’t copy a North American asset pack into every market and assume the report will sort it out. Build a core responsive library, then add regional fixed sizes only when country-level reporting shows a real placement gap. That approach controls production cost while leaving room for local inventory.

Why Optimizing Only for Legacy Sizes Leaves Reach on the Table

Legacy banners are easy to understand. You can see a 300 × 250, 728 × 90, or 160 × 600 in a folder, inspect it in a preview, and know exactly what will render. That clarity encourages teams to treat those formats as the entire Display strategy.

The problem is that fixed banners can enter only the slots that accept their dimensions. Responsive assets can adapt across the ratios Google’s current delivery model requests. Google explicitly recommends 1200 × 628 and 1200 × 1200 responsive images, and its documentation supports a broader asset-based workflow rather than a single fixed banner, as explained in Google’s responsive display asset guidance.

Responsive shouldn’t replace every fixed unit. It should act as the volume and adaptability layer, while fixed sizes provide deterministic control for inventory that demands an exact file. The hidden cost of a legacy-only plan is not necessarily poor performance inside the placements you reach. It’s the auctions and layouts your campaign never becomes eligible to enter.

A useful audit asks three questions:

1. Which fixed sizes are serving? Keep production attention on files with real delivery.
2. Which responsive ratios are missing? Add the ratio that corresponds to the placement gap.
3. Which assets are eligible but weak? Improve the image or message rather than adding another near-identical dimension.

The mix matters more than allegiance to one format. Legacy-only optimization can make reports look tidy while leaving adaptable mobile, native-style, and app inventory underrepresented.

Testing and Placement Reporting for Display Sizes

Treat size selection as a live optimization variable. Start with one campaign or ad group and create a controlled comparison between responsive image assets, rather than changing every banner and asset at once. The point isn’t to declare one universal winner. It’s to identify which creative structures earn useful delivery in your specific placement mix.

A practical reporting loop

1. Review placements: Use the Google Ads Placements report to see domains, apps, and other environments where the ads served.
2. Separate environment signals: Compare desktop, mobile web, and app delivery instead of relying only on account-level totals.
3. Inspect responsive assets: Use the asset report to identify images and combinations receiving delivery.
4. Find fit problems: A size that earns impressions but produces weak business outcomes may have a message, landing-page, or placement fit issue.
5. Refresh selectively: Retire assets that consistently under-deliver after the campaign has accumulated meaningful evidence. Don’t replace the whole library at once.

Use placement reporting to distinguish a delivery problem from a conversion problem. If a 300 × 250 serves heavily but produces poor-quality traffic, adding more 300 × 250 variants won’t solve the underlying issue. If portrait assets receive no delivery, check eligibility, campaign settings, audience constraints, and available inventory before concluding that portrait is ineffective.

For account structure and automation context, teams can also review Excellorix’s guide to AI automation and PPC campaign management. The operating principle is straightforward: change one meaningful variable, record what happened, and preserve enough consistency to interpret the result.

Connecting Display Sizes to Campaign Workflow

Creative specifications should enter the campaign workflow before launch, not after delivery problems appear. Start with the modular library, approve the responsive ratios, and then prepare fixed banners for the placements that justify exact control.

Inside Google Ads, keep responsive assets grouped by campaign objective and message. Upload the strongest square assets first, then add portrait where mobile-oriented eligibility matters. Fixed banners should remain clearly labeled by dimensions so a designer or buyer can identify the correct file without opening every export.

Placement exclusions also connect to sizing. If an app environment repeatedly delivers unsuitable traffic, exclude it based on reporting evidence rather than blaming the mobile format itself. Device, audience, frequency, and bid decisions should be evaluated alongside the creative environment.

Sizing also affects refresh cadence. A new offer may require a full responsive asset update plus only a few fixed banners, while a brand refresh may require every locked dimension to be rebuilt. Ongoing Google Ads account management from Excellorix describes this broader operating model, where creative, bidding, reporting, and landing-page decisions stay connected.

The campaign team should therefore maintain:

• An asset register: Ratio, dimension, message, status, and owner.
• A placement view: Where each format serves.
• A testing log: What changed and why.
• A refresh schedule: Which assets need replacement and which are still earning delivery.

Quick Reference Table for Every Display Size Covered

Use this matrix to brief a designer, review an existing campaign, or decide which files belong in the next production batch. A display campaign usually needs two asset tracks: responsive images built around ratios, and uploaded static ads prepared at exact pixel dimensions. Keep those tracks separate in the asset library so a missing fixed banner does not get confused with an incomplete responsive set.

The table is a planning reference, not a production checklist that requires every file. Responsive JPG and PNG assets cover ratio-based delivery, while uploaded static ads may use JPG, PNG, or GIF under Google’s format and size rules. Build the responsive set first, then add fixed dimensions that placement reports or regional requirements justify. Older formats can remain in the library, but label them by size and delivery evidence rather than exporting them automatically for every campaign.

A clean naming convention reduces avoidable errors. Include the campaign, message, format, and pixel dimensions in each filename, and keep responsive ratio variants distinct from fixed banners. Review delivery by asset and placement before requesting another batch from design.

Excellorix helps businesses manage Google Ads across Display, Search, Shopping, Performance Max, and YouTube, with creative iteration and landing-page support connected to campaign performance. Visit Excellorix to discuss a display asset system built around your placements, reporting, and growth goals.