Guide
Compressing photos to fit email attachment size limits
Modern phone photos routinely run 3-8MB each. Attach five and you're already past what most inboxes will accept.
By Buğra SözeriPublished
A single photo from a modern phone camera commonly runs 3-8MB, sometimes more with high dynamic range modes enabled. Attach four or five of those to an email and you’re already brushing against — or past — what Gmail (25MB combined) and Outlook (20MB by default) will accept in one message. The fix isn’t zipping the files, which barely helps since JPEGs are already compressed; it’s re-encoding the images at a lower quality or smaller pixel size before you attach them.
Why the limit is combined, not per-file
Both Gmail and Outlook measure the totalsize of an outgoing message, attachments included, against a single cap. That means three photos at 8MB each (24MB total) will fail under Gmail’s 25MB ceiling once you add the message body’s own overhead, even though no individual file looks oversized on its own. The base64 encoding email clients use to embed binary attachments in a text-based message also adds roughly 33% to the raw file size — see why Base64 makes files bigger for the mechanics — so a 20MB batch of photos can actually transmit closer to 26-27MB, tipping it over the limit even when the files themselves fit.
What happens over the limit
| Provider | Default limit | Over-limit behavior |
|---|---|---|
| Gmail | 25MB combined | Auto-converts to a Google Drive link |
| Outlook / Microsoft 365 | 20MB (admin-adjustable) | Auto-converts to a OneDrive link, or blocks send |
| Yahoo Mail | 25MB combined | Send is blocked with an error |
A cloud-link fallback isn’t always the smoother experience it sounds like — recipients on a corporate network with restrictive link-scanning policies, or on a work device without a personal Google or Microsoft account signed in, may not be able to open the link at all. Keeping files under the raw size limit avoids that failure mode entirely.
What settings actually get you under the cap
For photos that only need to be viewedon a screen (not printed large), there’s a lot of headroom to cut. Scaling the long edge down to around 2000px and compressing at 75-85% JPEG or WebP quality typically shrinks an 8MB phone photo to somewhere between 400KB and 1MB with no visible quality loss at normal viewing sizes — enough to fit a dozen photos in one email well under any provider’s cap. Use the image compressor to batch through your photos, checking the live before/after size readout as you go, and keep the original files separately if you might need full resolution later for printing.
Frequently asked questions
- What's the actual email attachment size limit?
- Gmail caps combined attachments at 25MB per message; Outlook.com and most Microsoft 365 tenants default to 20MB. These are totals for the whole message, not per file — five 6MB photos will already push past both limits.
- What happens if my attachments exceed the limit?
- Most email clients either block sending outright with an error, or silently convert the attachment to a cloud-storage link (Gmail does this automatically via Google Drive, Outlook via OneDrive) that the recipient has to click through and may need permission to open.
- Does compressing a photo for email hurt quality much?
- Not at web-appropriate settings. A modern 12MP+ phone photo compressed to WebP or JPEG at 80% quality and scaled to roughly 2000px on the long edge typically lands well under 1MB with no visible quality loss on a screen — the original resolution is usually far higher than needed for viewing, only useful for large prints.
- Should I zip photos before emailing instead of compressing them?
- Zipping barely helps — JPEG and WebP files are already compressed, so a zip archive of photos is typically only 1-3% smaller than the originals. Re-encoding the images themselves (lower quality setting, smaller pixel dimensions) is what actually reduces the byte count.
Sources & references
Authoritative references cited by this piece. Verified by Buğra Sözeri on the dates shown and re-checked at every deploy.
- Google — Gmail help: file size limits — Gmail's 25MB combined attachment limit and what happens above it(as of )
- Microsoft — Attachment size limits in Outlook and Outlook on the web — Outlook's default 20MB attachment cap (varies by admin policy)(as of )
Related
More guides on this topic
- Compressing images for page speed: what LCP actually needsGoogle's Core Web Vitals flag your largest image as the LCP element. What file size and format actually move that score, with real target numbers.
- Base64 image data URIs: when embedding beats a fileA data:image/png;base64 URI inlines an image directly in HTML or CSS, skipping a request — at the cost of a bigger file and no browser caching. When it wins.
- How to make a favicon: sizes, formats, and what browsers actually loadWhich favicon sizes matter in 2026 — 16/32 ICO, 180 apple-touch-icon, 192/512 PWA — plus SVG favicon support, dark-mode variants, and the minimal head markup that covers everything.
- What your photos reveal: EXIF data, GPS location, and how to remove itPhotos carry GPS coordinates, timestamps, and device identifiers in their metadata. What EXIF actually contains, which platforms strip it, and how to inspect and remove it locally.
Published September 25, 2026