Reference guide · cited sources
Emailing Photos Without Hitting Attachment Limits
Email attachment limits are lower than people expect and stricter than they appear, because an attached file is encoded on the way out and grows by roughly a third in the process. A handful of phone photographs can exceed a mailbox limit easily, and the failure often happens at the recipient's end where you cannot see it.
By Prashantkumar Kishanrao Sundge · Published · Reviewed
What this guide establishes
- Attachments are encoded for transport and grow by about 33%. A 20 MB file occupies roughly 27 MB of your limit.
- The recipient's limit matters as much as yours, and you cannot see it. The smaller of the two wins.
- Most photos sent by email never need full camera resolution. 1600–2000 pixels on the long edge is plenty for viewing.
- Send a link instead of attachments once you are past a few photographs. It is more reliable and easier for the recipient.
- Strip metadata before sending photos to people outside your household or organisation.
Why attachments are bigger than the files
Email was designed to carry text, and the transport path cannot be relied upon to handle arbitrary binary data safely. Attachments are therefore encoded into a restricted character set before being sent — the standard approach represents every three bytes of the original as four characters of output.
That ratio is where the overhead comes from: roughly a third larger than the file on disk. A 15 MB photograph becomes about 20 MB in transit. Add message headers and the boundaries between parts of a multipart message and the figure creeps a little higher.
So a stated 25 MB limit is not 25 MB of files. It is closer to 18 MB of actual content, and a set of attachments that looks comfortably under the limit in a folder can be rejected on send. This surprises people repeatedly because nothing in the interface explains it.
Different systems also measure the limit at different points — some against the encoded message, some against the sum of attachments — so the effective ceiling varies. Treating the stated number as generous rather than exact avoids the problem.
The recipient's limit is the one that matters
Your provider accepting the message only gets it as far as theirs. If the recipient's mail system has a lower limit, the message is rejected on delivery — sometimes with a bounce, sometimes silently into a quarantine neither of you will look at.
Corporate and institutional mail systems are frequently far more restrictive than consumer providers, and often for good reason. Limits well below 10 MB are common, as are rules that strip or quarantine certain attachment types entirely.
You cannot discover the recipient's limit in advance, which means the practical rule is to stay well under any plausible threshold rather than up against your own. A message of a few megabytes gets through essentially everywhere; a message of twenty megabytes is a gamble.
If a message must arrive — an application, a claim, a legal document — this is a reason to send a link or use whatever channel the recipient specified, rather than testing their infrastructure with a large attachment.
Sizing photos for email
A current phone camera produces images of twelve megapixels or more. The recipient is going to look at that photograph on a screen, usually in a mail client window. The full resolution is not contributing anything to that experience.
For viewing on any ordinary screen, 1600 to 2000 pixels on the long edge is generous. That covers a full-screen view on most displays with room to spare, and it typically reduces a multi-megabyte original to a few hundred kilobytes. Six photographs at that size fit comfortably in any mailbox.
Quality settings in the range of roughly 80 to 85 for photographic content are where most people stop noticing degradation while the file keeps shrinking. There is rarely a reason to go below about 70 for email unless a hard limit forces it.
The exception is when the recipient needs the full file — they are going to print it, edit it, or archive it. In that case do not compress it at all; send the original by a method that can carry it, because a downsized copy is not a substitute and they will have to ask you again.
Many mail clients offer to resize images when attaching. This is convenient and worth using, but check what size it actually produces, since some are aggressive enough to make photographs visibly poor.
When to send a link instead
Past a handful of photographs, attachments stop being the right mechanism. A shared folder or file-transfer link avoids every limit, lets the recipient download at their convenience, and does not sit in both mailboxes consuming storage indefinitely.
It also handles the case attachments handle worst: the recipient wants the originals. A link can carry full-resolution files that no mail system would accept.
The trade-offs are real and worth stating. A link usually expires, so the recipient must act within some window. It requires them to click through to a service, which some corporate environments block. And the files sit on a third-party service, which matters for anything confidential — check what the service does with content and who can reach the link before using it for sensitive material.
For a small number of ordinary photographs, attachments remain simpler and more reliable. The switch to links is about volume and size, not about attachments being wrong.
Formats and compatibility
JPG is the safe format for emailed photographs. It is accepted and displayed by every mail client in existence, and photographic content is exactly what it handles well.
HEIC is not safe. An iPhone photo attached in its original format may display for another Apple user and fail entirely for a recipient on Windows, Android, or an older mail client. Convert to JPG before sending unless you know the recipient can handle it.
WebP is likewise unreliable in email. Browser support is broad but mail clients lag considerably, and a recipient seeing a broken attachment will simply ask you to resend.
PNG is fine and is the right choice for screenshots, diagrams, and anything with sharp text — where JPEG would add visible halos around the letters. For photographs it produces much larger files for no benefit.
Send images as attachments rather than embedding them in the message body when the recipient may need to save them. Embedded images are sometimes awkward to extract, and some clients block them by default until the reader chooses to load remote content.
Privacy before you send
Photographs from a phone commonly carry the coordinates where they were taken, along with the capture time and device details. For a photo going to a family member this is harmless. For a photo going to a stranger, a marketplace buyer, an insurer, or a prospective employer, it is a disclosure most people did not intend to make.
Email strips nothing. Unlike some social platforms, which remove metadata on upload, an attachment arrives exactly as it left — so the recipient receives everything the file contains.
Preparing a copy with metadata removed takes seconds and is worth making habitual for anything leaving your immediate circle. Keep the original; send the cleaned derivative.
Check the visible content too. A photograph of an item for sale may include a window showing the street, a document on a desk, or a reflection. Metadata removal does nothing about any of that, and it is often what actually identifies a location.
How this guide was written
This is a reference guide. It explains published specifications, platform rules, and format behavior, and every factual claim is attributed to the sources listed below. It does not report an in-house PixelConvert measurement, and no result here should be read as one.
Read how PixelConvert separates measured and reference guides →Limitations
- This guide explains attachment encoding and general practice with citations; it reports no in-house PixelConvert measurement.
- Specific attachment size limits vary by provider and organisation, change over time, and are not stated here as fixed values.
- Quality and dimension recommendations are general guidance for photographic content viewed on screen, not measured thresholds.
Frequently asked questions
- Why does my email say the attachment is too large when the file is under the limit?
- Attachments are encoded for transport and grow by roughly a third. A 20 MB file occupies about 27 MB of a message, so a set of files that looks under the limit in a folder can exceed it on send.
- What size should I make photos for email?
- Around 1600 to 2000 pixels on the long edge at quality 80 to 85 is generous for on-screen viewing and usually reduces a multi-megabyte original to a few hundred kilobytes. Send originals only when the recipient needs to print or edit them.
- My email sent fine but never arrived. Why?
- Possibly the recipient's limit rather than yours. Their mail system may have rejected or quarantined the message, sometimes silently. Their limit is often lower than yours and you cannot see it, so stay well under any plausible threshold.
- Should I attach photos or send a link?
- Attachments for a handful of ordinary photos — simpler and more reliable. A link once you are past that, or when the recipient needs full-resolution originals. Check the service's privacy terms before using a link for anything confidential.
- Can I email HEIC photos from my iPhone?
- Not safely. Recipients on Windows, Android, or older mail clients may be unable to open them. Convert to JPG first unless you know the recipient can handle HEIC.
- Does email remove location data from my photos?
- No. Email strips nothing; the attachment arrives exactly as it left, including GPS coordinates and capture details. Prepare a copy without metadata before sending photos outside your immediate circle.