How to prepare PDFs for email attachments
Size limits, compressing, splitting, merging, naming and protection
A step-by-step routine for getting a PDF ready to attach: measure it, compress or split it, merge related files, flatten what should not change, name it well and protect sensitive content.
- By HelpMeJPG editorial team
- Published
- Updated
- 9 min read
On this page
Quick answer: Find out how large the file is and how many pages it has, compress it if images are the weight, split it if it is still too big, merge related files into one so the recipient gets a single attachment, give it a name that says what it is, and protect it with a password sent through a different channel if the content is sensitive. Leave headroom under whatever limit applies, because mail encoding makes an attachment larger than the file on disk.
Why attachment limits are tighter than they look
Every mail system has a ceiling on the size of a message, and the ceiling applies to the whole message – text, all attachments and the encoding overhead – not to each file individually, so several small attachments share it. Limits differ between providers, are frequently much lower on corporate servers and web forms than on personal accounts, and the receiving server enforces its own limit regardless of what yours allows. A message that leaves your outbox successfully can still bounce at the other end.
Encoding is the part people forget. Email was designed for text, so a binary attachment is converted to a text-safe representation (base64, defined in the MIME standards) before it is sent, and that representation is roughly a third larger than the file. A PDF that sits just under a stated limit on disk is over it in transit. The practical rule is to aim comfortably below any figure you are given rather than right at it, and when you do not know the recipient's limit, to assume it is modest.
Step 1: find out what you are sending
The PDF page counter reports the page count, the dominant page size and whether the file is encrypted. Dividing size by page count tells you what kind of document you have: a few tens of kilobytes per page is lean text that will not shrink much; several hundred kilobytes or more per page means scans or photographs, which compress well.
The PDF text extractor confirms the diagnosis: if it returns the words, the document has a text layer; if it reports pages with no text, they are images, and the guide to scanned versus searchable PDFs explains what that means for size. The PDF metadata viewer shows the title, author and producing application and flags forms, annotations, encryption and embedded JavaScript – worth a glance, because what the file says about itself travels with it.
Step 2: compress when images are the weight
If the per-page figure points to images, run the file through the Compress PDF tool. It rewrites the file with a compact structure, removes stored thumbnails and, in the lossy profiles, reduces oversized JPEG and Flate images to a sensible resolution and re-encodes them as JPEG at a moderate quality. Text, fonts and vector graphics are never rasterised, so a report stays searchable and prints as sharply as before.
| Profile | What changes | Use it when |
|---|---|---|
| Lossless | Structure only; images untouched | The file must not change visibly, or it is already lean |
| Balanced | Images downsampled and re-encoded; readable at normal zoom | The default for email |
| Strong | More aggressive downsampling | Mostly-text documents with incidental pictures |
| Extreme | Preview-grade images | Only when the legibility of pictures does not matter |
Three limits are worth knowing. Images stored as JPEG 2000, JBIG2, CCITT fax, CMYK or indexed colour are left as they are, because they cannot be re-encoded safely in a browser; a black-and-white fax-style scan will therefore barely move. Embedded fonts are not subsetted, so a file whose weight is fonts will not shrink. And an image is only replaced when the new version is meaningfully smaller, so a document that was compressed once already gains little from a second pass. Compress once, on the final version of the file, and read the before-and-after figures the tool reports. How to reduce PDF file size covers the profiles in detail and why PDF compression sometimes fails covers the exceptions.
Step 3: split when compression is not enough
When a compressed file is still too large, the choice is between a stronger profile and a split. For anything people need to read, prefer the split. The Split PDF tool divides a document every N pages or at the page ranges you type, numbering the parts so they sort correctly. Because bytes are not spread evenly – a text page costs almost nothing and a page with a photograph costs a lot – check the size of each part afterwards and move a boundary if one is out of proportion. How to split large PDF files explains range syntax and naming.
Often the better question is whether the recipient needs the whole document at all. Extract PDF Pages pulls out just the pages they asked for; Delete PDF Pages removes blank scans, cover sheets and appendices nobody will read. Both copy the remaining pages into a fresh document without re-rendering anything, so quality is untouched.
Step 4: merge what belongs together
The reverse problem is just as common: a dozen single-page scans, a cover letter and a form arriving as fourteen attachments. Merge PDF combines them into one document in the order you set, and one attachment with a sensible name is far more likely to be read in full than fourteen called scan (3).pdf. Pages are copied object for object, so nothing is recompressed; the merged file is the sum of its parts, so compress after merging, not before.
Two details to check in a merged file: bookmarks are not carried across, and form fields with the same name in different sources (every template has a "Date") can end up sharing a value. How to merge PDF files explains both.
Step 5: flatten what should not change
"Flattening" means turning the interactive parts of a PDF – form fields, comments, stamps – into ordinary page content so they can no longer be edited or accidentally changed in transit. It matters when you are sending a completed form, a quotation or anything a recipient should read but not alter.
None of the tools on this site is a dedicated flattener, but two routes get there. Resize PDF Pages places each page onto new paper as a graphic, which keeps text and vectors sharp but leaves form fields and links behind: the fields' visible appearance stays, their interactivity goes. The heavier option is to render the pages with PDF to JPG and rebuild them with JPG to PDF, which freezes everything but also destroys the text layer and usually increases the file size. If the form must stay fillable – because the recipient is the one completing it – do not flatten at all, and avoid resizing, which would remove the fields.
Step 6: name the file and check it
The file name is the first thing the recipient sees and the thing they will search for later. Invoice-2026-11-ACME-0042.pdf tells them what it is, when it is from and who it concerns; document.pdf, final_v3 (2).pdf and scan.pdf tell them nothing. Use a date in year-month-day order, avoid characters some systems reject (slashes, colons, question marks) and keep the .pdf extension.
Then open the finished file once, as the recipient will. Check that the first page is the page you expect, that the page count matches, that rotated scans are the right way up (fix them with Rotate PDF if not) and that the size on disk leaves room for the encoding overhead.
Protecting sensitive attachments
Email is not a confidential channel: messages are stored on several servers along the way and sit in inboxes indefinitely. If an attachment contains personal data, financial details or anything you would not want forwarded, encrypt it with the Protect PDF tool. Set an open password – the one that actually encrypts the content, with AES-256 – and send that password by another route: a phone call, a text message, a messaging app. A password in the same email as the file protects nothing.
Permission settings (no printing, no copying) are a different matter. They are enforced only by readers that choose to honour them and are lifted by anyone who knows the owner password, so treat them as a polite request rather than as security. How PDF passwords and encryption work explains the two passwords, and safe handling of confidential PDFs covers the things a password does not address: metadata that names the author, content hidden by cropping rather than removed, and comments you forgot were there. The compressor's option to remove document metadata is a quick way to drop the title, author and XMP history before a file leaves your hands.
For very large or very sensitive files, consider a link to storage the recipient already has access to: it carries no size limit and can be revoked, which an attachment cannot.
What not to do
- Do not rasterise a text document to make it smaller. Rendering pages to images and back usually makes a text PDF larger, destroys the text layer and ruins accessibility. Compression never touches text in the first place.
- Do not compress repeatedly. Each lossy pass costs quality, and a second pass over the same images saves little because the detail is already gone.
- Do not rely on "no copy" or "no print" permissions to keep content private. Only the open password encrypts the file.
- Do not send the password with the file.
- Do not split a file into many parts when a link would do.
- Do not rename the extension to get past an attachment filter; it is futile and a quick way to be mistaken for malware.
A checklist before you press Send
- Measure: size, page count, scanned or text.
- Compress once, with Balanced, if images are the weight; check the result.
- Split or extract if still too large; check each part.
- Merge related files into one; compress after merging, not before.
- Flatten, or leave fillable, deliberately.
- Name the file so it can be found; open it and check the first page and the count.
- Protect sensitive content with an open password sent separately; strip metadata if the author or history should not travel.
Frequently asked questions
How small should a PDF be for an email attachment?
Comfortably below the lowest limit in the chain – yours, the recipient's and any corporate filter in between – with roughly a third of headroom for mail encoding. Since you rarely know the recipient's limit, a few megabytes is a safe target for anything routine, and compressing with the Balanced profile usually gets scans there. If it does not, split rather than degrade.
Should I zip a PDF before emailing it?
Usually not. The images inside a PDF are already compressed and the structure is small, so a zip archive is about the same size, and some mail filters block archives while phones open them awkwardly. Zipping is only useful for bundling many files into one attachment, and merging them into a single PDF is the friendlier way to do that.
Is it safe to email a password-protected PDF?
Yes, provided the open password is strong and travels by a different route – a call or a message, never the same email. With AES-256 and a good passphrase the content cannot be read by anyone who intercepts or forwards the message. Remember that permissions such as "no printing" are not encryption and are not enforced by every reader.
Sources and further reading
About the author
HelpMeJPG editorial teamEditorial team
The people who build and maintain the HelpMeJPG tools. Guides are written from the tools' own behaviour and the standards they implement, and are revised whenever a tool changes.