PDF/A Conversion Fails Validation — How to Create a Valid Archival PDF
A PDF converted to PDF/A that still fails PDF/A validation has elements that are not permitted in the archival format: embedded multimedia, JavaScript, unembedded fonts, or non-device colour spaces. Here's how to fix each.
A PDF converted to PDF/A that still fails validation from VeraPDF, Adobe Acrobat, or another conformance checker contains elements that the PDF/A standard prohibits. PDF/A is a restricted subset of PDF designed for long-term archival: it bans JavaScript, external content references, encryption, and requires full font embedding and colour profile tagging. Each validation failure has a specific cause and a specific fix.
Most Common Failure: Unembedded Fonts
PDF/A requires every font used in the document to be fully embedded in the file. A PDF that references system fonts without embedding them fails PDF/A validation immediately. To fix in Acrobat Pro: File → Save As → PDF/A — Acrobat will attempt to embed fonts during the conversion. If a font cannot be embedded (licensing restriction or font file unavailable), Acrobat will warn you. In that case, you must either: (a) substitute the restricted font with a licensed-for-embedding alternative in the source document and re-export, or (b) convert the text using that font to outlines before the PDF/A conversion.
Colour Space Failures
PDF/A requires all colour spaces to be device-independent or accompanied by an ICC colour profile. Colours specified as "DeviceRGB" or "DeviceCMYK" without an ICC profile fail PDF/A-1b validation (PDF/A-2b is somewhat more permissive). Fix in Acrobat Pro: Edit → Preflight → select "Convert to PDF/A-1b." Acrobat embeds an output intent ICC profile (typically sRGB for screen documents, ISO Coated v2 for print documents) that satisfies the colour space requirement. After running Preflight, re-validate with VeraPDF to confirm the colour space errors are resolved.
Prohibited Content: JavaScript, Multimedia, Encryption
PDF/A prohibits: JavaScript actions, embedded audio or video, external content streams (XObjects pointing to external URIs), form submission actions, and encryption. If your PDF has any of these, the PDF/A converter must remove them — and if it does not, validation fails. Check the original PDF in Acrobat: Tools → Redact → Sanitize Document removes JavaScript and other active content. Remove embedded multimedia before conversion. Remove passwords before converting (PDF/A cannot be encrypted). If the document relies heavily on JavaScript interactivity, the archival version will lose that interactivity by design — PDF/A is for preservation, not interaction.
Transparency Failures (PDF/A-1 Only)
PDF/A-1 (the strictest level) prohibits transparency — soft masks, opacity layers, and blend modes. PDFs from design tools like InDesign or Illustrator that use drop shadows, feathered edges, or opacity blending fail PDF/A-1b validation. Solution: either flatten transparency before conversion (Acrobat Pro: Print Production → Transparency Flattener) or convert to PDF/A-2b instead, which does allow transparency. PDF/A-2b is accepted by most archival systems and is appropriate for most use cases. Only regulatory contexts that specifically require PDF/A-1 mandate the stricter standard.
Validating After Conversion
Always validate the converted file — do not assume the conversion succeeded. Free validator: VeraPDF (verapdf.org) is the most authoritative open-source PDF/A validator. Download it, run it on the converted file, and review the detailed report. Each failure includes the clause number from the PDF/A specification (e.g., "6.2.3 — Font not embedded") which tells you exactly what to fix. Run validation in a loop: fix → convert → validate → repeat until VeraPDF reports zero failures with a green "PASS."
Try Compress PDF Now — Free
Browser-based, private, and instant. No account or software required.
Open Compress PDF