Updated September 2026
A PDF that's too large to email usually fails silently or with a vague error — the message bounces, or your provider quietly switches it to a cloud-storage link instead. Here's how to get it under the limit, and what typical limits actually look like.
Exact limits vary by provider and, for work accounts, by whatever policy your organization's admin has set — always worth checking if you're not sure — but commonly-cited figures for personal accounts are:
Scanned PDFs — a stack of paper run through a scanner at a high resolution — are the most common way to blow past these limits, since a scanner can easily produce several megabytes per page.
Drop the file into the compressor above. For a scanned document, expect a 50–90% reduction, which turns most "too big to email" files into comfortably-sized attachments. For an exported report or presentation, expect a smaller but still real reduction from image and object cleanup. Nothing is uploaded during this — the file is compressed on your own device before you attach it to anything, so there's no extra copy of a sensitive document sitting on a third-party server in between.
Occasionally a document is large because of what's genuinely in it — many full pages of high-resolution scans, for instance — and compression alone doesn't get it under a strict limit. A few options at that point:
If you regularly need to email a batch of separate PDFs — invoices, scanned forms, individual contracts — the paid batch mode compresses multiple files in one pass and packages them into a single ZIP you can attach as one file instead of several. It's a one-time $9.99 unlock, not a subscription; see the batch compression guide for how it works. This doesn't merge the PDFs into one document — it just compresses and zips them together for a single attachment.
Compressing before you send is also a reasonable moment to double check what you're about to attach — scanned documents often include more pages than intended (a blank cover sheet, a stray page from the scanner feeder), and compressing gives you a natural checkpoint to open the result and confirm it's actually the file you meant to send.
Some webmail providers apply their own server-side compression or conversion when a file is too large — the "upload to Drive automatically" behavior mentioned above is one version of this. The difference between that and compressing first yourself is control: you decide what the final file looks like and confirm it before it leaves your device, rather than letting an email provider's own (opaque, provider-specific) process decide for you after the fact. For anything where the exact contents matter — a signed agreement, a filled-out form — checking your own compressed copy first is the safer habit.
The same size limits generally apply whether you're sending from a desktop mail client, a webmail tab, or a phone's mail app — the cap is set by the receiving/sending mail service, not by which device you're composing on. If you scanned a document directly on your phone and it's too large to attach, you can run it through the compressor from the same phone before attaching it; see compressing on different devices for the mobile-specific notes.
Does compressing a PDF for email change how it looks to the recipient? For text-heavy documents, no — the visible content is unchanged. For scanned pages, the re-rendered version is sized for normal screen reading and printing; see what changes during compression for the specifics.
Why not just let Gmail/Outlook auto-convert to a cloud link? That works, but it means the file now lives on a cloud drive with its own sharing and retention settings — compressing first and attaching directly keeps the document a plain attachment under your control, when that's what you'd prefer.
Does compressing help with attachment limits on group or mailing-list emails? Yes — the same per-message size limits generally apply regardless of how many recipients are on the message, so a compressed attachment helps equally there.