Free · Runs in your browser · No sign-up

Compress images so they send by email

Pick a target size that fits your mail provider, drop the photo in, and download a file that will not bounce.

Target file sizeCurrently aiming for 1.00 MB or less
KB

Sizes use 1 KB = 1,000 bytes, the way most upload forms count, so a "100 KB" result is at most 100,000 bytes.

Output formatPNG has no quality dial, so Auto compresses PNG input as WebP.

Drop a JPG, PNG or WebP image here

Compression runs in your browser. The file is not uploaded to a server.

Defaults to 1MB — comfortable for every major mail provider.

Step by step

  1. Choose a target size. 1 MB per image is safe almost everywhere; drop to 500 KB if you are attaching several.
  2. Drop the photo into the tool, or click to choose it from your device.
  3. Look at the before/after slider to confirm the photo still looks right.
  4. Download the compressed file.
  5. Attach the downloaded file — not the original — to your email.
  6. If you are sending more than five photos, compress each one and consider a shared link instead of attachments.

The attachment limits that actually apply

Gmail accepts attachments up to 25MB, Outlook.com up to 20MB, and Yahoo Mail up to 25MB. Those are the headline numbers, but they are rarely the number that matters. Email attachments are Base64-encoded in transit, which inflates them by roughly a third, so a 20MB set of photos arrives as about 27MB of message. Many corporate mail servers cap incoming messages at 10MB or even 5MB, and that cap applies to the inflated size.

The practical rule: keep the whole message under about 8MB and you will never think about it again. For a single photo that means 1MB is generous. For a set of ten, 500KB each keeps you comfortably inside every limit that exists in the wild.

Why the recipient matters more than your provider

Your outbound provider is only half of the journey. A message that Gmail happily sends can still bounce when it reaches a recipient whose employer runs a strict gateway. Bounce messages for oversized attachments are often delayed by hours, so you find out long after you assumed the email arrived.

Compressing before you send removes the entire class of problem. It also makes the email faster to download on a phone with poor signal, which is where most business email is actually read.

How much quality you actually lose

A typical 4MB phone photo compressed to 1MB is, in ordinary viewing, indistinguishable from the original. You are discarding detail that was never visible on a screen. At 500KB the difference becomes findable if you zoom in on textured areas, but it is still comfortably good enough for sharing holiday photos, sending a document scan, or showing a colleague a product shot.

The one case where care is warranted is photos someone will print. Printing needs the pixels, so if the recipient intends to print at anything larger than a postcard, use a file-sharing link and send the original rather than compressing.

What target size to pick

SituationTarget per imageWhy
One photo, personal email1 MBLooks essentially identical and sends anywhere
Three to ten photos500 KBKeeps the whole message under the strictest corporate caps
Attaching to a form or ticket system200 KBHelpdesk systems often cap far below mail providers
Scanned document or receipt200–500 KBText stays readable and the file stays small
Photo the recipient will printDo not compressSend a shared link with the original file instead

If something goes wrong

The email still bounced after compressing

Check the total message size, not the individual files. Ten 1MB photos is a 10MB message before Base64 inflation, which pushes it past strict gateways. Compress to 500KB each, or send fewer per message.

The photo looks washed out after compressing

That is usually a colour-profile issue rather than compression. Photos saved in a wide-gamut profile can shift when re-encoded. Try the WebP output option, which handles colour more predictably than JPG in browser encoders.

My phone photos are HEIC and will not open for the recipient

HEIC is an Apple format that Windows and older Android devices often cannot open. Convert to JPG first, then compress. There is a dedicated converter linked below.

Outlook shrinks my images automatically — should I still compress?

Outlook's built-in resize is coarse and applies to every attachment at once, with no preview. Compressing first gives you control over exactly which file the recipient gets.

Frequently asked questions

What is a safe image size for email?
Under 1MB per image, and under about 8MB for the whole message including all attachments. That clears Gmail, Outlook, Yahoo and virtually every corporate mail gateway.
Does compressing affect how the photo looks in the email body?
Inline images are usually displayed at a few hundred pixels wide, so a 1MB compressed file already carries far more detail than the display needs. There is no visible difference.
Are my photos uploaded to compress them?
No. Everything runs locally in your browser. Photos of family, documents, or anything sensitive never leave your device.
Should I use JPG or WebP for email?
JPG. Every mail client on earth renders JPG. WebP support in email clients is still inconsistent, particularly in older desktop Outlook versions.
Can I compress several images at once?
This tool handles one image at a time so you can check each result. For bulk work, the general compressor linked below processes a whole batch and hands back a ZIP.
Will compressing remove the location data from my photos?
Yes. Re-encoding drops EXIF, including GPS coordinates — which is usually what you want before emailing a photo to someone outside your household.

Related tools and guides