To fix a PDF/A validation error, first confirm the exact required profile—such as PDF/A-2b—then use the validator’s rule result to change the source document, not a random setting in the failed PDF. Keep the original and the validation report, fix one failure category at a time, export a new copy with the correct PDF/A preset, and validate that exact copy again.
Do not treat “opens normally,” a PDF/A label in metadata, or one green screening result as formal conformance. PDF/A profiles contain many machine-checkable rules, and level-specific requirements can differ. A safe repair preserves the intended content while satisfying the profile the archive or recipient actually named.
Fast repair workflow
- 1. Get the required profile in writing. “PDF/A” alone is not precise enough.
- 2. Preserve evidence. Keep the original PDF and the full rule-level report.
- 3. Screen the exact file. Identify obvious declaration, font, encryption, metadata, script, version, or color-profile problems.
- 4. Fix the source when possible. Correct Word, InDesign, scanning, or document-system settings before exporting again.
- 5. Validate with the named profile. Use a rule-complete validator or the recipient’s required tool.
- 6. Inspect the result. Compare pages, searchable text, links, signatures, and required accessibility after conversion.
- 7. Archive the tested copy. Keep the profile, report, and workflow evidence with the final file.
Start With the Profile, Not the Error Count
PDF/A is a family of ISO 19005 standards, not one universal preset. A recipient may require PDF/A-1b, PDF/A-2u, PDF/A-3a, PDF/A-4, or another named profile. The same document can pass one profile and fail another because the permitted PDF features and the required conformance level differ.
| Requirement you received | What to do before editing | Common mistake |
|---|---|---|
| “Send a PDF/A” | Ask for the part and conformance level | Choosing the first converter preset and hoping it matches |
| “PDF/A-2b required” | Validate specifically against PDF/A-2b | Testing generic PDF structure or a different PDF/A profile |
| “Archive-ready PDF” | Read the archive’s format, signature, metadata, and packaging policy | Assuming PDF/A alone satisfies retention and legal rules |
| A rule ID and object count | Save the full report and identify the failing object category | Repairing only the first displayed instance |
If you do not yet know the difference between the parts and levels, use Understanding PDF standards as orientation. The receiving organization’s requirement still takes precedence over a general recommendation.
Common PDF/A Errors and the Safest Fix
The exact wording depends on the validator and profile. Work from the rule details, affected objects, and source application—not just the red headline.
| Report points to | Likely issue | Preferred repair | Check afterward |
|---|---|---|---|
| PDF/A identification or conformance metadata | Missing, malformed, or contradictory XMP identification | Export again with the exact PDF/A preset; do not only type a label into metadata | Run the complete profile because a declaration is a claim, not proof |
| Font not embedded, invalid font, or glyph mapping | The export referenced a font, omitted glyphs, or cannot map required text correctly | Resolve font licensing/substitution in the source and enable embedding during export | Visually compare every affected character and test text search/copy |
| Encryption or security handler | The PDF is password-protected or encrypted | Create an authorized unencrypted archival copy from the trusted source | Confirm access policy separately; PDF/A does not replace repository permissions |
| Output intent, ICC profile, or device-dependent color | Color cannot be reproduced under the profile’s rules | Export with the archive-approved output intent or correct color settings at the source | Revalidate and visually inspect branded colors, scans, and charts |
| JavaScript, action, multimedia, or attachment | The file contains a feature the selected profile forbids or restricts | Decide whether the feature can be removed, flattened, or requires a different permitted profile | Test links, forms, attachments, and the business workflow that depended on it |
| Tagged structure, Unicode mapping, language, or alternate text | A higher conformance level requires information the source did not export | Repair headings, reading order, language, alternatives, and character mapping in an accessible source workflow | Run the named PDF/A profile and a separate accessibility review |
| Syntax, cross-reference, object, or stream failure | The PDF is malformed before PDF/A rules can be trusted | Re-export from the original source or retrieve a clean original instead of repeatedly converting the damaged copy | Run a general structural check, then the PDF/A profile |
1. Keep the Original and the Full Validation Report
Copy the failed PDF to a working folder and leave the received or signed original unchanged. Export the complete validation report if the tool supports it. A useful report names the profile, rule, clause or test condition, affected object type, number of failures, and sometimes the exact object or page.
Do not edit a signed PDF casually. Any change can alter signed bytes and invalidate the signature. Check the untouched file with the PDF Signature Checker, then return to the approved unsigned source, make the correction, and restart the signature workflow if necessary.
2. Screen the File Before Choosing a Repair
Run the failed copy through the PDF/A Validator. PDFCheck screens the declared PDF/A part and conformance level, embedded-font indicators, encryption, JavaScript, XMP metadata, PDF version, and ICC-profile indicators. This can quickly expose common categories and help you ask a better question of the source application or formal report.
Important capability boundary
PDFCheck does not evaluate every ISO 19005 rule or every object in the way a rule-complete conformance engine does. Its PDF/A result is a diagnostic screen, not an archive certificate. Use veraPDF’s validation profiles and rule results, Adobe Acrobat Preflight, or the recipient’s mandated validator for formal validation.
If the file cannot be parsed reliably, stop treating it as only a PDF/A problem. Use the general PDF Validator and the steps in How to fix an invalid PDF error before applying conformance-specific changes.
3. Fix Fonts in the Source, Not by Appearance Alone
A PDF can look correct on your computer because the viewer substitutes a locally installed font. An archive cannot depend on that machine. Inspect the file with the PDF Font Checker and follow how to identify PDF fonts before editing or printing.
- If embedding is prohibited by the font licence: replace it in the source with an embeddable font, then proof the layout.
- If only some characters fail: check that every used glyph is present and mapped correctly; a subset must still cover the rendered text.
- If OCR text fails: inspect the invisible text layer as well as the scan image. Searchability and correct Unicode mapping are separate from visual appearance.
- If the source is unavailable: document that constraint. Font replacement or outlining can change search, accessibility, layout, and evidence quality.
4. Re-export With the Exact PDF/A Preset
Use the authoring application’s PDF/A export option when it supports the requested profile. A source-level export can embed fonts, generate coherent XMP metadata, set an output intent, and remove or transform unsupported features in one controlled process. Write down the application version and preset.
If you use a PDF fixup or converter, save to a new file. Adobe’s Preflight fixup documentation warns that a fixup permanently changes the document. Review what the conversion may flatten, remove, remap, recompress, or rewrite.
Do not add a PDF/A identifier manually and stop. Formal validators test the actual objects and properties, not only the XMP claim. Likewise, do not remove every link or attachment automatically: permitted features vary by PDF/A part and profile, and the archive may need associated files. Fix the rule the report names.
5. Validate Again, Then Check the Document’s Job
Validate the new export against the same named profile. The current Adobe Preflight profile documentation, updated February 26, 2026, explains that profiles contain checks, fixups, or both. veraPDF documents rule-level conditions for PDF/A-1, PDF/A-2, PDF/A-3, and PDF/A-4, which makes its report useful for tracing a failure back to a specific object category.
A technical pass is necessary, but it does not prove that the repair preserved meaning. Open the final file and compare it with the source or trusted original:
- Review every page where a font, image, transparency, form, or color setting changed.
- Search and copy representative text, including accented or non-Latin characters.
- Test links, bookmarks, attachments, and form behavior the archive expects.
- Run accessibility checks separately when the document must also meet PDF/UA, WCAG, or organizational requirements.
- Validate signatures only after the final approved PDF/A file has been signed.
The PDF Association’s PDF/A FAQ notes practical validation issues such as embedded fonts and the use of purpose-built validators. Archive policy still needs to cover retention, access control, authenticity, and human review beyond file-format conformance.
What to Save With the Final PDF/A
Required profile
The part and conformance level supplied by the archive, regulator, or recipient.
Final validation report
The validator name/version, profile, result, rule details, and date.
Creation evidence
The source application, export preset, responsible workflow, and approved changes.
Exact final file
A controlled filename and, when policy requires it, a checksum that identifies the tested copy.
PDF/A Repair Checklist
- □ I know the exact PDF/A part and conformance level.
- □ I preserved the original and the complete failure report.
- □ I traced each important rule to its source object or export setting.
- □ I fixed the authoring source where possible and exported to a new file.
- □ I validated the new file with the required formal profile.
- □ I visually compared the result and tested search, links, fonts, and required features.
- □ I repeated signature and accessibility checks when they apply.
- □ I saved the final file, report, profile, and workflow evidence together.
For a broader delivery check around the repaired archive copy, finish with the seven-step PDF preflight checklist. It covers the recipient’s rules, visual review, required features, privacy, and sending the exact file you tested.