Reuse one key visual across Meta and Google

Campaign teams often receive one approved key visual and then face two different production paths: Meta placements that lean vertical and social-native, and Google placements that distribute across inventory with their own constraints. The fastest way to reach coverage without creative drift is to split the problem into two layers: a shared visual system and platform-specific output families. Below is a practical approach using Photoshop, Smart Objects, and a rules-based resizing workflow that keeps outputs editable.

Why cross-platform campaign adaptation creates double work

• One master, two ecosystems: Meta (Facebook, Instagram) emphasizes square and vertical placements, while Google networks require a mix of square, landscape, and portrait image assets for Responsive Display and Performance Max.
• Manual rebuilds invite inconsistency: Recreating layouts for each platform changes type scales, logo clearspace, and cropping—especially under short deadlines.
• Feedback loops multiply: Legal or pricing edits ripple across dozens of files if there’s no single source of truth.
• Distribution reality: Google placements may crop or scale assets to fit different contexts, and Meta overlays (UI chrome, CTAs) can occlude edges. If your master doesn’t plan for safe areas and scale rules, production turns into one-off fixes.

Shared visual system versus platform-specific output families

Start with a master PSD that encodes hierarchy rather than final pixels. Treat these as reusable system elements:

• Background/hero imagery (photography or illustration)
• Product or packshot
• Brandmark and clearspace
• Headline and sub-copy
• Call-to-action (when needed in-image)
• Legal, price, or promo modules
• Safe-area guides for edge-occlusion risk

In Photoshop, represent the key units as Smart Objects so you can scale and reposition without loss. Adobe’s Smart Object workflow is documented here: https://helpx.adobe.com/photoshop/using/create-smart-objects.html

Then define output families driven by aspect ratio, not by individual placements:

• Square (1:1) — core for Meta feeds and required for Google image assets
• Vertical portrait (4:5) — strong for Meta feed on Instagram/Facebook
• Full-portrait (9:16) — Stories/Reels on Meta; covers vertical placements
• Landscape (1.91:1) — common for Google image assets and some Meta link ads

This split lets you review the same hierarchy across shapes before multiplying sizes. It also creates consistent rules for type scaling, logo placement, and packshot size.

Anchor formats to review before platform-specific expansion

Choose anchors that represent the real extremes of your content:

• 1.91:1 landscape for horizontal emphasis (product lines, wide scenes)
• 1:1 square for balanced composition
• 4:5 portrait for feed-first vertical layouts
• 9:16 for full-portrait storytelling and tall packshots

Practical notes:

• Keep essential content away from edges; place the core subject in the center-safe region so automated crops on Google placements or UI overlays on Meta don’t compromise legibility.
• Favor vector or high-resolution art inside Smart Objects. Raster text becomes brittle during repeated resizing.
• Stress-test contrast and minimum text sizes at 100% zoom on exported assets, not just within the master.

Sourced specs to inform your anchors (verify before each campaign):

• Google Ads image assets. Google Ads Help documents image asset families for Performance Max and Responsive Display. As of publication, examples include square 1:1 (e.g., 1200×1200), landscape 1.91:1 (e.g., 1200×628), portrait 4:5 (e.g., 960×1200), and logos such as 128×128 (square) and ~1200×300 (horizontal). See Google Ads Help for details and any updates:
  • Performance Max image assets: https://support.google.com/google-ads/answer/14530211
  • Google Ads specs overview: https://support.google.com/google-ads/answer/13676244
• Meta placements. Across Facebook and Instagram, the working set typically includes 1:1, 4:5, and 9:16. For an aggregated view of social image sizes across networks, Buffer maintains a current guide: https://buffer.com/library/social-media-image-sizes/ Always confirm the most recent Ads Manager guidance for the specific Meta placements you plan to buy.

These references are platform facts; the next sections translate them into a Photoshop production system.

Internal file structure and naming for Meta plus Google delivery

Establishing predictable structure avoids time lost in handoffs and QA.

File architecture

• KV_Master.psb — contains brand, hero image, and typography as Smart Objects, with guides for the four anchor ratios.
• /Exports/ — root for production outputs with subfolders for Google and Meta.
• /Exports/Google/ — image assets grouped by ratio families and locales.
• /Exports/Meta/ — square, 4:5, 9:16 families and locales.

Naming conventions (example)

• GGL_PMax_1x1_EN-GB_Spring24_v03.psd
• GGL_PMax_191x1_EN-GB_Spring24_v03.psd
• META_Feed_4x5_EN-GB_Spring24_v03.psd
• META_Stories_9x16_EN-GB_Spring24_v03.psd

Conventions to agree in advance

• Channel prefix (GGL vs META)
• Ratio shorthand (1x1, 4x5, 9x16, 191x1)
• Market-language code (e.g., EN-GB, FR-FR)
• Campaign code and version (e.g., Spring24_v03)

Why PSB for the master? Large canvases, multiple Smart Objects, and resolution-independent artwork often tip over standard PSD limits. Linked Smart Objects keep the master lean while preserving editability in size variants.

How Smart Resize accelerates cross-channel output generation

Smart Resize is a Photoshop plugin used by production teams to generate many channel-ready PSDs from one approved master—without flattening layers. It fits into the system above by turning your anchor decisions and naming rules into repeatable outputs.

Typical flow

1. Load your approved master and map the key layers

• Identify hero image, pack, logo, headline, CTA, and legal modules as the elements that will transform across sizes. See the step-by-step in Load key visuals.

2. Enter the size list once

• Define the Google and Meta families in the Sizes panel: 1:1, 4:5, 9:16, 1.91:1 plus any pixel targets you need for trafficking. You can create separate lists for “Google PMax” and “Meta Paid Social” and reuse them on future jobs. See Enter sizes.

3. Apply consistent transform rules per element

• For example, logo fixed 6% from top-right with minimum 5% width; packshot scales between 28–36% of the shorter canvas dimension; headline pins under the logo with a responsive text size range. These rules help the same hierarchy survive across shapes.

4. Generate editable PSDs for each required output

• The plugin creates layered files for every size while preserving Smart Objects and live text, which keeps last-mile copy, price, or legal changes inside Photoshop. See Generate assets.

5. Output with predictable names and folders

• Configure per-channel naming tokens for market, version, and ratio so files land exactly where traffic managers expect them. See Output settings.

Where this helps most

• When the brief asks for both Google image assets (Performance Max/Responsive Display) and Meta feed + Stories coverage from one concept
• When many markets or languages reuse the same composition logic
• When legal or pricing changes hit late and you need to reflow dozens of sizes without re-layout

If you want to review cost and licensing for your team, see Smart Resize pricing.

QA checklist for consistency across platforms

Treat QA as a cross-platform gate, not a channel-specific chore.

Structure and legibility

• Verify the master hierarchy reads correctly in all four anchors (1:1, 4:5, 9:16, 1.91:1) before scaling out.
• Keep primary subject and logo within a centered safe region; avoid edge-only layouts that risk automated crops on Google inventory or UI overlays on Meta.
• Audit text sizes at 100% export scale; rasterize sparingly to keep hinting and kerning intact.

Brand and legal

• Enforce logo clearspace consistently; spot-check at the smallest deliverable.
• Confirm legal/promo modules reflow without covering the pack or core message.
• Check locale-specific hyphenation and line breaks.

Technical

• sRGB color profile embedded, consistent compression settings per channel, and file size within platform limits (confirm current limits on the spec pages linked above).
• For Google assets, provide the required set of logos (square and horizontal) and image ratios cited in Google Ads Help.
• For Meta verticals, run a quick pass in mock placements to ensure top/bottom UI doesn’t hide copy. As a practical rule of thumb, keep critical text away from the top and bottom edges in 9:16.

Content policy sanity check

• Avoid misleading overlays (fake UI, false features) and confirm claims comply with your industry standards. If Google or Meta flags an asset, inspect text density, image clarity, and cropping first; those are common culprits.

FAQ: when to split masters and when not to

When reuse works

• The core proposition, image style, and copy length carry across channels; only framing and emphasis change with ratio.
• The same packshot and headline can live in 1:1, 4:5, 9:16, and 1.91:1 without rewriting the story.

When to branch

• Meta concept depends on people-first, UGC-adjacent framing, while Google concept benefits from clean product-forward imagery with minimal text.
• Copy length, legal requirements, or CTAs differ materially by channel.
• Motion-first ideas where Meta runs Reels and Stories video, but Google needs static images.

Hybrid approach

• Share a brand system (color, type, logo, pack) across two masters; keep ratio logic and naming conventions aligned so production still scales.

Putting it together

• Decide once: pick your four ratio anchors and lock hierarchy at the master level using Smart Objects in Photoshop.
• Produce predictably: use a rules-based generator to output layered PSDs for both Google and Meta families.
• QA centrally: run a single checklist that accounts for crop behavior (Google) and UI overlays (Meta) before trafficking.

If you need a practical walkthrough before a client review, start with the Smart Resize quick start. When you’re ready to turn the approved KV into production files, map layers, enter your two size lists, and generate editable assets in minutes rather than days.