Compress images before email attachments

Email providers cap attachment size. Gmail and Yahoo Mail stop around 25 MB per message. Outlook often lands near 20–25 MB; corporate inboxes may cut that to 10 MB. One iPhone photo can reach 5–8 MB before you add a PDF or a second shot. Shrink the image file, pick a quality level that still looks fine on a laptop, and attach the lighter copy. Toolsy’s Compress image redraws JPG, PNG, or WebP at a quality you choose (default 75%). Re-encoding also drops classic EXIF, including GPS, which matters for family photos. Free daily quota applies. If the message still bounces, resize pixel dimensions or use a cloud link.

Why email blocks large photo attachments

You hit Send and the client stalls, or the server returns a size error. The photo looked normal in your gallery. Email systems measure bytes, not how nice the sunset was.

Attachment limits exist because mail servers store and forward whole messages. A 30 MB thread with four phone photos taxes routing, mobile downloads, and archive quotas. Providers publish caps so senders know the ceiling before the SMTP handshake fails.

Limits also differ by path. You might attach directly in Gmail’s web UI, paste into Outlook desktop, or route through a company Exchange server. Each hop can enforce a lower cap than the marketing page quotes. When in doubt, aim for a few megabytes per image unless the recipient confirmed a higher allowance.

Gmail, Outlook, and typical caps

Gmail’s help docs cite about 25 MB for attachments in a single message. Above that, Gmail pushes you toward Google Drive links instead of inline files. That number is a useful planning target even when you use another provider.

Outlook and Microsoft 365 commonly cite 20–25 MB depending on account type and admin settings. Hosted Exchange tenants sometimes set 10 MB for inbound mail. If your message reaches coworkers but bounces to an external client, the external server may be the stricter gate.

Yahoo Mail aligns with the same ballpark near 25 MB. iCloud Mail and smaller hosts vary. Search “email attachment size limit” when you switch providers; treat published numbers as a starting point and compress harder when the first send fails.

Why one photo can exceed the cap

Modern phones save 12 MP frames at high JPEG quality. Each file can sit between 3 MB and 10 MB without feeling “huge” on your phone. Attach three event photos and you are already flirting with a 25 MB ceiling before signatures and quoted text add weight.

HEIC from iPhone compresses efficiently on disk, yet many Windows recipients cannot open it without conversion. You might export a larger JPG “for compatibility,” which doubles the pain. Screenshots saved as PNG carry flat color but bloated files. The limit bites when format, resolution, and quality all stay at camera defaults.

What makes a camera photo balloon in size

File size comes from three levers: pixel count, compression format, and quality setting. Email clients rarely care about any of them until the total package crosses the provider cap.

Pixel count is the width times height. A 4032×3024 frame holds far more data than a 1280×960 version of the same scene. You need fewer than 4000 pixels across for someone reading mail on a laptop. Extra pixels mostly inflate storage without helping the inbox preview.

JPEG uses lossy compression. The encoder throws away detail you are unlikely to notice at normal viewing distance. PNG is lossless. It preserves UI text and flat fills but grows fast on photographs. WebP can beat JPEG on size at similar quality, yet some older mail clients and CMS forms still want JPG.

Metadata adds a small tail. EXIF can record camera model, capture time, and GPS. It is not usually what pushes a 6 MB file to 20 MB, but it travels with the attachment unless you strip or redraw the image. Compression that re-encodes the pixels clears classic EXIF as a side effect. For location privacy on family shots, see Remove EXIF GPS before sharing kids' photos.

Quality tradeoffs when you compress for email

“Compress image without losing quality” is a reasonable search. The honest answer is that all lossy compression discards something. The job is to discard what your recipient will not see on a mail preview pane.

Aim for a file that opens crisply at 100% zoom in a browser tab, not a pixel-perfect archive for print. Email is a delivery channel, not a photo vault. Keep the master in your camera roll or cloud library. Send a copy tuned for transit.

Drop quality in steps. Export at 80%, check faces and text edges, then try 70% if you still need bytes. Banding in skies or muddy shadows means you went too far. Bump quality up one notch and, if needed, shrink width instead of crushing JPEG further.

JPEG quality settings that still look fine

For everyday photos (birthdays, products on a table, team lunch), 70–80% JPEG quality survives email fine. Toolsy defaults to 75% on Compress image. That is a sensible first pass for a 4–6 MB phone JPG.

Portraits and fine fabric need more headroom. Faces punish heavy compression. Start at 80%, inspect eyes and hair, then lower only if the file must fit a strict portal cap. Documents photographed at an angle need readable text more than smooth gradients. Prioritize sharp letterforms over file size.

Avoid re-compressing the same JPG five times. Each save adds artifacts. Work from the camera original or the first export, compress once, attach that output.

PNG screenshots and UI captures

UI screenshots and slides with flat color often start as PNG. A full-screen PNG can exceed a multi-megabyte JPEG of the same scene because PNG stores pixels literally.

For email, convert wide photographic screenshots to JPEG unless you need transparency. Crop to the relevant panel before compressing. A 1920×1080 crop compresses smaller than a dual-monitor grab.

If the screenshot is mostly text (error dialog, settings page), PNG may stay smaller than JPEG. Run both exports and attach whichever weighs less at acceptable clarity. Mail readers rarely need alpha channels.

Prepare the file before you compress

Compression works better when you feed it a sensible source. Fix format and dimensions first, then tune quality.

Rename exports so you do not overwrite masters. A folder called email-out with dated filenames stops accidental resends of the wrong version.

Check orientation. Some tools bake rotation into pixels; others rely on EXIF. After conversion, open the file once locally before attaching.

Set a sensible max width

Long edge 1600–2000 pixels is plenty for email viewing on laptops and phones. A 4000 px wide wedding shot does not gain clarity in Gmail’s preview.

Use Resize image when dimensions, not quality, drive the bloat. Resize, then compress. Shrinking width often saves more bytes than lowering JPEG quality from 85% to 60%.

Keep aspect ratio locked. Distorted product photos erode trust faster than a soft JPEG.

Convert HEIC before you attach

iPhone defaults to HEIC. Windows Mail and many corporate scanners reject it. Convert to JPG before compressing so the recipient opens the file without extra software.

HEIC to JPG produces a widely readable JPEG. For why iPhone HEIC fails on Windows in the first place, see HEIC vs JPG: why iPhone photos won't open on Windows. Run compress on that JPEG if it is still heavy. Order matters less than checking the final attachment size in your file manager.

If the recipient asked for “original quality,” send a resized high-quality JPG rather than a raw HEIC they cannot open. Compatibility is part of courtesy.

Walkthrough: compress with Toolsy

Open Compress image in your browser. Upload the JPG, PNG, or WebP you plan to attach. The page accepts common photo formats without installing desktop software.

Leave quality at the default 75% for a first pass on phone photos. Lower it toward 70% if the download still exceeds your target. Raise toward 80% for portraits or product shots with fine detail.

Choose output format. Keeping JPEG for a JPEG source is fine. Switch PNG inputs to JPEG when the image is photographic. Keep PNG only when you need crisp UI text and transparency is irrelevant to email.

Download the result. Compare file size in your OS file inspector. Open the image at 100% zoom. If banding or blur appears, re-run at higher quality or resize first.

Free daily quota applies. Processing runs on the server briefly; uploads are designed to be discarded after the response. Read What happens to files after processing if retention rules matter for client work.

Check the attachment before you send

File size alone does not guarantee delivery. You still verify appearance and format.

Right-click the compressed file and note megabytes. On macOS, Get Info shows size; on Windows, Properties does the same. Stay under your provider’s cap with room for other attachments and the message body.

Open the image in the default viewer. Scan faces, text, and edges. Zoom to 100%. If it looks soft, re-export at higher quality or smaller dimensions.

Send a test to yourself first when the stake is high (client proof, job application, insurance claim). Mobile mail apps sometimes recompress inline images. A test message shows you what the recipient’s phone will fetch.

If your company uses DLP scanning, very large images may queue longer. Smaller files pass faster. That is another reason to compress even when you are under the published cap.

When compression alone is not enough

Sometimes the cap is 5 MB total for three images, or the recipient’s server rejects anything over 2 MB. Compression hits a floor where quality collapses.

Resize next. Halving width often quarters pixel count. A 1200 px wide JPEG at 75% frequently lands under a megabyte.

Split the send. Attach two photos now and two in a follow-up message. Ask if a shared album or drive link is acceptable before you assume.

Use a cloud link for originals. Compress a preview JPG for inline reading; host full-resolution files in Drive, Dropbox, or WeTransfer with a password if needed. State that clearly in the email body so mobile readers know which link to tap.

For marketplace or social dimensions (different from email weight), see OG image size and aspect ratio when you also prep link-preview art.

Privacy, EXIF, and what compression removes

Email attachments keep the bytes you upload. Unlike some social networks, inbox delivery does not strip GPS for you. A family photo can still carry location metadata until you remove it.

Re-encoding through Compress image redraws pixels and drops classic EXIF, including GPS and camera tags, on the download. That helps size and privacy at once. Some formats may retain other metadata blocks. Treat compression as a practical step, not a forensic guarantee.

When location privacy is the main goal and you do not need heavy shrinking, Strip EXIF targets metadata without pushing quality as hard. When you need both, compress the share copy and read Remove EXIF GPS before sharing kids' photos for a fuller checklist.

Work photos and scans may include embedded author names or color profiles. For client deliverables, spot-check metadata if your contract requires a clean file.

Frequently asked questions

What is the email attachment size limit for Gmail?

Gmail documents an attachment limit around 25 MB per message. If your files exceed that, Gmail steers you toward Google Drive links. Real-world delivery can fail earlier when the recipient’s server enforces a lower cap. Compress each photo to a few megabytes when you attach several images in one thread. Test with a message to yourself if a client inbox bounced your last send.

What is the Outlook attachment size limit?

Outlook and Microsoft 365 commonly allow roughly 20–25 MB per message for consumer and business accounts, but Exchange administrators can set 10 MB or custom values. A photo that sends fine to a Gmail address may bounce on a locked-down corporate host. Compress images and ask the recipient’s IT contact for the limit when mail keeps returning undeliverable.

How do I compress images for email without visible quality loss?

Work from the original, resize to about 1600–2000 px on the long edge, then export JPEG at 75–80% quality. Open the result at full zoom before attaching. If you see banding or muddy faces, raise quality or shrink width instead of compressing the same file repeatedly. One thoughtful pass beats three aggressive saves.

How do I reduce photo file size for email on iPhone?

AirDrop or export the photo to Files, convert HEIC to JPG if the recipient uses Windows, then run the JPG through an online compressor. On-device shortcuts exist, but a browser tool gives a clear quality slider and file size readout. Keep the HEIC master in Photos; attach only the compressed JPG copy.

Does compressing a photo remove EXIF and GPS data?

Re-encoding through a compressor redraws the image and typically drops classic EXIF, including GPS coordinates. Some tags or format-specific blocks may survive depending on the source. For sensitive family photos, follow Remove EXIF GPS before sharing kids' photos and inspect the file you will attach. Compression helps size; a dedicated strip tool helps when metadata is the main concern.

Should I send PNG or JPG in email?

Use JPG for photographs and most screenshots without transparency. Use PNG when you need crisp text, flat graphics, or alpha, and the file stays smaller than a JPEG alternative. Many phone photos start as HEIC or large JPG; PNG is rarely the right email format for camera shots. Convert, compress, and compare file sizes before you attach.

Why does my image still bounce after compression?

The recipient server may enforce a limit below yours, or multiple attachments plus a long HTML signature pushed the total over the cap. Recompress at lower quality, resize width, or remove an extra attachment. Split into two messages or share a cloud link for the full set. Ask the recipient to whitelist your domain only after you have shrunk the files.

Can I compress images to 100 KB or 50 KB for a form?

Some government and job portals cap uploads at 100 KB or 50 KB. That usually requires aggressive resize plus low JPEG quality. Faces and fine print may suffer. Crop to the required field, shrink dimensions to the form’s minimum acceptable resolution, and export until the portal accepts the file. Email workflows rarely need targets that small.

Is online image compression safe for work photos?

Read the processor’s retention policy before you upload client or HR images. Toolsy processes uploads briefly on the server and designs them to be discarded after the response; free daily quota applies. For highly confidential material, use offline desktop software on a managed machine. For everyday marketing or event photos, online compression is usually acceptable when policy allows cloud tools.

How is compressing different from resizing for email?

Compression lowers quality within the same pixel dimensions. Resizing reduces width and height, which often saves more bytes than another quality notch. Use both: resize down to a sensible long edge, then compress to JPEG at 70–80%. Resize image handles dimensions; Compress image handles quality. Check the final megabytes before Send.

If you also prep social link previews, read OG image size and aspect ratio for canvas dimensions separate from email weight. When the attachment is already a PDF, see Compress PDF for email attachments. For a dedicated compressor comparison, see TinyJPG vs browser image compress. For lossy vs lossless in plain English, see Lossy vs lossless compression.