PDF guides
Why a PDF Fails PDF/A Conversion (and What to Do)
Some PDFs cannot be turned into a PDF/A file that passes validation. This guide walks through the real reasons a conversion fails, how to tell which one applies to your file, and what you can try next.
Ready to try the tool this guide describes?
Two different kinds of failure
A conversion can fail outright — the tool cannot process the file at all — or it can produce a file that then fails validation against the PDF/A-2b rules. In the PDF to PDF/A tool, both outcomes end the same way for you: an explanation and no download. A file that fails validation is never offered, because it would only look like an archive copy.
Common causes
- Password protection: PDF/A forbids encryption, so a protected file is rejected before conversion. Remove the password first.
- Damaged structure: a file with a broken cross-reference table or truncated ending may not convert reliably. Try Repair PDF first and convert the repaired file.
- Fonts that cannot be embedded: some fonts do not permit embedding, or a font is referenced but missing from the file. PDF/A requires every font to be embedded.
- Embedded files, JavaScript or multimedia: PDF/A-2 restricts what may be embedded and does not allow scripts or audio and video.
- Unusual color or transparency constructs: colors have to be expressed in a defined color space, and some exotic constructs cannot be mapped cleanly.
- Very large or complex pages: a file that hits the tool’s size, page-count or time limits is stopped rather than half-processed.
What to try
- Confirm the file is not password-protected and opens normally in a viewer.
- If it is damaged, run it through Repair PDF and try the repaired copy.
- If it came from Word or another application, re-export it from the source: many applications have a “PDF/A” option that embeds fonts as it writes the file.
- If it is a scan, run OCR PDF first if you need searchable text, then convert.
- If the file is close to the limits, split it and convert the parts separately.
Why not just hand over the best-effort result?
A file that says it is PDF/A but does not validate can be rejected later by a records system, and by then the original may be gone. Refusing to provide a non-compliant file up front is deliberate: you find out now, while you can still fix the source.
Why PDF/A Conversion Fails FAQ
- The tool says validation failed. Was my file damaged?
- Not necessarily. It means the converted result did not meet every PDF/A-2b rule. The source may simply use features PDF/A does not allow.
- Can I download the failed result anyway?
- No. A file that fails validation is not offered, so nobody mistakes it for a conforming archive copy.
- Does a bigger file size mean the conversion worked?
- No. Larger output is normal for PDF/A because fonts and a color profile are embedded, but only validation shows whether the result conforms.
- Will exporting PDF/A from Word or another editor work better?
- Often yes, because the application still has the original fonts and structure. It is worth trying when a converted PDF will not pass.
- Is the file uploaded to fix these problems?
- The file is uploaded for conversion and deleted immediately afterward, because conversion and validation run on the server. It is not stored.
Related guides
- What Is PDF/A?What the PDF/A archival standard actually requires — embedded fonts, defined color, no encryption or scripts — who asks for it, when an ordinary PDF is enough, and why validation matters.
- PDF/A-1 vs 2 vs 3Compare the parts and conformance levels of PDF/A, learn what the a, b and u letters mean, and see why the PDF to PDF/A tool creates PDF/A-2b and when a requirement needs something else.
