{{ summaryHeading }}
{{ summaryMetric }}
{{ summaryLine }}
Local merge {{ 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
{{ pdfArtifactTitle }}
{{ pdfArtifactNote }}
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
PDF Splitter Split one PDF in your browser into page ranges, one-page files, or fixed packets with overlap checks, a manifest, and ZIP output.
PDF Page Numberer Add page numbers to a PDF in your browser, choose ranges and label styles, then check placement coordinates before downloading.
PDF Compressor Compress a PDF in your browser with a local rewrite, production-size estimates, and warnings for image-heavy, encrypted, or oversized files.
PDF Page Deleter Delete PDF pages in your browser, verify source-to-output renumbering, catch range or fidelity warnings, and download a cleaned copy.
Customize
Advanced
:

Most document packets are assembled from pieces. A contract may have a cover sheet, signature pages, schedules, and invoices. A records request may include scans from different offices. A school or court filing may need a main form followed by exhibits. Merging PDFs is the page-sequencing job that turns those separate files into one continuous document.

The sequence matters because PDF readers present the combined document from the first copied page to the last copied page. A missing source changes the page total. A source in the wrong position can put an exhibit before the document that explains it. A file that looks like a PDF but cannot be parsed can leave the packet incomplete unless the skipped-file warning is noticed.

PDF merging is different from attaching files inside a wrapper. A PDF portfolio can hold several separate files together, while a normal merged PDF creates one reading order. It is also different from compression, redaction, page deletion, and page extraction. Those jobs change size, content, confidentiality, or page membership. A merge should be used when every accepted source page belongs in the final packet and the main decision is order.

Source PDF
An original PDF whose pages are copied into the combined document.
Merge queue
The ordered list of accepted PDFs that controls the final page sequence.
Page total
The sum of pages from the accepted sources, useful as a quick completeness check.
Document info
Basic PDF metadata such as a title; it does not prove the page content or legal status of the file.
Ordered PDFs copied into one combined document Three source PDFs are arranged in order, then copied into one combined PDF with the page total checked against the source pages. Cover Main PDF Exhibits 2 pages 18 pages 4 pages Combined PDF 2 + 18 + 4 = 24 pages

Good merge preparation starts before the download. Check that each source opens, remove pages that do not belong, put cover material and exhibits where the reader expects them, and compare the final page total with the source packet. The page total is a useful check, but it cannot prove that the pages are visually correct, signed, accessible, redacted, or acceptable for a regulated filing.

Some PDF features need a separate review after the merge. Bookmarks, page labels, forms, digital signatures, attachments, accessibility tags, and archival requirements can behave differently from plain page content. A combined PDF may be ready for ordinary reading while still needing inspection in a full PDF reader before print production, records retention, legal filing, or public release.

How to Use This Tool:

Create the queue, confirm the order, then merge only after the page totals and warnings match the packet you intended to build.

  1. Choose or drop two or more files in PDF files. Accepted PDFs appear in the queue with their file names, sizes, and page counts.
  2. Read any warning shown above the queue. Unsupported file types, missing PDF headers, parse failures, empty PDFs, over-limit files, or excess files can be skipped before they reach the merge.
  3. Use Merge order to move rows up or down. The first row becomes the first pages in the combined PDF, so review the list from top to bottom.
  4. Set Output filename. Unsafe filename characters are cleaned and a PDF extension is added when it is missing.
  5. Open Advanced when the default limits do not match the job. File guard defaults to 20 PDFs and accepts 2 to 50. Browser work limit defaults to 120 MB and accepts 10 MB to 300 MB.
  6. Choose Output metadata if the PDF title matters. The neutral option writes generic merged metadata, and the first-file option uses the first accepted PDF name as the title.
  7. Select Merge PDFs. If the action status says Need two PDFs, File guard exceeded, Work limit exceeded, or PDF engine loads on demand, resolve that condition before relying on the output.
  8. Review Merged PDF, Merge Summary, Merge Queue, and Readiness Checks before downloading or copying results.

Interpreting Results:

The page count is the strongest quick check. Source pages should equal the total pages from the accepted PDFs, and Output page count should match after the merge. A mismatch usually means a source was skipped, removed, unreadable, or outside the queue when the merged file was created.

File size should be read carefully. Output size is the size of a newly saved combined PDF, not a compression score. It can be larger or smaller than the source total because the PDF is rewritten. If the goal is a smaller document, compression is a separate decision.

Result cue What to trust What to verify
Merge order The row order used for the combined page sequence. Check the queue top to bottom before downloading.
Source PDFs The number of accepted PDFs, not necessarily every file originally selected. Compare it with your expected source list and warnings.
Warnings A file, limit, parser result, or readiness condition needs attention. Fix the warning and merge again instead of assuming the packet is complete.
Readiness Checks A compact pre-download review of queue, limits, output, page counts, and privacy path. Use it before download, then spot-check the PDF in a reader.

Technical Details:

PDF is a page-oriented document format with a structured binary body. A normal merge opens each accepted source, copies the pages from that source, appends those copied pages to a new document, writes the selected document title metadata, and saves new PDF bytes. It does not turn the pages into screenshots or inspect the visual content for correctness.

A PDF header check is only an early sanity filter. A file can have the right extension and still fail when parsed because it is encrypted, damaged, malformed, or empty. A readable merge source must parse successfully and report at least one page.

Formula Core:

When every queued source is accepted, the combined page count is the sum of the page counts from the accepted source PDFs in order.

Pcombined = ∑ i=1 n Pi

Here, n is the number of accepted source PDFs, Pi is the page count for each accepted source, and Pcombined is the page count of the merged output. A 2-page cover, 18-page report, and 4-page exhibit should produce a 24-page combined PDF.

Rule Core:

Rule Accepted condition Boundary or failure behavior
Source count At least two accepted PDFs are queued. The merge action stays unavailable until two accepted sources are present.
PDF identity The incoming file has a PDF extension or media type and begins with a PDF header marker. Unsupported or header-mismatched files are skipped with a warning.
Page readability The source parses and reports one or more pages. Encrypted, damaged, malformed, or empty sources are skipped.
File guard The queue stays within the selected cap, from 2 to 50 PDFs. Extra incoming files are ignored, and an over-cap queue cannot merge.
Browser work limit Total accepted source bytes stay within the selected cap, from 10 MB to 300 MB. A file that would push the queue over the cap is skipped, and an oversized queue cannot merge.
Metadata mode The output title uses neutral merged metadata or the first accepted PDF name. Changing the mode clears the prior output so the next download matches the current setting.

The transform path is deterministic. Reordering a source changes where its pages appear. Removing a source changes both the page total and the output bytes. A previous output is no longer valid after queue or metadata changes because it represents the earlier state.

Page copying does not guarantee that every higher-level PDF feature survives with the same meaning. Bookmarks, page labels, form-field relationships, signatures, attachments, tagged structure, and long-term preservation requirements should be checked separately when they matter.

Privacy Notes:

The selected source PDFs are read and merged in the browser session. The PDF engine may need to load before the first merge, but the merge action does not upload the selected PDF files to a server.

  • Use the Privacy readiness check to confirm the local processing path.
  • Handle client, legal, medical, regulated, or confidential files only on a device and browser session you are allowed to use.
  • Clear the queue or close the tab when finished on a shared computer.

Worked Examples:

Meeting packet. A 2-page agenda, 18-page report, and 4-page appendix are loaded in that order. Source PDFs should show 3, Source pages should show 24, and Merge order should begin with the agenda. The downloaded Output page count should also be 24.

File guard boundary. A clerk selects 21 small PDFs while File guard is still 20. One incoming file is ignored after the cap is reached. Raise the guard in Advanced only if all 21 sources belong in one packet, then reload the missing source and merge again.

Large scan packet. A 92 MB scan and a 44 MB exhibit exceed the default 120 MB Browser work limit. Reduce the batch, compress the scans first, or raise the limit on a device that can handle the memory load.

Unreadable source. A file named financials.pdf has a PDF-looking name but cannot be parsed. It is skipped, Source PDFs stays lower than expected, and Warnings names the failure. Load a readable copy and check Source pages before merging.

FAQ:

Do my PDFs get uploaded?

No. The selected source files are read in the browser session, and the merged PDF is created there.

Can I merge only selected pages?

No. Every page from each accepted source PDF is copied. Split or delete pages in another workflow before loading the source here.

Why was a file skipped?

Common causes include unsupported type, missing PDF header, too many queued files, source bytes over the current limit, no pages, password protection, or parse failure.

Will the merged file be smaller?

Not necessarily. The output is a newly saved combined PDF, not a compression result. Check Output size after merging.

Will bookmarks, forms, or signatures still work?

Do not assume they will. Page content is copied, but bookmarks, form behavior, signatures, attachments, and accessibility tags should be checked in a PDF reader when they matter.

Glossary:

Source PDF
An accepted original PDF whose pages are copied into the combined document.
Merge queue
The ordered list of accepted PDFs that controls the final page sequence.
PDF header
An opening marker that helps identify a PDF before deeper parsing.
Output metadata
Document information written into the new file, such as the merged PDF title.
Browser work limit
The source-size cap used to protect one browser tab from an oversized local merge run.
Combined PDF
The newly saved PDF containing copied pages from all accepted sources.

References: