Documents · PDF Toolkit
What Survives a PDF Merge: Metadata, Bookmarks, Forms and Comments
· Why it matters
pdf metadata document-review
A merged PDF is more than its visible pages. Author names, creation tools, bookmarks, form fields and review comments can all ride along or be lost, so this post explains what to check before the combined file goes out.
The client saw a colleague's name — how a merged file exposed a document property nobody looked at
A combined report can look complete while carrying less structure than its sources. ToolAcre’s merge creates a new PDF and copies pages in file-list order. Visible content, page size, and rotation survive that page copying, but the operation is not a byte-level concatenation or a complete clone of every document feature.
That distinction protects against two opposite mistakes: assuming hidden properties ride along, or assuming they are scrubbed comprehensively. The implementation states which major structures are dropped. Inspect the result as a recipient would, retain the sources, and avoid using a page merger as a metadata-sanitization guarantee.
Fresh output metadata is not copied from a selected source file
The outline asks which source Info dictionary or XMP packet is retained, but this operation creates a new `PDFDocument` and does not select one input’s document metadata for copying. The reliable description is fresh output containing copied pages, not “the first file wins” or another undocumented precedence rule.
A viewer properties panel remains useful because it shows what the output actually contains. Check title, author, subject, keywords, producer details, and dates if disclosure matters. Absence of source metadata in the configured operation does not prove there are no visible names or identifiers embedded within page content itself.
Bookmarks are dropped by this merge
Bookmarks and outlines are document-level navigation structures, and the merge configuration explicitly says they are not carried across. A twelve-section report can therefore retain all pages while losing its sidebar table of contents. Printed contents pages remain visible but do not recreate clickable navigation.
Plan to rebuild navigation in suitable software if recipients depend on it. Do not tell users bookmarks “may or may not” survive this particular tool; its documented behavior is specific. The output order follows the selected file order, while any navigation tree from those files is omitted from the new document.
Forms and annotations are dropped rather than traveling with copied pages
The outline suggests page-attached comments and form fields often travel. ToolAcre’s merge documentation instead states that annotations and form fields are not carried across. A filled visual appearance may still be part of page content in some sources, but interactive widgets, comments, highlights, and definitions are not promised in the output.
Test forms and reviews before merging if they matter. Export or flatten through an authorized workflow designed for that purpose, then inspect the resulting pages. A thumbnail or casual page view can miss lost interactivity, so open the comments list, tab through fields, and compare expected controls rather than relying only on appearance.
Attachments are dropped; optional-layer preservation is not claimed
Document-level attachments are also dropped. A portfolio PDF that contains an embedded spreadsheet may emerge with every visible page and no spreadsheet. The source does not establish handling for optional-content layers as a class, so this article omits a broad claim instead of converting an outline possibility into a product promise.
Use the attachments panel in the output viewer, and separately examine whether page appearance relies on toggled layers. If those features are essential, choose a specialist workflow whose preservation behavior is documented and tested. ToolAcre’s merge is intentionally a page copier, not a general package or layer migration utility.
A pre-send checklist — properties panel, bookmarks pane, comments list and a page-by-page look at the result
A sound pre-send check opens document properties, bookmarks, comments, forms, and attachments, then steps through every page boundary where source files meet. Verify page dimensions and orientation, especially when A4 and Letter documents are mixed. Search several known words to confirm the expected visible text remains selectable.
Finally, consider signatures. The merged file is newly serialized, so a signature over an input no longer authenticates the result and is invalidated. If the combined packet requires signing, merge and review first, then apply a new signature through the approved process. Never describe copied signature artwork as cryptographic validity.
This tool’s exact handling is known from its implementation and configuration
For this tool, exact handling is not an unknown delegated to generic PDF behavior. Configuration and source say bookmarks, forms, annotations, and attachments are dropped, while page content, dimensions, and rotation are copied. Encrypted inputs are refused, and every existing digital signature is invalidated by the fresh output.
Other PDF software can make different choices, so the rule does not generalize to all mergers. This article also avoids claiming a metadata-cleaning standard or preservation profile. Its purpose is operational: know what ToolAcre copies, know what it omits, and check the downloaded artifact before it reaches a client.
Takeaway — check the combined file the way the recipient will, and use the PDF Toolkit so the checking happens on your device rather than after an upload
A merge result is a new page collection, not a container preserving every source document subsystem. The visible pages are the strong preservation unit here. Navigation, interactivity, attachments, and signature validity are the predictable losses that should shape a consultant’s review checklist.
Run the merge locally, then inspect locally before sharing. No PDF bytes are uploaded by the operation, though consented production analytics is separate and excludes file fields. Privacy during processing does not remove the need for output review; it simply lets that review happen without first transferring the source reports to a processing server. Record any required bookmarks or attachments before merging so their deliberate reconstruction is not discovered only after the originals have left the working folder.