What is PDF/A?
PDF/A is a family of ISO standards for long-term preservation of electronic documents. It places restrictions on ordinary PDF features so that a future viewer has enough information inside the file to reproduce the intended page appearance without relying on external resources.
PDF versus PDF/A
An ordinary PDF can contain encryption, external dependencies, JavaScript, multimedia, unembedded fonts or color definitions that are unsuitable for archival preservation. PDF/A conformance is therefore not established by changing a filename or adding a metadata field. The file structure, metadata, color management and permitted feature set must all meet the target conformance rules.
What is PDF/A-2b?
The planned target for this browser tool is PDF/A-2b. Level B focuses on reliable visual reproduction rather than logical structure or tagged reading order. A visual browser pipeline can be a practical fit because pages can be rendered and rebuilt without introducing unembedded text fonts, but it still requires a valid color profile, output intent, XMP metadata and independent validation.
Why ICC profiles matter
Archival color reproduction must not depend on an unspecified device color space. A proper PDF/A workflow associates page color with a valid ICC profile and output intent. Writing a string such as “sRGB” into metadata without embedding and linking a real profile is not enough.
Why metadata alone is not compliance
XMP identification properties such as pdfaid:part and pdfaid:conformance tell a validator what the file claims to be. They do not prove that the rest of the PDF follows the rules. A file can contain correct-looking PDF/A metadata and still fail because of encryption, fonts, transparency, annotations, color spaces or forbidden actions.
Visual archival conversion
The intended production architecture is to render each source page at archival quality, rebuild it as a new page image, preserve page dimensions, embed a legally distributable sRGB ICC profile, add an OutputIntent and compliant XMP, avoid encryption and active content, and then validate representative outputs. Rasterization can flatten searchable text, links, annotations and forms, so that tradeoff must be disclosed.
Independent validation is a release gate
This page is intentionally conservative. The build environment could parse and structurally inspect PDFs but did not contain veraPDF or another independent PDF/A conformance validator. Because the project requirements explicitly make external validation a release condition, the conversion control remains disabled. This is safer than distributing a normal PDF labelled as archival PDF/A.
When should you use PDF/A?
PDF/A is useful for records that need stable long-term visual preservation, such as finalized reports, legal records, institutional archives and controlled document repositories. Requirements differ between organizations, so always confirm the exact PDF/A level demanded by the receiving system.
Does PDF/A preserve searchable text?
A structure-preserving PDF/A converter can preserve text when fonts and other resources meet the relevant rules. A visual archival mode that rasterizes pages preserves page appearance but can remove text searchability and interactive behavior. That difference must be understood before conversion.
Privacy
The intended PDF/A implementation remains browser-side. An independent validator used during development does not need to be deployed to the live site. User PDFs should never be uploaded to a remote compliance service without explicit design and consent.
Why this converter is intentionally gated
PDF/A is defined by ISO conformance rules covering metadata, color management, resources, encryption and other document features. Adding an identification string to an ordinary PDF is not enough. A valid PDF/A-2b workflow needs a real output intent with an appropriate ICC profile, correct XMP identification, compliant resources and removal or flattening of features forbidden by the target profile. Just as importantly, representative files produced by the exact implementation must pass an independent conformance validator. Because that validator step has not been completed in this build environment, production PDF/A generation is deliberately disabled rather than presenting an unverified file as archival PDF/A.
What a visual PDF/A-2b pipeline would change
The intended browser architecture is a visual archival reconstruction. Each source page would be rendered at controlled archival resolution and rebuilt as a new PDF page of equivalent visible dimensions. Page images avoid introducing unembedded document fonts, while a distributable sRGB ICC profile would be embedded and referenced through a proper OutputIntent. Compliant XMP metadata would identify part 2, conformance level B. Interactive features such as forms, JavaScript actions and unsupported annotations would be flattened or omitted by construction, and the output would not be encrypted. This preserves visual appearance but can sacrifice selectable text and interactivity.
Validation is part of conversion, not optional documentation
A recognized PDF/A validator such as veraPDF should be run against representative outputs covering text, photographs, mixed page sizes, annotations, forms, transparency and Unicode. Any failed rule must be treated as a release-blocking defect for the PDF/A converter. The validation report included with this package therefore records the current status instead of fabricating a PASS. Once a verified browser pipeline and validator are available, this page can be enabled without changing its permanent URL or misleading users in the meantime.
When to use PDF/A and when not to
PDF/A is intended for long-term preservation workflows where self-contained visual reproduction and conformance rules matter. It is not automatically the right target for every PDF. Interactive forms, encryption, JavaScript, multimedia and some annotation behavior can conflict with archival requirements or need flattening, so converting to PDF/A can intentionally remove features that are useful in an ordinary PDF. Organizations may also require a different PDF/A part or conformance level than PDF/A-2b, and a browser tool should not guess that policy. Before archival conversion, confirm the receiving archive, university, government office or records policy actually accepts PDF/A-2b. After conversion, validation should be performed with the same recognized rules expected by that workflow. This page remains useful even while generation is gated because it prevents an unsafe shortcut: a file with PDF/A metadata but failing conformance is not a reliable archival deliverable. The production control will only be enabled after the exact generated pipeline has passed representative independent validation.
Archival copies and source preservation
Even a validated PDF/A derivative should not automatically replace the original source file. An archival visual conversion can flatten interactivity and may increase file size because it favors self-contained reproduction rather than minimum bytes. Keep the original PDF when policy permits, record which PDF/A profile was produced, and retain validator results when formal archival evidence is required. A receiving organization may run its own validator and can impose additional document policies beyond the ISO profile. This tool therefore treats conformance status as something that must be demonstrated, not a marketing badge.
Frequently Asked Questions
Why is the PDF/A button disabled?
The required independent PDF/A-2b conformance validation could not be executed in this build environment, so the release gate remains closed.
Why not simply add PDF/A metadata?
Metadata can claim conformance but cannot make non-compliant PDF features valid.
What target is planned?
PDF/A-2b, focused on long-term visual preservation.
Would visual PDF/A keep selectable text?
Not necessarily. A rasterized visual workflow can flatten text, links, forms and annotations.
Is encryption allowed in PDF/A output?
The intended archival output must not be delivered encrypted.
What is an OutputIntent?
It associates the PDF with a color reproduction condition and normally references an embedded ICC profile.
Which validator should be used?
A recognized independent conformance checker such as veraPDF is appropriate for development QA.
Can I use another PDF/A converter meanwhile?
Yes. For archival requirements, use a converter whose target conformance has been independently validated and confirm the output with your receiving institution.