Email graphics are small design assets with a large delivery risk: a banner that looks sharp in a design file can become blurry, oversized, inaccessible, or unreadable in an inbox. This checklist gives content and design teams a repeatable way to prepare email banners, logos, icons, and promotional graphics for desktop, mobile, dark mode, and image-blocked viewing.
Overview
A reliable email graphic is not defined by appearance alone. It must also load efficiently, remain understandable when images are unavailable, fit the message hierarchy, and behave acceptably across different email clients. Treat every image as a production asset with specifications, not as a last-minute export.
Email clients do not share one rendering environment. Available screen width, image caching, dark-mode treatment, font handling, link behavior, and support for newer formats can vary. For that reason, use conservative defaults for important graphics and test the final email in the environments your audience actually uses. The recommendations below are practical starting points rather than universal platform rules.
Keep the source file separate from the delivery export. The source should retain editable text, vector logos, spacing guides, and brand colors. The delivery folder should contain clearly named, compressed assets in the formats used by the campaign. A simple naming pattern such as campaign_section_asset_variant_v01.ext makes revisions easier to track and reduces the chance of linking an obsolete image.
What to track
Dimensions and pixel density
Design the visible layout at the width your email template is intended to support, then export key raster images at approximately twice that width when a sharper display is needed. The HTML or email builder should scale the image down to its intended display size. This is the usual approach for retina email images, but it should be paired with compression so the extra pixels do not create unnecessary weight.
| Asset | Practical display starting point | Retina export starting point | Notes |
|---|---|---|---|
| Full-width banner | 600–650 px wide | 1,200–1,300 px wide | Keep essential text and logos away from edges. |
| Logo | Set by the header layout | About 2× displayed size | Prefer a transparent PNG when a raster fallback is needed. |
| Product or editorial image | Match its content column | About 2× displayed size | Crop for the smallest expected mobile view. |
| Small icon | 16–48 px, depending on use | About 2× displayed size | Do not rely on fine details at small sizes. |
| Animated graphic | Match the content column | Use only when necessary | Provide a useful first frame for clients that do not animate it. |
These ranges are workflow defaults, not requirements for every template. Confirm the actual content width from the email system before exporting. Do not place important copy only inside a banner; live HTML text is generally easier to resize, translate, search, and read with assistive technology.
Formats and compression
Use JPEG for photographs and complex imagery with no transparency. Use PNG when you need transparency, crisp interface elements, or flat graphic shapes. Use GIF only when animation has a clear communication purpose and the first frame works on its own. SVG can be valuable for logos and icons, but support and rendering behavior may vary, so keep a tested raster fallback for important content.
Compress each export after resizing it to its delivery dimensions. Compare quality at 100% view and at the actual email display size. Remove unused metadata where the export tool allows it, and avoid repeatedly recompressing the same file. As a starting control, set a team target for each image and for the complete email rather than treating a universal maximum as fact. A lightweight banner that is visually indistinguishable from the source is usually preferable to a large, technically sharp file that slows the experience.
Alt text, links, and fallbacks
Write alt text that communicates the image's purpose. For a linked promotion, describe the offer or destination rather than writing “banner image.” For a decorative divider, use empty alternative text when the email system supports it. If the image contains essential information, repeat that information in nearby live text or in the linked destination. Check that the image's hyperlink and any adjacent button lead to the intended destination, use the correct campaign parameters where applicable, and remain usable when images are blocked.
Use a linked-image fallback deliberately. The surrounding HTML should still provide a meaningful headline, call to action, and destination if the image fails. Avoid making a single image the only route to an important message. For logos, include an accessible text alternative and test how the header looks when the logo does not load.
Dark-mode behavior
Review graphics against both light and dark backgrounds. Transparent logos may disappear if their artwork has insufficient contrast, while solid white or pale backgrounds can create unwanted boxes in a dark interface. Consider alternate logo artwork, a controlled background, or a border that preserves separation. Do not assume that every client will honor your preferred dark-mode treatment; inspect the rendered result and ensure the message remains understandable even when colors change.
Cadence and checkpoints
Use a short pre-send checklist for every campaign and a broader review on a recurring schedule. The pre-send pass should happen after the final copy, links, and graphics are assembled—not only in the design application.
- Confirm the brief: Verify the purpose, audience, destination, required dimensions, brand version, and whether the asset needs to work in light and dark mode.
- Inspect the source: Check for correct logo artwork, readable type, safe cropping, sufficient contrast, and no accidental guides or hidden layers.
- Export deliberately: Resize for delivery, choose the simplest suitable format, compress the file, and record the export version in the asset name.
- Check accessibility: Add useful alt text, identify decorative images, provide live text for essential information, and verify keyboard-accessible links in the email layout.
- Test image blocking: Confirm that alt text, live headings, buttons, and link destinations still explain the message when images are unavailable.
- Preview responsive states: Inspect desktop and narrow mobile views for cropping, excessive height, tiny text, awkward stacking, and tap targets that are too close together.
- Preview dark mode: Look for disappearing logos, low-contrast text embedded in images, unexpected borders, and backgrounds that become visually harsh.
- Verify delivery: Confirm file URLs, link targets, tracking parameters, file names, and the final version stored in the campaign folder.
Quarterly, review the results of recent tests and note recurring failures by email client, template, format, or asset type. Recheck the guidance when your email platform changes its editor or image-processing behavior. Refresh compression examples and reference exports at least every six months, or sooner if the team changes tools, brand assets, or template widths.
How to interpret changes
When a graphic looks different in a test, first separate an asset problem from a layout or client problem. A blurry image may be caused by exporting at display size instead of a higher pixel density, but it may also result from a platform resizing the image. A dark-mode issue may come from transparent artwork, automatic color treatment, or a background defined outside the image.
Record observations in a simple table with the campaign name, asset file, client or preview environment, viewport, image state, and outcome. Use categories such as dimensions, compression, format, alt text, link, and color treatment. This prevents isolated rendering differences from turning into vague team opinions.
Prioritize fixes by consequence. Correct broken links, missing essential information, unreadable contrast, and misleading crops before pursuing small quality improvements. If one format behaves inconsistently but a simpler format meets the visual requirement, choose the dependable option for the important asset and document the exception.
Do not judge success only by a design preview. Compare the source, compressed export, rendered email, image-blocked view, mobile view, and dark-mode view. A graphic has passed when its purpose and action remain clear across those states.
When to revisit
Return to this checklist before every major campaign, especially when introducing a new template, format, email builder, brand identity, or type of promotional graphic. Schedule a quarterly review to examine client previews and recurring defects. Perform an additional review after a notable platform change or when subscribers report missing, distorted, or unreadable images.
Keep one approved example of each common asset—a banner, logo, product image, icon, and dark-mode variant—in the team’s design asset library. Label each example with its intended display width, export dimensions, format, compression target, alt-text pattern, and fallback behavior. Link the examples to the active template documentation so new contributors can use a tested starting point.
Before the next send, make a duplicate of this checklist and mark each item complete. If a test fails, record the cause and the chosen fix rather than silently replacing the file. That small habit turns email graphics from one-off creative assets into a maintained production system: easier to review, easier to hand off, and more reliable to revisit as campaigns and rendering environments change.