What names appear in the new bookmarks?
The bookmarks use source filenames and point to their retained contribution. They are not copies of the original chapter or section outlines.
PDF WORKBENCH / FREE BROWSER TOOL
Merge PDF files with file-name bookmarks
Join supported PDFs in order and add bookmarks named after the source files. Preview page boundaries before saving the combined document.
No signup · File contents stay on this device Files are processed on this device
Drop your files here
PDF documents · files stay on your device
Up to 20 files · 25 MiB per file · 80 MiB total
Sequential processing keeps memory use lower.
Processing happens in your browser. File contents are not uploaded. Close the tab to release active files; temporary handoffs use local browser storage. · Privacy details
IMAGE → DOCUMENT WORKFLOW
Sample checks you can repeat
Measured with the listed sample and settings; these may differ from this page’s starting preset. Timings are individual processing-function runs in the stated environment and exclude page loading. Library caches may be warm. These small-file checks do not establish performance or compatibility for every document.
| Sample | Settings | Observed output | Environment |
|---|---|---|---|
| sample-document.pdf (3 pages; 2,246 bytes); sample-generated.pdf (2 pages; 238,413 bytes) ↗ | All 5 source pages in original order; new file-name bookmarks | approximately 234.5 KB; 0.02 sec; 5 PDF pages | Chrome · Apple M2 / macOS · 15 Oct 2026 · local test |
Specific tasks
Using this tool
How to use merge pdf files
- Choose the PDFs and arrange their file order before opening the page preview.
- This page starts with file-name bookmarks enabled. Remove unwanted pages or change their sequence if needed.
- Merge the selection and reopen the saved PDF to check the first page of each source and the new bookmarks.
Before you start
What to keep in mind
- Encrypted PDFs, signature fields, certified documents and interactive forms are rejected. Use an unencrypted, unsigned or flattened copy you are authorized to edit.
- Source document bookmarks, attachments and document-level metadata are not copied. Links or annotations on a copied page may remain, but their destinations are not repaired.
- Combining files does not automatically reduce their size or repair damaged PDFs. Retain the originals for signatures, forms and document verification.
- Use at most 20 PDFs, 25 MiB per file, 80 MiB in total and 200 input pages across the batch. Choosing fewer output pages does not raise the input-page limit.
Add simple navigation to a multi-document packet
This preset enables new bookmarks named after the source files. When several PDFs form a report packet, those entries help a reader jump to the first retained page contributed by each source. They are simple file-boundary bookmarks, not a reconstruction of the original chapter outline. Give source files understandable names before selecting them if those names will be exposed in the merged document.
Order the files first, then use the page preview to check boundaries and remove an unnecessary cover. If pages from a source are moved, verify where its new bookmark leads in the output. The merger copies supported pages, but original document-level outlines, attachments and complex interactive behavior are outside the guarantee. Files containing encryption, digital signatures or interactive form fields are rejected rather than silently flattened or altered. Keep the source PDFs and open the downloaded merged copy in a reader that shows bookmarks. Check page count, the start of each section and the final page. Combining files is a document assembly step; it does not validate the truth or completeness of the material being assembled.
Understand where a source-file bookmark points
New bookmark entries use the source filenames and point to the first retained contribution from each file in the selected output order. If every page from a source is omitted, that source contributes no bookmark. These entries describe file boundaries, not the original chapters of a source document.
Reopen the result in a PDF reader with its bookmark panel visible and follow each entry. Reordering pages can make the useful destination different from the source’s original first page. Page copying does not repair cross-document link destinations or carry over every document-level structure. This workflow rejects encrypted, signed and form-bearing PDFs, so use the originals for those features. A merged packet is a new assembly, not a signed or verified replacement for every source.
Common questions
About merge pdf files
Can a protected PDF be unlocked and merged?
This merger rejects encrypted PDFs, including those you may be able to view with a password. Password-supported rendering is a separate tool and does not preserve document structure.
Does merging compress the PDF automatically?
No. This is page assembly rather than a PDF size optimizer. The final byte size depends on the copied content and new document structure.
Do the source PDFs leave my device for merging?
No. Page copying and new-PDF creation run locally after the browser loads the required library. The files are not submitted to a server-side merge API.
Should I verify the downloaded copy?
Yes. Reopen it and check page count, sequence, document boundaries and any newly created bookmarks. A completed merge does not establish that the source packet was complete or correctly ordered.