Technical

Email Image Optimization: 13 Tools, Formats, and a Pre-Send Workflow

Optimize the asset, the HTML around it, and the way the email behaves when images are blocked. A smaller file helps only if the message still works without it.

The best single pick for most email teams is Email on Acid, because the image problems that cost readers the most, such as a hero that clips in one client, an empty frame when images are blocked, or a dark-mode inversion, appear only when the compiled email is rendered. Its Basic plan is listed at $99 a month for 1,000 previews, and Premium is listed at $199 a month for 2,000 previews with accessibility tests and HTML analysis added. Pair it with a compressor you already trust for the file step, because a preview tool does not make an image smaller.

Readers who search for email image optimization tools usually have one of three problems: a template that feels heavy when it loads on a phone, a campaign where the hero image is the only place the offer appears, or an accessibility review that flagged missing descriptions. Each problem needs a different tool, and none of them is solved by a single compression setting. This guide covers 13 tools across four jobs: preparing files, delivering them, checking accessibility, and rendering the final message.

Prices on this page were checked on 7 October 2026 on each vendor’s pricing page. Where a vendor does not publish a price, this guide says so and links to the official page. Written by the editorial team behind this site.

What image optimization has to solve

An image in an email has four jobs at once. It has to look right at the width the reader sees, download quickly enough that the message does not feel broken, carry meaning when it does not load, and survive the way each client handles remote content. Compression addresses only the second job. A file can be perfectly small and still fail the other three: a product photograph can be clipped on a narrow screen, a logo can disappear in dark mode, and a call-to-action graphic can leave the reader with nothing to click when images are off.

That is why the most useful workflow starts with the message rather than the file. Decide which words must survive without images, which images support those words, and which images are decoration that can be replaced by a colour or dropped entirely. Only then decide the format, the export width, the compression preset and the hosting route. A template that follows this order usually needs fewer and smaller images, and the images it keeps have a clear reason to exist.

For the surrounding markup and client checks, see the email template testing guide. For the accessibility rules that apply to alt text and contrast, see the email accessibility guide. For layouts that adapt to narrow screens, read responsive email templates, and for images on dark backgrounds, see dark mode email templates.

Formats in plain terms

Format choice matters less than the decision to include the image at all, but the format still changes the file size and the risk. The following rules describe the default choices this guide recommends and the checks each one needs.

  • JPEG suits photographs and smooth gradients. Choose a quality setting by looking at faces, product edges and small type at the displayed size, because artifacts appear there first.
  • PNG suits logos, sharp interface graphics and images that need transparency. It is usually larger than a JPEG for photographs, so use it only where the detail or the alpha channel earns the extra weight.
  • GIF can carry short motion, but the first frame matters. Some clients show only a static frame, so the first frame has to communicate the message on its own, and long animations add weight without adding much clarity.
  • SVG and WebP can work for specific clients and platforms, but support is uneven. Provide a tested raster fallback and keep the essential meaning in live text, because a format that works in one client can fail silently in another.

Two habits prevent most format problems. First, export at the width the image will display, plus a density factor only where the layout needs it. Second, keep the original file untouched in a separate folder so that a later compression change can be made from the source rather than from an already compressed copy.

Set an image budget before you compress

A file-size target is useful only when it is set for a specific template and measured on the compiled email. A universal number ignores how many images share the message, how the connection behaves, how the client clips long content, and how much the surrounding HTML weighs. Instead, write a budget for each template: the total weight of images in the message, the largest permitted single image, and the number of images allowed above the fold.

Measure the budget on the file that will be sent. Compile the final HTML, collect every image it references, and add their sizes. If the total is above the budget, reduce the export width, change the format for one image, or remove an image whose only job is decoration. Writing the budget into the template notes makes it a standard the next editor can check, rather than a judgement made again each time.

Budgets also make the image decisions easier to defend. When a stakeholder asks for a full-width photograph in the hero, the team can show the weight it adds, what the same space would carry in live text, and whether the photograph is worth the extra download on a mobile connection.

The 13 tools at a glance

The table below summarizes each tool’s main job, its price where one is published, and the limitation that matters most for email work. Use it to shortlist before reading the individual sections.

ToolBest forPriceKey limitation
SquooshManual compression with side-by-side comparisonNo paid plan named hereOne file at a time; no batch or naming rules
ImageOptimLocal batch compression on macOSNo paid plan named heremacOS only; results vary by file type and version
TinyPNGQuick PNG and JPEG reductionPricing on requestThird-party upload; needs approval for confidential imagery
ImageMagickScriptable transforms in a buildNo paid plan named hereSteep command syntax; a bad recipe scales its mistakes
SharpNode-based responsive derivativesNo paid plan named hereOptimizes files only; needs developer ownership
CloudinaryManaged transformations and CDN deliveryPricing on requestAdds a delivery dependency and access-policy decisions
ImgixURL-based delivery with predictable parametersPricing on requestParameters are not an email fallback; signed URLs need review
Cloudflare ImagesHosted storage near an existing Cloudflare stackPricing on requestPublic retrieval and fallback must be tested for inbox clients
Email on AcidRendering checks with images on, off and in dark modeBasic $99 a month (1,000 previews); Premium $199 a month (2,000 previews)Metered by previews; a screenshot does not test download speed
LitmusPre-send review with approvals and historyPricing on requestPreview cost is separate from hosting and compression
WAVEAccessibility checks on a hosted previewNo paid plan named hereCannot judge whether alt text explains the image
WebAIM Contrast CheckerText over image backgrounds and overlaysNo paid plan named hereA ratio does not prove readability over a photograph
Google PageSpeed InsightsThe landing page behind the email call to actionNo paid plan named hereAudits a web page, not an inbox message

Each tool, for an email team

The sections below describe what each tool does well for email work, where it falls short, what it costs where a price is published, and where to find the vendor’s pricing page. A tool is described for its role in the workflow, not for a claim about how any inbox client will treat its output.

1. Squoosh

Best for: manual compression with side-by-side comparison.

A designer who needs to decide how far to push a hero photograph can compare the original and several encoded versions at the same time, change the format, quality and dimensions, and watch the file size change. For email work the decision is visual, and this makes the trade-off visible before the asset enters a template.

What it does well: Because the comparison is side by side, it is the easiest tool in this list for explaining to a non-developer why one setting is acceptable and another causes banding in sky gradients or halos around product edges.

Where it falls short: It works one file at a time, so it does not batch a folder of product images or write consistent names and dimensions for a template library. Export at the width the image will display, not at the camera original, and then judge the result inside the compiled email rather than in the browser preview.

Price: No paid plan is named in this guide. The project page explains its terms. Pricing page

2. ImageOptim

Best for: local batch optimization on macOS.

Teams that keep a shared asset folder on a Mac can run a whole directory through ImageOptim in one pass. Nothing is uploaded, which matters when the imagery shows unreleased products, staff, or customers.

What it does well: It removes unnecessary metadata such as camera and location data and applies lossless or lossy compression, so one repeatable pass can clean an entire campaign folder before it is handed to a template developer.

Where it falls short: It runs only on macOS, so Windows or Linux colleagues need a different step. Compression results change with the file type and the tool version, which means the settings should be recorded alongside the originals and not recreated from memory next quarter.

Price: No paid plan is named in this guide. The project page explains its terms. Pricing page

3. TinyPNG

Best for: quick PNG and JPEG compression for non-developers.

Marketing coordinators who need to reduce a handful of PNG or JPEG files before a send can do it with drag and drop and no installation. It also gives teams a concrete picture of what a realistic size reduction looks like on their own assets.

What it does well: It is well suited to one-off campaign work and to training: people can see the before and after file size immediately, which helps them understand why a logo that is pure flat color should not be exported as a photograph.

Where it falls short: Images are processed by a third-party service, so confidential product imagery needs internal approval first. Supported formats, usage allowances and terms can change, and the service is not designed to enforce one standard across hundreds of templates.

Price: Pricing on request. See the vendor’s pricing page for the current plans. Pricing page

4. ImageMagick

Best for: scriptable image transforms in a build.

Developers who generate the same set of derivatives for every template can script resizing, cropping, format conversion and metadata removal from the command line. When the rules are predictable, the output is predictable too.

What it does well: Because the recipe is text, it can be reviewed, versioned and run in continuous integration. A change to a crop or quality setting becomes a visible diff rather than a silent change made in a design tool.

Where it falls short: The command syntax is steep for marketing staff, and an incorrect crop or colour profile can damage an important asset across every send that uses it. Pin the version, keep source files immutable, and inspect representative outputs before trusting a green build.

Price: No paid plan is named in this guide. The project site explains its licence. Pricing page

5. Sharp

Best for: Node-based asset pipelines for JavaScript or TypeScript projects.

When email templates are built with code, Sharp can generate responsive derivatives during the build step at the widths the template components support. File names, quality settings and output folders can all be set in code and reviewed like any other change.

What it does well: It fits neatly into a repository that already contains the template, so a pull request can show the new image sizes alongside the markup that uses them.

Where it falls short: Sharp optimizes files. It does not know which inbox clients will download them, how a client will render the result, or whether the image is blocked by default. Document the generated widths, quality settings, cache headers and the fallback path, and test the built output before it is sent.

Price: No paid plan is named in this guide. The project site explains its licence. Pricing page

6. Cloudinary

Best for: managed transformations and delivery across many campaigns.

A team with many products, regions or brands can keep one master image and request resized, reformatted variants through delivery URLs. This removes much of the duplicate preparation that happens when each campaign exports its own copies.

What it does well: Central transformation rules make it easier to enforce a single compression standard, and CDN delivery means the template does not carry the weight of every variant.

Where it falls short: A delivery URL creates a dependency. Access policies, transformation quotas, storage and delivery allowances change over time, and the team needs a plan for what happens when a transformation fails or a URL becomes unavailable. Use stable HTTPS addresses and test them from a representative send.

Price: Pricing on request. See the vendor’s pricing page for the current plans. Pricing page

7. Imgix

Best for: URL-based image delivery with predictable parameters.

When images already live in a managed source, Imgix lets a template request a width, quality or crop through URL parameters. A shared component can therefore reference one asset without the designer exporting every derivative by hand.

What it does well: It suits a component-based template system, where the same hero image is used at several widths and the parameters are defined once.

Where it falls short: A parameterized URL is not a substitute for an email-safe fallback. Signed URLs, cache behaviour, source availability and bandwidth pricing all need review. Keep important copy in HTML, because an email client may block or rewrite remote images.

Price: Pricing on request. See the vendor’s pricing page for the current plans. Pricing page

8. Cloudflare Images

Best for: hosted storage and variants close to an existing Cloudflare stack.

Teams that already run their website or application on Cloudflare can keep email assets in the same operational place, with storage, variant generation and delivery managed together.

What it does well: Operational ownership is simpler when the people who run the landing pages also own the image URLs that the emails reference.

Where it falls short: Packaging, storage limits and transformation rules should be confirmed on the official page. Confirm that generated URLs can be retrieved publicly by inbox clients, that they use HTTPS, and that a sensible fallback exists if an asset is unavailable.

Price: Pricing on request. See the official product page for current packaging. Pricing page

9. Email on Acid

Best for: rendering checks across clients with images on, off and in dark mode.

Teams that need to see the compiled email the way subscribers will see it can use Email on Acid to preview dimensions, clipping, image blocking and mobile layouts across a client matrix. It is most useful after the final HTML and real copy exist.

What it does well: The Premium plan adds accessibility tests and HTML analysis, which connect the visual check to the markup behind the images, including alt text and structure.

Where it falls short: A preview does not measure download speed, and a clean screenshot does not prove that alt text is good. The plan is metered by previews, so a large template library tested across many clients will need a plan that matches the number of previews.

Price: Basic: $99 a month for 1,000 previews a month, with 100+ preview clients and devices and API access. Premium: $199 a month for 2,000 previews a month, adding accessibility tests and HTML analysis. No free plan is listed on the pricing page. Pricing page

10. Litmus

Best for: enterprise pre-send review with approvals and history.

Organizations that run recurring campaigns and need a review trail, with client previews, comments and an approval step, can use Litmus to make image decisions visible to legal, brand and product stakeholders.

What it does well: Preserved review history helps a team explain why a difference between clients was accepted, which is useful when the same image issue comes back in a later campaign.

Where it falls short: Plan features and client coverage change, and the cost of previews is separate from the cost of hosting or compression. Test the compiled message, including dark mode and blocked images, and keep the source asset and final URL in the release record.

Price: Pricing on request. See the vendor’s pricing page for the current plans. Pricing page

11. WAVE

Best for: accessibility checks on a hosted preview.

When a rendered email or a page linked from it is available at a stable address, WAVE can flag missing or questionable alternative text, contrast problems and structural warnings. It is a practical second look before the send.

What it does well: It is quick to run and easy to explain to a non-specialist: each finding points to an element on the page, which turns an abstract accessibility concern into a specific fix.

Where it falls short: Email layout tables and client-specific markup can produce findings that need human judgement. WAVE cannot decide whether alt text explains the purpose of an image. Read the message with images disabled and listen to the alt text order where you can.

Price: No paid plan is named in this guide. The project site explains its terms. Pricing page

12. WebAIM Contrast Checker

Best for: checking text placed over image backgrounds.

Content and design teams use it to verify the foreground and background pairs around image modules, overlays and fallback text. Each pair can be saved with the component decision so that the same colours are not re-argued later.

What it does well: It is simple enough for a copywriter to run and gives a clear pass or fail for normal text and large text.

Where it falls short: A contrast ratio does not prove that text is readable over a photograph with a busy background, in dark mode, or after a client changes colours. Sample the rendered output and keep critical text as live HTML rather than baking it into an image.

Price: No paid plan is named in this guide. The project site explains its terms. Pricing page

13. Google PageSpeed Insights

Best for: checking the hosted landing page behind the email call to action.

When an image-heavy email sends readers to a landing page, the destination can be as slow as the email. PageSpeed Insights audits the web page itself, which shows whether the hero on the landing page is the real bottleneck.

What it does well: It helps a team see that the email asset is only one part of the loading experience and that the landing page may need its own image work.

Where it falls short: It audits a web page, not an inbox message, and its results do not show how an email image will load or render in a client. Verify the destination separately and keep the email usable when images are blocked.

Price: No paid plan is named in this guide. The project site explains its terms. Pricing page

What the tools cost at realistic volumes

Compression itself is usually the cheapest part of an image workflow. Costs appear in three places: the sending volume that a template reaches, the automation that runs the resize step, and the number of rendering previews the team needs. The table compares published plans at three realistic sending levels, followed by the preview and automation plans that sit beside them. Only the figures published on each vendor’s pricing page are used here, and the price for any vendor without a published figure is marked as pricing on request.

ScenarioPlanMonthly priceWhat the limit means
Small list, about 2,500 subscribers and 15,000 emails a monthSender Free Forever$0Covers 2,500 subscribers and 15,000 emails a month, so a single template can be sent without a plan fee.
Growing sends, about 6,000 emails a monthSender Standard$6.30 (monthly or annual billing at the same rate)Covers 6,000 emails a month. The listed subscriber figure for this tier is 500, so check it against your list before choosing.
Larger sends, about 12,000 emails a monthSender Professional$10.50 (monthly or annual billing at the same rate)Covers 12,000 emails a month. The listed subscriber figure is also 500, so confirm the cap for your list.
Automated resize step, 10k credits a monthMake Core$10.59 billed monthly, or $9 a month billed annuallyUnlimited active scenarios and scheduling to the minute. Each module action in a scenario uses one credit.
Light preview testing, 1,000 previews a monthEmail on Acid Basic$99Includes 100+ preview clients and devices and API access. No free plan is listed.
Heavier preview testing, 2,000 previews a monthEmail on Acid Premium$199Adds accessibility tests and HTML analysis to the previews.
Combined example: Sender Standard, Make Core annual and Email on Acid BasicStack total$114.30 ($6.30 + $9 + $99)A realistic starting stack for one sending team that automates resizing and checks each template before release.
Hosted image delivery, a compression API, or a rendering review platformCloudinary, Imgix, Cloudflare Images, TinyPNG, LitmusPricing on requestQuotes depend on volume and usage. Ask for the plan that matches peak campaign volume rather than a demo file.

The figures above are monthly list prices. Derived totals are arithmetic on those figures, and they assume the plans are used as listed. Add any tax, seats or usage charges that a vendor applies in your region, and keep the pricing page open while you compare, because plan limits change.

When two options look close on price, look at the unit that drives the cost. Email on Acid is metered by previews, so the number of templates, clients and revision cycles decides the plan. Make is metered by credits, so the number of module actions in each scenario decides the plan. A sending platform is metered by subscribers and emails, so the image budget has to be planned against those numbers rather than against file sizes.

Automating the resize step with Make

Manual exports fail when the team is busy. A designer uploads a new hero, the template developer forgets to export the mobile width, and the email goes out with a full-resolution file. Automation can remove that step by watching a folder or a storage location and running the compression or resize action whenever a new file appears. Make is one way to build that flow without writing a service from scratch, provided the compression tool offers an interface a scenario can call.

The Free plan lists 1,000 credits a month with no time limit, a maximum of two active scenarios, scenarios that can run at most every 15 minutes, a five-minute maximum execution time and seven days of execution log storage. For a small team that resizes a few files a week, that is enough to test the flow. The Core plan lists unlimited active scenarios, scheduling down to the minute and access to the Make API, starting at $10.59 a month billed monthly or $9 a month billed annually for 10k credits. Pro lists $18.82 monthly or $16 annually for the same 10k credits and adds priority execution and full-text execution log search. Teams lists $34.12 monthly or $29 annually and adds shared scenario templates. Enterprise pricing is on request.

Set the automation up in stages. First, run one file through the flow by hand and check the output in the compiled email. Second, add the rule that names files with a version suffix and never overwrites an original. Third, add a notification when a step fails, so that a missing export does not reach the send unnoticed. Automation reduces the number of manual steps; it does not replace the rendered check, and a scenario that produces a bad file will produce it reliably until someone looks.

Alt text and the image-off test

Alt text is what a reader gets when an image does not load, and it is also what a screen reader announces. Write it for the purpose of the image. Describe what the reader needs to know or do, not what the picture contains. A product photograph that shows the item the offer is for should name the item and the offer, while a decorative divider should be marked as decorative rather than given a sentence that adds nothing.

Test the message with images off before every send. Read the email from top to bottom and ask whether the offer, the price, the product names and the call to action still make sense. If a single line of text depends on an image, move that text into HTML. Keep alt text short enough that a screen reader does not stall on it, and avoid starting every description with the phrase “image of”, because the reader already knows that an image is present.

Premium Email on Acid plans list accessibility tests and HTML analysis, which can flag structural problems alongside the visual preview. Pair those results with a manual read in the image-off state, because an automated check cannot judge whether the words say what the image was meant to say.

Contrast, text over images and dark mode

Text placed over a photograph is the most fragile part of an image module. Its legibility depends on the photograph, the overlay opacity, the text size and the client’s colour treatment. The WebAIM Contrast Checker gives a fast ratio for the foreground and background colours, and the result can be saved with the component so that the same pair is reused rather than re-argued. A passing ratio is a starting point, not a guarantee, because the photograph behind the text can vary across the area the text covers.

Dark mode adds a second layer. A client may invert colours, lighten a logo or change a background, and an image with a transparent background can gain a visible edge. Compare each image module in light and dark rendering, and keep the logo on a solid panel or in a format that tolerates the change. Where possible, make the critical text live HTML so that the colour treatment applies to the text itself, rather than to a picture that was exported with fixed colours.

Use WAVE on the hosted preview to catch contrast issues it can detect and structural problems in the markup. Then read the rendered sample yourself. The combination of an automated check and a rendered sample catches more problems than either alone, and it leaves a record that the next editor can review.

Which tool for which job

Most teams do not need all 13 tools. The table below matches common jobs to the tools that fit them, and the reason each fits. Use it to pick one tool per job, then add a second only when the first leaves a gap that a real send has exposed.

If you need to…PickBecause
Shrink a few PNG or JPEG files this weekTinyPNG or SquooshVisual comparison or drag-and-drop, with no setup and no developer needed.
Batch a folder of assets on a MacImageOptimIt runs locally, strips metadata and leaves nothing on a third-party server.
Generate the same sizes on every buildSharp or ImageMagickThe recipe is code or a script, so it can be reviewed, versioned and pinned.
Serve resized images from hosted URLsCloudinary, Imgix or Cloudflare ImagesTransformations are requested by URL, so one master file serves many campaigns.
See the compiled email with images off and in dark modeEmail on Acid or LitmusOnly a rendered preview of the final HTML shows clipping, blocking and inversion.
Audit a hosted preview for accessibilityWAVE, then the Premium accessibility tests if you have themAutomated checks catch missing alt text and structure; a person still judges the wording.
Check text placed over a photographWebAIM Contrast Checker, then a rendered sampleIt gives a ratio quickly, and the sample shows what the ratio cannot.
Improve the landing page behind the call to actionGoogle PageSpeed InsightsIt audits the destination page, which is often where the wait happens after the click.

Setup checklist for a new image workflow

A workflow is easier to keep when the steps are written down in order. The checklist below can be copied into a template’s release notes. Each step lists the action and the condition that shows the step is finished, so a reviewer can check the work without asking the person who did it.

StepActionDone when
1. InventoryList every image in the template with its role, display width, pixel density, alt text owner and destination link.Each image has a row and a named owner.
2. ExportExport at the displayed width, with 2x density only where the layout needs it. Name files with a version suffix.No file is named final or latest.
3. CompressRun the chosen tool with a recorded preset. Keep the untouched originals in a separate folder.The preset and tool version are written down.
4. HostUse absolute HTTPS URLs that do not expire between sends. Test each URL from outside your network.Every URL loads in a private browser window.
5. CompileSet width and height attributes, real alt text, and live HTML for offers, prices and calls to action.The message reads correctly with images off.
6. PreviewCheck target clients with images on, blocked, zoomed and in dark mode, at desktop and mobile widths.Screenshots are archived with the release.
7. Release and repeatRecord the final files, URLs, exceptions and approver. Repeat after any template, CDN or sender change.The next editor can find the source files without asking.

When you move an existing template to a new sender or to a new compression pipeline, treat it as a new template. Hosted assets can expire, cached references can point at old files, and image dimensions can change under a different rendering path. Run the full checklist once on the migrated template before the first real send, and keep the record with the template so that the next migration starts from the same place.

How to choose

Start with the message. If the email depends on an image to carry its offer, fix that first, because no compressor will make a hidden offer visible. Then decide who owns each step. A designer who prepares images on a Mac may be best served by ImageOptim and a shared preset. A developer who builds templates may be better served by Sharp or ImageMagick, with the settings in code. A team with many products and regions may need a managed delivery service, with its quotas and access rules owned by someone.

Next, choose the rendering check. The cost of a preview plan depends on the number of previews, so count the templates, clients and revision cycles you run in a typical month before choosing a plan. Email on Acid is the most direct option for a visual check of the compiled email, and its Premium plan adds accessibility tests and HTML analysis. Litmus suits teams that need review history and an approval step, and its pricing is on request.

Last, decide what you will not do. Do not put the only copy of an offer in an image. Do not rely on WebP or SVG without a tested fallback. Do not use a single universal file-size rule. Do not treat a green build or a passing ratio as proof that the email works. Each of these habits is cheap to keep and expensive to fix after a send.

Pre-send checklist

  • Every image has a purpose, a display width, an owner and a documented fallback.
  • The offer, prices, product names and call to action are live HTML, not image text.
  • Images use absolute HTTPS addresses, explicit width and height, and tested alt text.
  • Each format was checked against the clients the audience actually uses, with a fallback where support is uneven.
  • The compiled email was reviewed with images on, images off, zoomed, at a narrow width and in dark mode.
  • Destination pages and tracking links were clicked from a representative test send.
  • Original files, derivatives, compression presets, screenshots and accepted exceptions are archived with the template.

Frequently asked questions

What is the most important image decision in an email?

Deciding what the image is for. If the image carries the offer, the price or the only call to action, the email fails when images are blocked. Move that meaning into live HTML first, then use the image to support it. Compression and format choices come after that decision, because they cannot fix a message that depends on pixels.

Do I need a paid tool to optimize email images?

No. Squoosh, ImageOptim, Sharp and ImageMagick cover compression and resizing without a subscription in this guide. The paid part of most workflows is either hosting and transformation, or rendering previews across clients. Email on Acid lists its Basic plan at $99 a month for 1,000 previews and its Premium plan at $199 a month for 2,000 previews.

Is WebP safe to use in email?

Not everywhere. Support varies by client and by platform, so a WebP that renders in one inbox can be blank in another. If you use it, provide a tested fallback in a format every target client supports, and check the result in the rendered preview rather than trusting a general support table.

Should the hero image contain the headline?

It is better when it does not. A headline inside an image disappears when images are blocked, cannot be read by a screen reader, and can be clipped on a narrow screen. Keep the headline as live text above or beside the image, and let the image reinforce it.

How many previews do I need to test a template?

Multiply the number of templates by the number of clients, states and widths you need to cover. A template tested in four clients, with images on, images off and dark mode, uses twelve previews before any revision. Count the revisions as well, because each new compile needs a new check. Basic covers 1,000 previews a month and Premium covers 2,000.

What background colour should I use behind an image that might not load?

Pick a background colour that keeps the text readable and the layout intact if the image is blocked. Background-image support differs by client, especially in some Outlook versions, so test the fallback and do not rely on a background image to carry the message.

Can I automate resizing when a designer uploads a new file?

Yes, if the compression step has an interface you can call. Make can watch for new files and run a scenario, and its Free plan includes 1,000 credits a month with a limit of two active scenarios. Its Core plan lists $10.59 a month billed monthly or $9 a month billed annually for 10k credits. Automation reduces manual steps; it does not replace the rendered check.