Why the order of merging and compressing matters
When you merge two PDFs and then compress the result, the compression engine (in PDFWix, this is Ghostscript via WebAssembly) analyses the entire merged document as a single unit. It can deduplicate shared resources — fonts used in both documents appear only once, identical image resources are deduplicated, and the compression dictionary covers the entire document. This produces a smaller final file than compressing each PDF individually before merging.
If you compress first then merge: each PDF is compressed independently and packaged with its own resource dictionaries. When merged, these separate resource packages are combined, sometimes resulting in a file that is larger than either compressed file alone. The merge adds structural overhead on top of two already-compressed documents.
The recommended workflow: Merge → Compress
- Open PDFWix Merge PDF.
- Upload all the PDF files you need to combine. Reorder them if needed by dragging.
- Click Merge and download the combined PDF.
- Open PDFWix Compress PDF.
- Upload the merged PDF. Choose Recommended or High compression.
- Download the final compressed merged PDF.
When compressing before merging makes sense
There is one scenario where compressing before merging is the right approach: when one source PDF is very large (50MB+) and you need to reduce it before merging because your browser cannot handle the combined file size in one operation. In this case, compress the oversized file first to reduce it to a manageable size, then merge. This is an edge case — for most everyday merging tasks, merge first then compress.
For more on merging PDFs with mixed page sizes, see our guide to merging PDFs with different page sizes.