Free · Fast · Privacy-first

Merge PDF Files Then Compress

The most common real-world PDF workflow is not just merging or just compressing in isolation.

⚡

Merge + compress in two steps

🔒

No file size limits

✨

No quality watermarks

⚡

Free both tools

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this PDF Merger to your website

Drop the PDF Merger into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/pdf/pdf-merger?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="PDF Merger by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/pdf/pdf-merger?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="PDF Merger by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Why merge first and compress second, not the other way around

The order of operations matters significantly in the merge-then-compress workflow. Compressing individual PDFs before merging looks efficient at first glance, but it creates a quality consistency problem. Each file is compressed independently against its own content profile, and when you merge multiple separately-compressed files the resulting document may have inconsistent image quality across pages. Page 1 might be compressed at 75 percent JPEG quality because the source had mostly text with one small photo, while page 2 from a different source might be at 60 percent quality because that source was photo-heavy and the compressor pushed harder. Merging first and compressing the combined output once gives you a single uniform quality pass across every page in the document.

When you compress the merged PDF as one unit, the FixTools compressor analyses the entire document together rather than each source separately. It identifies duplicate font embeddings, which is common when merging PDFs from the same source application because every source file embeds its own copy of the same fonts. It removes redundant ICC colour profiles that multiple sources may have included independently. It applies a single image compression setting uniformly across all embedded images regardless of which source file they came from. A 30-page merged PDF assembled from five separate reports might share three identical font files that were embedded five times across the sources, and compressing the merged output removes four of those duplicates, saving space that no amount of pre-merge compression would have addressed.

For compression level selection after merging, the right choice depends on the content mix of the combined document. If all pages are primarily text and vector graphics typical of office documents, reports, and presentations, medium compression reduces file size by 30 to 50 percent with zero visible change at normal viewing zoom. If some pages are scanned images, high compression reduces those pages' image quality noticeably at the resulting 150 DPI image resolution, which is acceptable for screen reading and emailing but not ideal for high-quality printing. If the merged document will be printed, use medium compression only. If it is for digital review or email delivery, high compression is fine and produces dramatic size reductions.

There is one edge case where pre-merge compression makes sense, which is memory management for very large source files. If any single source PDF is over 80 to 100MB, compressing that one file before the merge reduces the browser memory needed for the merge session itself and avoids potential tab crashes during the merge step. In this case the workflow becomes compress-the-large-sources, then merge, then run one final consistency compression on the merged output. This three-step variant is overkill for normal documents but worth knowing about when you are assembling large archival bundles or merging multiple high-resolution scans into a single deliverable file.

PDF compression standards overview Image compression in PDF files

How to use this tool

💡

Use the PDF Merger to combine your files, then immediately compress the merged result using the PDF Compressor.

How It Works

Step-by-step guide to merge pdf files then compress:

1
Step 1, Merge your PDFs
Open the PDF Merger, upload all the PDF files you want to combine, arrange them in the order they should appear, and click Merge PDF. The browser assembles a new combined document from your sources without re-encoding any of the content. This first step preserves the exact original quality of every page so that the subsequent compression pass has the cleanest possible input to work from.
2
Download the merged PDF
Download the merged file to your device. Keep a copy in your Downloads folder rather than deleting it immediately because if the compression step produces an unsatisfactory result you can go back to the merged-but-uncompressed file and try a different compression level without having to re-merge from the original sources, which saves time on large merges.
3
Step 2, Compress the merged PDF
Open the PDF Compressor linked below, upload the merged PDF you just downloaded, choose a compression level appropriate to your content and your target file size, and click Compress PDF. Medium compression is the right default for most documents because it reduces file size meaningfully while keeping all visual content sharp at normal viewing zoom.
4
Download the compressed result
Download the compressed PDF. The file is now both merged and optimised, ready for sharing via email, uploading to a portal, attaching to a chat message, or archiving in a document management system. Open the compressed file briefly to confirm legibility before you send it, because a five-second visual check catches anything that would be embarrassing to discover after the fact.
5
Optional, keep both files
Keep the uncompressed merged file as your archive copy and use the compressed file for distribution. The uncompressed version preserves maximum quality for any future use such as printing or re-purposing, while the compressed version solves the immediate sharing problem. Storage is cheap and having both versions costs almost nothing, but having only the compressed version may force you to re-merge later if higher quality becomes necessary.

Real-world examples

Common situations where this approach makes a real difference:

Marketing manager assembling a campaign report

A marketing manager merges five weekly campaign performance PDFs into a monthly summary for distribution to the leadership team. The merged file is 22MB because each weekly report contains full-resolution chart screenshots and embedded brand assets. A single medium compression pass on the merged output reduces the file to 6MB, well under Gmail's attachment limit and small enough to clear most corporate mail servers in one shot. The chart readability remains identical to the source files at normal viewing zoom in the email client.

Architect sending planning documents to council

An architect merges a site plan, elevations, and detailed specifications into one 85MB submission package for an electronic planning portal. The portal enforces a 20MB file size limit per submission. After merging, one high-compression pass on the combined output reduces the scanned drawing pages to 14MB, well inside the portal's ceiling. The text annotations and dimensions on the drawings remain fully legible at the compressed resolution, which is what the planning officers need to review.

Teacher compiling student handout packet

A secondary school teacher merges eight individual handout PDFs into one 18MB class packet for distribution before a lesson. The school's email policy caps outbound attachments at 10MB. Running one medium compression pass on the merged packet brings the file to 7MB, comfortably inside the policy limit. All diagrams, text, and worksheet illustrations remain sharp enough for classroom printing on standard A4 paper without any visible degradation.

Consultant packaging a tender response

A consultant combines a cover letter, 40-page technical proposal, 12-page case study appendix, and fee schedule into a single 55MB PDF for upload to an e-procurement portal with a 25MB submission limit. Merging first produces a single coherent document with consistent pagination, and a medium compression pass on the merged file brings the size to 19MB, well within the portal limit. The tender is submitted on time without splitting the response across multiple uploads, which would have been a procurement compliance issue.

Pro tips

Get better results with these expert suggestions:

Run one medium compression pass rather than multiple aggressive passes

Running the compressor twice on an already-compressed PDF provides diminishing returns on size reduction but causes progressive quality loss because each pass introduces a small amount of new artifact data. One well-chosen compression level is always better than two sequential compressions. If medium compression does not get you below your target size, run high compression once on the original merged file rather than running medium twice in succession on the same content.

Check file size immediately after merging to plan your compression level

If the merged PDF is under 15MB and your target is under 10MB, medium compression will almost certainly get you there with no visible quality change. If the merge is 80MB and your target is 10MB, you need high compression and should expect some softening on image-heavy pages. Setting expectations from the file size before you compress avoids the trial-and-error loop of trying medium first, finding it insufficient, and then having to redo the compression at a higher level.

Keep a copy of the uncompressed merged PDF

Before compressing, save the merged-but-uncompressed PDF to your device as an archive copy. If the compressed output is too small with poor quality or too large because not enough was removed, you can go back to the clean merged file and try a different compression level without having to re-merge from scratch. This is especially valuable when your merge session involved many large files because re-merging takes far longer than a fresh compression pass on an existing combined file.

For print-ready documents, never use high compression

High compression reduces embedded image resolution to around 96 to 150 DPI, which looks acceptable on a phone or laptop screen but prints with visible pixelation on anything larger than A5. For documents that will be printed professionally on A4 or larger paper, use medium or low compression only and accept the larger file size. The visible difference on printed output between medium and high compression is the difference between a polished deliverable and a document that looks like it was produced in a hurry.

FAQ

Frequently asked questions

Currently the merge and compress operations live in separate tools on FixTools, which actually gives you more control over the final result because you can choose a different compression level depending on what your merged file turned out to look like. After merging, click through to the PDF Compressor and run the combined file through compression. Both tools are free, require no sign-up, and the complete two-step workflow takes under three minutes for most documents. The split also lets you reuse the uncompressed merged file later if you need a higher-quality copy.

Typical reduction is 20 to 80 percent depending on content composition. PDFs with many embedded images compress the most because images are usually the largest objects in a PDF. A 50MB photo-heavy merged file often compresses to 10 to 15MB at high compression. Text-only or vector-heavy PDFs compress less because there is less redundancy to remove. A 10MB text-only report may reduce to 6 or 7MB at medium compression, which is still a meaningful saving for the cost of one quick processing pass.

For standard office documents and business reports, medium compression is essentially invisible at normal viewing zoom. Text remains sharp because it is stored as glyph references rather than rasterised pixels, vector graphics stay crisp because they are mathematical descriptions rather than images, and embedded logos show no visible change. Embedded images may reduce slightly in resolution at high compression, though this is usually only noticeable when zoomed in past 200 percent or when printing at full A4 size. At normal screen viewing the difference is invisible.

For email, aim for under 8MB to clear most corporate mail servers in one shot, under 20MB for personal Outlook accounts, and under 25MB for personal Gmail. For WhatsApp documents the limit is 100MB so almost any merged PDF is fine. Slack and Microsoft Teams generally allow 25MB on most plans. Google Drive and Dropbox have no practical size limit for storage uploads, so if you are sharing a link rather than an attachment the size becomes much less important. For specific portal submissions, always check the stated limit before compressing.

If you compress after merging the compressor applies a single uniform setting to every page in the document. If the merged content includes both high-detail image pages and simple text pages, the high-detail pages may look softer than they would if you had compressed them individually with content-tuned settings. To address this on a critical document, split the merged file into image-heavy and text-only sections using the Splitter, compress each section separately at the appropriate level, then re-merge. For most everyday work the uniform compression is more convenient and produces acceptable results.

For memory management purposes, yes. Compressing very large source files of 80MB or more before merging reduces the browser memory required for the merge session itself and lowers the risk of a tab crash mid-operation. For final quality and file size results, merging first and compressing once still produces the most consistent output. The full workflow for very large jobs becomes compress-large-sources, merge everything together, then run a final consistency compression on the combined file. For normal-sized documents just merge first then compress.

Yes. The PDF Compressor on FixTools is completely free with no usage limits, no watermarks added to the compressed output, and no sign-up required. Both tools, merger and compressor, are free and process files locally in your browser, which means neither tool sees your file content and neither has any technical means to limit you based on file count or usage history. The same business model that supports the merger supports the compressor, so the experience is consistent across the two steps of the workflow.

Yes. The compressor produces standard PDF files compatible with every modern PDF reader including Adobe Reader, Preview on Mac, the built-in PDF viewer in Chrome and Edge, mobile PDF apps on iOS and Android, and any web-based viewer. The compression does not introduce any proprietary extensions or non-standard structures, it simply re-encodes embedded images and removes redundant objects within the standard PDF format. Compressed files open and render identically to uncompressed files except for the slight visual softening on heavily compressed images.

Yes. Both the merger and the compressor work in mobile browsers on iOS and Android. The workflow is the same as on desktop: merge in the browser, download the result, then upload to the compressor and run a compression pass. Mobile devices have less RAM than desktops so very large sessions over 100MB may struggle on older phones, but for typical email-sized merges of 10 to 30MB the full merge-then-compress flow works smoothly on any modern phone or tablet.

Yes. External hyperlinks that point to URLs are preserved through both the merge and compression steps and remain clickable in the final output. Internal cross-document hyperlinks, where a link in one source file pointed to a specific page in another source file, will not work in the merged output because the target pages now have new page numbers in the combined document. This is a limitation of any merge operation, not specific to FixTools. If you need internal links to work after merging, they have to be re-created in a PDF editor.