Compressing JPEGs for Email Without Losing Quality
Email has different rules from the web: hard attachment limits, encoding overhead that inflates every file by a third, and clients that cannot open WebP. Here is how to get photographs small enough to send while still looking right.
The Talentra Editorial Team
Research and editing
Published
6 min read
What is the maximum attachment size for email?
Gmail allows 25 MB per message, Outlook.com 20 MB, and corporate Exchange servers are commonly configured at 10 MB or lower. The receiving server's limit applies as well as the sender's, so the practical ceiling is whichever is smaller — and you usually do not know the recipient's. Under 10 MB total is the safe target.
Optimising images for email is a different problem from optimising them for the web, and the differences matter enough that web advice can actively mislead you.
Three constraints shape it. There is a hard size limit rather than a soft performance target. Every attachment is inflated by about a third in transit. And the recipient's software is an unknown, so the modern formats you would use on a website are off the table.
The size limits you are working against
| Service | Limit per message |
|---|---|
| Gmail | 25 MB |
| Outlook.com | 20 MB |
| Yahoo Mail | 25 MB |
| Corporate Exchange | Commonly 10 MB, often lower |
The trap is that both ends apply a limit. You can send a 24 MB message from Gmail and have it bounce at a corporate server configured at 10 MB. You generally have no way of knowing the recipient's limit in advance.
The 33% you did not account for
Email attachments are not sent as raw binary. They are Base64-encoded, which represents every three bytes of data as four ASCII characters — an overhead of about 33%, plus MIME headers.
So a folder of photographs totalling 20 MB on disk becomes roughly 27 MB in transit and will be rejected by a 25 MB limit. This is the most common reason a message that "should fit" does not.
Practical rule: aim for under 10 MB of files on disk. That leaves headroom for encoding overhead and for a recipient with a stricter server. If you cannot get there, use a link instead of attachments.
Why not WebP
On the web, WebP is the obvious answer — smaller than JPEG at equivalent quality, supported by every current browser. Email is different.
Email clients render with wildly varying engines. Desktop Outlook has historically used the Word rendering engine for HTML. Many recipients open attachments in whatever image viewer their operating system defaults to, some of which are old. Print shops and photo labs frequently reject anything but JPEG or TIFF.
A recipient who cannot open your attachment is a worse outcome than a file that is 30% larger. Send JPEG for photographs, PNG for graphics with transparency, and leave the clever formats for the web.
The compression workflow
Step 1: Resize first — this does most of the work
Same principle as for the web, and even more decisive here because there is a hard ceiling.
Ask what the recipient will do with the image:
| Purpose | Longest edge |
|---|---|
| Viewing on screen | 1600–2000 px |
| Inserting into a document or slide deck | 1200–1600 px |
| Reference or approval | 1000–1200 px |
| Professional printing | Do not compress — send the original by link |
A photograph straight from a phone is 3000–4500 pixels wide. Reducing the longest edge to 1600 removes roughly 80–85% of the pixels before any compression is applied.
The exception that matters: if the recipient is going to print the image, or edit it, or use it in a design, do not compress it at all. Send the original through a file-transfer link. Compressing a photograph destined for print is the one genuinely unrecoverable mistake in this whole process.
Step 2: Set quality by eye
Quality 75–82 is where most photographs stop being distinguishable from the original at normal viewing size.
Where compression shows first: skies, skin tones, and any smooth gradient. Where it hides: foliage, fabric, crowds, anything with busy natural texture.
If the image contains text — a screenshot, a scanned document, a slide — JPEG is the wrong format entirely. Text compresses badly under JPEG and picks up visible fringing at exactly the sizes that make it hard to read. Use PNG, or better, send an actual PDF.
Step 3: Let the metadata go
Re-encoding an image through most compression tools discards its EXIF data: GPS coordinates, camera model, serial number, timestamps, sometimes the photographer's name.
For email this is usually a benefit rather than a cost. A photograph taken at home carries the coordinates of your home, and sending it to a client or a marketplace buyer shares that without anyone intending to. Stripping metadata is a genuine privacy improvement.
Two exceptions: keep the originals if you need the capture data for your own records, and be aware that colour-profile information can go with the metadata, which occasionally shifts how colours appear. For ordinary photographs this is not noticeable.
Step 4: Check the total, not each file
Ten photographs at 900 KB each is 9 MB on disk and about 12 MB in transit. Select all the files, look at the total, and apply the under-10 MB rule to that number rather than to any individual image.
Different content, different approach
Portraits and people. Skin tones show compression artefacts before anything else. Stay at 80 or above, and check the face at 100% before sending.
Screenshots and text. Not a JPEG job. PNG, or export a PDF.
Documents and scans. PDF, every time. Multi-page, searchable if OCR is available, and far smaller than a set of photographs of pages.
Product photography on white. Large flat areas make JPEG artefacts unusually visible as faint mottling in the background. Stay at 85 or above, or consider PNG if the product has a clean edge.
Landscapes and busy scenes. Compress hardest here. Foliage and texture hide artefacts extremely well; 70 is often fine.
Anything going to print. Do not compress. Send a link.
When to stop attaching and start linking
Attachments are the wrong tool once you cross any of these lines:
- More than about ten images
- Any file needed at full resolution
- A recipient whose mail server limit you do not know
- Anything going to a printer, a photo lab or a designer
- A set you may need to update after sending
Google Drive, Dropbox, OneDrive and WeTransfer all handle this better than email was designed to. They preserve full resolution, they do not consume the recipient's mailbox quota, and you can replace a file without sending a second message.
For anything client-facing, a link is also simply more professional than a 24 MB message that may bounce.
A pre-send checklist
- Resized to the size the recipient actually needs
- Saved as JPEG (photographs) or PNG (text, graphics, transparency)
- Quality 75–82, checked at full size for faces and skies
- Total on disk under 10 MB, allowing for 33% encoding overhead
- Originals kept somewhere safe
- Filenames that mean something —
kitchen-north-elevation.jpg, notIMG_4471.jpg - Anything for print or editing sent as a link instead
That filename point is small and repays itself constantly. A recipient who saves twelve files called IMG_44xx.jpg into a folder has no idea what any of them are a week later.
Our free image compressor resizes and re-encodes in your browser and shows the total before and after, so you can check against the 10 MB rule before you attach anything. Nothing is uploaded, which matters more than usual when the photographs are of a client's property or a personal document.
Related: how to reduce image size for a website and JPG vs PNG vs WebP vs AVIF.
Sources
Primary references used in this guide. Rules change — check the source directly if you are relying on it for a decision.
About this guide
Talentra's editorial team researches, drafts and fact-checks every guide on this site, and revisits each one when the underlying rules change. This page was last reviewed on August 21, 2026. It is general information, not legal, tax or financial advice — see our disclaimer and editorial policy. Spotted something out of date? Tell us.