How to Compress Images for Email Without Losing Quality

Modern phone photos are huge. A single image from a recent iPhone or Android can run 4–6 MB. Try to attach 5 of them to an email and you’re already brushing up against the 25 MB limit Gmail enforces — and Outlook’s limit is even lower at 20 MB. The email bounces, your recipient doesn’t get it, and you have to figure out what to do next.

The fix is compression. Done right, you can take a 5 MB photo down to under 500 KB without the recipient being able to tell the difference. Here’s how.

The fastest way: compress in your browser

Use the Image Compressor. Drop in your photos, choose a target quality or size, click compress. The result downloads to your computer.

The flow:

Open the Image Compressor
Drag in one or more images (JPG, PNG, WebP)
Pick a quality level or target file size
Click compress
Download the smaller versions

No upload, no signup, no watermarks. The compression happens entirely in your browser using browser-image-compression, which uses the same lossy algorithm your phone camera uses but with smarter parameter choices.

How small can you go without it looking bad?

For photos meant for human viewing (email, social media, web), here’s what to expect:

Quality 0.9 (90%) — visually indistinguishable from the original. ~30–50% smaller file.
Quality 0.8 (80%) — still indistinguishable in most cases. ~50–70% smaller. This is the sweet spot for email.
Quality 0.7 (70%) — slightly softer if you zoom in 200%+, but normal viewing is fine. ~70–80% smaller.
Quality 0.5 (50%) — visible artifacts in solid color areas (skies, walls). Still OK for thumbnails and quick previews. ~80–90% smaller.
Quality 0.3 (30%) — obviously degraded. Use only when file size matters more than appearance.

Most people land at quality 0.8 and never need to touch it again. A 5 MB iPhone photo at quality 0.8 typically becomes about 600–900 KB. You can email ten of them under Gmail’s limit easily.

Resize first or compress first?

This is where people lose quality unnecessarily.

Phone photos are typically 4032 × 3024 pixels — way more resolution than anyone needs for email viewing on a laptop or phone screen. If you compress at full resolution, you’re encoding detail no one will see, and the file is still large.

Resize first, then compress. That order gets you to small file sizes without making the image look bad.

Target dimensions:

Email attachment: 1600 px on the longest side is plenty. Phone screens are 1080–1440 px wide, laptop screens 1920 px. Most email clients show photos shrunken anyway.
Sharing as a thumbnail: 800 px on the longest side.
Just showing it to someone: 1200 px is fine.

Use the Image Resizer first to bring the dimensions down, then run the resized image through the Image Compressor for the final size reduction. Two tools, 30 seconds total, and a 5 MB photo becomes 200 KB while still looking great.

What about iPhone HEIC photos?

If you’re emailing photos from an iPhone, they might be in HEIC format. Some email clients display them fine; others don’t. To be safe, convert HEIC to JPG first with our HEIC to JPG tool, then run the JPG through the compressor.

The full workflow for emailing iPhone photos:

HEIC to JPG — convert from iPhone’s format to universal JPG
Image Resizer — bring dimensions down to ~1600 px
Image Compressor — apply quality 0.8 compression

Total time: under a minute even with several photos. Final size: typically 80–90% smaller than the original.

Common mistakes that hurt quality

Compressing already-compressed JPGs over and over. Every time you save a JPG, it gets slightly more degraded. If you compress, then someone forwards it, then they compress again, then you save and recompress — by the fifth round you can see the damage. Compress once, save the result, work from that.

Using PNG for photographs. PNG is lossless, which sounds great, but it’s much less efficient than JPG for photos. A PNG version of a photo is usually 3–5× the JPG size at no visible quality benefit. Save PNG for graphics, screenshots of text, and images with sharp edges. Save JPG for photos.

Compressing screenshots of text. When you compress, you’re applying a lossy algorithm. On photos, the lossiness hides in noise and detail. On screenshots of text, it shows up as fuzziness around letters. Either use PNG, or compress at quality 0.95+ for screenshots.

Resizing to less than 800 px. You can’t go back. If you resize a photo down to 500 px wide and the recipient asks for a higher-res copy, you have to start over with the original. Save the original, share the small version.

Privacy: photos contain location data

Photos from your phone often include EXIF metadata — GPS coordinates of where the photo was taken, the time, the camera model, sometimes even your phone’s serial number. When you email a photo, that data goes with it.

Most of the time this is harmless. But if you’re emailing a photo of your kid in front of your house, your child’s school, or anywhere you’d rather not advertise your location, the GPS data is in the file.

We have a separate tool for this: EXIF Stripper. Drop the image in, get back a clean version with no metadata. You can run this on any image, before or after compression, in any order.

For sensitive photos, the safe full workflow is:

HEIC to JPG if needed
EXIF Stripper — remove location and metadata
Image Resizer
Image Compressor

What if the email service is really strict?

Gmail caps at 25 MB. Outlook at 20 MB. Yahoo at 25 MB. Some corporate email systems are far stricter — 5 or 10 MB.

If even compressed photos won’t fit:

Send fewer at a time. Two emails of 4 photos each beats one bounce.
Compress harder (quality 0.6 instead of 0.8) for the largest photos.
Resize more aggressively (1200 px instead of 1600 px).
For really large batches, share via a link instead — Google Drive, Dropbox, or just zip the folder and use WeTransfer.

But for the typical “I have a few photos to send my mom” use case, compress at quality 0.8 and you’re done.

TL;DR

5 MB phone photos won’t fit in email. Run them through the Image Compressor at quality 0.8 and they’ll become around 500 KB with no visible difference. Resize first with the Image Resizer if you want maximum file size reduction. Use EXIF Stripper before sending if the photos contain sensitive location data. All three run in your browser — your photos never get uploaded.