PDF/A Compliance: Your Guide to Long-Term Document Archiving

PDF/A defines multiple conformance levels that specify different degrees of compliance. PDF/A-1 defines two levels: Level B (basic) ensures visual reproducibility, meaning the document will look the same when rendered. Level A (accessible) adds requirements for logical document structure and text extraction, essentially requiring the document to be tagged and accessible. Level A compliance is significantly more demanding because it requires proper tag structure, Unicode character mapping, and language specification.

PDF/A-2 introduced a third level: Level U (Unicode), which sits between B and A. Level U requires that all text in the document has Unicode equivalents, ensuring text can be searched and extracted, without requiring the full structural tagging of Level A. This addressed a practical gap, as many organizations needed searchable documents but found Level A tagging too burdensome.

For most organizations, the choice between conformance levels involves trade-offs between effort and capability. Level B is the easiest to achieve and is sufficient if the goal is purely visual preservation. Level U adds text searchability with modest additional effort. Level A is required when accessibility is mandated or when the structural semantics of the document must be preserved. Government agencies in many countries require Level A for public-facing documents, while Level B or U may suffice for internal archives.

PDF/A achieves long-term preservation by prohibiting features that create external dependencies or ambiguity. Understanding these restrictions is essential for creating compliant documents. Fonts must be fully embedded, including all glyphs used in the document. This prevents rendering failures when fonts are unavailable on the viewer's system. Font subsetting is allowed (embedding only used glyphs), but the embedded subset must be sufficient to render all text.

All color information must be device-independent. PDF/A requires either an output intent (an ICC color profile describing the intended rendering) or the exclusive use of device-independent color spaces like CalRGB, CalGray, or Lab. Device-dependent color spaces (DeviceRGB, DeviceCMYK, DeviceGray) are only allowed when an output intent is present. This ensures that colors are defined in absolute terms rather than being dependent on a specific printer or display.

JavaScript is entirely prohibited in PDF/A. Scripts create unpredictable behavior and external dependencies. Similarly, encryption is not allowed because it could prevent future access if the password is lost. Multimedia content (audio, video) is prohibited in PDF/A-1 but allowed in PDF/A-2 and PDF/A-3 with restrictions. External content references (URLs, file links) are prohibited because the referenced content may not exist in the future. All referenced content must be embedded within the document.

The most reliable way to create PDF/A-compliant documents is to generate them directly from the authoring application. Microsoft Office, LibreOffice, and InDesign all support PDF/A export. In Microsoft Word, use File > Save As > PDF and click Options to select a PDF/A conformance level. LibreOffice offers PDF/A-1b, PDF/A-2b, and PDF/A-3b in its PDF export options. InDesign provides detailed control over PDF/A settings through its PDF export presets.

When creating documents destined for PDF/A, keep the restrictions in mind from the start. Use standard fonts or fonts that you have the right to embed. Avoid transparency effects in PDF/A-1 (though PDF/A-2 and later allow transparency). Use vector graphics instead of low-resolution images where possible. Ensure all images are embedded rather than linked. Set the document language in the document properties.

For PDF/A Level A compliance, use proper heading styles, create tagged content using the authoring application's structure features, add alternative text to all images, and ensure that tables are properly structured with headers. If the document is complex, plan the tag structure before you begin creating content. Retrofitting accessibility into a completed document is significantly more time-consuming than building it in from the start.

Converting existing PDFs to PDF/A format is a common requirement, particularly for organizations digitizing legacy document collections. Adobe Acrobat Pro's Preflight tool includes several PDF/A conversion profiles that analyze a PDF, identify non-compliant elements, and attempt to fix them automatically. The conversion process may embed missing fonts, convert color spaces, remove JavaScript, and flatten transparency.

Automatic conversion works well for simple documents but often requires manual intervention for complex ones. Common issues that prevent automatic conversion include missing fonts (if the original font cannot be located, the converter may substitute a different font, altering the document's appearance), device-dependent colors without an output intent, and referenced external content that must be either embedded or removed.

Open-source tools provide alternatives for batch conversion. Ghostscript can convert PDFs to PDF/A using specific output device settings. The VeraPDF tool validates PDF/A compliance and provides detailed reports of non-conformances. LibreOffice can batch-convert office documents to PDF/A through command-line scripting. For large-scale conversion projects, commercial tools like ABBYY FineReader, Foxit PDF Editor, and callas pdfaPilot offer batch processing with detailed reporting and higher success rates for complex documents.

Creating a PDF and selecting PDF/A in the export options does not guarantee compliance. Many authoring tools produce files that claim to be PDF/A (by including the appropriate metadata) but contain non-conforming elements. Validation using a dedicated tool is essential.

VeraPDF is the industry-standard open-source validator for PDF/A documents. Developed as part of the European PREFORMA project, it validates all parts and conformance levels of the PDF/A standard. VeraPDF provides detailed reports listing every conformance violation, categorized by severity and with references to the relevant clause in the ISO standard. It can be used as a GUI application, command-line tool, or integrated into workflows via its REST API.

Adobe Acrobat Pro's Preflight tool also validates PDF/A compliance and can attempt to fix identified issues. The Preflight profiles for PDF/A are comprehensive and regularly updated. Callas pdfaPilot provides both validation and correction capabilities and is widely used in production workflows.

When validating, test the document at the specific conformance level you intend. A document that passes PDF/A-1b validation may fail PDF/A-1a validation due to missing tags. Similarly, a document compliant with PDF/A-1b may use features (like JPEG2000 or transparency) that cause it to fail PDF/A-1b but pass PDF/A-2b. Establish a validation step in your document production workflow to catch compliance issues before distribution or archival.

Different industries have adopted PDF/A in specific ways reflecting their preservation needs. In the legal industry, PDF/A is increasingly required for court filings and document retention. The U.S. federal court system (PACER/CM/ECF) accepts PDF/A documents, and some jurisdictions mandate it. Law firms use PDF/A to archive case files, contracts, and correspondence, ensuring that these records remain accessible throughout their retention period, which can span decades.

Healthcare organizations use PDF/A for archiving medical records, clinical trial documentation, and regulatory submissions. The FDA accepts PDF/A for electronic submissions, and many electronic health record (EHR) systems can export documents in PDF/A format. The long retention requirements for medical records (often 10+ years for adults and longer for pediatric records) make PDF/A's preservation guarantees particularly valuable.

Government agencies are among the largest adopters of PDF/A. The U.S. National Archives (NARA) recommends PDF/A as a preferred format for permanent electronic records. The European Union requires PDF/A for official publications and legislative documents. Many national libraries and archives worldwide have adopted PDF/A as part of their digital preservation strategies. Financial institutions use PDF/A for regulatory compliance, archiving transaction records, statements, and audit documentation in a format that regulators can reliably access during examinations.