Documents · PDF Toolkit
PDF/A, Linearized and Tagged PDFs: Which Properties Survive Editing?
· Background
pdf document-conformance accessibility
Some PDFs carry promises beyond their pages: archival conformance, fast web view, or an accessibility structure. This post explains what those properties are and why any rewrite, including a merge or split, can affect them.
The archive rejected the merged file — how a conformance check fails after a routine page operation
An archive can reject a file that looks perfect because visual appearance is not the same as conformance. ToolAcre creates fresh outputs for merge, split, reorder, rotation, and watermarking. It does not display archival, web-optimization, or accessibility certification before or after those operations.
The safe records workflow treats every edited result as needing the checks required by its destination. Preserve the accepted source, perform only necessary page work, then validate the exact downloaded bytes. A successful browser preview proves readability, not compliance with an external profile.
PDF/A requirements and preservation are outside the supplied source evidence
The workbook supplies a summary of PDF/A requirements, but the required repository sources contain no PDF/A validator, profile declaration, or standards citation. This article therefore omits a requirements list and makes no claim that the toolkit preserves, breaks, creates, or repairs a specific archival conformance level.
That restraint is operational rather than academic. An archival promise should come from a recognized validator and policy, not from a page tool’s visual success. If PDF/A is required, test the output using approved software and retain the report alongside the document according to the records process.
Linearization behavior is not inspected or promised by this toolkit
Linearization, sometimes presented by viewers as fast web view, is not inspected in this interface. The source saves fresh bytes through pdf-lib and does not expose a control or assertion for a web-optimized object arrangement. The article cannot truthfully state that the property survives or is deliberately removed.
If first-page streaming matters, check the downloaded output with a tool that reports linearization and can regenerate it when needed. Local Blob download behavior says nothing about how the same file will be served later over HTTP. Delivery optimization and page correctness are separate review dimensions.
Tagged-PDF preservation is not tested or promised
Tagged-PDF structure and screen-reader behavior are likewise not tested or promised in these operations. Page copying preserves visible content, but the merge documentation explicitly drops forms, annotations, bookmarks, and attachments. That known list does not establish what happens to every accessibility structure.
Accessibility review must include specialist inspection and assistive-technology testing where required. PDF-to-image definitely loses the text layer and should not be used when searchable or readable text is needed. For copied-page outputs, avoid both reassurance and alarm unsupported by a tag-tree validation result.
Fresh serialization changes bytes and drops known structures; other profile effects remain unverified
Fresh serialization changes file bytes and invalidates existing digital signatures. Merge and split rebuild documents from copied pages and omit documented structures. Reordering also copies pages in a new sequence. Those facts justify rechecking downstream properties, but they do not prove a universal outcome for every conformance profile.
Rotation and watermarking also save new files even though their visible changes are narrow. A profile can constrain more than appearance. Use the operation mechanism to identify risk, then let the proper validator determine the result. Do not infer compliance from unchanged page rendering or similar file size.
Use specialist validators because this interface exposes no conformance indicators
The PDF Toolkit provides no badge for PDF/A, linearization, or tagging and no built-in conformance report. Check those properties after download with tools approved by the archive, accessibility program, or publishing platform. Record tool version and profile target so another reviewer can reproduce the decision.
When a validator fails, diagnose its reported rule rather than repeatedly rerunning the page operation. Repair may require metadata, fonts, structure, or serialization features outside this toolkit. Keep intermediate files clearly named to prevent an unvalidated result from replacing the accepted source accidentally.
This tool documents known page-copy losses but does not certify special profiles
Known behavior remains useful: encrypted inputs are refused; copied-page operations lose bookmarks, forms, annotations, and attachments; signatures are invalidated; raster output loses selectable text; and hard size caps apply. None of those statements amounts to certification or a complete profile analysis.
The tool pages are the right place to learn operation limits, but not a substitute for the external specification and validator required by a records workflow. This article intentionally omits detailed profile rules because no supplied source supports them. An unverifiable background claim is safer left out than presented as product evidence.
Perform page work before validation, without assuming a profile survives
Sequence the workflow so page editing occurs before final conformance validation, signing, and archival ingestion. That avoids certifying one byte sequence and then changing it. If subsequent edits are unavoidable, repeat every required validation and signature step on the new output.
ToolAcre keeps the page operation on the device, reducing transfer exposure while the file is edited. Local processing does not grant archival or accessibility status. Treat privacy, page fidelity, conformance, and signature validity as separate controls, each with its own evidence and responsible tool. Archive the validator report with the exact output checksum if policy requires proof that the assessed bytes are the bytes ultimately retained. If a later transfer system modifies or optimizes the file, validate that delivered copy again rather than assuming the earlier report still applies to altered bytes. The same ordering applies to signatures: validate the finalized structure first, sign the accepted bytes, and avoid any subsequent page operation that would invalidate that evidence. Assign ownership for that final gate.