Back to Guides

Guide

How to compress images for email without making them look blurry

Email is one of the easiest places for image workflows to go wrong. Files are often larger than they need to be, but over-compressing them can make the result look cheap or hard to read. This guide explains the tradeoff in a practical way.

9 min readAnyone sending image-heavy emails, proposals, updates, or attachments.
By the Slim Files Editorial TeamReviewed and maintained by the team that builds the tools referenced in this guide.

Why email attachments get heavy so quickly

A lot of email images start as full-size camera photos, large screenshots, or oversized product images that were never prepared for attachment use. Email does not need the same image weight that print, editing, or raw storage might require.

That means the goal is not maximum fidelity at any cost. The goal is to reduce the file enough that it sends smoothly and still looks clean in the context the recipient will actually use. A photo that will be viewed at 600 pixels wide in a mail client does not need to be 4000 pixels wide when attached.

The two main contributors to attachment size are dimensions and quality. Handling both gives you much more control than focusing only on compression quality. A 4000-pixel photo compressed to quality 60 is often still larger than a 1200-pixel photo at quality 85, and the smaller one will usually look better at the size it is actually displayed.

What email providers allow in terms of attachment size

Gmail allows attachments up to 25 MB per email. Outlook and Microsoft 365 accounts typically allow 20 MB to 25 MB, though corporate IT policies sometimes impose lower limits. Apple Mail uses whatever the sending provider allows. Many corporate and government email systems have stricter limits, sometimes as low as 5 MB or 10 MB per message.

If you are sending to a recipient whose email limits you do not know, keeping total attachments under 10 MB is a reasonable general-purpose target. For images specifically, aiming for 200 KB to 500 KB per image is usually sufficient for professional communication and keeps total message size practical even with multiple attachments.

Some email servers also resize or strip attachments automatically. If a recipient tells you they received a blurry or missing image, the cause is often server-side resizing by the recipient's email provider rather than something you did wrong during compression.

Compression works best when the dimensions are already reasonable

If an image is thousands of pixels wide but will only be viewed in a mail client or opened quickly on a phone, resizing first can make as much difference as compression quality. Overly large dimensions often carry unnecessary weight before any quality tradeoff is even introduced.

That is why a good email workflow is often resize first, then compress. You reduce both visual excess and storage excess in the same sequence. For most email contexts, resizing to 1200 pixels on the longest edge before applying compression is a reasonable starting point.

If the image is already a reasonable size — a screenshot at 1400 pixels wide, for example — then compression alone is usually the right move. But when you are working with raw phone photos or large exported images, resizing first almost always produces a better result at the same file size target.

Format compatibility across email clients

JPG is the most universally safe format for email attachments. Every major email client, mobile app, and webmail service handles JPG reliably. PNG is also widely supported for attachments. WebP has improved its email client compatibility in recent years but is still not universally rendered inline in all clients, particularly older Outlook versions.

For screenshots with text, PNG often produces better results than JPG because text edges stay crisp. If file size is a concern, compressing a PNG screenshot is usually preferable to converting it to JPG and losing sharpness. For photos, JPG at quality 80 to 85 is the reliable default.

If you are sending images as part of an HTML email newsletter or template rather than as a direct attachment, WebP is more viable because modern email clients that render HTML properly also tend to support WebP. But for simple file attachments, JPG or PNG is the safer default.

What to preserve and what to sacrifice

Photographic images can usually tolerate moderate JPG-style compression without causing obvious problems in email. Screenshots, interface captures, and images with lots of text need more care because softness becomes visible much faster.

If readability matters more than tiny file size, it is better to stop at a balanced result than to chase the smallest number possible. The best email image is not the tiniest file. It is the smallest file that still looks intentional.

For photos where visual quality matters — client-facing proposals, product samples, portfolio work — quality 80 to 85 for JPG is usually the right floor. Going below quality 70 for anything professionally important is risky. Artifacts at lower quality levels become more noticeable on high-resolution displays.

  • Photos usually compress more gracefully than screenshots.
  • Text-heavy graphics should be tested more carefully before sending.
  • A smaller, clearer image is usually better than a giant original a mail client has to scale down.
  • Quality 80 to 85 is a safe floor for professionally important JPG images.

When to embed images vs. attach them

There are two ways to include images in an email: as file attachments that the recipient downloads, or as inline images embedded in the body of the email. Direct attachments are simpler and more reliable for most purposes. The recipient clicks the attachment and opens the file.

Inline embedding is more common in HTML newsletters and marketing emails, where images appear directly in the email body. For regular business email, direct attachment is almost always the right approach. Inline images in plain business emails can trigger spam filters and look strange in some clients.

If you are sending a batch of images — for a project review, a set of product samples, or a photo series — consider zipping them rather than attaching them individually. A zip file keeps the email cleaner and makes it easier for the recipient to download everything at once.

A repeatable email workflow

For recurring email workflows, the easiest process is: choose sensible dimensions for the context, compress to a balanced quality level, and verify readability before sending. That avoids both huge attachments and unnecessary visual damage.

If the email contains multiple images, consistency matters too. A set of evenly prepared attachments usually feels more professional than a mix of giant originals and heavily degraded files. Decide on a standard preparation process for your most common email image types and apply it consistently.

Related guides

How to compress images for email without making them look blurry | Slim Files