Use this reusable preflight checklist to prepare JPEG images for email newsletters, from export settings and dimensions to filenames, alt text, fallback behavior, and final campaign testing.
Overview
JPEG images for email newsletters need to balance visual quality, download weight, accessibility, and dependable rendering. A file that looks excellent in a design application can still create problems in a campaign if it is too large, poorly cropped, missing alternative text, or dependent on a background image that some recipients will not see.
The safest approach is to treat every newsletter image as a small delivery package rather than a standalone picture. The package includes the exported JPEG, its intended display dimensions, a descriptive filename, useful alt text, a working image URL, and a text or color fallback. Keep the editable source file separately, then upload and test the delivery version.
Exact limits vary by email service, template system, mailbox, and device. Before scheduling, check the current requirements of the marketing platform you use. The guidance below provides a durable workflow for preparing assets without depending on one provider's temporary rules.
Quick export-size template
| Asset type | Working file | Delivery JPEG | Preflight note |
|---|---|---|---|
| Single-column hero | At least the intended display width, with room for cropping | RGB JPEG, moderate quality, compressed after resizing | Keep important text and faces away from crop edges |
| Content card | Display width plus any planned responsive crop | RGB JPEG sized to the card rather than the original photo | Check legibility at mobile width |
| Photo grid | Each tile prepared separately | Consistent dimensions and compression across tiles | Confirm the layout still works if one image is blocked |
| Decorative background | Wide enough for the planned container | JPEG only when the design remains usable without it | Provide a solid color and readable live text fallback |
Checklist by scenario
For a promotional hero image
- Confirm the image supports the message rather than carrying the entire message.
- Use a crop that leaves a clear visual area for the headline, button, or logo.
- Export in RGB color mode and inspect the result on both a light and dark interface if the design may be viewed in different themes.
- Resize to the template's actual content width before compression. Do not upload a camera-original file when the email displays it at a much smaller size.
- Write alt text that explains the image's role. If the image is promotional, the surrounding live text should still state the offer or action.
- Confirm that the linked destination works independently of the image.
For an editorial or creator newsletter
- Choose a consistent aspect ratio so recurring issues feel coherent.
- Use a descriptive filename such as
spring-studio-process.jpgrather than a camera-generated name. - Write alt text that identifies the subject and relevant context without repeating the caption word for word.
- Check that the image is licensed for the newsletter's intended use. Keep license notes with the source asset when working with stock photos for commercial use.
- Make sure the story remains understandable if images are blocked or delayed.
For a product, portfolio, or catalog send
- Use consistent framing, background treatment, and visual scale across the set.
- Inspect edges for unwanted halos, compression blocks, and clipped products.
- Keep product names, prices, and key specifications as live text where possible instead of placing them only inside the JPEG.
- Give each image a focused alt description, such as the product name and view, rather than a vague phrase such as “product image.”
- Test image links, tracking links, and fallback copy separately.
For a seasonal or time-sensitive campaign
- Check dates, offer language, and regional details in both the image and the HTML copy.
- Keep a version without time-sensitive text if the image may be reused in an automated sequence.
- Verify that the filename, alt text, preview text, and landing page use the same campaign language.
- Schedule a real-device or test-recipient review before the send, especially when the design uses an unusual crop or animated companion asset.
What to double-check before scheduling
1. Dimensions and responsive behavior
Start with the content column, not the original image. Find the widest intended display area in the email template, then export near that size while allowing for the template's responsive behavior. A large retina-ready version may be appropriate in some systems, but it should still be resized and compressed deliberately. Confirm whether the platform automatically resizes uploads; automatic processing can change dimensions or quality.
Review the image at desktop width and at a narrow mobile width. Look for faces, logos, product edges, and text that become cropped or difficult to read. If the image uses an art-directed crop, keep the focal point documented in the asset notes.
2. Compression and file weight
Export a JPEG at a practical quality setting, then inspect it at its actual email display size. Look for blocky shadows, ringing around high-contrast edges, banding in skies, and softened small details. If the file is still unnecessarily heavy, reduce dimensions before lowering quality aggressively. A smaller, well-resized source often looks better than an oversized file compressed too far.
Photographs generally suit JPEG, while logos, flat-color illustrations, transparency, and sharp text may require another format or a live HTML treatment. Do not force a photo format onto every visual asset.
3. Alt text and fallback content
Decide whether each image is informative or decorative. Informative images need concise alt text that communicates their purpose. Decorative images can use empty alternative text when the surrounding content already provides the meaning. Avoid placing essential instructions, dates, or calls to action only inside the JPEG.
Check the fallback state with images disabled. A solid background color, readable live text, useful link label, and sensible layout should remain. Background-image treatments deserve extra scrutiny because their behavior can differ between email clients.
4. Client and platform comparison
| Environment | What to compare | Practical test |
|---|---|---|
| Webmail | Image blocking, scaling, link behavior, and narrow-window layout | Open the test message in a browser at multiple window widths |
| Desktop mail app | Image rendering, line wrapping, background treatment, and download behavior | Review the message with images enabled and disabled |
| Mobile mail app | Crop, tap targets, readable live text, and loading over a cellular connection | Inspect on a phone or an accurate mobile preview |
| Marketing platform | Upload limits, automatic resizing, hosted URLs, and tracking modifications | Send a platform-generated test rather than relying only on the design preview |
This comparison is a testing framework, not a permanent compatibility table. Recheck the platform's current documentation whenever its editor, image hosting, or template system changes.
5. Filename, metadata, and storage
Use lowercase filenames with meaningful words and simple separators. Avoid spaces, duplicate names, and strings that reveal private project details. Remove unnecessary metadata when privacy or file size matters, while retaining whatever production record your team needs. The JPEG Metadata and EXIF Privacy Guide explains what to review before sharing image files.
Keep the source, approved export, and campaign reference together in a predictable folder. A reusable asset library reduces the chance of uploading an outdated crop or an unapproved version; see the asset library organization guide for a broader filing approach.
Common mistakes
- Exporting the original photo. Large camera files add weight without improving a small newsletter display. Resize first.
- Putting the entire message in the image. Image blocking, accessibility needs, and responsive crops can hide the campaign's purpose. Use live text for essential information.
- Ignoring the mobile crop. A balanced desktop composition may cut off the subject on a narrow screen. Set a focal point and test the actual template.
- Using vague alt text. “Banner” does not tell a recipient what the image contributes. Describe the subject or purpose briefly.
- Skipping the no-image state. A newsletter should still offer context and a usable link when images do not load.
- Trusting a design preview alone. Upload processing, hosted URLs, tracking, and mailbox rendering can alter the final result. Send a real test.
- Replacing a bad export with a more aggressive quality setting. Revisit dimensions and crop first. Quality reduction is not the only compression control.
- Forgetting the source license. Store usage notes with stock images and commissioned assets so a later reuse does not create uncertainty.
When to revisit this checklist
Use the checklist before every newsletter issue, but schedule a deeper review at predictable moments. Revisit it before seasonal planning cycles, when a template is redesigned, when you change marketing platforms, or when your workflow begins automatically resizing or converting images. It is also worth reviewing after a campaign shows unexpected clipping, slow loading, broken links, missing alt text, or poor performance in a particular test environment.
At the start of a new campaign, copy this short final pass into your production notes:
- Confirm the intended display width and mobile crop.
- Resize, export to RGB JPEG, and inspect compression at display size.
- Use a clear filename and remove unnecessary metadata.
- Add purposeful alt text or mark the image decorative.
- Confirm the link, landing page, and live fallback copy.
- Test with images enabled and disabled on the relevant devices and clients.
- Record the approved file and archive the source separately.
For related production checks, pair this workflow with the JPEG image audit checklist and the filename and alt text checklist. If your newsletter images are also being prepared for a website, review the JPEG-to-WebP workflow separately rather than assuming a web conversion is suitable for email delivery.