Skip to main content
VVertex Solutions
All toolsPDF ToolsImage ToolsText ToolsCalculatorsDeveloperBlog
VVertex Solutions

Browse tools for merging and compressing PDFs, resizing and converting images, formatting text and JSON, running calculators, and working with code.

Popular Tools

  • Mortgage Calculator
  • GPA Calculator
  • Tip Calculator
  • BMI Calculator
  • Percentage Calculator
  • EMI Calculator
  • Merge PDF
  • JSON Formatter

Categories

  • All tools
  • PDF Tools
  • Image Tools
  • Text Tools
  • Calculators
  • Developer Tools

Company

  • About
  • About the Author
  • Editorial Standards
  • How We Verify Tools
  • How Data Is Processed
  • Calculator Comparisons
  • Disclaimer
  • Privacy Policy
  • Cookie Policy
  • FAQ
  • Accessibility
  • Changelog
  • Terms of Service
  • Contact
  • Blog
  • RSS Feed

© 2026 Vertex Solutions. All rights reserved.

Free tools. No signup. Privacy first.

  1. Home
  2. Blog
  3. Email Attachment Limits and PDF Size: A Practical Guide
Office Guidesinformational5 min readPublished 2026-03-27 · Last updated 2026-10-23

Email Attachment Limits and PDF Size: A Practical Guide

A PDF at 11 MB can bounce even when a help page quotes a higher cap. Provider limits count the encoded message, and scan-heavy files hit that cap first.

By Rehan Baqir

Quick answer

Most email gateways cap messages at 10 to 25 MB, including about 33% Base64 MIME overhead, so the raw PDF often needs to stay under 7 to 20 MB depending on the recipient. Compress a scan-heavy PDF once at medium quality, split logical sections if it is still over the cap, or send a permissioned link.

Email limits count the whole message. The number in the file's properties is only the raw PDF. Compress PDF can shrink a scan-heavy file, and it cannot shrink a PDF that is already optimized text. Base64 MIME encoding adds about 33% in transit, so a stated 10 MB cap often means the PDF itself should stay under 7 to 8 MB. If compression is not enough, Split PDF or a link is the next step.

The bounce usually arrives at a bad moment: a signed contract, someone waiting, and uncompressed scans that total tens of megabytes. The wording is often "Message size exceeds maximum allowed."

Why a PDF hits the cap

A text PDF is small. A scan PDF is not. A week of expense receipts at 300 dpi in color can dwarf a slide deck, and the mail system counts:

  • The PDF attachments
  • Signature images in an HTML email
  • Encoding overhead, about 33% for a MIME attachment
  • The thread history, if you reply instead of starting a new message

Typical limits in 2026

Verify these with your own organization. The table is a starting point.

| Provider / context | Stated limit | Practical PDF target | |-------------------|--------------|---------------------| | Gmail (consumer) | 25 MB | 20 MB or under, raw PDF | | Outlook.com | 20 to 34 MB, and it varies | 18 MB or under is safer | | Microsoft 365 (default) | 25 to 150 MB, set by an admin | Ask IT. Often 25 to 35 MB | | Corporate gateways | 10 to 25 MB is common | 8 MB or under unless IT confirms | | Mobile carriers | Indirect, through the app | Smaller is easier |

Numbers change. Your IT policy wins over any table in a blog post.

When the send fails

1. Check actual PDF size on disk
2. Remove duplicate attachments / old thread
3. Compress once (medium) → [Compress PDF](/pdf/compress-pdf)
4. Still too big? Split logically → [Split PDF](/pdf/split-pdf)
5. Still too big? Share link with expiry
6. Last resort: re-scan at lower DPI (see scanning guide)

Jumping straight to step 6 is how a signature becomes illegible.

Rescue a blocked send

1. Measure the file

Right-click, then Properties on Windows, or Get Info on a Mac. Read megabytes, not megabits.

2. Compress, then look

Open Compress PDF at a medium setting. Open the output. Zoom in on:

  • The smallest footer text
  • Any scanned signature page
  • Stamps or handwritten notes

If those are readable, send it. If they are not, use a lighter compression or split the file.

Read When Should You Compress a PDF? before you push compression as far as it will go.

3. Split by what the part is

A bad split is pages 1 to 20 and 21 to 40, with no labels.

A usable split:

  • contract-body.pdf
  • contract-exhibits-signatures.pdf

Tell the recipient that both parts matter. Filenames carry the order better than the sequence of attachments.

4. Start a new message

A reply-all chain adds weight. New message, one PDF (or the two split parts), and a small signature image.

5. A link, when policy allows it

Google Drive, OneDrive, or Dropbox: view only, an expiry date, and a password if you need one. Confirm the client can open it before you close the laptop.

Habits by provider

Gmail's web UI offers a Drive link when the attachment is too large. Take it for an external client if the NDA allows that cloud storage.

Outlook on the desktop may warn and still fail later, when the send bounces. Watch the bounce.

A corporate SMTP error is often vague on purpose. An IT ticket with the exact file size saves a round of questions.

Which PDFs fail first

| PDF profile | Email friendly? | |-------------|-----------------| | A 2-page letter export | Usually yes | | A 50-slide deck with photos | Borderline | | An 80-page scan packet | Almost always no, without compress or split | | A merge of ten scanned invoices | Plan to compress before you send |

Merging before compressing beats compressing ten files one by one.

Mistakes

Sending a print-resolution archive. Keep the archive offline. Email a copy at screen resolution.

A password on an encrypted PDF does not make the file smaller. You may still need to split it.

A WeTransfer link with no expiry, on client data. Set the retention on purpose.

WhatsApp is not an unlimited substitute. Document limits differ, and the PDF preview quality varies.

Privacy

Email between businesses is rarely end-to-end encrypted. A sensitive packet needs a password PDF (password guide), a portal, or an encrypted share. Hoping that IT does not log the message is not a control.

Other ways to deliver it

  • An upload slot on the client portal
  • SFTP for a partner you send to often
  • Numbered parts plus an index page
  • PDF to JPG only when the recipient has asked for images. That is unusual for a contract

Related reading

  • When Should You Compress a PDF?
  • How PDF Compression Works
  • How to Scan Documents Properly

Limits

The recipient's gateway is invisible to you. Gmail may allow 25 MB outbound while the recipient's corporate Exchange gateway rejects anything over 10 MB for the whole message.

Compression cannot shrink a text PDF that is already optimized. If there are no high-resolution images left to downsample, use Split PDF or a link with access controls.

Measure the file, compress once and read the result, split by section when you still need to, and use a link when policy allows it. The file that arrives, still readable, is the one that matters.

Related Tools

Free browser-based tools referenced in this article.

Featured
Compress PDF
Compress PDF by redrawing pages as JPEGs. Text selection, links, and form fields are not kept.
Split PDF
Split PDF pages into separate files or extract a page range with pdf-lib on your device.
PDF to JPG
PDF to JPG by rendering each page with PDF.js. The worker script loads from unpkg.com.
Featured
Merge PDF
Merge PDF files into one document with pdf-lib in your browser. Pages are copied, not re-rendered.

Key takeaways

  • MIME Base64 encoding adds roughly 33% overhead in transit, so a 20 MB raw PDF can hit a 25 MB email gateway limit.
  • Compress merged or scanned PDFs once at medium settings and verify small text and signatures at 100% zoom before sending.
  • When a file still exceeds corporate caps (often 10 MB), split by logical section (body vs exhibits) or use an expiring link.

Frequently Asked Questions

Common questions answered to help you get the most from this tool.

Gmail allows about 25 MB per email, including encoding overhead. A practical safe zone for the raw PDF is often 20 to 22 MB. In the web interface, Google Drive link sharing starts automatically above that.

Base64 encoding inflates the size in transit. A corporate gateway measures the MIME-encoded message, not the file size on disk. Leave a margin.

ZIP helps when you are sending many files. One PDF inside a ZIP rarely shrinks much, because the PDF is already compressed internally.

For a large deliverable, yes, if policy allows an external link. Set an expiry and a password when the client expects the file to stay confidential.

Often. A PDF that is almost entirely scans may still need a split or a link after compression.

About the author

Rehan Baqir is the founder & editor of Vertex Solutions. He builds browser-based tools and writes guides about PDF workflows, calculators, image tools, and developer utilities. Article pages show their publication and update dates when available. Read the editorial standards and tool-testing method for the site's stated approach to content and verification.

More about Rehan Baqir →

pdfemailattachmentsfile-sizeoffice
Back to all articles

On this page

  • Why a PDF hits the cap
  • Typical limits in 2026
  • When the send fails
  • Rescue a blocked send
  • 1. Measure the file
  • 2. Compress, then look
  • 3. Split by what the part is
  • 4. Start a new message
  • 5. A link, when policy allows it
  • Habits by provider
  • Which PDFs fail first
  • Mistakes
  • Privacy
  • Other ways to deliver it
  • Related reading
  • Limits

Related Articles

  • Discount Calculator: Sale Price, Markup, and Percent Off
  • How to Scan Documents Properly Before Saving as PDF
  • What a context window actually holds