A merged PDF can display every page and still fail to preserve how the original document worked. Forms may no longer accept input, bookmarks may be missing, attachments may not travel with the pages, and digital signatures may no longer validate. Page appearance is only one test. Before merging, identify the features that matter to the recipient and decide whether a page-copy workflow is appropriate. Folio Bench copies page content into a new document; it does not certify preservation of document-level structures or signatures.
Separate visible content from interactive features
Ordinary page content includes text, images, lines, and shapes that appear when a page is rendered. A PDF can also include form fields, comments, hyperlinks, bookmarks, attachments, metadata, layers, accessibility tags, scripts, and digital-signature information. Some of these features are stored outside the visible drawing commands. A copy operation that transfers pages may not transfer every related structure from the source document.
Make a feature inventory before combining files. Open the source and test whether fields can be filled, whether links navigate to the intended destination, whether bookmarks appear, and whether attachments are listed. If the task depends on any of these, use a tool whose documentation explicitly covers preservation and confirm with the recipient or responsible professional. Do not infer support from a preview image.
Treat signed documents as a special case
A digital signature is associated with a particular document state. If a file is edited or rewritten, the signature may no longer validate against the resulting bytes, even if the visible signature mark remains on the page. A copied signature image is not the same thing as a valid cryptographic signature. Do not merge signed agreements or official records and then represent the output as an unchanged signed original.
Keep the original signed PDF and share it separately when authenticity or verification matters. If a combined packet is needed for convenience, label it as a convenience copy and follow the recipient’s instructions for the authoritative signed source. A responsible organization may require the original file, a verification report, or a particular signing platform. Ask before processing rather than trying to restore a signature after merging.
Check fillable fields and document navigation
Forms can contain named fields, calculations, validation rules, and appearance settings. After a merge, a visible field may render but fail to accept input, or repeated field names may behave unexpectedly. Do not rely on the merged file for a form submission unless you test the required fields and have confirmed that the document remains usable. Keep a blank original and completed version if the workflow calls for both.
Bookmarks and links also deserve a separate check. A merged document may change page positions, so an internal link or bookmark can lead to the wrong destination or disappear. External links should be checked before sharing, especially if the recipient needs to open a reference directly from the file. The Folio Bench merge tool does not provide a report of links or field mappings.
Verify the output without overwriting the source
Save the merged output under a new name. Open it with a PDF reader that exposes the features you need. Test form fields, inspect the attachment panel, expand bookmarks, activate relevant links, and check signatures with the appropriate validation tool. For accessibility, use the receiving organization’s or accessibility specialist’s required review process; visual inspection alone cannot verify reading order or tags.
Record which source files and versions were used. If a feature is missing, stop and return to the original inputs. Choose another workflow that supports the document requirement, or send the sources separately if allowed. Repeatedly saving the merged copy may not restore structures that were lost in the first operation. A fresh copy from the original source is easier to reason about.
Feature-preservation checklist
- List forms, signatures, links, attachments, bookmarks, and tags before processing.
- Keep signed or authoritative originals unchanged.
- Confirm whether the recipient accepts a page-content copy.
- Save the merged file separately and inspect the relevant features.
- Validate digital signatures with the appropriate verification process.
- Ask a responsible professional about archival, legal, or accessibility requirements.
Frequently asked questions
Will a signature image prove that the signature is valid?
No. A visible mark may remain even when the cryptographic signature no longer validates the resulting file. Keep the source and verify the original using the required process.
Can I merge two fillable forms with the same field names?
This tool does not map, rename, or validate form fields. Use software that explicitly supports form preservation and inspect the merged result before submitting it.
Are internal links guaranteed to point to the same page?
No guarantee is made. The tool copies page content, and page positions can change. Test navigation in the output if links or bookmarks matter.
Does this merge tool make an accessible PDF?
No. It does not certify or create accessibility tags or reading order. Ask the recipient or an accessibility specialist for the required process.
Related guides
Read how to merge PDFs safely, preparing a packet for handoff, and diagnosing a failed PDF.
Sources
- PDF-LIB PDFDocument API — describes page-copy methods and notes limitations in copying other document information.
- Adobe: Combine files into one PDF — explains a combine workflow and the need to review page arrangement.
- Folio Bench merge tool — discloses that it copies page content and may not preserve every document-level feature.