Detect and Repair Non-Conformant PDF/A Documents

Share this page

Validate PDF/A Before Sending Documents to an Archive

PDF/A is a family of ISO-standardized PDF formats designed for long-term preservation. It limits or standardizes document features that can make future rendering dependent on external resources, software behavior, or unavailable content. That makes PDF/A useful for records-management programs, legal and financial archives, government documents, and other collections that must remain dependable over time.

A filename or metadata label is not enough to establish conformance. A document can claim to be PDF/A while still containing a non-conformant font, color, metadata, or structural condition. The pdfRest Query PDF API Tool validates the file with the industry-standard veraPDF engine and returns the pdfa query as a straightforward true or false value. That result can drive the next action without requiring an application to interpret a lengthy validation report.

Convert Only the Files That Need Repair

Running every document through conversion adds processing that conformant files do not need. A more efficient intake workflow first submits each PDF to Query PDF with the pdfa query. Files that return true can continue to the archive or the next quality-control step. Files that return false can be routed to the pdfRest Convert to PDF/A API Tool.

This conditional approach is valuable when an organization receives documents from many sources. For example, a records system may ingest contracts created by office applications, scanned correspondence, and PDFs generated by third-party portals. Query PDF provides one consistent decision point, while Convert to PDF/A standardizes only the files that fail the check.

Each pdfRest output includes a resource ID. The application can pass that ID from one compatible operation to the next without downloading and uploading the intermediate PDF. This keeps the validation and conversion sequence easier to automate and reduces unnecessary file transfers.

Choose the PDF/A Version That Matches the Archive

Convert to PDF/A supports PDF/A-1b, PDF/A-2b, PDF/A-2u, PDF/A-3b, and PDF/A-3u. The correct target depends on the archive policy and downstream requirements.

PDF/A-1b focuses on reproducible visual appearance under the original PDF/A specification.
PDF/A-2 variants support newer PDF features; the u level also requires Unicode mappings for document text.
PDF/A-3 variants allow embedded files, with the u level adding the Unicode requirement.

Choosing the target explicitly helps avoid a technically conformant output that does not match the receiving archive's rules. When a policy or regulation governs the collection, use the exact version and conformance level specified by that authority.

Build Repair and Verification into One Workflow

Convert to PDF/A includes an optional rasterize-on-error fallback for problematic source content. Instead of stopping an entire archival batch when an isolated page prevents standard conversion, the fallback can preserve that page's visual appearance in a conformant output. Applications can enable this resilient processing path according to the archive's preservation policy.

After conversion, submit the new file to Query PDF again. The resulting pdfa: true response provides automated confirmation that the delivered output passes the conformance check. An application can store that result with the file's processing record, creating a clear and scalable chain of evidence for archive intake.

Together, Query PDF and Convert to PDF/A provide a practical control loop: evaluate the incoming file, convert only when needed, and record the conformant result before preservation. Use API Lab to configure the requests, then review the Query PDF and Convert to PDF/A API references for current request and response fields.