PDF/A vs PDF for Legal Documents: What's Required?
The Core Difference Between PDF and PDF/A
A standard PDF is a flexible container. It can embed JavaScript, link to external resources, include multimedia, reference fonts hosted on a remote server, and encrypt content in ways that may prevent future rendering. That flexibility is useful for interactive forms or presentations, but it creates a serious problem for legal documents: a PDF that depends on an external font server or an embedded script may look completely different — or fail to open — ten years from now when the software landscape has changed. PDF/A is an ISO-standardized subset of PDF specifically designed for long-term archiving. The 'A' stands for Archive. The standard was first published as ISO 19005-1 in 2005, and it has since been updated through ISO 19005-2 (PDF/A-2, 2011) and ISO 19005-3 (PDF/A-3, 2012). The fundamental requirement across all versions is self-containment: every font, color profile, and piece of metadata the document needs to render correctly must be embedded inside the file itself. No external dependencies are permitted. In practical terms, this means a PDF/A file cannot contain JavaScript, cannot link to external URLs for resources, cannot use encryption that would prevent the file from being opened, and must include an embedded ICC color profile. It also requires XMP metadata — a structured XML block inside the file that identifies the document as PDF/A-compliant and records which conformance level it meets. If any of these conditions are violated, the file is not PDF/A, regardless of what the filename says. For a law firm filing a contract that needs to be retrievable and readable in 2045, that self-containment requirement is not bureaucratic overhead — it is the entire point.
Which PDF/A Level Does Your Jurisdiction Actually Require?
PDF/A is not a single format. There are three generations, and within PDF/A-1 and PDF/A-2, there are two conformance levels: 'a' (accessible) and 'b' (basic). PDF/A-3 adds a third level, 'u' (unicode). Understanding which level a court or regulatory body requires matters because submitting the wrong conformance level can result in rejected filings. PDF/A-1b is the most commonly mandated level for legal filings. It guarantees visual reproducibility — the document will look the same when rendered in any conforming viewer — but it does not require the document to be tagged for accessibility or have a logical reading order. PDF/A-1a adds those accessibility requirements, which means all text must be tagged, reading order must be defined, and the document must be fully searchable with correct Unicode mappings. The U.S. federal courts operating under CM/ECF (Case Management/Electronic Case Files) generally accept standard PDF but increasingly prefer or require PDF/A for certain document types. The European Court of Human Rights has explicitly required PDF/A-1b since 2014. Germany's e-justice initiative (ERV — Elektronischer Rechtsverkehr) mandates PDF/A-2b for court submissions through the beA (besonderes elektronisches Anwaltspostfach) system. The UK's HM Courts and Tribunals Service recommends PDF/A but does not yet mandate a specific level for all filing types. Before converting any document, look up the specific technical requirements for your jurisdiction. Court websites typically publish these under sections titled 'Electronic Filing Requirements' or 'Practice Directions.' If you cannot find a specific level listed, PDF/A-1b is the safest default — it has the broadest software support and the longest track record.
Common Failure Points When Converting Legal Documents to PDF/A
The conversion process introduces several predictable failure points that can silently produce a file that looks like PDF/A but fails validation. Knowing where these failures occur helps you catch them before submission. Font embedding is the most frequent issue. Microsoft Word documents often reference system fonts like Calibri or Times New Roman without embedding them. When you export directly from Word to PDF using 'File > Export > Create PDF/XPS,' the resulting PDF may or may not embed all fonts depending on your settings. In Word's PDF export dialog, clicking 'Options' and checking 'ISO 19005-1 compliant (PDF/A)' instructs Word to embed all fonts and disable features incompatible with PDF/A-1b. This works reasonably well for simple documents, but complex documents with custom fonts installed only on your machine may still fail if those fonts have embedding restrictions set by the font manufacturer. Transparency effects are another common problem. PDF/A-1 does not allow transparency. If your document was created in Adobe InDesign or contains graphics with transparent layers — a logo with a transparent background, for example — a naive conversion will either fail validation or flatten the transparency in a way that changes the document's appearance. PDF/A-2 does permit transparency, which is one reason some practitioners prefer PDF/A-2b over PDF/A-1b despite the older standard's wider adoption. Color profiles cause subtle failures. PDF/A requires an embedded ICC color profile for all color content. A document that uses RGB colors without an embedded sRGB profile will fail validation. Most conversion tools handle this automatically, but if you are using a command-line tool like Ghostscript, you need to explicitly specify the output color profile with a flag like '-sColorConversionStrategy=sRGB'. Encryption is an absolute disqualifier. PDF/A prohibits any encryption that restricts opening or reading the file. If a document was password-protected before conversion, the protection must be removed first.
How CocoConvert Handles PDF/A Conversion — and Where Its Limits Are
CocoConvert supports conversion to PDF/A-1b and PDF/A-2b from a range of source formats including Word (.docx), Excel (.xlsx), PowerPoint (.pptx), and image formats such as JPEG, PNG, and TIFF. The service handles font embedding, color profile injection, and XMP metadata tagging automatically as part of the conversion pipeline. For straightforward Word documents using standard system fonts, the output will typically pass validation in tools like Adobe Acrobat's Preflight or the free veraPDF validator. However, there are real limitations worth understanding before you rely on CocoConvert for high-stakes filings. First, CocoConvert cannot currently validate the PDF/A output it produces — it converts but does not run a conformance check on the result. You should always validate the output file independently using veraPDF (free, open-source, available at verapdf.org) or Adobe Acrobat Pro's Preflight tool (Acrobat Pro > Tools > Print Production > Preflight, then select the PDF/A profile). Do not skip this step. Second, CocoConvert does not process documents that contain complex embedded objects such as OLE objects in Word files, or documents where fonts have manufacturer-set embedding restrictions. In these cases, the conversion may succeed technically but the resulting PDF/A may substitute fonts, which changes the document's appearance. For legal documents, any visual change from the original is potentially significant. Third, CocoConvert does not currently support PDF/A-3, which allows embedding arbitrary file attachments (including XML data files used in e-invoicing standards like ZUGFeRD). If your jurisdiction requires PDF/A-3 for structured data attachments, you will need a tool like Adobe Acrobat Pro or a dedicated server-side solution. For routine conversion of standard Word contracts and correspondence to PDF/A-1b or PDF/A-2b, CocoConvert is a practical and fast option. For complex litigation documents, court exhibits, or filings with strict technical requirements, treat the CocoConvert output as a starting point and validate it before submission.
Privacy Considerations When Converting Confidential Legal Documents
Legal documents frequently contain privileged communications, personal identifying information, and confidential business data. Uploading these to any online conversion service — including CocoConvert — requires a clear-eyed assessment of the privacy implications. CocoConvert processes uploaded files on its servers and deletes them after conversion is complete. The retention period is 24 hours for converted files available for download, after which they are permanently removed from storage. Files are transmitted over TLS 1.2 or higher encryption in transit. These are standard practices for reputable online conversion services. Despite these measures, there are document categories where online conversion is inappropriate regardless of the service's privacy policy. Attorney-client privileged communications, documents under protective orders, sealed court filings, and documents containing sensitive personal data subject to GDPR or HIPAA should generally not be processed through third-party online services unless your firm has a data processing agreement (DPA) in place with that service provider. CocoConvert does not currently offer DPAs, which makes it unsuitable for GDPR-regulated processing of personal data in the EU context. For these sensitive categories, the appropriate approach is local conversion using desktop software. Adobe Acrobat Pro can save to PDF/A-1b or PDF/A-2b directly (File > Save As > PDF/A). LibreOffice 7.x and later can export to PDF/A-1b via File > Export as PDF > select 'Archive PDF/A-1a' or 'Archive PDF/A-1b' in the PDF Options dialog — this is a free option that keeps all processing local. Microsoft Word 365 can export to PDF/A-1b using the ISO compliance option described earlier. The privacy risk is not hypothetical. In 2023, several law firms faced bar association inquiries after using AI-based document tools that retained uploaded content for model training. Always read the terms of service and privacy policy of any online tool before uploading client documents.
Validating PDF/A Compliance Before Filing
Producing a file that claims to be PDF/A and producing one that actually passes conformance validation are two different things. Courts and regulatory agencies that mandate PDF/A increasingly have automated validation systems that will reject non-compliant files, sometimes without a clear error message explaining what failed. veraPDF is the reference validator for PDF/A compliance. It is free, open-source, and maintained by the PDF Association and the Open Preservation Foundation. You can run it as a desktop application or integrate it into a workflow via command line. To validate a file against PDF/A-1b, the command is: 'verapdf --flavour 1b your-document.pdf'. The output report identifies each failed rule by its ISO clause number, which makes it possible to understand exactly what is wrong rather than just knowing that something failed. Adobe Acrobat Pro's Preflight tool is the other widely used option. Open the document, go to Tools > Print Production > Preflight, and in the Preflight dialog select 'PDF/A-1b' or whichever profile applies. Run the check. Acrobat will display a list of errors and warnings. A common finding is 'Font not embedded' or 'Transparency not permitted in PDF/A-1' — both fixable by reprocessing the source document with the correct settings. One practical workflow for law firms: establish a validation step as a mandatory part of the filing checklist. Before any document goes to the court filing system, a paralegal or legal tech staff member runs veraPDF on it and logs the result. This takes about 30 seconds per file and catches the majority of conversion errors before they become filing rejections or, worse, compliance problems discovered during discovery. If a document fails validation after conversion, do not simply re-export it and hope. Identify the specific failure, fix it in the source document or conversion settings, reconvert, and validate again.
Practical Recommendations by Document Type
Not every legal document has the same archiving requirements, and treating all documents identically wastes time and creates unnecessary friction. Here is a practical breakdown by document type. Contracts and agreements intended for long-term retention — more than seven years — should be PDF/A-1b or PDF/A-2b. Use PDF/A-2b if the document contains transparency effects or was created in a modern DTP application. Validate before storing. Court filings should match the specific technical requirements of the filing system. For U.S. federal courts using CM/ECF, check the local rules of the specific district — some accept standard PDF, others require PDF/A. For European courts, PDF/A-1b is the safe default unless the court specifies otherwise. Discovery documents produced in litigation are often governed by an agreed-upon ESI (Electronically Stored Information) protocol. The protocol may specify PDF with text layer (searchable PDF), PDF/A, or native format. Follow the protocol exactly; do not convert to PDF/A if the protocol requires native format. Internal working documents — draft contracts, internal memos, research notes — do not need to be PDF/A. Standard PDF is appropriate. Converting everything to PDF/A by default creates larger files (due to embedded fonts and color profiles) and removes useful features like password protection for documents that benefit from access controls. Scanned documents presented as evidence require a text layer to be properly searchable, which means running OCR before or during conversion. CocoConvert supports OCR for scanned PDFs during conversion, but for critical evidence documents, verify that the OCR output is accurate — automated OCR has an error rate that varies with scan quality, typically 1-3% character error rate on clean scans, higher on poor-quality originals. Review the output before filing.