This workflow is for the production stage: turn approved source assets into Mailchimp-ready delivery copies, upload them cleanly, add accessibility context, and test the email before sending.
Start with a source inventory
List every asset before upload: hero, logo, product images, thumbnails, diagram, background image and optional GIF. For each one, record the intended block, the visible width, the format, whether critical text appears in the image, and whether it needs a link. This prevents the common mistake of compressing a folder of files before knowing what each file must do.
Create working masters and delivery copies
Keep the editable originals untouched. Create delivery copies named for their role, such as spring-lamp-hero-rgb.jpg or logo-header-transparent.png. The delivery copy is the one you resize, compress and upload. If a stakeholder asks for a crop change later, return to the master rather than editing the already-compressed email copy.
1. Confirm builder and block
Identify new builder, legacy builder or custom-coded template. Then verify the image block, column, padding and displayed width.
2. Export RGB
Use RGB for email/web display. Convert print-oriented CMYK assets before upload to reduce color surprises.
3. Choose the format
Use JPG for most photos, PNG for transparent or sharp graphics, and GIF only when the first frame and file weight still make sense.
4. Reduce avoidable weight
Mailchimp recommends keeping images around 1 MB or smaller and avoiding images much larger than the content area. Reduce dimensions and compression carefully so the image still serves the subscriber.
5. Upload or select from Content Studio
Mailchimp's Content Studio organizes files used across emails and other content. If you use custom HTML instead, make sure image URLs are public, absolute and stable.
Preparation and testing checkpoint table
| Checkpoint | What to verify | Failure prevented | Pass condition |
|---|---|---|---|
| Source quality | Original is sharp and large enough for the intended displayed width. | Blurry hero or product image. | Source remains clear at the planned crop. |
| Delivery copy | File is RGB, role-specific and not repeatedly recompressed. | Color shift or compression damage. | Saved from the master, not from a previous compressed copy. |
| Block fit | Image matches the block/column width and aspect ratio. | Stretching, crop surprises or mobile layout pressure. | Preview shows proportional scaling. |
| Accessibility | Alt text describes purpose and critical copy exists as real text. | Message lost when images are blocked or read by screen readers. | Images-off preview still communicates the offer. |
| Links | Linked images go to the expected page and text links duplicate important actions. | Dead clicks or unclear image-only CTA. | Mailchimp link checking and manual clicks pass. |
| Inbox rendering | Mobile, desktop, dark mode and important email clients are reviewed. | Client-specific spacing, background or contrast surprises. | Test email or Inbox Preview shows no critical failure. |
Add alt text and real supporting copy
Alt text should describe what the image contributes, not stuff keywords. If the image is decorative, keep the alt text minimal or follow the builder's decorative-image handling where available. If the image contains a product, event or diagram, write alt text that helps the recipient understand its purpose.
Do not place the only coupon code, deadline, price, disclosure or call to action inside the image. Many email clients block images by default, and some recipients use screen readers. Real HTML text is the safer place for information the subscriber must not miss.
Upload and preview inside Mailchimp
After upload, inspect the actual block. Confirm the image is not being enlarged, stretched, cropped unexpectedly or hidden behind a background. Use Mailchimp preview while building, then send a test email. Mailchimp's testing tips recommend proofreading, checking links and previewing how the email looks on mobile and desktop.
Inbox Preview, when available on the account, can help compare email clients and devices. Feature access and token limits can depend on plan and account context, so do not promise a fixed entitlement to every reader. The practical point is to test the clients your audience actually uses.
Custom-coded template checks
If you are coding your own email, do not use relative image paths. Email clients need public absolute URLs so they can fetch the images when the message loads. Avoid private, login-protected or free file-hosting URLs that may block outside requests. Also avoid JavaScript, forms, iframes and other web elements that Mailchimp identifies as poor fits for most inboxes.
Before sending
- Open the campaign with images enabled.
- Open the campaign with images disabled if your testing environment allows it.
- Check a phone-width preview.
- Confirm logos and transparent graphics remain visible in dark or altered color modes.
- Click every linked image and every text CTA.
- Confirm unsubscribe, sender identity and consent practices are not hidden in images.
- Send only after the message is understandable without relying on one image.
Where to go next
FAQ
Should I compress Mailchimp images before or after choosing the content block?
After. Choose the builder, block, column and displayed width first. Then export a delivery copy that fits the role without unnecessary weight.
What should I name Mailchimp delivery-copy files?
Use clear, simple filenames without special characters, such as spring-sale-hero.jpg or desk-lamp-product-01.jpg. Keep the editable master elsewhere.
How do I test Mailchimp images before sending?
Use Mailchimp preview, send a test email, check mobile and desktop, verify links, review images-off meaning, and use Inbox Preview where your account supports it.
What if my campaign uses custom HTML image paths?
Use absolute, public image URLs. Relative paths, private servers and unsuitable free hosting can cause broken images in inboxes.
Can I rely on image optimization to improve campaign results?
No. Better images can improve clarity and loading, but campaign results depend on consent, audience relevance, copy, offer, sender reputation, timing and other factors.
