Irreva logo
Explore Irreva
ImageMarch 16, 2026· 6 min read· Updated June 10, 2026

How to Reduce Image Size for Email Attachment

Hasanur Rahman

Written by Hasanur Rahman

Founder & Full-Stack Developer · Irreva · Rangpur, Bangladesh

Email was not built for multi-megabyte photos. Gmail warns around 25MB total per message; corporate servers often cut off far sooner. If your message sits in the outbox or the recipient gets an empty attachment, the images are almost certainly too large. Learning how to reduce image size for email attachment problems takes five minutes and saves repeated send failures.

Why email rejects large images

Mail servers limit attachment size to protect storage and delivery speed. A single modern phone photo can exceed an entire message quota. Multiple photos multiply the problem quickly.

Mobile data matters too. Recipients on slow connections may not wait for a 15MB download. Smaller attachments arrive faster and feel more considerate.

Some companies strip large attachments entirely, replacing them with a notice that the file was removed. Compressing before sending avoids that silent failure.

  • Gmail: roughly 25MB total message size
  • Outlook and Exchange: often 10–20MB limits
  • Corporate gateways: sometimes under 5MB
  • Mobile recipients: slow on large files

Resize before you compress

Email viewers rarely show images wider than 800–1200 pixels. Sending a 4000-pixel original wastes space without improving what the recipient sees.

Resize to the display size you expect — full width for a newsletter inline image might be 600 pixels; a photo a colleague will open separately might be 1600 pixels max.

After resizing, compression has less work to do and quality stays higher at the same file size.

Best format and quality for email

JPG is the safest choice for photos in email because every client displays it. WebP is smaller but some desktop clients still render it inconsistently in 2026.

Use PNG only for screenshots with text or logos needing transparency. PNG photos are unnecessarily large.

Quality between 70% and 80% is the sweet spot for email photos. Check one image at full size before batch-processing the rest.

Step-by-step compression workflow

Select all images you plan to attach. Open the Irreva Image Compressor, drag them in, and set quality to around 75%.

Review total size in your file manager after download. Aim for well under your server's limit — under 5MB total per message is a safe target for corporate recipients.

Attach the compressed files, add a short note describing the content, and send. If files are still large, resize further or split across two messages.

Compress email attachments on Irreva

The Irreva Image Compressor shrinks photos in your browser before you attach them. No upload to a third-party server, no watermarks, no account required.

Batch-process a whole set, download a zip, and attach the smaller files. Your message sends on the first try, and recipients get images that open quickly on any device.

Frequently Asked Questions

What size should email photos be?

Keep individual photos under 500KB when possible and total attachments under 5–10MB for compatibility with strict servers.

Should I zip images before emailing?

Zipping helps many files but some recipients cannot preview inside archives easily. Compressing images directly is usually clearer.

Does reducing size ruin print quality?

Email-sized images are meant for screen viewing. Keep original files separately if the recipient needs to print at high quality.

Can I compress iPhone HEIC photos for email?

Convert HEIC to JPG first using the HEIC to JPG tool, then compress. Most email clients handle JPG reliably.

Is cloud storage better than large attachments?

For many large files, sharing a link is smarter. For a few photos, compressed attachments feel simpler for non-technical recipients.

Hasanur Rahman

About the author

Hasanur Rahman

Founder & Full-Stack Developer · Irreva · Rangpur, Bangladesh

Hasanur Rahman is the founder of Irreva and a full-stack developer based in Rangpur, Bangladesh. He builds all of Irreva's tools with a focus on privacy-first, browser-based processing.