The practical answer: there is no single mandatory Salesforce Marketing Cloud email image width. Prepare each image for the actual width of its Content Builder template, content block or reusable campaign component.
A 600px-wide hero with a 1200px source is a useful 2x example, but the correct values must follow the layout your team actually uses.
How Content Builder handles email images and campaign assets
Salesforce describes Content Builder as a cross-channel repository for marketing content, including images, email assets, blocks and templates. An image uploaded to Content Builder is therefore part of a wider production workflow rather than a guarantee that it will fit every possible campaign.
Image size depends on where the asset appears: a full-width hero, a reusable header, a two-column promotional tile or a dynamic product recommendation can all require different dimensions. Establish approved display sizes before teams start uploading artwork.
- Separate source photography from campaign-ready delivery assets.
- Name files consistently so marketers can recognise the intended placement and dimensions.
- Keep logos, hero banners and product tiles in organised Content Builder folders.
- Retain a clear distinction between a stored image asset and an editable Image Block.
- Check whether a reusable component is shared across multiple campaigns or business units.
Calculate the correct Content Builder image dimensions
Salesforce Marketing Cloud supports different email templates and custom HTML structures. A 600px content area is a common email-design convention, but it is not an official platform-wide requirement. Some organisations use 640px, another custom width or narrower padded content blocks.
| Example Content Builder placement | Example display size | Possible 2x source |
|---|---|---|
| 600px campaign hero | 600 × 300px | 1200 × 600px |
| 640px reusable banner | 640 × 320px | 1280 × 640px |
| Two-column product tile | 280 × 280px | 560 × 560px |
| Brand header logo | 180 × 60px | 360 × 120px |
| Personalised offer image | 300 × 180px | 600 × 360px |
Measure the available inner width after padding, table-cell spacing and column gutters. Treat these dimensions as examples, not a mandatory Salesforce standard.
Set standards for reusable headers, banners and image blocks
Reusable Content Builder blocks can save production time, but a poorly sized image can also repeat the same visual problem across many sends. Define the visible width, preferred aspect ratio, acceptable format and accessibility expectations for each approved component.
Reusable brand header
A 180 × 60px display area can use a 360 × 120px transparent PNG. Keep padding consistent so the same logo works across newsletters and triggered journeys.
Campaign offer module
A 300 × 180px promotional slot can accept a 600 × 360px JPG source. Maintain one aspect ratio so different offers do not make adjacent blocks jump in height.
Version approved assets carefully. Replacing an image used by multiple campaigns can affect future messages, automated journeys and content that other teams assume is stable.
Use Retina image sources with explicit email HTML widths
A Retina-ready source should improve image sharpness without expanding the visible email layout. When a hero is designed to display at 600px, a 1200px source can provide 2x horizontal detail while the HTML still specifies the intended 600px width.
<img src="https://example.com/campaign-hero-1200.jpg"
width="600"
alt="Explore the new seasonal collection"
style="display:block;width:100%;max-width:600px;height:auto;border:0;">Check custom HTML blocks, reusable content and any AMPscript-generated markup. A high-resolution source with no reliable display width can render too large in some email clients.
See our Retina Email Images Guide for display-width calculations.
Check desktop and mobile behaviour before approving assets
A responsive Marketing Cloud template may stack columns, change padding or scale a wide banner to a narrow phone screen. These changes affect composition even when the underlying image file technically fits.
- Check that a two-column product row remains balanced when stacked.
- Keep small promotional lettering readable when a desktop banner shrinks.
- Make linked images easy to identify and ensure surrounding calls to action remain visible.
- Test personalised images with short and long customer data values.
- Review both light and dark email-client appearances where practical.
Use a dedicated mobile crop only when the template supports the required behaviour. Do not assume that every Content Builder block automatically provides separate mobile image files.
Account for Outlook rendering and accessible image alternatives
Outlook desktop, Outlook on the web and mobile Outlook applications do not all render email HTML identically. Explicit image widths, dependable table structures and well-defined fallback colours help avoid layout surprises.
Alternative text should describe the purpose of an informative image. If an image is blocked, recipients still need enough context to understand the relevant promotion or action. Avoid putting the only important price, deadline or call to action inside a picture.
Useful distinction: image optimisation can improve download performance and visible quality. It does not guarantee identical rendering in every Outlook version or automatically make campaign content accessible.
Review personalised images, AMPscript and fallback assets
Dynamic campaigns can select different artwork according to subscriber attributes, audience segments or journey conditions. The images should share compatible dimensions and an agreed visual structure so a different record does not break the same email layout.
Salesforce documents ContentImageByKey() as a function that returns an image tag for an Image-type asset in Content Builder. Its documentation specifically states that the function does not work with Image Block content. Confirm the asset type before relying on a dynamic reference.
- Use stable asset references and a suitable default image.
- Check that every personalised variant has a compatible aspect ratio.
- Verify alt text when the visual message changes between segments.
- Preview multiple representative subscribers, including records with missing data.
- Test triggered and Journey Builder messages as carefully as scheduled campaigns.
Teams operating more than one enterprise platform can compare this approach with our Oracle Eloqua email image sizes guide.
Salesforce Marketing Cloud campaign image QA checklist
- Confirm the template width and the usable width of every image block.
- Check image pixel dimensions, aspect ratio, format and reasonable file weight.
- Review alt text, fallback colours and readability with blocked images.
- Inspect desktop, mobile and high-density display behaviour.
- Preview representative subscriber records and dynamic content variations.
- Test linked destinations, campaign tracking and personalised offer consistency.
- Send live test messages to relevant Outlook, Gmail and Apple Mail accounts.
- Recheck shared assets before approving a scheduled campaign or automated journey.
For broader planning across email clients, use the Email Image Size Guide.
Frequently asked questions about Salesforce Marketing Cloud images
What is the best image size for Salesforce Marketing Cloud emails?
Salesforce Marketing Cloud does not impose one universal email image width. Measure the usable width of the relevant Content Builder template or content block. A 600px display width is a common practical starting point, but the actual template determines the correct size.
What size should a Salesforce Marketing Cloud email banner be?
For a template with a 600px-wide content area, a banner can display at 600px and use a 1200px-wide source for 2x detail. A template with a 640px content area would instead use a 640px display width and a possible 1280px source.
Can Content Builder store reusable email images and blocks?
Yes. Salesforce describes Content Builder as a cross-channel repository for assets including email content and images. Teams can organise images and reusable content blocks, while still checking each block against the final campaign layout.
How should Retina images be coded for Outlook?
Use a high-density source file but set the visible HTML image width to the intended layout width. For example, a 1200px-wide file can use width="600" and appropriate responsive styling. Test the final email across relevant Outlook versions.
Does ContentImageByKey work with every Content Builder image block?
No. Salesforce states that ContentImageByKey works with Image-type content in Content Builder and does not work with Image Block content. Check the asset type and implement a suitable fallback when using dynamic image references.
Should Salesforce Marketing Cloud images include alternative text?
Yes. Describe the purpose of meaningful images so recipients can understand the campaign if images are blocked or a screen reader is used. Avoid repeating adjacent copy and check personalised or dynamically selected images separately.
How should Marketing Cloud teams test campaign images?
Preview the email with representative subscriber records, check desktop and mobile layouts, review dynamic content variations, verify links and alt text, and send test emails to the Outlook, Gmail and Apple Mail clients relevant to the audience.
Official Salesforce documentation and training
- Salesforce Content Builder asset and content documentation
- Salesforce Content Builder content blocks and custom block widgets
- Salesforce AMPscript ContentImageByKey reference
- Salesforce Trailhead email preview, testing and sending guidance
ImageOptimise is independent and is not affiliated with, integrated with or endorsed by Salesforce.
Prepare better images before uploading to Content Builder
Measure the real content area, protect accessibility, optimise each asset and test every meaningful campaign variation.