Email Attachment Size Limits: Gmail, Outlook, Yahoo & iCloud Compared

Every major email provider caps how much you can attach to a single message, and none of them use the same number. Worse, the number on the help page isn't the number that actually fits, because of how email encodes files. Here's what each provider really allows, why your file needs more headroom than you think, and how to get a batch of photos or documents under the limit without losing quality.

Why email even has an attachment limit

Mail servers cap attachment size for a few practical reasons: a giant attachment ties up storage on both the sender's and recipient's mail servers, it makes syncing a mobile inbox painfully slow over cellular data, and unlimited attachments would turn email into a free file-hosting service — which is exactly what spammers and phishing campaigns try to abuse. So every provider draws a line, and that line has stayed roughly in the same range (20–25 MB) for over a decade, even though phone cameras and scanned PDFs have gotten much bigger in that time.

The actual limits, provider by provider

These are the current published limits from each provider's own support pages, not third-party estimates:

Two details in that table matter more than the headline numbers. First, every one of these limits is a total for the message — the sum of every attachment combined, not a per-file allowance. Three 10 MB photos in one email hits a 25 MB cap just as hard as one 30 MB file. Second, on Gmail and Google Workspace, the limit you actually hit is whichever is smaller: your own outgoing cap, or the recipient's incoming cap. A 40 MB file from a Workspace Enterprise Plus account will bounce at a personal Gmail address's 50 MB incoming limit only if it somehow got that far — but it never leaves your outbox in the first place if it exceeds your own 25 MB personal-account send limit.

The base64 tax nobody accounts for

Email was designed to carry plain text, not binary files, so before a photo or PDF is attached, it gets converted to base64 — a text-safe encoding that represents each 3 bytes of the original file as 4 characters. That inflates the file by roughly 33–37% in transit. A file that's exactly 20 MB on your hard drive becomes about 27 MB once it's encoded for sending, which is already over iCloud's 20 MB cap and uncomfortably close to Yahoo's and Outlook.com's 25 MB one.

Practically, that means the safe target isn't the provider's published number — it's about three-quarters of it. Aim for under 18 MB of actual file size if the stated limit is 25 MB, and under 15 MB if it's 20 MB. That buffer also covers the small overhead email adds for headers and the message body itself.

Getting a file under the limit without losing what matters

The fix depends on what you're sending:

• A batch of photos (listing photos, a rental application, insurance documentation): compress each one first. Phone photos routinely run 3–8 MB apiece at full resolution, which is far more detail than a screen or a printed page needs. The Image Compressor can knock a photo down to a few hundred KB with no visible quality loss for anything short of large-format printing, which turns a batch that would blow past 25 MB into one that comfortably fits.
• Several pages that belong together (a signed contract, scanned receipts, ID photos for a form): don't send them as five or ten separate image attachments. Combine them into a single PDF with Images to PDF first. One well-compressed PDF is usually smaller than the same images sent loose, it's one attachment instead of many (so a recipient's phone doesn't have to download ten separate files to see all the pages), and it opens in the correct order every time — separate image attachments have no guaranteed order once they're in someone else's inbox.
• One large file that resists compression (a video, a large design file): use the provider's own cloud link instead of fighting the limit — Gmail and Outlook do this automatically once you're over the cap, and it's usually the better experience for the recipient anyway.

A realistic case where this actually bites

Say you're applying for an apartment and the leasing office asks for pay stubs, a photo ID, and a reference letter — four files, photographed on a phone rather than scanned, because that's what most people actually do. Each photo comes out of a modern phone camera at 4–8 MB. Attach all four as-is and you're at 20–32 MB before you've added anything else, which is already past iCloud's limit and flirting with Gmail's and Outlook's. The email either bounces with a vague size error, or — worse — appears to send successfully from your outbox while the leasing office's mail server silently rejects it, and you don't find out until they follow up asking where the documents are.

Running the four photos through a compressor first, then combining them into a single PDF, typically gets the whole packet under 3 MB — small enough to clear every provider in the table above with room to spare, and it arrives as one clean, correctly-ordered document instead of four photos the recipient has to open individually.