pageit
PDF to link PDF to webpage Free tools Blog
← Back to blog

PDF Too Big to Email? Send a Link Instead

Swapnil Jain

Your PDF is too big to email because it’s bigger than your provider’s attachment cap: 25MB on Gmail and Outlook.com, as low as 10MB on a lot of corporate Exchange accounts. Email was never built to move large files reliably in the first place. Compressing the file buys you some room, but a scanned document or an image-heavy PDF often won’t shrink enough to matter. The fix: stop attaching the file, host it, and send a link instead.

TL;DR: PDF attachments cap out around 20-25MB on Gmail and Outlook, lower on business email. Compression mostly helps text-heavy PDFs, not scans. Hosting the file and sending a link gives you one 30MB cap you clear once, higher than Gmail, Outlook, and Exchange’s own attachment caps, instead of a different limit every time you resend, and it opens on any device without a download.

Why is my PDF too big to email?

Two things are working against you at once. First, every provider enforces a hard cap, and it’s lower than people assume:

Current attachment caps

Every major inbox has a ceiling

Gmail single attachment, personal account
25 MB
Outlook.com single attachment, web app
25 MB
Outlook desktop total message, sending to internet accounts
20 MB
Exchange / corporate mail total message, typical default
10 MB

Sources: Gmail attachment limits (Google Help), and Outlook.com sending limits plus Outlook's attachment-size guidance (Microsoft Support). Gmail's own help page says the same thing this guide does: attachments over the cap get swapped for a Google Drive link automatically. The fallback IS a link.

Second, the cap isn’t measured against your file on disk. It’s measured against the email after your file has been encoded for transit. Attachments travel as base64, which inflates the file by roughly a third. A 19MB PDF sitting comfortably under Gmail’s limit on your desktop can push the actual message past 25MB once it’s wrapped for sending. That’s the gap between “my file browser says 19MB” and “Gmail says it’s too big.”

Does compressing the PDF actually fix it?

Sometimes. A text-heavy PDF, like a contract, a report, or a slide deck exported with embedded fonts, usually compresses well, often 50% or more, because there’s real redundancy in the underlying data to strip out. Your PDF app’s built-in compressor, or your operating system’s own “export as reduced-size PDF” option, handles this in a couple of clicks.

A scanned PDF is a different problem. It’s already a sequence of images, and images don’t compress the same way text does. You can knock the resolution down and lose some detail, but you’re rarely getting a 40MB scanned contract under 10MB without it becoming hard to read. If your file falls into that category, compression is a detour, not a fix.

The actual fix is to stop treating the PDF as something that has to travel through the email pipe at all. Host it somewhere, and email the link instead of the file. The workflow is the same regardless of where you host it:

  1. Upload the PDF. It goes to a host, not to the recipient’s inbox.
  2. It gets a URL. One link, and nothing on the recipient’s side caps how big the file behind it can be.
  3. You send the link. Paste it into the email instead of attaching the file.
  4. They open it anywhere. Phone, laptop, or tablet, no download required.

On PageIt, that’s the whole flow: drop the PDF in, it’s hosted at its own URL immediately, and you paste that URL into your email. Your recipient’s inbox never sees the file, so their attachment cap doesn’t apply to them at all. Only PageIt’s own 30MB upload limit does, once, when you host it, and that single cap already clears Gmail and Outlook.com’s 25MB ceiling, Outlook desktop’s 20MB, and Exchange’s stingy 10MB default. It also sidesteps the base64 inflation that pushes a file which looked fine on disk over Gmail’s or Outlook’s stated cap. If your source file is already over 30MB on disk, compress it first using the steps above, then host the result. You can also lock the link down: add a password, set an expiry date, or turn off downloads so people can read but not save it. If you need to fix a typo or ship a corrected version later, you replace the file and the link stays exactly the same. Nobody has to go dig up a new email.

What does the person you send it to see?

They get a link. Clicking it opens the PDF straight in their browser, on desktop, phone, or tablet, with no app to install and no account to create. It’s private by default: the link isn’t indexed or listed anywhere public, so only someone with the URL can open it.

Here’s the practical difference against a straight attachment:

Email attachmentA hosted link
Size limitCapped by your provider (10-25MB), and it changes per recipientYou upload once, up to 30MB, higher than any of the caps on the left, and the recipient never hits one
Opens on mobileDepends on the mail app and PDF viewerAny browser, no app needed
Fixing a mistake after sendingResend the whole file, new email threadReplace the file, same link
Knowing if it was openedNot unless you askView count, if the host tracks it
What the recipient needsEnough inbox storage to download itNothing, it opens in the browser

When you should still attach the file

A link isn’t the right call every time. Some workplaces archive email attachments for compliance, and a link doesn’t satisfy that. Some recipients genuinely need the file itself, not a page that renders it, especially if they’re working somewhere without reliable internet. And a handful of corporate mail filters flag or strip outbound links, which defeats the point.

Send a link when:

  • The file is over the recipient’s inbox limit
  • They’ll open it on a phone or tablet
  • You’ll need to replace or update the file later
  • You want to know if it was actually opened

Keep the attachment when:

  • The recipient’s system archives email attachments for compliance
  • They need the file itself with no internet access later
  • Your organization blocks outbound links in email filters
  • The file is small enough that a link adds a step for nothing

If what you actually want is for the PDF’s content to read well on a phone rather than just be viewable as a hosted copy of the original file, that’s a related but different job. Converting it into a proper webpage does more reformatting than simply hosting the PDF as-is.

FAQ

Why does Gmail say my PDF is too big?

Gmail caps attachments at 25MB per message on personal accounts. Once an attachment crosses that line, Gmail’s own send flow will offer to swap it for a Google Drive link automatically, a good sign that hosting a link solves the problem better than shrinking the file does.

What’s the real attachment size limit for Gmail and Outlook?

Gmail and the Outlook.com web app both cap a single attachment at 25MB. The Outlook desktop app enforces a 20MB total message limit when sending to internet email accounts, and a lot of Exchange-based business accounts default lower, often 10MB.

Does compressing a PDF always get it under the limit?

No. Text-based PDFs compress well because there’s redundant data to strip. Scanned or image-heavy PDFs are mostly incompressible without visibly losing quality, so a large scanned file may still be too big after compression.

A hosted link isn’t indexed publicly, so only someone with the URL can open it. If the content is sensitive, add a password and an expiry date so access is limited on top of the link itself being unguessable.

Uploading a PDF to get a link takes a quick Google sign-in. Opening one never does: recipients just click the link and the PDF opens in their browser, no account required on their end.

Can I still send the original file this way, not a converted version?

Yes. Hosting a PDF as a link keeps the original file exactly as it is; nothing about the document gets converted or re-rendered unless you specifically choose to turn it into a webpage instead.

Next time a PDF bounces back with a size error, skip the compression tool and the “can you resend that smaller” reply.

Stop emailing file attachments. Share a PageIt link instead.

Get started