PDF size limit for email attachments — Gmail, Outlook, Yahoo compared

The hidden 33% MIME-encoding tax

Every attachment sent through SMTP is encoded using Base64, defined in RFC 2045 and RFC 4648.¹ Base64 represents three binary bytes as four ASCII characters, which means the encoded form is exactly 4/3 (≈1.333×) the size of the raw binary. Add a few percent for header lines, MIME boundaries, and line-wrapping, and the practical inflation factor is about 1.34 — roughly 34 percent. All major email providers (Gmail, Outlook, Yahoo, iCloud, Proton) enforce their attachment-size cap against the encoded message size, not the raw file size.

The practical rule, in plain terms: a "25 MB" attachment cap is actually a budget of around 18.7 MB of real file before the encoded form crosses the line. A 20 MB cap is roughly 14.9 MB of real file. A 40 MB cap is roughly 29.8 MB. The "real file budget" column in the table below applies that conversion so you can plan from your actual PDF size rather than the headline number.

Per-provider attachment limits, 2026

Sourced from each provider's public help documentation as of May 2026.² Corporate-Exchange and Microsoft 365 limits are tenant-tunable; the figures here are the most common ranges seen in practice. Inbound limits apply on the recipient side and are usually quieter than outbound limits, but they are what causes the dreaded "your message has been delivered… to the bounce queue" effect.

Gmail in detail — why 25 MB has not moved since 2012

Gmail launched in 2004 with a 5 MB attachment cap. The cap moved to 10 MB in 2005, 20 MB in 2007, and 25 MB in 2012 — the same year Google added the Drive-link fallback that automatically catches anything over 25 MB. The receive-side cap was bumped to 50 MB in the same change so users could accept up to 50 MB even though they cannot originate it. The 25 MB outbound number has stayed flat for fourteen years, partly because the Drive-link fallback removes most of the user-visible pain.

What that means for a sender: if your PDF is over 18.7 MB true file size and you are on Gmail, expect the message to be auto-converted to a Drive share link. That works fine for personal recipients but fails for two important categories: corporate firewalls that block external share links, and counterparties whose IT policy considers a Drive share with implicit access too permissive. Compress the PDF before sending if you need it to ride inline as an attachment.

Outlook in detail — the 20 / 150 MB confusion

Outlook.com (the consumer service) caps attachments at 20 MB per message — strict and non-tunable. Microsoft 365 (work and education) has a default limit of 150 MB per message, but administrators can lower the limit per mailbox, per connector, or per transport rule. In practice most tenants run with 25 to 50 MB caps for outbound mail because of mail-flow performance considerations. If you are on a corporate Microsoft 365 tenant, the relevant question is not "what is the documented limit?" but "what has IT set for our tenant?" — and the answer is usually 25 to 50 MB.

Outlook's compose UI surfaces a OneDrive share-link suggestion when you exceed the cap, similar to Gmail's Drive flow. For work tenants the link is to OneDrive for Business or SharePoint, both of which honour tenant-level access controls and are usually whitelisted by corporate recipients — the link path tends to work better in B2B contexts than Gmail's Drive equivalent.

Apple Mail and Mail Drop — the highest free ceiling

iCloud Mail caps inline attachments at 20 MB, which is the lowest headline number on the table. Apple makes up for it with Mail Drop: any attachment over 20 MB is uploaded to Apple's CDN, replaced with a download link in the email body, and stored for the recipient to fetch for 30 days. Mail Drop supports attachments up to 5 GB per message and is free for everyone with an Apple ID.³ For sending large PDFs to anyone — not just Apple users — Mail Drop is the simplest built-in option in 2026.

One caveat: Mail Drop links are public to anyone who has the link, so do not use Mail Drop for genuinely sensitive material without password-protecting the PDF first using Protect PDF and sending the password through a separate channel.

The "size budget you can actually use" rule

Three quick rules of thumb, taking MIME overhead and recipient caps into account:

• For consumer-to-consumer sends (Gmail to Gmail, Outlook to Outlook), aim for a real file under 15 MB. That fits inside even the lowest 20 MB outbound cap on the table and leaves room for the MIME tax.
• For sends to an unknown corporate recipient, aim for a real file under 7 MB. Most enterprise mail servers cap inbound at 10 MB, and a 7 MB real file encodes to ~9.4 MB, well inside that cap.
• For anything over 20 MB real file, plan to send via a cloud-share link rather than an inline attachment. Apple Mail Drop, OneDrive for Business, and Google Drive are the three most common; password-protect the file first if it is sensitive.

What to do when your PDF is over budget

Three actions, in the order to try them:

1. Compress. ScoutMyTool's Compress PDF tool typically halves the file size with no visible quality loss for scanned documents and image-heavy PDFs. Runs entirely in your browser — your file is never uploaded.
2. Slim down. If compression alone is not enough, use Remove Pages to drop blank or duplicate pages, or Extract Pages to send only the section the recipient needs.
3. Split or link. Use Split PDF to break the document into chunks small enough to send as several emails, or fall back to a cloud-share link. The sister article How to send large PDFs over email walks through the full size-reduction playbook in detail.

Related ScoutMyTool tools and articles

• Compress PDF — the fastest path from "over the limit" to "under it".
• Aggressive Compress PDF — for scans where standard compression is not enough.
• Split PDF — break a long file into chunks that each fit the cap.
• Remove Pages — drop pages you do not need to send.
• Extract Pages — send only the section the recipient asked for.
• Protect PDF — password-protect before sending via cloud share.
• How to send large PDFs over email — sister piece with the full reduction playbook.

Frequently asked questions

Why is my 24 MB PDF rejected by Gmail when the limit is 25 MB?

Because the 25 MB limit applies to the encoded message size, not the raw file size. Email attachments are encoded using Base64, which inflates the binary by roughly 33–34 percent for transit through SMTP. A 24 MB PDF becomes around 32 MB on the wire — over the 25 MB cap. The practical rule of thumb: keep raw file sizes under 75 percent of the headline cap. For Gmail's 25 MB outbound, that means real files at or below 18.7 MB. For Outlook.com's 20 MB, around 15 MB. The same rule applies to every SMTP-based mail provider because the limit is enforced after MIME encoding.

Whose limit matters — mine or the recipient's?

Both, and the lower of the two wins. If your provider lets you send 25 MB and the recipient's tenant caps inbound at 10 MB, the message bounces from their side with a 552 "message size exceeds maximum permitted" non-delivery report. You will receive a bounce notification but the recipient sees nothing. Always assume the recipient's cap is whichever number is smaller, and when sending to a corporate domain you do not control, default to under 10 MB true file size to be safe.

Has Gmail's 25 MB attachment limit ever changed?

Yes. Gmail launched in 2004 with a 5 MB attachment cap. The limit moved to 10 MB in 2005, 20 MB in 2007, and 25 MB in 2012 when Google introduced the Drive-link fallback for anything over 25 MB. It has not moved since — for nearly fourteen years now. The receive-side cap of 50 MB was added with the Drive-link feature so users could accept up to 50 MB even though they cannot send that much directly. The flat receive figure occasionally moves quietly as Google adjusts caps; check the current help page if a borderline file matters.

Does the limit apply per attachment or per message?

Per message, in essentially every major provider. Three 10 MB attachments fail Gmail just as a single 30 MB attachment would, because the total encoded message size exceeds 25 MB. Splitting one large PDF into three smaller files and attaching all three to one email does not help — you have to send three separate emails, each with one attachment under the cap.

What happens if I send through SMTP with a custom domain (Mailgun, Postmark, SES)?

Each transactional-email provider has its own limit. Amazon SES allows messages up to 40 MB raw (about 30 MB true file). Mailgun caps at 25 MB. Postmark caps at 35 MB. These are typically for system-generated mail rather than user attachments, but the same MIME-encoding overhead applies. Use the relevant provider documentation — and remember the recipient's inbox cap still governs delivery regardless of what your sending service allows.

Will compressing the PDF actually get me under the limit?

Usually yes, dramatically. Standard image-downsampling compression cuts most large PDFs by 30 to 70 percent — a 35 MB scanned document typically drops to 10–18 MB, which fits under every major provider's cap. Aggressive grayscale compression can push the reduction to 80 percent for text-only scans. Use a client-side tool (the PDF never leaves your machine) for anything sensitive.

Is the size limit different on iPhone vs desktop?

No — the limit is enforced at the mail server, not the client. Apple's Mail app on iPhone has the same 20 MB inline cap as on Mac for iCloud Mail, and the same Mail Drop fallback for anything larger. Gmail and Outlook mobile apps display the same 25 MB / 20 MB caps as their web counterparts. Compression and other size-reduction tricks need to happen on a device or via a browser-based tool, but the actual limit number is consistent across platforms.