PSD + JPG + PNG export workflow for campaign production in Photoshop

What “PSD + JPG + PNG” means in a campaign pipeline

Production teams usually have two simultaneous obligations:

• Maintain an editable source of truth (PSD) for late copy changes, locale variants, and legal updates.
• Ship compressed, platform‑compliant assets (JPG/PNG) for trafficking and CMS uploads.

A reliable workflow treats the PSD as the design system artifact and JPG/PNG as disposable outputs—generated consistently, named predictably, and easy to reissue after feedback.

Structure the master PSD to survive export

A clean master makes exporting simple and rework fast. Recommended structure:

• Live text only. Avoid rasterizing; keep font layers editable.
• Vector where possible. Use shape layers and place logos/illustrations as Smart Objects. Adobe’s Smart Objects preserve source data and avoid cumulative transform damage.
• Logical groups. Separate background, key visual, product, copy, CTA, and legal. Name predictably.
• Alignment rules. Define safe areas and anchors (e.g., “logo top-left 24 px from edge; CTA bottom-right on 8 px grid”).
• Reusable comps. Consider Layer Comps for messaging variants if your team already uses them.
• Color management. Set the working space to sRGB IEC61966-2.1 if the deliverables are web-bound and keep a single profile from design through export to limit surprises.

If you’re evaluating an automated resizing approach, start with the PSD conventions outlined in the PSD setup guide.

JPG vs PNG: format choices that affect size, clarity, and transparency

• JPG
  • Strengths: Small files for photos/gradients; adjustable compression.
  • Controls: Quality (70–90 is a good production starting range), chroma subsampling (4:2:0 typical for web), progressive encoding if your CMS supports it.
  • Risks: Artifacts on fine type, icons, and flat fills.
• PNG
  • Strengths: True transparency (alpha), crisp edges for UI and logos, lossless.
  • Controls: PNG‑24 for gradients/transparency; PNG‑8 for limited palettes when ultra‑small sizes are required (watch for banding/dithering).
  • Risks: Larger files; some ad platforms set strict file‑size caps.

Guideline: Default to JPG for photography‑led ads without transparency. Choose PNG where transparency or razor‑sharp edges are mandatory. Export to sRGB.

Platform spec snapshot (sourced) vs workflow interpretation

Sourced facts (verify current guidance before handoff):

• Google Ads Performance Max image assets list common aspect ratios with minimum dimensions such as 1:1 square (min 300×300), 1.91:1 landscape (min 600×314), and portrait 4:5 (min 480×600). Recommended larger uploads like 1200×1200 (square), 1200×628 (landscape), and 960×1200 (portrait) are typical as of 2026 per Google Ads Help.
• Social channels frequently request 1080×1080 for square posts and around 1200×630 for link previews, per consolidated industry roundups in 2026.

Workflow interpretation: Instead of chasing every platform size, define a canonical set of aspect ratios (1:1, 1.91:1, 4:5) at sufficiently high pixel counts. Generate these consistently, then let trafficking or the ad system resize down as needed—so long as you stay within max file size and dimension caps. Document your canonical set in the brief so design, production, and trafficking align.

Step-by-step: a dependable PSD → JPG/PNG pipeline

1. Source setup

• Confirm final copy and legal statements, but expect late changes. Keep them as live text.
• Place logos as vector Smart Objects to preserve sharpness across sizes.
• Normalize color to sRGB at the master level.

2. Define sizes and breakpoints

• Choose a minimal, canonical set that maps to target platforms (e.g., 1080×1080, 1200×628, 960×1200). Capture them in the spec sheet.
• Note any platform limits (file size caps, animation bans, min dimensions). Keep a link to your trafficking team’s reference doc.

3. Safe areas and scaling rules

• Mark a headline safe area, CTA zone, and logo placement rules in a non‑exporting guide layer group.
• Decide how elements scale across sizes (e.g., logo scales with height percentage, CTA paddings remain fixed, background crops from center). Write this into the production brief.

4. Export configuration

• JPG: set baseline quality bands (e.g., 85 for photo‑heavy, 75 for gradient backgrounds if banding is controlled). Ensure sRGB and strip unnecessary metadata.
• PNG: reserve for transparency or iconography. Use PNG‑24 when gradients meet transparency; PNG‑8 only if QCed for banding.
• Filenames: standardize with tokens like campaign_size_locale_variant.ext.

5. Batch generation

• Run a batch process that produces both editable PSDs for each size and JPG/PNG deliverables per the naming scheme.
• If using Smart Resize, you’ll map key visuals once, enter sizes, and generate both layered outputs and delivery renders. See Enter sizes and Generate assets for the run sequence.

6. QA and handoff

• Visual checks: edge sharpness, crop on key product, line breaks, and legal legibility.
• Technical checks: pixel dimensions, sRGB profile, file size, and correct file extension.
• Packaging: include editable PSDs and exported JPG/PNGs. Maintain a manifest of sizes with version numbers.

Native Photoshop options for batch export (and their limits)

• Export As: Good for small sets; can’t emit size‑specific layered PSDs alongside JPG/PNG.
• Generator (Layer name.png/.jpg): Quick, but ties outputs to layer naming and increases maintenance overhead.
• Image Processor / Actions: Useful for simple resizes; version control and multi‑ratio crops need careful action design.

These tools work, but once you’re managing copy variants, locales, and multi‑ratio crops, keeping editable per‑size PSDs synchronized becomes the hard part—not the JPG/PNG save step.

Where Smart Resize fits

Smart Resize is a Photoshop plugin designed for campaign adaptation. Typical usage in a PSD → JPG/PNG workflow:

• Load one approved key visual and map layer roles once (logo, headline, legal, CTA). See Load key visuals for the mapping step.
• Enter target sizes by pixel dimensions or aspect presets. See Enter sizes.
• Generate size‑specific, fully editable PSDs that preserve live text, Smart Objects, and vector shapes—ready for late‑stage edits and localizations.
• In the same run, export JPG/PNG deliverables per size with sRGB, quality, and naming rules controlled in Output settings.

The result: you retain an editable archive of per‑size PSDs while shipping consistent delivery files. If you’re evaluating licensing or procurement, see Smart Resize pricing. If you need a process preview for internal buy‑in, start with Smart Resize quick start.

File naming, versioning, and metadata that scale

• Recommended pattern: brand_campaign_channel_size_locale_variant_vNN.ext (e.g., acme_spring_pmax_1200x628_en_us_a_v03.jpg).
• Mirror the pattern for layered PSDs and final exports so traceability is obvious.
• Include a simple manifest (CSV or text) listing sizes, versions, and timestamps.
• Strip nonessential metadata from delivery JPG/PNGs to reduce size unless your CMS relies on it.

Color, compression, and QC tips for production teams

• Color: Keep a single sRGB workflow from PSD to export to reduce color shifts in browsers and ad servers.
• Banding: If gradients band at lower JPG quality, add subtle noise or switch that element to PNG‑24 if file size permits.
• Sharpening: If you downscale significantly, apply a gentle output sharpen per size; don’t bake this into the master.
• Transparency: Only use PNG when transparency is essential—ad platforms often compress again.
• Accessibility: Maintain minimum text size and contrast; include these numbers in your internal spec.

Practical QA checklist before delivery

• Dimensions match the spec sheet (spot‑check with OS previews and your DAM).
• Color profile is sRGB and embedded if your pipeline expects it.
• Files open cleanly in common preview apps and your trafficking platform’s uploader.
• Naming matches the manifest; versions incremented for each approval cycle.
• Spot‑check compression at 100% zoom: type edges, product edges, gradients.

Example run with Smart Resize (high level)

• Prepare the master using the conventions above. If you’re new, review the PSD setup guide.
• Load the approved key visual and map layers once. See Load key visuals.
• Enter the campaign’s sizes (e.g., 1080×1080, 1200×628, 960×1200). See Enter sizes.
• Configure output quality, color profile, and file naming. See Output settings.
• Generate layered PSDs and delivery renders in one pass. See Generate assets.
• Hand off JPG/PNGs and archive the per‑size PSDs. For budgeting or purchase, see Smart Resize pricing, or proceed to the Smart Resize download when procurement clears.

Notes on specs and change management

• Specs move. As of 2026, Google Ads commonly recommends square 1200×1200, landscape 1200×628, and portrait 960×1200 for image assets, with minimums such as 300×300, 600×314, and 480×600. Always confirm with the latest Google Ads Help before shipment.
• Social requests like 1080×1080 and ~1200×630 remain widespread but also evolve. Keep a small, reviewed set of canonical ratios and update quarterly.

By treating PSD as your system of record and JPG/PNG as reproducible outputs—supported by consistent structure, color, naming, and automation—you’ll reduce last‑mile risk and make mid‑flight changes a routine operation rather than a scramble.

PSD setup guide · Smart Resize quick start · Load key visuals · Enter sizes · Output settings · Generate assets · Smart Resize pricing