Archive-ready (PDF/A) delivery
Goal
Deliver a PDF that an archive, court or regulator will accept as PDF/A, and have a report that shows it.
A registry demands "PDF/A-1b or better" for your annual filing. You have a normal PDF with a filled form on page 3. You need a file that passes, not one that merely says it is PDF/A.
Be clear about the tools
PDF/A Validator only checks. It never changes your file. Documentize's PDF/A conversion lives in Converter (PDF to PDF/A). Its chapter lists the targets PDF/A-1a, 1b, 2a and 3a, and the site warns that very complex or dynamic PDFs may not fully conform. The plan's chain stopped at the Validator; a deliverable needs a conversion step, or the original authoring program's own "Save as PDF/A".
Starting state
- A PDF without password (encryption is forbidden in PDF/A; Unlock if needed).
- The exact standard and letter the receiver wants (for example PDF/A-1B). Ask them; B, U and A mean different things, and A is hardest.
- No signature yet.
Chain
Flatten → Optimize → Converter (PDF to PDF/A) → PDF/A Validator → fix at source and repeat?
freeze tidy make the PDF/A prove it
Step by step
1. Flatten
Press Flatten with options empty to freeze form fields. Interactivity and scripts are among the usual causes of PDF/A failures. See Flatten.
2. Optimize (optional)
No options. It tidies structure without touching the look. If you also need a smaller file, run Compressor here, before conversion, not afterwards. See Optimize.
3. Converter, PDF to PDF/A
Open the PDF to PDF/A page, pick the target closest to what the receiver names, press CONVERT. Why here: this is the step that embeds fonts and the structure; everything after it must not rewrite the file. See Converter.
4. PDF/A Validator
Choose Detect automatically (judges the file against the standard it claims) and, if the receiver names a level, run once more with that level selected. Keep Group identical problems on. Press Validate PDF/A. Read the verdict, error and warning counts, and the problem list (severity, clause, page, object). Keep the JSON report pdfa-validation-report.json with the file. See PDF/A Validator.
Why this order
Remove what breaks PDF/A (form fields), tidy, produce the PDF/A, then validate the exact file you will deliver. Any step after the conversion can change whether the file is valid, so validation is always last.
Expected result
A PDF/A file and a validation report that says valid for the standard the receiver requires.
Check it worked
- Verdict is valid for the named level, not only against the fallback (PDF/A-1B) used when the file claims nothing.
- Error count is zero; read the warnings.
- The file opens, text is selectable, and pages look right.
- For a legally critical filing, the receiver's own validator agrees (validators can differ on borderline cases).
Variations
- Validation fails: read the clauses. Typical causes are unembedded fonts, missing colour profiles, transparency, encryption, JavaScript and external links. Fix at the source and convert again, or re-export from the authoring program as PDF/A. Fixing one error can reveal another: re-run.
- Scanned archive: Searchable first, then convert and validate (see Digitise an archive).
- Need to sign: validate first; a signed PDF/A must be signed last, and after signing do not touch it. Whether the signing step keeps the PDF/A status is not documented in the book: validate the signed file (verify on the live app).
What can go wrong
- Assuming "converted" means "valid": always validate.
- Compressing, protecting or unlocking after validation.
- Picking the wrong letter: ask the receiver.
- Heavy, dynamic PDFs may not fully conform: choose a simpler source.
- PDF/A is not accessibility: the B levels do not guarantee it (PDF/A-A and PDF/UA-1 do).