3 min readWorkflows
Bundle a set of documents into one archive locally
When a ZIP helps and when it does not, why archiving already-compressed PDFs saves almost no space, and how to name a bundle so the recipient can use it.
The short answer
Select the PDFs, name the archive after what it contains, and package them into a single ZIP built in the browser. A ZIP solves the problem of sending many separate files; it does not meaningfully reduce size, because PDF content is already compressed and has little redundancy left for the archiver to exploit.
- ZIP reduces file count, not file size; expect a few percent saving at best on a set of PDFs.
- Choose merging over archiving when the documents are meant to be read in sequence as one thing.
- Name the archive and the files inside it for someone who has no context, because that is who receives it.
Sending twelve separate attachments is unpleasant for everyone. It clutters the message, invites a mail gateway to complain, and guarantees that at least one file gets lost between the download folder and wherever it was supposed to go. An archive fixes the count problem cleanly.
What a ZIP does and does not do
The ZIP packaging tool builds an archive from the files you select, in the browser, without uploading them. Two expectations are worth setting.
It reduces the number of files to one. That is the real benefit: one attachment, one download, one folder on the recipient's machine, and a structure that survives the journey.
It barely reduces size. This surprises people, so it is worth explaining. ZIP compresses by finding redundancy. PDF content streams are already compressed — text with Flate, images with JPEG or similar — and compressed data is close to random from an archiver's point of view. There is almost nothing left to squeeze. A set of PDFs typically compresses by a low single-digit percentage. Occasionally zero.
So if the reason you are reaching for a ZIP is that the attachment is too large, it will not help. Reduce the documents themselves with the compression tool, or send fewer pages, as the email size guide sets out.
Archive or merge?
These solve different problems and choosing wrongly makes life harder for the recipient.
| Situation | Better choice |
|---|---|
| Documents read in sequence as one pack | Merge into a single PDF |
| Separate documents that stay separate | ZIP archive |
| Files that must be individually filed or forwarded | ZIP archive |
| A report with appendices | Merge |
| Twelve signed contracts for twelve clients | ZIP archive |
| Mixed file types, not only PDFs | ZIP archive |
The test is whether the recipient will treat the contents as one thing or as many things. A tax pack that will be read start to finish should be merged, as described in the merging guide. Twelve invoices that each need filing separately should not be — merging them creates work at the other end.
Name it for someone with no context
The person receiving the archive does not know what you were thinking when you built it. Two naming decisions carry most of the value:
The archive name should say what it contains and when. invoices-acme-2026-q2.zip
is instantly filable. documents.zip is not, and neither is final.zip.
The file names inside should be self-describing and should sort correctly.
01-cover-letter.pdf, 02-statement-january.pdf, 03-statement-february.pdf
tells the recipient the intended order without a covering note. Zero-pad the
numbers, or 10 will sort before 2.
Avoid characters that behave differently across operating systems — colons, slashes, question marks, and trailing dots cause extraction failures on some platforms. Stick to letters, digits, hyphens, and underscores. Keep paths short, because deeply nested archives with long names still hit path length limits on some systems.
Practical habits
- Check the file count before sending. Expecting fourteen files and packaging thirteen is a mistake that only surfaces at the far end.
- Say what is inside. A one-line summary in the message body, listing the documents, means the recipient can tell immediately whether something is missing.
- Do not archive one file. A ZIP containing a single PDF is pure friction.
- Watch for gateways that block archives. Some corporate mail filters quarantine ZIP attachments as a matter of policy. If the recipient is behind one, a merged PDF or a shared link is the pragmatic answer.
- Package after editing, not before. An archive is a container; correcting one document inside it means rebuilding it.
A note on privacy
Archiving is not protection. A ZIP is a container, not a lock: anyone with the file can open it and read every document inside. If the contents are confidential, encrypt the documents themselves before packaging, and send the passphrase through a different channel from the archive.
Because the archive is assembled in this browser workflow, the documents are not uploaded to a product bundling endpoint. That matters when the archive contains client files intended to remain on the operator's device.
Tools used in this guide
Each workspace runs in this browser tab. Open one directly to apply the steps above to your own document.
Written by The PdfEditorOnlineFree team. Published and last reviewed . Product behaviour described here reflects the linked workspaces at the time of review; check the tool page for current limits.