Email Attachment Size Limits and How to Shrink the File

This article is the limits, then the levers: PDF vs photo vs zip, local tools so the attachment never visits a random converter, and when to give up on SMTP. The PDF-only walkthrough is How to compress a PDF for email without uploading it. Use that when you already know the file is a PDF. Use this when you do not.

The limits that actually bounce you

Gmail (consumer and typical Google Workspace). 25 MB per message. Encoding overhead means a 24.8 MB file can still fail. Aim nearer 20 MB if you are packing several files.

Outlook.com / many Microsoft 365 mailboxes. Often 20 MB, sometimes 10 MB, sometimes a custom cap. The recipient’s server can be smaller than yours. You send fine; they bounce.

Apple iCloud Mail. Historically around 20 MB; check current help if you live there. Do not design a legal process around a consumer mailbox.

Corporate gateways. Attachments blocked by type (.exe, sometimes .zip), by size, or by DLP. Compression will not fix a blocked type.

Mobile. The phone sent a 40 MB HEIC stack as a “PDF.” The limit is the same; the file is worse. Convert HEIC first if the “PDF” is really photos: Why iPhone photos won’t open on Windows.

Treat the cap as the whole MIME message. Subject, HTML signature with a 2 MB logo, and three attachments share the budget.

Identify what you are sending

A text-heavy PDF (export from Word, invoices with vector logos) is often already small. Compression will not save you. Extra pages might. PDF Split or PDF Delete Pages.

A scan PDF is JPEGs in a trench coat. Size lives in the photos. PDF Compressor re-encodes those. Quality will drop if you go aggressive; check signatures and fine print at 100%.

Photographs. Attach JPG, not HEIC, not a 12 MP PNG screenshot of a photo. Online Image Compressor, HEIC to JPG, PNG to JPG when you do not need transparency.

A folder of mixed files. Email is the wrong bus. Zip only if the other side can open zip and the gateway allows it. Prefer one PDF of the pages they asked for.

Video. Will not fit. Use the video host or Drive your org allows. Do not “convert video to PDF” as a joke that becomes a 200-page smear.

Levers in order

1. Remove pages you should not send. Privacy and size. Are online PDF converters safe? if the content is sensitive - use local tools.
2. Compress the PDF with PDF Compressor. Download, check size and readability, keep the original.
3. Compress images before wrapping them into a PDF, or compress photos as attachments. How to compress images for the web applies; email is just another upload slot.
4. Split into two messages: form vs appendix. How to split a PDF by page or range.
5. Stop using email. Link from the file share that already has access control. Gmail’s Drive suggestion is a product nudge, not a confidentiality review.

Zip is last, not first, for a single PDF. You will waste a step and still be over 25 MB.

Encoding overhead and “it was 24 MB in Explorer”

Base64 attachment encoding inflates size. Clients differ. If Explorer says 23 MB and Gmail still refuses, you are in the overhead band. Compress a little more or split. Do not chase exact bytes.

Multiple small images can beat one huge PDF for a photo set - or lose, if the client resizes badly. Test to the actual recipient when the send matters.

Quality: readable vs attached

A 25 MB scan that becomes a 3 MB blur fails the real requirement: someone must sign or read it. Prefer two emails of clean pages over one unreadable smear. For contracts, ask whether they accept a link. For receipts, a 400 KB JPG of each page is often enough.

Page numbers after a split help: PDF Page Numbers. Merge only if you are combining files that were split for size and the result is still under the cap: PDF Merge.

Local vs cloud, again, because email is how leaks travel

The attachment is already about to travel. That does not mean a third website should see it first. Passport + “free compress PDF” is a worse idea than Gmail’s 25 MB wall. Use PDF Compressor in the browser. The PDF tools hub is the rest of the chore list.

If the file is a public flyer, a cloud compressor is a taste choice. If it is HR, health, or ID, it is not.

Provider notes that change the tactic

Gmail to Gmail. 25 MB is the story. Drive links appear when you exceed it. A Drive link is not “smaller”; it is a different permission surface. For a confidential PDF, a Drive link to “anyone with the link” can be worse than a 20 MB attachment to one person.

Outlook to a customer. Assume 10 MB if you have been burned once. Compress to ~8 MB or split. Their bounce may arrive after you left the office.

Apple Mail. Large files may become Mail Drop links. Again, a link with a TTL is not the same as an attachment. Know which one you sent.

Two attachments that are both “small.” 12 MB + 12 MB fails Gmail even if each file would pass alone. Compress both or send two messages.

Signatures and logos. A 1.5 MB company banner in the HTML signature is a tax on every send. That is not a PDF problem. Fix the template.

Etiquette when you split

Say “pages 1–6 in this email, appendix in the next” in the body. Stamp numbers with PDF Page Numbers so nobody prints two page 1s. Do not split in the middle of a table if you can delete blank scans instead.

When the limit is a policy, not physics

Some orgs block all attachments and force a portal. Compression will not help. Some orgs block zip. Some strip images. Read the bounce. “Message too large” is size. “Content rejected” is something else.

A worked example: 28 MB PDF, 25 MB Gmail, 10 MB Outlook

You can send from Gmail. The recipient is on a tenant that bounces at 10 MB. Your send succeeds; their bounce arrives later. Compress as if the cap is theirs.

1. Note the original size and page count.
2. PDF Compressor. If you land at 18 MB, Gmail is happy and Outlook is not.
3. Compress again or split into two ~8 MB parts with PDF Split.
4. Tell them which pages are in which message.
5. Keep the original 28 MB file. If they complain about blur, you still have it.

If the 28 MB file is mostly a photo of a whiteboard, export the photo as JPG and attach that instead of a one-page PDF wrapper. Container overhead is real; so is a camera PDF that is just one JPEG.

Already-optimized PDFs from a design export may not shrink. You will waste time on the compressor. Split or use a link. That is not a tool failure.

Password-protected PDFs may not compress in a browser tool until they are opened with the password in software that supports it. Do not paste the password into an “unlock PDF” site to shrink the file. Unlock locally in Acrobat or the creator app, then compress locally.

Corporate disclaimers at the bottom of every email can add tens of kilobytes of HTML. They rarely cause a 25 MB bounce by themselves; they do push a 24 MB payload over the line. If you are in the overhead band, compress the attachment, do not rewrite the legal footer.

Reply-all threads with the same 18 MB PDF quoted six times also fail. Send the file once. Compress it first with PDF Compressor.

Calendar invites with huge ICS plus PDF attachments share the same message cap on some servers. Send the PDF in a follow-up mail if the invite already bounced.

Some phones downsample outgoing attachments; the file on the recipient’s side is smaller and blurrier than what you saw in Files. Check a sent-mail copy.

If both of you use Google Workspace, a Drive link with a named person (not “anyone”) may be the right 40 MB send. That is still not a random PDF website.

Gmail’s 25 MB, Outlook’s quieter 10–20 MB, and your recipient’s server are three numbers. Shrink PDFs and photos locally, split when quality would die, and use a real file share when email is pretending to be one. The compressor and split tools are enough for the honest 28 MB scan. They are not a way to sneak a movie past SMTP.