{{ summaryHeading }}
{{ summaryMetric }}
{{ summaryLine }}
Disabled {{ engineBadge }} {{ fileCountLabel }} {{ totalSizeLabel }}
{{ message }}
Drop or browse PDFs, then adjust the merge order before downloading the combined file.
{{ dropzoneTitle }}
{{ dropzoneHint }}
Ignored {{ ignoredFileCount }} unsupported or excess file(s).
Name the merged PDF before downloading it.
Merge order:
Order PDF file Pages Size Controls
{{ index + 1 }} {{ entry.name }} {{ entry.pageCount }} {{ formatBytes(entry.size) }}
{{ actionStatusLabel }}
{{ actionHint }}
Choose how document info fields are written into the merged PDF.
Accepted range: 2-50 PDFs per merge queue.
files
Total source size cap for one local merge run.
MB
Field Value Copy
{{ row.field }} {{ row.value }}
Order Source file Pages Size Status Copy
Add two or more PDFs to build the merge queue.
{{ row.order }} {{ row.name }} {{ row.pages }} {{ row.size }} {{ row.status }}
Check Status Detail Copy
{{ row.check }} {{ row.status }} {{ row.detail }}
Tags: File Tools, Productivity
Export to PDF Fullscreen
Customize
Advanced
:

PDF merging takes separate page-oriented documents and assembles their pages into one new file. It is common for reports, exhibits, scanned forms, signed cover sheets, application packets, and appendix material that need to travel as a single attachment or be reviewed in one reading order.

The useful question is not only whether the files can be combined. The order of the pages has to match the way someone will read, cite, print, or archive the packet. A cover letter placed after the appendix, or a revised attachment inserted before the wrong section, can make the combined PDF harder to trust than the separate files it replaced.

Three source PDF files copied into one merged PDF in the selected order

A merge is also not a full document audit. The page images and page content may appear correct while bookmarks, document metadata, form behavior, accessibility tags, signatures, or attachment relationships still need checking in a PDF reader. Treat the merged file as a new document that deserves a quick review before it is sent, filed, or printed.

Technical Details:

PDF is a structured, page-oriented format. A basic merge creates a new PDF and appends copied pages from each accepted source document. The first source in the queue contributes the first pages, the second source follows, and the same pattern continues until every queued page has been copied.

The page count is the simplest integrity check for this kind of merge. If a two-page cover packet is followed by a 12-page report and a 4-page appendix, the merged output should contain 18 pages in that exact order. A different count means a file was skipped, the queue changed, or the source could not be parsed as expected.

File recognition starts with ordinary PDF signals. A source file needs a PDF extension or PDF media type, then its bytes must begin with the PDF header marker. After that, the document must be parseable and contain at least one page. Encrypted, damaged, empty, or disguised files are skipped and reported as warnings rather than silently becoming part of the merged output.

Stage What happens What to verify
Source acceptance Files are accepted when they look like PDFs by name or media type and begin with the PDF header marker. Skipped files appear in warnings and do not increase Source PDFs.
Page reading Each accepted source is parsed to count pages before it is added to the queue. Source pages should match the packet you expect to assemble.
Queue ordering All pages from each source are copied into a new PDF in the visible row order. Merge order should list the files in the intended reading sequence.
Output writing The new PDF receives a sanitized output name and either neutral document metadata or a title based on the first source name. Output filename, Output metadata, and Output size should fit the handoff.

Browser memory is the main practical limit. The source bytes have to be read, parsed, copied, and saved in the same browser session, so a merge run can temporarily use more memory than the final file size suggests. The file guard and browser work limit protect the tab from oversized batches.

Rule Current behavior Result when it fails
Minimum source count At least two queued PDFs are required. Need two PDFs appears and the merge action stays unavailable.
File guard The default cap is 20 PDFs, adjustable from 2 to 50. Excess incoming files are ignored, or an over-cap queue reports File guard exceeded.
Browser work limit The default source-size cap is 120 MB, adjustable from 10 MB to 300 MB. Files that would exceed the cap are skipped, or the queue reports Work limit exceeded.
Parse readiness The PDF writing component must load before reading or merging can run. PDF engine unavailable appears with a reload cue.
Output page count The merged page count should equal the sum of loaded source page counts. A mismatch needs review before the downloaded PDF is trusted.

Everyday Use & Decision Guide:

Start with the smallest complete packet. Add the cover, main document, and appendices in the order readers should see them, then use the arrow controls in Merge order until the queue reads correctly from top to bottom. The merge does not sort by filename, date, or document title.

For ordinary office packets, keep the default File guard at 20 and the Browser work limit at 120 MB. Raise them only when the browser and device can comfortably handle a larger batch. If a source group is very large, splitting the work into smaller packets usually gives clearer warnings and easier review.

Use Output filename before merging, especially when the result will be sent to someone else. Unsafe characters are replaced and a PDF extension is added when needed. Use Output metadata when the document title matters in a reader or document-management system; neutral metadata avoids carrying over a source title, while the first-file option uses the first queued PDF name as the merged title.

  • Check Merge Queue for file names, page counts, sizes, and loaded status before running the merge.
  • Use Readiness Checks when a button is unavailable or a warning appears; it names the failing condition directly.
  • Use Merge Summary after merging to compare Source PDFs, Source pages, Output size, and Merge order.
  • Open the downloaded PDF and scan the first page, the transition between each source file, and the final page before relying on the packet.

A ready status means the browser produced a new PDF, not that the merged packet is legally signed, accessible, compressed, bookmarked, or approved for release. Keep any formal review step that your document workflow already requires.

Step-by-Step Guide:

Use the file picker, visible queue, guard settings, and result tabs as a short merge review path.

  1. Choose PDF files with Browse PDFs or drop files into the upload area. The summary should move from Add PDFs to a queued-page count after files are read.
  2. Review any warning above the file picker. Unsupported, excess, empty, encrypted, damaged, or over-limit files are skipped and do not appear as loaded rows in Merge Queue.
  3. Use the up, down, and remove controls in Merge order until the first row is the first pages in the final PDF and the final row is the last section.
  4. Set Output filename. Open Advanced if you need a different Output metadata mode, File guard, or Browser work limit.
  5. Click Merge PDFs. If the action label reports Need two PDFs, File guard exceeded, Work limit exceeded, or PDF engine unavailable, fix that condition and try again.
  6. When the summary reads Merged PDF Ready, use Download PDF. Then open Merge Summary and Readiness Checks to confirm the page count, output name, source size, and local privacy path.
  7. Open the downloaded PDF in a reader and spot-check source transitions, page count, and title metadata before sending or archiving it.

The strongest handoff is a downloaded PDF whose visible pages, queue order, summary values, and readiness checks all match the packet you meant to assemble.

Interpreting Results:

Source pages and Output page count should tell the same story. For a normal successful merge, the output page count equals the total pages loaded from the queue. If a file was skipped during reading, it will not be included in either number.

Merge order is the result field to trust for sequence. A correct output name and successful status do not prove the packet order is right. Read the row list from left to right or top to bottom before downloading, then inspect the downloaded PDF around each source transition.

  • Generated locally and ready to download means the new PDF was written in the browser session.
  • Within cap for File guard means the queue count is less than or equal to the current guard value.
  • Within cap for Browser work limit means total queued source bytes are less than or equal to the current MB limit.
  • Warnings means at least one skipped file, missing engine, over-cap queue, or over-limit size needs review before relying on the output.
  • Merged PDF Ready does not prove signatures, bookmarks, form behavior, or accessibility structure survived in the way your workflow requires.

Worked Examples:

A contract packet has cover.pdf with 2 pages, agreement.pdf with 18 pages, and exhibit-a.pdf with 4 pages. After those rows are ordered cover, agreement, exhibit, Source PDFs should read 3, Source pages should read 24, and the downloaded PDF should begin with the cover and end with the exhibit.

A reviewer loads 22 small PDFs while File guard is still 20. Two incoming files are ignored, the queue contains 20 rows, and a warning reports unsupported or excess files. The corrective path is to raise the guard in Advanced if a 22-file packet is intentional, or split the work into two merged PDFs and review both outputs separately.

A 90 MB scan and a 45 MB appendix exceed the default 120 MB Browser work limit when loaded together. The second file is skipped or the queue reports Work limit exceeded. Reduce the queue, raise the limit only on a capable desktop browser, or compress the source documents with a separate workflow before merging.

A password-protected source named financials.pdf looks like a PDF but cannot be parsed. The warning names the skipped file, Source PDFs stays below the expected count, and Merge order lacks that document. Remove the password with an approved PDF workflow, load the readable copy, and confirm the page count before merging again.

FAQ:

Why is the Merge PDFs button unavailable?

The action needs a loaded PDF writing component, at least two queued PDFs, no more files than the current File guard, and total source bytes within the Browser work limit.

Can I choose only certain pages from each PDF?

No. The merge copies all pages from each loaded PDF in queue order. Remove pages or create smaller source PDFs in a separate workflow before loading them here.

Do the PDFs leave my browser?

The source and merged PDF bytes stay inside the browser session. The readiness table reports the privacy path as local, and this merge workflow does not use a backend helper.

Can encrypted PDFs be merged?

Encrypted or otherwise unparseable PDFs are skipped with a warning. Use a readable source copy, then check Source PDFs and Source pages before merging.

Will merging reduce the file size?

No compression control is provided. The output size can be smaller or larger than the total source size depending on how the new PDF is written, so use Output size as the actual value.

Glossary:

PDF header
The opening byte marker that helps identify a file as a PDF before parsing.
Merge queue
The ordered list of loaded source PDFs whose pages will be copied into the new document.
Source page
A page from one of the loaded PDFs before it is copied into the merged output.
Output metadata
Document title information written into the newly created PDF.
Browser work limit
The total source-size cap used to avoid oversized merge work in one browser session.

References: