Free · Fast · Privacy-first

Merge Two PDF Files Into One

Merging two PDF files is the single most common PDF task.

⚡

Combine two PDFs in under a minute

🔒

Clean output, no watermarks

✨

No sign-up or account needed

⚡

Files stay private in your browser

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.

What happens technically when you join two PDF files

Joining two PDFs creates a new document whose page sequence is the complete set of pages from file A followed by the complete set of pages from file B. At the PDF structure level, the merged file contains a new cross-reference table that indexes all page objects from both source files, a new page tree root that references both page sequences in order, and copies of all content streams, fonts, images, and resources from both originals embedded into the combined output. The result is a self-contained PDF with no dependency on the source files. If you delete the two originals after merging, the combined file remains complete and fully functional because nothing in the output references back to the source files.

File B does not simply get appended to the end of file A by concatenating byte streams. The PDF Merger creates an entirely new PDF document and populates it by copying all the internal objects from both source files into the new structure. This matters because it means the merged output avoids potential conflicts between the two sources. If both files use an internal object numbered as 5, which is common in PDFs generated by the same producing software, the merger re-numbers objects in the output to avoid collisions in the new combined object graph. This object renumbering is transparent and never visible to a user reading the file, but it is why the merged output is slightly larger than the simple sum of both source file sizes due to the new structural overhead.

For the simplest two-file merge, the only decision you need to make is the order in which the two files should appear in the output. Should file A's pages come first, or file B's? The answer depends on the use case. For a report with an appendix, the report goes first and the appendix follows. For a signed cover letter to be attached to a resume, the cover letter goes first and the resume follows. For scanned pages that were accidentally captured in reverse capture order by a scanner that fed sheets last to first, put the second file first to restore correct reading order. The merge tool lets you flip the order by dragging the two file cards at any point before clicking Merge.

After the merge, the combined file inherits the structural characteristics of both sources mixed together. The output will be a PDF version equal to the higher of the two source versions, which is usually PDF 1.7 in current files. The output's embedded fonts will include the union of fonts from both sources, with any duplicates removed by the merger to save space. The output's image quality will match the source quality exactly because no re-encoding occurs during the merge. The combined file is functionally indistinguishable from a single PDF that had been authored containing all the same pages from the start, which is the goal of a good merge operation.

ISO 32000 PDF standard PDF cross-reference table specification

How to use this tool

💡

Upload two PDF files, check the order (drag to swap if needed), and click Merge. Your combined file downloads immediately.

How It Works

Step-by-step guide to merge two pdf files into one:

1
Open the PDF Merger
Go to fixtools.io/pdf/pdf-merger in your browser. The page loads in a couple of seconds and presents the merger interface ready for files. No sign-up step appears, no account creation prompts you, and no upsell modal interrupts the workflow. The tool is immediately ready for your two-file merge on first visit and on every subsequent visit thereafter.
2
Upload your two PDF files
Click Upload and select both files from the file picker, or drag both files onto the page from your file manager. You can upload them together in one selection or one at a time as you locate them in different folders on your device. The files load into your browser tab without going to any server during upload, which keeps your documents private throughout the merge.
3
Set which file comes first
Drag the file cards so the file whose pages should appear first in the combined output is at the top of the list. The merged PDF will contain all pages from the top file followed by all pages from the second file in that exact order. Visual confirmation of the order takes a couple of seconds and prevents the need to re-merge after discovering the sequence was wrong.
4
Merge and download
Click Merge PDF. The browser combines the two files in seconds for typical sizes and presents a download link for the merged output. Download the file and rename it from the default merged.pdf to something descriptive that reflects its content before sharing with anyone else. A descriptive name helps recipients identify the file and helps you find it later.
5
Verify the result
Open the downloaded merged PDF in any PDF reader and check that the total page count equals the sum of pages from both source files, that the first page is the expected first content, and that the boundary between the two sources occurs at the right point in the sequence. A thirty-second verification step catches anything unexpected before the file leaves your hands for downstream use.

Real-world examples

Common situations where this approach makes a real difference:

Attaching a signed cover letter to a resume

A job applicant has a signed cover letter as a one-page PDF and a two-page resume as a separate PDF. The employer's application portal requires one PDF upload per applicant and rejects multi-file submissions. Merging the cover letter as the top file and the resume as the second file produces a three-page application PDF in the conventional cover-first order. The whole operation takes under 30 seconds and requires no account on any service, which lets the applicant submit before the portal deadline without scrambling for paid software.

Adding a signed signature page to a contract

A solicitor receives a signed final page of a contract as a separate scan PDF from the client and needs to rejoin it with the main contract body to produce the executed version. Merging the 18-page contract body as the top file and the 1-page signed scan as the second file produces the complete 19-page executed contract in correct page order. The merged file is then emailed to all parties as the canonical executed copy for their records.

Joining a report and its appendix

A consultant produces a 15-page main report and a 12-page data appendix as separate PDFs during the drafting phase because they were written in different tools. Before sending to the client, they merge both into one 27-page deliverable with the report first and the appendix following. The merged file becomes the final deliverable that the client archives, rather than two separate source files that might get separated or filed differently in the client's system over time.

Combining two-sided scan output from a single-pass scanner

A single-sided scanner produces two files when scanning a double-sided document, one for the front faces of all sheets and one for the back faces. For a 10-page document that is a 5-page odd PDF and a 5-page even PDF. Simple two-file merging places all odd pages first followed by all even pages, which is not the correct reading order. For correct reading order, the interleave workflow is needed instead, but for some archival uses the simple two-file merge is sufficient if the recipient understands the structure.

Pro tips

Get better results with these expert suggestions:

Verify which file has the lower first page number before uploading

If your two PDFs are parts of a single numbered document, for example pages 1 to 10 in one file and pages 11 to 20 in another, confirm that the first-part PDF is uploaded as the top file before merging. The merged PDF will present both files' pages in the upload order shown in the merger cards, so getting this right before merging avoids the need to re-merge after discovering the document reads in the wrong sequence in the output.

Check the merged page count immediately after downloading

After merging, open the file and check the total page count shown in your PDF reader's status bar. The total should equal the combined page counts of both source files added together. If the total is higher than expected, one of the source files had trailing blank pages that you can strip out with the Splitter before re-merging. If the total is lower, something went wrong during the merge that warrants re-running the operation.

Drag to reorder before merging rather than re-uploading

If you upload file B before file A by mistake, just drag the file cards to swap their order in the merger interface. You do not need to clear all files and start the upload again from scratch. The drag handle on each card lets you move it above or below the other file in one gesture, which corrects the order in seconds without any re-upload required.

For a cleaner cover-page join, make sure the cover page PDF has no trailing blank page

Documents exported from Microsoft Word sometimes add a blank final page caused by a leftover paragraph mark in the source document. If your cover letter is two pages long but the second page is blank, the merged PDF will show an unwanted blank page between the cover letter and the main document body. Use the Splitter to extract only the first non-blank page of the cover before merging, which produces a clean transition between cover and body in the output.

FAQ

Frequently asked questions

Open the FixTools PDF Merger in any browser, upload both PDF files by selecting them in the file picker or dragging them onto the page, drag the cards so the file whose pages should appear first is at the top of the list, and click Merge PDF. Download the resulting combined file and rename it from the default merged.pdf to something descriptive before sharing. The entire process takes under 60 seconds for typical file sizes and requires no account, no payment, and no software installation.

Yes. The merger shows your uploaded files as draggable cards in a vertical list. Drag the cards so the file whose pages should appear first is at the top of the list and the file whose pages should appear second is below it. When you click Merge, the pages from the top file appear before the pages from the second file in the output document. Reordering takes a moment and gives you full control over the sequence without needing to re-upload anything.

No. The merger copies all page content from both files into the combined output without re-encoding images, re-rasterising vector graphics, or altering text streams. The merged output is the same quality as both originals at the page-content level, with fonts rendering identically, images at the same resolution, and any embedded interactive elements transferring cleanly. Quality only changes if you subsequently compress the merged file through the PDF Compressor, which is a separate optional step under your control.

Password-protected PDFs must be unlocked before merging because the merge operation needs to read the source file's page content streams and password protection blocks that access. Use the FixTools Unlock PDF tool to remove the password from the protected file, which also runs locally in your browser, then include the unlocked file in your merge alongside the unprotected one. Both files must be readable for the merge to complete successfully and produce a valid combined output.

There is no enforced size limit because the merge runs in your browser without uploading files to a server. The practical constraint is your browser's available memory. Two files totalling under 300MB merge reliably on most desktop browsers. For very large files of 100MB or more each, close other browser tabs to free memory and consider compressing each source first to reduce the per-session memory load. On mobile devices the practical limit is lower, typically supporting two-file sessions up to about 100MB total.

Yes. File sizes and page counts do not need to match between the two sources for a successful merge. A single-page PDF merged with a 50-page PDF produces a 51-page output document. The one-page file can be placed first or second in the order using the drag handle, depending on whether it functions as a cover, an insert, or a signature page. This pattern is common for adding a one-page cover letter to a longer body document or appending a single signature page to a multi-page contract.

The merged PDF is a new document with its own file structure including a new header, a new cross-reference table, and a new trailer at the end of the file. This structural overhead adds a small amount of data, typically a few kilobytes to a few hundred kilobytes depending on the complexity of the source files, regardless of how large the actual content is. For documents under 20MB total the overhead is negligible. For very large merges the percentage overhead becomes even smaller relative to the content.

Yes. PDFs exported from Microsoft Word, Google Docs, Adobe InDesign, Acrobat Pro, scanners and multifunction printers, browser print-to-PDF, mobile scan apps, and any other PDF-generating application all conform to the same underlying PDF file format defined in the ISO 32000 specification. The merger handles any combination of sources without compatibility issues, because the file format is standardised even though the producing applications vary widely in features and rendering choices.

The original source files are not modified by the merge operation. They remain on your device exactly as they were before, so if the merged output is not what you wanted you simply discard it and re-run the merge with corrected order or different source files. There is no permanent change to undo because nothing was overwritten. This is one of the safety benefits of the merger producing a new file rather than modifying any of the inputs in place.

Form fields are generally preserved through the merge because they are stored as part of the page object structure that gets copied into the combined output. Filled-in form data may carry through if the fields were saved with values in the source files. For documents with complex form logic spanning multiple pages, verify after merging that the form behaves correctly in the combined file. For critical form submissions, complete the form in the original source file rather than in the merged version to avoid any subtle structural issues.