Gmail sends up to 25MB, counted before encoding, but the recipient's server may count the encoded message, which is about 37 percent larger. An 18MB file clears a 25MB cap at either end. Compress the PDF, do not use Drive links unless you have to, and aim tighter if the recipient reads mail on a corporate server.
Compress a PDF for Gmail targets exactly 18MB. Drop your file in, wait a few seconds, done.
A PDF that opens fine sits at 22 MB on your disk. You send it from Gmail, and it bounces, or the person never gets it. The 25 MB limit your file is under is real, but it only covers Gmail's half of the trip.
Google's help page puts the personal Gmail limit at 25 MB, and anything larger is swapped for a Google Drive link automatically. What the page does not say is that the file changes size on the way: attachments are encoded for transit, and the server at the other end may measure that larger figure.
What the 25 MB limit measures
Email attachments cannot be sent as raw binary. The protocol that carries them, SMTP, was designed in the early 1980s for text and only handles a limited set of characters. To ship a PDF through it, the file is converted into a text-friendly format called base64.
The same applies whichever service says a PDF file is too large to email: the size that decides it is the one the receiving server measures, and that is often the encoded one.
Base64 encoding uses 4 characters for every 3 bytes of the original file. That is a fixed 33 percent expansion, and line breaks and MIME headers add a little more. Google's own receiving-limits page puts the total at about 37 percent.
Google is explicit about which side counts what. Its Workspace sending limits are measured before encoding, so Gmail itself will send a 22 MB PDF, while its receiving limits are measured after encoding. Other providers' servers make their own choice, and Microsoft's Exchange measures the encoded message.
Measured before encoding, per Google. Larger attachments become a Drive link.
Google's figure for base64 plus line breaks. The same share at every file size.
Raw size that still fits a 25 MB cap measured after encoding.
Do the arithmetic on a 22 MB PDF. Encoded, it becomes roughly 30 MB. Gmail lets it go, because its own check is on the 22 MB. A receiving server that holds the encoded message to 25 MB refuses it, and the bounce arrives in your Gmail inbox, which is why it looks like Gmail's decision.
Compress the PDF to fit
The right target depends on what kind of file you are shipping. An 18 MB target clears a 25 MB cap measured at either end. Scanned pages usually need more compression than documents exported from Word, because nearly all of their weight is images.
Open a compressor that targets a specific size
Generic "compress PDF" tools give you one output at a fixed quality. A size-targeted compressor tries stronger settings in turn and stops as soon as the file fits.
Drop the file into a tool that targets 18 MB
Compress PDF for Gmail tidies the file structure first, then recompresses the images in seven steps from 200 ppi down to 60 ppi, and rebuilds pages as pictures only if that is still not enough. It stops at the first stage under 18 MB.
Verify readability before sending
Open the compressed file, zoom to actual size on the pages with the smallest text. If it reads clearly, you are done. If not, you have room: Gmail itself sends up to 25 MB, so a 20 MB file will leave your outbox, and the only risk is the recipient's server.
Compress vs Google Drive link
When attachments add up to more than 25 MB, Gmail uploads them to Google Drive and puts a link in the message instead. This works, but it is worth understanding what changes for the person on the other end.
Behaves like every other email
- Arrives as an attachment with a preview icon
- Survives corporate email gateways and forwards
- Works forever, independent of your Drive
- No permission dialogs, no sign-in prompts
Changes the recipient's experience
- Shows as a link, not an attachment
- Sometimes flagged as suspicious by spam filters
- May ask the recipient to sign in or request access
- Breaks if you ever move or delete the file
Neither is wrong. Compression is the default when the file is compressible and the recipient is anywhere outside your organization. Drive links are the fallback for anything too large to shrink, or for internal sharing where everyone already lives in the same Google Workspace.
The recipient's server matters
Gmail's limit is not the only limit in the chain. Every mail server your attachment passes through applies its own cap, and the tightest one wins. Corporate inboxes are usually where things fail.
Microsoft's Exchange Server, common in larger companies, defaults to 10 MB for mail entering or leaving an organisation, and that limit is measured after encoding, which leaves roughly 7.5 MB for the attachment. The Outlook and Exchange limits are set out with Microsoft's own figures in the companion guide.
The rule of thumb: if you know the recipient sits behind a corporate address, aim for under 10 MB instead of 18 MB, and nearer 7 MB if their server may be a strict 10 MB Exchange default. Compress PDF under 10 MB works the same way as the Gmail tool with the lower target.
When compression will not be enough
Some PDFs cannot shrink to 18MB and stay legible. A hundred-page colour photograph book is one example. Full-resolution architecture drawings are another. When you hit that wall, you have three real options.
Split the file
Two 15MB emails almost always beat one 30MB email that bounces. Break the PDF into a "part 1 of 2" and "part 2 of 2" using our Split PDF tool. Recipients can save both and combine later if they want, or read them in sequence. Common in legal work, where discovery productions are routinely delivered as numbered batches.
Send via a link that you control
Google Drive, OneDrive, Dropbox, iCloud Drive: each offers link-based sharing. The email carries a URL instead of the file. The catch is that some recipients treat cloud links as suspicious, some gateways strip previews, and the link breaks if you move or delete the file. In exchange the email stays small and arrives at once.
Use a file-transfer service
WeTransfer, Send Anywhere, and Swiss Transfer let you send large files as time-limited links with little or no sign-up. Good for one-off large deliveries. Not appropriate for anything you want indexed in the recipient's inbox permanently, since the link expires.
Habits that stop the problem before it happens
Once you understand why big attachments fail, you can build small habits that keep files under the ceiling without thinking about it.
Compress at export. When saving PDFs from Word, Pages or InDesign, pick the smallest-file or optimised preset, which reduces image resolution before the PDF is written.
Scan documents in greyscale. A colour scan stores three channels for every pixel where greyscale stores one, so unless you need colour, greyscale usually gives a much smaller file.
Leave headroom. A file that lands just under the target has no margin for the message text and headers that go around it.
Ask before a first large send. One message to a new corporate contact asking what size their inbox accepts saves a silent bounce.
Compress a PDF for Gmail in your browser
Targets 18 MB and stops at the first setting that fits. Runs on your device; nothing is uploaded.
Common questions
Details that come up after the first bounce.
01What is Gmail's real attachment size limit?
25 MB for a personal account, measured before encoding, according to Google; Workspace administrators can set their own. The limit to plan around is the recipient's, which is often measured after encoding adds about 37 percent. An 18 MB file stays under a 25 MB cap measured either way.
02Why does my 22MB PDF fail when Gmail claims 25MB?
Gmail sends it, since its own check is on the file before encoding. The failure comes from the receiving server: encoded, the file is about 30 MB, and a server that holds the encoded message to 25 MB refuses it. The bounce lands in your Gmail inbox, which makes it look like Gmail's decision.
03Will Gmail's automatic Drive link save me?
It bypasses the size cap but changes what your recipient sees. The message arrives with a link icon instead of a paperclip. Some corporate spam filters treat oversized Drive links as suspicious. The file breaks if you ever move or delete it from your Drive. Compression, when it works, keeps the experience identical to a normal email.
04How much can compression realistically shrink a PDF?
It depends on where the weight is. Scanned documents and image-heavy PDFs shrink a lot, because nearly all of their size is pictures that can be resampled. Text-based PDFs exported from Word or Google Docs shrink much less, because there is little to remove. If a text-only PDF is over 18MB, something unusual is inside (embedded fonts, uncompressed images), and re-exporting from the source with better settings is the better fix.
05What if the recipient is on corporate email?
Aim for under 10MB, and about 7MB if their server may be Exchange on its 10MB default, which Microsoft measures after encoding. Even if Gmail sends a 20MB file, the recipient's server may reject it, and corporate gateways do not always bounce the message back.
06Does PDFslime upload my file to compress it?
No. Compression runs entirely in your browser. Files are read into local memory and never sent to a server. Close the tab and the data is gone. This matters when the PDF contains anything you would not want on a stranger's server, which is most business documents.