You attach a PDF to an email and hit send. From your perspective it's simple — the file goes from your device to the recipient's inbox. What actually happens between those two points is more involved, and a few things along the way can affect whether the file arrives intact, at the right size, and in the expected state.
The File Gets Encoded Before It Leaves Your Device
Email was originally designed to carry plain text. Attaching a binary file like a PDF required a workaround — the file gets converted to a text-safe format before transmission. The standard method is Base64 encoding, which converts the PDF's binary data into a string of printable characters.
Base64 encoding increases the file size by approximately 33%. A 15MB PDF becomes roughly 20MB as encoded email data. This is why files close to attachment size limits sometimes fail to send even though they appear to be under the limit — the encoded version exceeds the threshold. The recipient's email client reverses the encoding on receipt, so they get back the original file at its original size.
The Journey Through Mail Servers
After leaving your device, the email passes through your outgoing mail server, potentially one or more relay servers, and then the recipient's incoming mail server before reaching their inbox. Each server performs checks on the message — spam filtering, virus scanning, size verification, and content policy enforcement.
Any of these servers can reject or modify the message. A corporate mail server with a 10MB attachment policy will reject a 20MB PDF, even if both the sender's and recipient's consumer email services would have accepted it. Some antivirus filters quarantine attachments for manual review before delivery. A few older or misconfigured mail servers can corrupt binary attachments during processing — rare but it does happen, which is why a PDF that worked fine to one recipient may arrive damaged to another.
What Mail Servers Do to PDF Attachments
Most corporate and enterprise mail systems scan attachments for malware before delivery. A PDF can contain JavaScript, embedded files, and executable content — all of which security scanners look for. A PDF with unusual structure or embedded scripts may be quarantined or stripped of those elements before reaching the recipient.
Some systems convert PDF attachments to other formats — typically to render them safely in a preview pane without executing any embedded content. The recipient may receive a converted version rather than the original PDF. For documents with complex formatting, this conversion can change how the document looks.
The PDF Content Itself Doesn't Change in Transit
In the vast majority of cases — when the email delivers successfully and no security filters intervene — the PDF the recipient opens is byte-for-byte identical to the one you sent. The encoding and decoding process is lossless. The file that arrives is exactly the file you attached.
This is worth knowing because it means if a PDF looks different after being emailed, the issue is usually in how it's being viewed — different PDF viewer, different default zoom, different font availability — not in the transmission itself. The file is the same; the viewing context is different.
When Delivery Fails — and How to Know
Delivery failures come in two types: bounces you hear about and silent drops you don't. A bounce notification tells you the message was rejected — usually with an error code indicating why. Common reasons include file size exceeding limits, the recipient's mailbox being full, or the recipient's domain not existing.
Silent drops are more insidious — the email appears to send, no bounce arrives, but the recipient never receives the attachment. This can happen when a security filter quarantines the attachment without notifying the sender, or when a corporate policy strips attachments above a threshold without generating an error. For important documents, asking the recipient to confirm receipt of the attachment is the only reliable way to know it arrived.
Making PDF Email Delivery More Reliable
- Keep files under 10MB: accounting for Base64 encoding overhead, a 10MB PDF encodes to roughly 13MB — safely under most server limits. Use PDF Compression on anything larger before attaching.
- Avoid embedded scripts: PDFs with JavaScript or unusual embedded content are more likely to be flagged by security filters. Standard document PDFs without interactive scripts travel more reliably.
- Use cloud sharing for large files: uploading to Google Drive or Dropbox and sending a link sidesteps all attachment size limits and encoding overhead.
- Confirm receipt for important documents: a quick reply confirming the PDF arrived is the only reliable way to close the loop on successful delivery.