All Google display ad sizes (complete guide)

Google display production used to be discussed as a poster of fixed banner sizes. That still matters in some organizations, but it is no longer the whole story. Modern Google Ads campaigns often run through responsive display or Performance Max workflows, and those workflows ask for image asset groups rather than only a static banner sheet.

That shift is exactly why design teams get frustrated. Marketing asks for "Google display sizes," but production cannot answer with one clean template anymore. The right answer depends on campaign type, asset requirements, logo variants, and whether the campaign still needs fixed-size banners for direct trafficking or legacy ad operations.

Start by separating sourced specs from internal workflow decisions

If your team merges platform requirements and internal production habits into one list, confusion follows immediately. A better approach is to split the work into three layers:

1. sourced Google requirements
2. internal interpretation for the specific campaign type
3. Photoshop production rules that keep outputs editable and consistent

That distinction matters because Google's own specs page now includes multiple image sections for different campaign types. On the same reference page, you will see recurring image buckets like:

• horizontal 1.91:1 at 1200 x 628
• square 1:1 at 1200 x 1200 or 600 x 600 depending the context
• vertical 4:5 at 960 x 1200 or 1200 x 1500 depending the context
• logo variants such as square 1:1 and horizontal 4:1 at 1200 x 300

Those are sourced facts. What your team chooses to build first is the workflow decision.

Why Google display work causes production churn

The usual failure mode looks like this:

• strategy says "let's launch on Google"
• the design team receives a legacy banner list from one stakeholder
• the media team references responsive display from another
• someone asks for Performance Max assets after the first files are already built

Now the same concept is being forced through multiple delivery models. If the Photoshop source file was not built for adaptation, the team ends up doing layout surgery rather than production.

This is why Google display work often feels harder than social adaptation even when the concept is already approved. The complexity is in the asset package, not the initial design.

The sourced Google requirements you should verify first

Before any resizing starts, confirm the campaign type in writing.

Responsive display or image-asset-led work

Google's current specs documentation repeatedly centers the workflow on image ratios rather than only old fixed banners. The most common asset buckets are:

• horizontal 1.91:1
• square 1:1
• vertical 4:5
• square logo 1:1
• horizontal logo 4:1

For many teams, that means the most important production decision is not "How many banners do we need?" It is "Which asset family does this campaign actually need?"

Fixed-size banner deliverables

Some ad ops pipelines still require fixed output sizes like medium rectangle, leaderboard, half-page, or large mobile banner. Those should be treated as an extra distribution layer, not the starting point for the design system. When teams start from fixed banners alone, they often build too many narrow files too early and lose the flexibility to support the broader asset-based campaign.

A better Photoshop workflow for Google display campaigns

Once the campaign type is confirmed, the production team needs a master that can survive reframing.

1. Build one adaptable key visual

Your source PSD should separate:

• hero product or subject
• background extensions
• headline and support copy
• CTA
• logos and legal

This seems obvious, but many campaign PSDs are still handed off as visually finished compositions instead of adaptable systems. That is the root cause of slow Google resizing work.

2. Approve the hierarchy across three shapes first

Before expanding into the full asset set, test the concept in:

• horizontal 1.91:1
• square 1:1
• vertical 4:5

If the concept fails in one of those shapes, no amount of export labor will fix it cleanly later. Review the campaign as a system, not as isolated outputs.

3. Add logos as their own production track

Google's documentation treats logo assets as their own requirements. That means production teams should too. Do not bury logos inside the main key-visual resizing workflow. Keep square and horizontal logo assets on a clean, separate track so they are versioned independently from the campaign art.

What to call "workflow advice" versus "platform fact"

This is where a lot of SEO content gets sloppy. Platform facts come from Google's specs pages. Workflow advice comes from your production judgment.

Sourced factual data

Google currently documents image buckets such as 1.91:1 horizontal, 1:1 square, 4:5 vertical, and dedicated logo formats for responsive display and Performance Max contexts.

Interpretation

The presence of those image buckets means teams should organize approvals around three reusable visual shapes instead of dozens of one-off crops.

Workflow advice

Build and review a master visual in those three shapes first, then expand to the exact campaign deliverables once the system holds together.

That structure keeps the content honest and keeps production teams from mistaking internal habit for platform requirement.

Where manual production usually breaks down

Manual Google resizing breaks for the same reason manual social resizing breaks, but the review load is worse:

• too many PSD duplicates
• no stable crop logic between horizontal and square
• logos handled inconsistently
• versioning chaos when the media plan changes
• export folders full of files with no obvious source-of-truth PSD

If the campaign has to go live across Google and Meta, this multiplies quickly. A designer may be technically capable of producing the files, but the process becomes hard to audit and hard to revise.

Where Smart Resize fits in the Google workflow

Smart Resize is not a replacement for campaign thinking. It is the acceleration layer after the concept and hierarchy are approved.

That makes it useful for Google display production because the real pain is repetitive adaptation. Production teams need to generate multiple sizes, keep PSDs editable, and still move fast when the media team asks for more formats or a revised headline. Smart Resize is built for that stage of the job.

If you want to see the practical setup, the Smart Resize loading workflow and the pricing page are the best internal next steps. They show the tool in the exact context where Google display work gets expensive: one approved key visual, many required output files, and no time for manual banner rebuilds.

A production checklist for Google-ready asset sets

Before delivery, confirm:

• campaign type is documented and agreed
• main image assets cover the required ratios
• logo assets are delivered separately where required
• the master PSD remains the source of truth
• output names identify ratio, platform, and version
• final JPG or PNG exports match the editable PSD set

When that checklist is handled inside a predictable adaptation system, Google display production stops feeling like a file explosion and starts behaving like a repeatable workflow.

The practical conclusion

Google display ad sizes are no longer one static banner chart. They are a moving combination of campaign type, asset requirements, and trafficking context.

The teams that handle this well do one thing differently: they separate sourced platform specifications from internal production decisions. Once that separation is in place, Photoshop adaptation becomes a systems problem instead of a firefight, and tools like Smart Resize can save time where it actually matters.