Sycago
All toolsReport an issue ↗

PDF tools / FREE ONLINE TOOL

Merge PDF

Combine unencrypted PDF documents in a chosen file order into one downloadable PDF.

No signupNo API keysLocal processing

YOUR WORKSPACE

Merge PDF

How to use ↓

Add your files

Drop files here, or choose from your device.

Unencrypted PDF · 25 MB per file · 100 MB total
Up to 20 files · Device memory may impose lower limits.

Ready. Your inputs stay in this tool's browser session.

Sycago Merge PDF combines unencrypted PDF documents into one downloadable file. Put the files in the order you want readers to encounter them, check that every source belongs in the packet, and create a merged copy in your browser. The pages from each file follow that file's existing internal sequence. This makes merging useful for reports with appendices, meeting packs, application materials, and collections of related records. The most important work happens before the button press: establish the intended sequence, confirm the correct versions, and know which document features need checking after the merge.

Plan one coherent document

A merged PDF should give the reader a clear route through the material. A common structure is a short introduction, the main report, supporting evidence, and appendices. Another is chronological: earliest record first, followed by later updates. Choose the structure that supports the reader's task, then write down the intended file order. This small plan prevents a packet from becoming a collection of unrelated documents simply because they happened to be selected together.

Merging is appropriate when each source already has the right pages in the right order. It combines documents rather than rewriting their contents. If one source includes a draft page, a duplicate scan, or an appendix that should not be shared, prepare a suitable copy first using the relevant page workflow. The merge queue is a file-level sequence. It is not an editor for rearranging individual pages scattered across several documents.

Consider whether a single PDF will actually help the recipient. One packet reduces the number of downloads and can make printing easier, but it also combines everything into a shared artifact. If different readers need different subsets, create deliberate separate packets. A filename such as project-review-with-appendices.pdf gives more useful context than combined-final-new.pdf, especially when recipients receive several updates over time.

Check the source documents before selecting them

Open each source PDF and confirm its version, page count, orientation, and visible content. A similarly named draft can easily enter a queue beside the approved document. Check the first and last pages of each file, then inspect any pages known to have changed. If the source came from a scanner, look for blank reverse sides, missing edges, or pages captured upside down. These issues are easier to identify before several documents become one long packet.

Only unencrypted PDFs are supported. Password protected documents cannot be merged here, and the tool does not remove encryption or bypass restrictions. Obtain an authorized unencrypted export from the document owner or source application if that is appropriate. A damaged PDF may also fail to open or copy correctly. Recreate the export where possible instead of assuming a different filename will fix the underlying structure.

Each PDF may be up to 25 MB. The queue accepts up to 20 files with a combined input size of 100 MB, and PDF operations are limited to 400 total source pages. Calculate the total before starting a large packet. A group of small files can exceed the page limit, while a few image-heavy files can exceed the byte limit. Both constraints matter independently.

Merge in six careful steps

  1. Add the unencrypted PDF files that belong in the packet.
  2. Compare each filename and page count with your planned source list.
  3. Move files in the queue until the sequence is correct.
  4. Run the merge and wait for the new PDF to become available.
  5. Download it using a clear versioned filename.
  6. Open the downloaded copy and inspect the page boundaries and important content.

Do not rely on the order in which files appeared in the system file picker. It may be sorting by modification date or name, and the selection gesture may not match the narrative order you intended. Review the visible queue after adding files. In a packet containing a cover, a report, and two appendices, explicitly place the cover first and the appendices in the sequence referenced by the report.

Check the merged result rather than assuming that a completed progress indicator proves the document is ready to send. The download is a new artifact with its own filename and storage location. Opening it also protects against a common practical error: sharing a previous attempt from the download folder. Keep only clearly distinguished versions or move the reviewed copy into the folder from which you intend to distribute it.

Understand file order and page order

The merge sequence has two levels. First, the queue determines which source file comes first, second, and so on. Second, the pages inside each source keep their existing sequence. If file A has four pages and file B has three, placing A before B produces A's four pages followed by B's three pages. Moving file B above A moves the entire three page document, not just its opening page.

Queue itemSource lengthPosition in the merged document
Cover and introduction2 pagesPages 1-2
Main report8 pagesPages 3-10
Appendix A3 pagesPages 11-13
Appendix B2 pagesPages 14-15

This mapping is useful when checking boundaries. Inspect pages 2 and 3, 10 and 11, and 13 and 14 because those are where one source ends and another begins. A missing source or accidental duplicate becomes obvious at these transitions. If you need alternating pages from two files, prepare that arrangement with a page reordering workflow after merging, rather than expecting the file queue to interleave pages automatically.

Worked example: a monthly review packet

Suppose a team has four PDFs for a monthly review: a two page agenda, a nine page performance report, a four page budget appendix, and a three page action register. The intended packet is eighteen pages. Open each source, confirm that the reporting month matches, and note the final page of the report. A report from the previous month might have the same filename pattern but the wrong figures, so version checks are as important as sequence.

Add the four files, then arrange the agenda, report, budget appendix, and action register in that order. Merge and download the result. The expected transitions are agenda to report at pages 2-3, report to budget at pages 11-12, and budget to actions at pages 15-16. Inspect those page pairs and verify the total length of eighteen pages. This targeted review supplements, rather than replaces, a scan through the whole packet.

Next examine any charts, landscape pages, and form-like tables. A source report may contain its own visible numbering starting at one. Those printed numbers remain part of the original page content; merging does not automatically renumber them into one continuous sequence. If the packet needs visible continuous numbers, plan that as a separate operation and place them carefully so they do not cover existing footers.

Worked example: records from different sources

Imagine assembling a maintenance history from a service invoice, a scanned inspection sheet, and a two page repair report. Their page sizes differ, and the scan is in landscape orientation. A merge can keep them together without requiring every source to be rebuilt in the same application. Arrange them by event date if chronology is the main reading task, or place a summary first if a reviewer needs context before reading the evidence.

Check the scan before merging because its defects will follow it into the packet. A sideways scan can be corrected in a rotation workflow; an unnecessary blank reverse side can be removed in a separate prepared copy. Keep the original record files untouched. If evidence handling matters in your process, record which source versions were used and retain the originals according to your existing procedures.

After merging, review the document at a normal reading zoom. Different page dimensions can make some pages look smaller in a continuous viewer even when their content has not been deliberately resized. Printing may also apply the reader's own scaling settings. Test the intended print settings if paper output matters. The merge itself is not a guarantee of uniform paper dimensions, a standard submission layout, or consistent printer behavior.

Review bookmarks, forms, signatures, and navigation

A PDF is more than a stack of visible pages. It can contain bookmarks, interactive fields, document metadata, attachments, internal destinations, and digital signatures. A page-copying merge should not be assumed to preserve every document-level feature from every source. The practical contract is to create a combined page document, then inspect the functions that matter to you. If a feature is essential, keep the original source and verify the merged copy explicitly.

Digital signatures are especially important. Rewriting a PDF generally invalidates existing cryptographic signatures, even if the visible signature graphic remains on a page. Do not use a merged copy as a substitute for signed originals when signature validation is required. Preserve the separately signed files and follow the receiving process's requirements. A visible handwritten or digital signature appearance does not itself demonstrate that the new combined file has a valid cryptographic signature.

Interactive forms and unusual documents may fail to read or behave differently after rewriting. Check filled values, field behavior, links, and page references in the downloaded packet. A contents page can still point to the old source's printed page numbers after other material is placed before it. Consider adding a separate packet overview in the source authoring workflow if readers need navigation that matches the combined physical page positions.

Understand what merging changes and what it leaves to you

Merging does not intentionally rasterize every page into a photograph. Ordinary text and vector page content can remain PDF content when pages are copied. That does not mean every PDF feature is guaranteed to survive unchanged. Inspect the result, especially for documents produced by unusual software or containing complex forms. If the purpose is simply to collect ordinary exported pages, the workflow is much more straightforward than preserving a sophisticated interactive document package.

The tool does not compress PDFs, perform OCR, or convert Word files. If one source is a DOCX document, export an appropriate PDF in its original application before adding it. If a source consists of scanned pages, the merge does not create searchable text. If the resulting file is larger than a recipient allows, make an informed source preparation decision rather than assuming that merging automatically reduces file size.

Check duplication as well as omission. A source may already include its appendix, making a separately added appendix redundant. A report may have an embedded cover that duplicates your packet cover. Compare the planned page count with the finished count, then investigate any discrepancy. The right count alone is not sufficient, because one missing page and one duplicated page can cancel each other numerically while leaving the packet incorrect.

Keep processing and version handling under control

The browser combines the PDF pages locally using bundled functionality; source documents are not sent to an external conversion API. Your device needs enough available memory to load and write the combined document. Browser processing is useful for a direct workflow, but you still control which documents are selected and where the downloaded result is kept. Handle the finished packet according to the sensitivity of all its contents.

Combining files can change the audience for individual pages. A private appendix may have been appropriate as a separately restricted attachment but inappropriate in a packet sent widely. Review every source's purpose and audience before adding it. Neither a new filename nor a single PDF container removes sensitive information. If some pages should be excluded, prepare and verify an appropriate copy before merging.

Keep a simple source checklist when the packet will be updated regularly: source name, version date, page count, and queue position. This helps you recreate the packet and makes updates more reliable. When a single appendix changes, rebuild from the current approved sources instead of repeatedly appending replacements to an old merged PDF. Otherwise outdated pages can remain hidden in an increasingly confusing document.

Troubleshoot a merge systematically

If one file prevents merging, open it separately and confirm that it is unencrypted and structurally readable. Try a small job with that source and one ordinary PDF to isolate the problem. A damaged, encrypted, or highly specialized form document may need a fresh authorized export from its source application. Renaming the file or changing its extension does not repair its internal PDF structure.

If the browser runs slowly, reduce the number of sources and close unrelated demanding tabs. Check the 25 MB per-file limit, 100 MB combined limit, 20 file maximum, and 400 total page maximum independently. Even an allowed job can challenge a limited device. Keep originals and your intended queue order available so a retry does not become a guessing exercise.

If the output sequence is wrong, inspect the queue order first, then the internal order of the relevant source. If pages appear missing, compare source and output counts and inspect file boundaries. If the result contains unexpected duplicates, check whether two source documents overlap. If a form value, signature, or bookmark behaves differently, return to the original document and decide whether a combined page copy is suitable for that use.

Plan section starts when printing matters

A file boundary is not automatically a new physical sheet in a duplex print job. If a five page report is followed immediately by a three page appendix, the appendix begins at physical PDF page 6. With ordinary duplex printing, that can place its opening page on the reverse of the sheet containing the report's final page. Whether this is desirable depends on how the packet will be handled.

Decide on sheet layout before final distribution if each major section must begin on a fresh front side. The merge operation does not interpret your chapter structure or automatically insert blank separator pages to achieve that result. Prepare any intentional separator pages in an appropriate source workflow, include them deliberately in the queue, and count them in the expected total. Avoid treating accidental scanner blanks as reliable layout devices.

Test a short representative print containing one section boundary and a landscape page. Confirm binding direction, page scaling, and the handling of any intentional blanks in the actual print application. Keep a screen reading version distinct if its needs differ from the print packet. A single continuous PDF can support both uses, but the final arrangement should be chosen with the real reading and paper workflow in mind.

Frequently asked questions

How is the merged page order determined?

The file queue determines the order of source documents. Pages within each source follow that document's existing sequence. Move complete files in the queue until the packet reads correctly, then check the transitions between sources in the downloaded result.

Can I merge password protected PDFs?

No. Only unencrypted PDFs are supported. The tool does not accept a password or remove encryption. If you are authorized to create an unencrypted version, obtain one through the source application or document owner before using this merge workflow.

What are the file and page limits?

Each PDF can be up to 25 MB. A job can contain up to 20 files and 100 MB combined, with no more than 400 total source pages. Available browser memory can impose practical limits below these thresholds, especially on constrained devices.

Are source files overwritten?

No. The workflow creates a new merged PDF download. Keep your original documents and use a clear output filename. Retaining the source set also makes it easier to correct a queue mistake or rebuild the packet when a document changes.

Will all pages have the same paper size?

Merging should not be treated as a page-size standardization operation. Source pages can have different dimensions and orientations. Inspect the combined document and test relevant print settings if a consistent paper workflow is important to the people receiving the packet.

Does merging reduce the file size?

This tool does not provide PDF compression. Combining documents can produce a file whose size reflects the source content. If a recipient has a size limit, inspect the actual result and prepare suitable sources through an appropriate separate workflow.

Can I merge Word files directly?

No. This operation accepts PDFs. Export the Word document as a PDF using an appropriate authoring application, inspect that export, and then add it to the queue. The merge does not perform DOCX conversion or edit the underlying document text.

Does a merge create searchable text in scans?

No. Scanned page pictures remain scanned content. This tool does not provide OCR. If searchable text is required, prepare an appropriate text-enabled source through another workflow and verify it before assembling the final packet.

Are existing digital signatures preserved?

Rewriting a PDF generally invalidates cryptographic signatures. A visible signature appearance can remain without providing valid verification for the new combined file. Keep signed originals when signature checking matters and follow the actual requirements of the receiving process.

Will forms and bookmarks work afterward?

Do not assume every document-level feature survives a page merge. Check interactive field values, links, bookmarks, and navigation in the downloaded result. Specialized forms or damaged documents may fail or behave differently, so retain the original sources for reference.

Can I alternate pages from two documents?

The merge queue moves whole files, so it does not automatically interleave their pages. You can first combine the sources, then use a suitable page reordering workflow to establish the complete sequence, checking page positions carefully against the merged document.

Can I remove an unwanted page while merging?

Prepare a source copy without that page using an appropriate page deletion or extraction workflow, then merge the prepared copy. This keeps the merge queue focused on file order. Confirm that the revised source contains all required pages before assembling the packet.

Are PDFs sent to an external conversion service?

The merge runs in your browser without an external conversion API receiving the documents. Your device handles loading and writing. Still inspect all source content and manage the downloaded combined document according to the sensitivity of everything included.

Why is my contents page no longer accurate?

A contents page may refer to printed numbering within its original document. Adding earlier files shifts physical positions in the combined PDF. Merging does not automatically rewrite that visible contents text. Prepare updated navigation in the authoring workflow if the packet requires it.

What should I do if one PDF fails?

Confirm that the source is unencrypted and opens correctly elsewhere. Try a small job to isolate it. If the file is damaged or uses specialized form structures, obtain a fresh appropriate export rather than repeatedly retrying the same problematic source.

What is the final pre-sharing check?

Verify the total page count, queue order, boundaries between sources, small text, landscape pages, and any important links or form values. Check for drafts, duplicates, and private appendices. Share the exact downloaded copy you reviewed, with a descriptive filename.