Display Ad Sizes: Meta and Web Specs Guide

Most guides about display ad sizes are really inventory dictionaries. They list 300×250, 728×90, 320×50, and a few other familiar units, then leave you to guess which files deserve design time. That advice is incomplete. The hard part today isn't memorizing every banner rectangle. It's deciding which placements matter, which ratios travel across inventory, and how to export assets that survive platform rendering without cropping the message.

A practical buying workflow starts with placement context. Google now recommends a small group of responsive image ratios for broad coverage, while Meta's hierarchy favors portrait creative for feed, Stories, and Reels. Fixed IAB units still matter on the open web, but they should support a deliberate inventory plan rather than dictate your entire production calendar. The sections below treat pixels as a media-buying decision, not a trivia exercise.

Table of Contents

• The Shift From Fixed Banners to Responsive Ratios
  • Ratios first, pixels second
• Legacy IAB Standards and Modern Open Web Inventory
  • The fixed units worth keeping
  • Where legacy production stops paying
• Meta Placement Specifications and Portrait Hierarchy
  • Match the canvas to the screen
• Navigating Safe Zones and UI Overlap Prevention
  • Build a protected content field
• File Types and Compression Settings for Ad Networks
  • A format decision that survives review
  • Color and compression checks
• Scaling Creative Production Across Multiple Ratios
  • A production model that stays controlled
  • Avoid the batch-production trap
• Export Settings and Pre-Upload Quality Checks
  • The five-pass export check
• Quick Reference Matrix for Campaign Objectives
  • Display 廣告尺寸與比例矩陣
  • 如何使用矩陣
• Troubleshooting Common Ad Upload and Delivery Errors
  • When the platform rejects the aspect ratio
  • When text warnings appear
  • When the file looks soft or colors shift
  • When an approved ad does not deliver well

<a id="the-shift-from-fixed-banners-to-responsive-ratios"></a>

The Shift From Fixed Banners to Responsive Ratios

A campaign rarely needs a separate design for every familiar banner unit. Responsive delivery lets platforms combine supplied assets and adapt them to available placements, so production should begin with ratios and placement needs. Google's current responsive display specifications center on horizontal 1.91:1 at 1200×628 pixels, square 1:1 at 1200×1200 pixels, and vertical 9:16 at 900×1600 pixels, with smaller minimum dimensions also listed in the Google's responsive display ad specifications.

This changes the production brief. Build a message system that works across horizontal, square, and portrait canvases. The image, headline hierarchy, logo treatment, and call to action should remain recognizable after each adaptation. A wide composition can give a long headline room, while a portrait version may need a shorter line and a tighter focal point.

The Google specifications allow 1 to 15 images per ad and recommend 5 images, which supports an asset-set workflow rather than a single fixed banner. Fixed-size files still have a place. Buyers should reserve custom production for placements where a fixed unit creates genuine access or visual value.

<a id="ratios-first-pixels-second"></a>

Ratios first, pixels second

Aspect ratio controls composition, while pixel dimensions affect rendering quality. Make both decisions together. A product shot framed for portrait can lose its focal point in a wide rectangle, and a long headline that fits 1.91:1 may become cramped in 9:16.

Use this production order:

• Build the concept: Set the product focus, proof point, offer, and action before opening several canvases.
• Create the ratio set: Adapt the idea to horizontal, square, and vertical compositions. Do not stretch one file across every placement.
• Reserve fixed units selectively: Add open-web rectangles or leaderboards only when the media plan calls for them.
• Inspect the assembled result: Responsive systems can combine assets in ways that pass technical checks but weaken hierarchy or readability.

Practical rule: Design for the placement where the user will see the ad, then extend the idea across ratios. A desktop banner alone is not a mobile strategy.

Keep coverage separate from performance testing. Ratios help the campaign reach more inventory. Creative angles, hooks, imagery, and calls to action provide the variables for testing. That separation prevents a new canvas from being mistaken for a new advertising idea, and it keeps production focused on assets that can both upload cleanly and communicate at the intended placement.

<a id="legacy-iab-standards-and-modern-open-web-inventory"></a>

Legacy IAB Standards and Modern Open Web Inventory

Responsive production has expanded available placements, yet the open web still depends on established fixed units. The historic IAB portfolio gives publishers and buyers a shared vocabulary, including the 300×250 Medium Rectangle, 336×280 Large Rectangle, 728×90 Leaderboard, and 160×600 Wide Skyscraper (Google's standard display ad size guidance).

Each dimension corresponds to familiar page inventory. Rectangles commonly sit within article content, leaderboards span prominent desktop areas, and skyscrapers fit tall side columns. Their value comes from the fact that publishers still build inventory around them.

<a id="the-fixed-units-worth-keeping"></a>

The fixed units worth keeping

The 300×250 remains a practical anchor for common in-content placements. The 336×280 provides a larger rectangle where publishers support it. The 728×90 still fits broad desktop headers, while 160×600 and 300×600 serve tall sidebar inventory. The larger unit also gives brand-led creative more room.

A working open-web set can include 300×250, 728×90, 160×600, 300×600, 970×250, 320×50, and 320×100, plus related rectangle, skyscraper, leaderboard, and mobile formats listed in Google's Display & Video 360 guidance (open-web IAB standard banner overview). Treat this as an inventory map, not a production checklist. Confirm the planned publisher mix before creating every variation.

<a id="where-legacy-production-stops-paying"></a>

Where legacy production stops paying

Long-tail units can consume design hours without creating meaningful access. The 468×60 banner is increasingly treated as a legacy format with declining availability, so request it for compatibility only when the media plan requires it (2026 display ad dimensions analysis).

Prioritize adaptations that match confirmed inventory. Premium publisher buys may justify a leaderboard or billboard-style unit. Broad automated delivery often benefits more from responsive ratios paired with a compact fixed set. That decision also reduces upload checks, version control, and last-minute resizing before launch.

<a id="meta-placement-specifications-and-portrait-hierarchy"></a>

Meta Placement Specifications and Portrait Hierarchy

Meta creative planning should start with the placement, not with the square file many teams still use as a default. The working hierarchy is 4:5 for feed, 9:16 for Stories and Reels, and 1:1 as a flexible fallback for placements that cannot use portrait creative (Meta ad specifications overview).

For feed, export 1440×1800 pixels at 4:5 when the design benefits from vertical space. For Stories and Reels, use 1440×2560 pixels at 9:16. Keep a square fallback at 1440×1440 pixels for compatible placements, but recompose it rather than relying on automatic cropping. The same practical guidance places typical minimum widths around 600 pixels. That threshold supports acceptance, not necessarily a sharp, adaptable production file.

<a id="match-the-canvas-to-the-screen"></a>

Match the canvas to the screen

Portrait creative takes up more mobile feed space than a short horizontal banner. The added height gives the product, supporting message, and action room to establish a clear sequence. It also makes weak hierarchy obvious. If the product, headline, and CTA compete for the same area, a taller canvas will not solve the layout.

Use this production order:

1. Build the 4:5 feed version first when feed delivery drives the campaign. Keep the product and primary promise visually dominant.
2. Create a native 9:16 version for Stories and Reels. Do not stretch the feed file or fill the added space with an empty background.
3. Prepare 1:1 as a controlled fallback. Reposition the headline and product so the square version has its own hierarchy.
4. Review every placement preview. A file can meet the ratio requirement while its CTA falls beneath interface elements or disappears during cropping.

Export at the specified dimensions even when the platform accepts smaller files. Higher-resolution source material gives the platform more room to render and crop without making the design sharper by itself. Native compositions also prevent a subject placed near one canvas edge from being cut off in another placement.

For repeatable production, name files by placement and ratio, then upload each version against the intended placement before launch. This catches the common failure where one acceptable file is reused everywhere and the wrong crop controls the message.

<a id="navigating-safe-zones-and-ui-overlap-prevention"></a>

Navigating Safe Zones and UI Overlap Prevention

Correct dimensions won't protect text that sits underneath interface controls. Stories and Reels place platform elements over the creative, while feed environments add profile, engagement, and navigation treatments around the ad. The safest approach is to treat the canvas as a full-bleed background and establish a central content field before placing copy.

<a id="build-a-protected-content-field"></a>

Build a protected content field

Keep the most important information away from the top and bottom edges of a 9:16 composition. Place the logo, central promise, product proof, and primary action where they remain readable if the platform adds controls or crops the preview. Decorative elements can occupy the edges because losing them won't change the meaning.

A reliable hierarchy looks like this:

• Primary promise: Place it in the visual center, with enough contrast to survive compression.
• Product or subject: Keep the focal point clear of likely control clusters and avoid pushing it against the lower edge.
• Brand mark: Use a consistent position that doesn't compete with native profile or account treatments.
• CTA treatment: Leave breathing room around the action and check it in the actual placement preview.
• Background detail: Extend it to the bleed, but don't rely on edge details to explain the offer.

For 4:5 feed assets, the central field can be denser because the format isn't full-screen in the same way. Even there, don't put a legal qualifier or key product detail at the extreme bottom. Cropping and UI behavior can vary between previews, feeds, and devices.

You can also review the platform's privacy information before connecting creative tools or account workflows through ProdSnap's privacy policy. That check belongs in a production process whenever assets, product references, or brand materials move through a third-party system.

The following video provides a visual reference for evaluating mobile composition and protected areas:

<iframe width="100%" style="aspect-ratio: 16 / 9;" src="https://www.youtube.com/embed/ysxHAP01cOw" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>

Don't approve a creative from the design file alone. Open the ad preview, inspect the smallest readable text, and ask whether the message still works with the native controls surrounding it. A safe zone is useful only when it protects meaning, not merely empty space.

<a id="file-types-and-compression-settings-for-ad-networks"></a>

File Types and Compression Settings for Ad Networks

Choose the format based on the visual, then compress for the placement. PNG works well for sharp typography, flat color fields, logos, and transparent elements. It preserves hard edges, but photographic scenes and textured backgrounds can make the file unnecessarily heavy.

JPEG is usually the better fit for photography, lifestyle imagery, gradients, and product scenes with subtle tonal changes. Compression can soften small text and high-contrast edges. Export from a clean source, then inspect the compressed file at the size viewers will see.

<a id="a-format-decision-that-survives-review"></a>

A format decision that survives review

Use this quick decision table before exporting:

Creative characteristic	Preferred format	Main risk
Text-heavy graphic or logo treatment	PNG	Larger files or slow loading when the artwork includes complex photographic detail
Product photography or lifestyle scene	JPEG	Compression artifacts around type, edges, and fine product features
Motion concept	MP4 where the placement supports video	Separate duration, codec, audio, and platform requirements

Open-web inventory often applies tighter file-weight limits than social uploads. The 150KB maximum from the Google guidance cited earlier means a JPEG with controlled quality may be necessary even when PNG looks cleaner in the design application. Treat that limit as an open-web upload requirement, not a universal rule for every network.

Meta uses a different workflow. Its placement ratios and file handling should be evaluated separately, so do not force an open-web compression target onto a social asset. Export for the destination, then check image clarity, upload acceptance, and the platform preview before approving the file.

<a id="color-and-compression-checks"></a>

Color and compression checks

Use sRGB for predictable web color rendering. Convert the final file instead of assuming the design application's working profile will survive upload and platform processing.

For JPEG, lower quality gradually. Stop when text develops ringing, edges break up, or product details lose definition. For PNG, remove unnecessary metadata and confirm that the export is not carrying oversized hidden layers from the design file. A small export checklist prevents repeated upload failures across ratios.

MP4 suits motion-first placements, but it adds variables that static assets avoid, including duration, codec, audio, and placement support. If the first test concerns the message or offer, start with a sharp static asset. That gives the campaign a cleaner baseline before motion variants introduce additional delivery and interpretation issues.

<a id="scaling-creative-production-across-multiple-ratios"></a>

Scaling Creative Production Across Multiple Ratios

Manual resizing fails because it treats adaptation as a mechanical crop. A winning 1:1 ad usually contains a relationship between headline, product, proof, and CTA that must be rebuilt for 4:5 and 9:16. Stretching the canvas preserves dimensions, not hierarchy.

Start with a reference-driven system. Save the visual references, product photos, competitor examples, approved brand colors, fonts, and voice rules alongside the original concept. Then define which layers can move and which must remain fixed. The product identity and core claim may be locked, while background treatment, headline placement, and supporting imagery can change by ratio.

<a id="a-production-model-that-stays-controlled"></a>

A production model that stays controlled

Use one seed concept and create deliberate adaptations:

• Square: Compact composition for broad reuse. Keep the focal object central and reduce copy to the strongest line.
• 4:5: Use the additional height for product context, proof, or a clearer CTA without turning the asset into a poster.
• 9:16: Build a vertical visual path from opening hook to product to action, while reserving the interface-sensitive areas described earlier.
• Iteration layer: Change one variable at a time, such as headline, color, or product crop, so the team knows what changed.
• Winner library: Save approved concepts and strong performers as references for the next batch, not as files to duplicate blindly.

A tool such as ProdSnap can support this workflow with swipe-file storage, reference-driven generation, brand kits, product context, iterative controls, and outputs designed for 1:1, 4:5, and 9:16 Meta placements. The important operational principle is not automation by itself. It's keeping research, concept selection, ratio adaptation, and revision in one traceable loop.

<a id="avoid-the-batch-production-trap"></a>

Avoid the batch-production trap

Generating many files isn't the same as generating useful tests. Tag each asset by angle, audience, product, ratio, and revision reason. If a designer changes the background, headline, and offer together, the resulting performance signal becomes difficult to interpret.

A strong workflow also includes a human review pass. AI or template systems can preserve a ratio and brand kit while still producing awkward line breaks, incorrect emphasis, or a product crop that weakens the claim. Multi-ratio production should accelerate judgment, not replace it.

<a id="export-settings-and-pre-upload-quality-checks"></a>

Export Settings and Pre-Upload Quality Checks

Upload failures often begin before the file reaches Ads Manager. The wrong canvas, an embedded color-profile mismatch, or excessive compression can pass an in-app review and fail after upload. A focused preflight catches these problems before the campaign enters approval.

<a id="the-five-pass-export-check"></a>

The five-pass export check

Pass one, confirm the format. Use PNG for crisp, text-led artwork and JPEG for photographic compositions. Keep the applicable file-weight limit in view for open-web inventory. The Google requirements cited earlier specify under 150KB for image assets, so a large PNG can create an avoidable upload problem when the design contains only limited text.

Pass two, verify the canvas. Inspect width, height, and ratio in the exported file, not only in the design document. Compare Google assets with the responsive dimensions cited earlier, then confirm that Meta files use the intended 4:5, 9:16, or 1:1 canvas. A correctly named file can still contain the wrong dimensions.

Pass three, convert to sRGB. This helps limit color changes between the design application, browser preview, and ad platform. After conversion, inspect skin tones, brand colors, white backgrounds, and dark gradients. Pay particular attention to subtle shadows that can flatten during export.

Pass four, inspect safe zones. Open the asset in a placement preview. Review the top and bottom of vertical creative, feed cropping, and square fallback behavior. A logo may fit the canvas and still sit beneath interface controls or lose contrast against the surrounding UI.

Pass five, perform final QA. View the file on a large screen and a phone. Zoom out until the creative is close to its expected viewing size. The product, message, and action should remain obvious without relying on fine print.

For teams producing multiple Meta-ready variations, ProdSnap's pricing page provides a place to review available workflow options. Whatever tool you use, store approved exports in a clean folder with ratio and version names. Separate final files from working drafts, and open each file once before trafficking. That last check catches stale exports, accidental overwrites, and files saved with the wrong ratio.

<a id="quick-reference-matrix-for-campaign-objectives"></a>

Quick Reference Matrix for Campaign Objectives

尺寸選擇應先服從投放版位，再配合 campaign 的工作。品牌認知通常需要較大的視覺空間，轉換廣告則要讓產品、優惠與行動指示在擁擠的動態消息中保持清楚。以下矩陣適合作為起點，實際上線前仍要按版位檢查預覽。

<a id="display"></a>

Display 廣告尺寸與比例矩陣

Campaign 目標	主要版位	建議比例	目標尺寸
廣泛響應式網站覆蓋	Google 響應式展示廣告庫存	1.91:1	1200×628 pixels
廣泛響應式網站覆蓋	Google 響應式展示廣告庫存	1:1	1200×1200 pixels
廣泛響應式網站覆蓋	Google 響應式展示廣告庫存	9:16	900×1600 pixels
Mobile feed 認知	Meta feed	4:5	1440×1800 pixels
Mobile feed 轉換	Meta feed	1:1 fallback	1440×1440 pixels
全螢幕品牌敘事	Meta Stories	9:16	1440×2560 pixels
短片產品示範	Meta Reels	9:16	1440×2560 pixels
文章內開放網絡觸及	Publisher article placement	Fixed rectangle	300×250 pixels
較大型開放網絡矩形	Publisher article 或 premium placement	Fixed rectangle	336×280 pixels
桌面標題列曝光	Open-web leaderboard	Wide horizontal	728×90 pixels
高聳側欄曝光	Open-web skyscraper	Vertical	160×600 pixels
Premium 高聳側欄	Open-web high-visibility unit	Vertical	300×600 pixels
Mobile web 橫幅覆蓋	Open-web mobile placement	Horizontal	320×50 pixels
較大型 Mobile 橫幅	Open-web mobile placement	Horizontal	320×100 pixels

表內 Google 響應式尺寸依照前文引用的 Google 指引，Meta 尺寸則依照前文所述的直向優先層級。固定開放網絡尺寸同樣沿用前文提到的標準版位規格。這些數字應視為製作基準，不是保證所有環境都會以原比例顯示的承諾。

<a id="section"></a>

如何使用矩陣

先選出真正負責交付的版位，再補上能處理明確覆蓋缺口的鄰近格式。若 campaign 主要投放 mobile feed 與全螢幕影片，把大部分設計資源放在 desktop leaderboard，不會改善手機上的觀看體驗。若 publisher buy 指定 728×90，就因版位要求而製作，不要為了湊齊清單，替每個 campaign 都準備同一批尺寸。

這個矩陣也揭示一項常被忽略的取捨，可投放不等於有價值。廣泛支援的格式，未必適合目前的訊息；較小的 mobile 單元反而可能更有效，前提是它符合使用者螢幕與 campaign 版位。

實務上，先把預算與製作時間放在最常出現、最接近轉換路徑的比例，再處理低頻版位。這種 placement-first 流程比背誦一份固定尺寸清單更能減少重做，也較容易在不同平台維持清晰的產品與行動訊息。

<a id="troubleshooting-common-ad-upload-and-delivery-errors"></a>

Troubleshooting Common Ad Upload and Delivery Errors

A file can pass design review and still fail at upload, render poorly, or lose its CTA in delivery. A 4:5 asset may contain the wrong canvas, a small export may be enlarged until it looks soft, and a correctly approved creative may place key content beneath the lower interface area.

Start by classifying the failure as canvas, content, compression, or placement. The category determines the fix and prevents unnecessary redesign.

<a id="when-the-platform-rejects-the-aspect-ratio"></a>

When the platform rejects the aspect ratio

Open the exported file properties and compare its actual width and height. Do not rely on the filename. A file labeled “vertical” may contain a square canvas with a portrait image inside it. Re-export from a document set to the intended ratio, then inspect the final pixel dimensions before uploading.

Check placement settings as well. If automatic placement customization sends one asset into environments it was not designed for, upload a native version for the priority placement. One crop rarely serves feed, Stories, Reels, and open-web units equally well.

<a id="when-text-warnings-appear"></a>

When text warnings appear

Text warnings often expose a hierarchy problem rather than a strict mathematical failure. Remove copy that does not support the action, increase contrast, and make the product and promise identifiable before secondary detail.

Review the design at phone scale. A headline that looks readable on a full artboard can become unclear after platform processing. If the message requires several lines, rebuild the hierarchy instead of shrinking the type. Keep the CTA away from areas where platform controls may cover it.

<a id="when-the-file-looks-soft-or-colors-shift"></a>

When the file looks soft or colors shift

Re-export at the target pixel dimensions, convert the file to sRGB, and inspect a JPEG at the selected compression level. PNG does not guarantee sharper output when the source canvas is too small. A large export can also look poor if the source image is blurred or compression has damaged fine edges.

For open-web delivery, confirm that compression has not pushed the file beyond the relevant file-size limit. Meta follows a different workflow, so review the supplied high-resolution creative in the platform preview instead of applying an unrelated web-banner limit.

<a id="when-an-approved-ad-does-not-deliver-well"></a>

When an approved ad does not deliver well

Technical approval and media performance are separate checks. A 300×250 can access broad inventory while still carrying a weak message in an in-content environment. A 9:16 creative can fill a mobile screen while its product sits beneath interface elements.

Review placement previews, inspect the first readable frame, and compare the asset's intended job with its actual environment. If the priority is mobile feed or full-screen video, judge the creative in those placements first rather than relying on approval status.

Keep a troubleshooting log containing the original file, exported version, error message, and correction. That record reveals recurring workflow mistakes and helps the team fix the source template instead of repeatedly repairing individual exports.

ProdSnap supports media buyers with swipe-file references, brand-aware creative generation, multi-ratio Meta outputs, and controlled iteration for testing display concepts without rebuilding every file manually. Use the ProdSnap workflow to organize references, adapt core ideas to 1:1, 4:5, and 9:16 placements, and prepare cleaner assets for your next campaign upload.