PDF too large for Gmail?

Why this works

This page runs the same compressor as our main tool but with a Gmail-tuned target: under 24 MB to stay safely below the 25 MB ceiling and account for MIME-encoding overhead.

Gmail's exact attachment behaviour, demystified. The visible cap is 25 MB per message, including all attachments combined plus the message body. Above 25 MB, Gmail auto-uploads the attachment to your Google Drive and sends a link in the message body instead. That sounds convenient but has real problems: the recipient often has to be signed in to Google to view the file; some corporate firewalls block drive.google.com entirely; the link expires if your Drive storage gets reorganised; some email clients render the link as just text rather than an actionable preview, making it look like spam.

The 24 MB target matters because of MIME encoding overhead. When email attachments are encoded for transmission, they bloat by roughly 33% (the binary file is encoded into a base64-compatible text representation that adds about a third to the byte count). A 24 MB file becomes a 32 MB attachment after MIME encoding — still over 25 MB, so Gmail still triggers the Drive conversion. The actual maximum pre-encoded file size that fits inside Gmail's 25 MB envelope is closer to 20 MB. To be safe, target under 20 MB. If you absolutely must use 24 MB, do so knowing that some emails will tip over to Drive depending on header overhead.

Why your recipients hate Drive links. Corporate-firewall blocking is the most common complaint — some IT departments block drive.google.com because it's a known vector for data exfiltration, so the link arrives but the recipient sees "this page is blocked." Sign-in prompts are second — even when a Drive link is set to "anyone with the link can view," some recipients see a Google sign-in prompt due to how their browser is configured, and many people abandon at that point. Permission churn: if your Drive storage rearranges or you change your sharing settings months later, the link breaks retroactively, leaving the recipient with a dead reference in their inbox. Expectation mismatch: recipients expect attachments to be attached — a Drive link in place of an attachment is a different mental model and some people simply don't realise the link is what they're looking for.

What the Gmail-safe target actually does. We run the standard compressor with the target preset to 20 MB (well under the 25 MB ceiling after MIME overhead). The compression strategy is the same as the main Compress tool — image downsampling to 150 DPI, stream re-compression, font subsetting, redundant-resource removal — just with the cutoff explicitly set to your Gmail-clearing target rather than a generic "recommended" preset.

What to do when your file is genuinely over 100 MB. At that scale, compression alone is unlikely to get you under Gmail's cap without significant quality loss. Better options: split the document into logical sections using the Split tool and send a series of emails; convert to grayscale first if it's a colour scan (halves the size); host on a public link service (Dropbox, WeTransfer) that recipients are more familiar with than Drive; send via Gmail's Confidential mode, which can attach larger files through Drive but with expiration controls.

A workflow note for repeat senders. If you regularly send large PDFs to the same recipients (monthly reports, contract packages, etc.), the most reliable path is to compress once at the source — build the PDF to fit under 20 MB at generation time, rather than compressing after the fact every month. For exports from accounting software, design tools, or report generators, that usually means picking a "web" or "email" preset rather than "print" at export time.

How it works