Guide··7 min read

Your PDF Is Too Big to Email. Here Is What Actually Works

Attachment limits are smaller than people assume, and most "compress PDF" advice quietly destroys your text layer. A walkthrough of what makes a PDF large, which fix suits which document, and what each one costs you.

You attach the file, click send, and the message bounces: attachment too large. The first search result tells you to "compress your PDF online". You do, the file shrinks, and three weeks later someone asks why they cannot search the contract you sent them.

There are several genuinely different ways to make a PDF smaller, and they are not interchangeable. This article covers what limits you are actually up against, why your file is big in the first place, and which fix fits which document.

The limits you are hitting

Mail providers advertise generous attachment sizes and then apply a smaller effective limit, because attachments are encoded in base64 for transport — which inflates them by roughly 33 per cent. A 20 MB nominal limit means a real ceiling closer to 15 MB of original file.

  • Gmail and Outlook.com: 25 MB nominal, so plan for about 18 MB of actual file.
  • Microsoft 365 / Exchange: often 25 MB, but administrators routinely lower it to 10 MB.
  • Corporate gateways and government portals: 10 MB is common, 5 MB is not unusual.
  • The recipient's limit applies too — your 24 MB attachment leaves your outbox and is rejected at theirs.

Aim for under 10 MB if you do not know the recipient's setup. It is the size that survives almost every mail system without a conversation about it.

Why your PDF is large

Before choosing a fix, work out which kind of file you have. The distinction decides everything that follows.

  • A scan. Every page is a photograph. A 30-page scan at 300 DPI in colour can easily reach 50 MB. This is the most common cause and the most compressible.
  • A slide deck or report with images.Text is vector and tiny; a handful of full-bleed photographs account for nearly all the bytes.
  • Pure text exported from a word processor.Usually already small. If such a file is large, the cause is almost always embedded fonts or an unusually long document, not image data.
  • A document with hundreds of pages.No individual page is heavy; there are simply a lot of them.

Fix 1: send fewer pages

This is the option people skip, and it is frequently the right one. If the recipient needs clauses 4 to 9, sending them the whole 200-page master agreement is not generosity — it is a 40 MB attachment and a worse experience for them.

Extract Pages gathers the pages you choose into one new document. It is lossless: the pages that survive are copied at full fidelity, so text stays selectable and searchable. Delete Pages does the same job from the other direction when it is easier to describe what to remove.

Fix 2: compress, and understand the trade

Compression is the right answer for scans and image-heavy decks. It is worth knowing exactly what most browser-based compressors — including ours — actually do: each page is rendered to an image at a chosen resolution, and those images are packed into a new PDF.

That is why the saving is so reliable on a scan. It is also why the result has one significant limitation: the output pages are pictures. If the input had a real text layer, that layer is gone. The recipient cannot search it, copy from it, or have a screen reader read it aloud.

For a scan, you lose nothing — a scan without OCR had no text layer to begin with. For a contract exported from Word, you have quietly downgraded the document.

Resolution guidance, in DPI: 72 is a thumbnail-grade minimum that stays legible on screen, around 108 is the sensible default for on-screen reading, and 144 is what you want if the document might be printed or read on a high-density display. Below 72 DPI, body text starts to break down.

Fix 3: fix the images before the PDF exists

If you are the one building the document, the cheapest saving happens before export. A 12-megapixel phone photo dropped into a report is roughly forty times more pixels than a full-page print needs. Running the images through Image Resize and Image Compress first produces a document that is small and still has a real text layer — the outcome page-level compression cannot give you.

Fix 4: do not attach it

A link to shared storage has no size ceiling, survives the recipient's mail gateway, and lets you revoke access later. The trade-off is that the file now lives on a service, and access control becomes something you have to manage. For anything genuinely confidential, a smaller attachment sent directly is often the safer choice.

A decision shortcut

  • Scanned paperwork: compress at 108 DPI. Nothing is lost that was ever there.
  • Long document, recipient needs part of it: extract the relevant pages. Lossless and more useful for them.
  • Report or deck you are building: shrink the images before export.
  • Contract or filing that must stay searchable: do not compress. Send fewer pages, or send a link.
  • Already-small text PDF that is somehow large: compression will make it bigger, not smaller. Look at embedded fonts instead.

One habit worth keeping

Whatever you do, keep the original. Every fix above except page extraction is irreversible: you cannot recover a text layer from a rasterised page, and you cannot restore detail that JPEG compression discarded. Compress a copy, send the copy, archive the original.

And consider where the compression happens. A document large enough to bounce from email is often exactly the kind of document — a signed contract, a medical record, a scanned passport — that you would rather not upload to a free service in order to make it smaller. Every tool linked in this article runs entirely inside your browser: the file is never transmitted anywhere.

Related reading

Continue reading