Applies to: Preservation format selection; the receiving archive’s named PDF/A profile and validator control acceptance.
PDF/A is a constrained ISO-standardized form of PDF intended for long-term preservation. It emphasizes self-contained rendering and restricts features that depend on external resources or active behavior. Use it when a records policy requests it—not as a universal replacement for source files.
Why PDF/A exists
Ordinary PDFs can depend on fonts, encryption, multimedia, scripts, or other features that may not support predictable long-term rendering. PDF/A profiles restrict PDF features and require information needed to reproduce the document.
The PDF/A family is defined by ISO 19005. Different parts and conformance levels support different capabilities, so “save as PDF/A” is not a complete specification by itself.
What a compliant file changes
Requirements vary by PDF/A version, but the goal is a self-contained, device-independent document with appropriate metadata. PDF/A-1, for example, disallows encryption and requires fonts to be embedded and legally embeddable.
A PDF/A file can still contain poor scans, incorrect OCR, missing pages, or misleading metadata. Conformance is not the same as content accuracy or accessibility.
Choose a workflow, not just a checkbox
- Ask the receiving archive or records system which PDF/A part and level it accepts.
- Keep the original source or scan master when policy requires it.
- Convert a working copy using a trusted application.
- Validate conformance with the receiving system’s approved tool.
- Visually compare page count, fonts, color, links, and annotations.
- Document the conversion process for important records.
PDF/A and scanned documents
For scanned records, preservation programs may treat source image files as masters and use searchable PDFs as convenient access copies. The right choice depends on institutional requirements, retention policy, and the characteristics of the original.
Do not delete source images merely because a PDF/A file passes validation. Confirm the recordkeeping policy first.
Keep validation and content review as separate records
For a fictional archive transfer, record the requested profile, the conversion application, the validator result and a page-level comparison. A file can pass profile validation while containing a missing page or incorrect scan, so keep both the validation report and the visual review result.
Do not use a filename ending in pdfa.pdf as proof of conformance. Ask which PDF/A part and conformance level the receiver requires. Retain the source file so a later migration does not depend on reversing a flattened or otherwise altered access copy.
Sources and further reading
Vendor instructions and background references are linked below. Worked examples are our explanatory calculations, not vendor performance claims. Check the instructions for your current software and device.
Report a correction with this page’s title and the step or result that needs attention.