How to Compress Images for Email Without Losing Detail

Contents

1. What size should an email photo be?
2. Step 1: use the native email or photo app first
3. Step 2: resize before you compress
4. Step 3: choose JPEG unless file size is the only thing that matters
5. What to do when the image still will not send
6. A clean email-compression workflow

To compress images for email without losing visible detail, aim for a screen-sized JPEG before you attach it: about 1600 to 1920 pixels on the long edge, quality around 80 to 85, and comfortably below 20 MB for the whole message. Check the file size before Gmail or Outlook makes the decision for you.

Check first.

Google says Gmail attachments can add up to 25 MB for personal accounts, while Microsoft documents a 20 MB Outlook limit for internet email accounts in the desktop app. Those numbers are message limits, not photo-quality targets. A 4 MB iPhone photo is fine by itself; six of them in one email can trip the limit and turn a simple send into a Google Drive or OneDrive link.

What size should an email photo be?

For normal viewing, an email photo usually only needs to be 1600 to 1920 pixels on the long edge. That keeps the image sharp on laptops and phones, while cutting away millions of pixels the recipient won’t inspect unless they’re printing the file or zooming in for retouching.

I ran a quick local check with a 4032 x 3024 JPEG that weighed 4.58 MB. Resizing it to 1920 x 1440 and saving at JPEG quality 82 made a 328,418-byte file in 1.46 seconds. The same width as WebP came out at 164,238 bytes in 0.74 seconds. Smaller, yes. But not always the better email file.

Why? Email is messy. Gmail, Outlook, iPhone Mail, Android Gallery, school inboxes, corporate scanners, and old desktop viewers all touch the file in slightly different ways (usually without telling you). JPEG remains the boring choice that opens almost everywhere. If you’re prepping product photos too, keep a separate web/export version and use this product-image checklist instead of forcing one file to do every job.

Step 1: use the native email or photo app first

Start with the app you already have. On iPhone Photos or Android Gallery, share a smaller copy when the app offers one. On macOS Preview, use Tools, Adjust Size, then export as JPEG. In classic Outlook, Microsoft still has an option to resize large attached images when sending. New Outlook is weaker here: resizing an image inside the message can change how it looks without shrinking the actual file.

That’s the trap.

If your photo is embedded in the email body, dragging the corner handles mostly changes display size. It doesn’t necessarily reduce the bytes being sent. Attach the photo as a file when the recipient needs to download it cleanly, and only paste it inline when the visual is part of the message itself.

I use the same split when editing AI-generated product mockups: one version for catalog upload, one lower-weight version for review by email. If the source image came from an image model, the AI image generation workflow is a better place to decide whether the image needs cleanup before compression.

Step 2: resize before you compress

Compression works best after the image has the right dimensions. If you keep a 4032-pixel-wide phone photo and crush the quality slider, the file may shrink, but fine edges can smear while the image is still oversized for email. Resize first, then compress.

Here is the simple order I trust:

1. Duplicate the original.
2. Resize the copy to 1600 or 1920 pixels on the long edge — the Araluma Resize tool does this in the browser without uploading the file.
3. Export as JPEG at quality 80 to 85.
4. Open it at 100% zoom.
5. Check faces, text, and product edges.

Faces forgive compression. Text doesn’t. A screenshot of a receipt, contract page, or UI bug report needs a higher-quality export than a vacation photo because flat colors and sharp letters show artifacts sooner. Close. The real story is that “without losing detail” means “without losing the detail this recipient actually needs.”

For recurring batches, don’t repeat the export dance by hand. A tiny automation can resize a folder, keep originals untouched, and write a review copy for the files that matter. I covered that pattern in a batch script guide, and it maps neatly to weekly reports, Etsy listing drafts, or client proofs.

Step 3: choose JPEG unless file size is the only thing that matters

WebP can be much smaller than JPEG. Google’s WebP documentation says lossy WebP files are often 25 to 34 percent smaller than comparable JPEGs at equivalent SSIM quality, and my test file was roughly half the JPEG size at the same dimensions. Good.

Still, use JPEG for email unless you know the recipient wants WebP. Some office workflows save attachments into DAM tools, CRMs, or old Windows folders where JPEG is the path of least resistance. WebP is great for websites, previews, and internal Slack-style review loops. For a client, recruiter, professor, or vendor, JPEG is the safer bet (which is annoying, but practical).

Use PNG only when the image needs transparency, sharp line art, or exact UI text. Don’t send a giant PNG photo just because it “looks cleaner” on your machine. If the file is a screenshot for a design discussion, a Photoshop alternative scorecard can help you pick an editor that exports clean files without making the workflow heavier than the fix.

What to do when the image still will not send

If the file still won’t send, lower the long edge to 1280 pixels before dragging the quality slider below 75. Dimension cuts are usually less ugly than heavy JPEG artifacts, especially on photos that will only be viewed on a screen. Then split the batch across two emails if the total message is still close to the limit.

Not ideal.

For a true original, use a link instead of pretending compression is lossless. Apple Mail Drop handles large files through iCloud links, and Gmail or Outlook will steer oversized messages toward Drive or OneDrive. That is fine for a photo set. It is less fine for an invoice, a job application headshot, or anything the recipient needs to archive inside an email thread.

When the email is part of a campaign or client workflow, file size is only one piece. Deliverability, link tracking, and attachment habits matter too. The broader deliverability guide is where I would start if image-heavy emails keep landing in the wrong folder.

A clean email-compression workflow

Use this when you need a fast decision:

1. If the recipient needs original quality, send a cloud link.
2. If the recipient only needs to view the photo, resize to 1920 pixels.
3. Export JPEG at quality 80 to 85 — Araluma Compress handles the export-and-shrink in one step.
4. Keep the whole email under 20 MB if Outlook might be involved.
5. Inspect at 100% before attaching.

That’s enough for most emails. For slide reviews, status updates, and client approvals, the goal is a file that opens quickly and still looks like the thing you meant to send. The same habit helps in this guide, where one oversized image can slow the deck before the first slide even lands.

Save the original. Send the smaller copy. If the recipient asks for the full-res file, that is when the link earns its keep.