PDF vs PDF/A: Which Format Should You Use for Archiving?

PDF and PDF/A have different goals

PDF is a broad document format intended to preserve layout across devices and applications. It can contain text, images, vector graphics, annotations, forms, attachments, encryption and many other features. PDF/A is a family of standards based on PDF that adds requirements intended to make documents more self-contained and predictable for long-term preservation. It is designed for archiving, not simply for making a file smaller or locking it from editing. The specific requirements depend on the PDF/A conformance level and version.

A file with “PDF/A” in its filename is not automatically compliant. Compliance is a technical property that should be tested by a validator. Likewise, an ordinary PDF may be perfectly suitable for everyday sharing even if it is not appropriate for a particular archive policy. Choose the format based on the receiving organization’s rules and the intended lifetime of the record.

Fonts, color and embedded resources

Archival standards commonly require fonts to be embedded so future systems can render the text without depending on a font installed on the viewer’s computer. External dependencies and certain dynamic features may be restricted. Color management requirements can also apply so that appearance is more reproducible. These controls reduce reliance on the original authoring environment, but they do not guarantee that every viewer will display every file identically forever. Software and hardware still change, and preservation may require monitoring over time.

Converting to PDF/A can change a file. A converter may embed fonts, normalize color information, remove unsupported features or transform transparency. Check visual output after conversion, especially for brand colors, thin lines, signatures, embedded images and forms. If the original contains interactive features or attachments, confirm whether the target conformance level allows them and whether the organization requires them to be retained.

Choosing a conformance level

PDF/A has multiple parts and conformance levels with different capabilities. Some levels focus on reliable visual reproduction; others also support structural or Unicode-related requirements. The correct choice depends on the archive system and its policy. Avoid selecting a level just because it is the highest number in a menu. Ask the receiving institution which profile it accepts and whether it has a preferred validator. A strict level may require remediation of source features that a simpler profile would allow.

If a file fails validation, read the actual error report rather than blindly converting it repeatedly. A font may not be embedded, metadata may be malformed, or an unsupported feature may remain. The repair depends on the cause. Keep the original and record which conversion settings were used so the process is reproducible.

Validation and preservation workflow

A sensible workflow is to retain the original file, create the archival rendition, validate the output with a recognized validator, inspect important pages visually, and record the validation report alongside the archive record. For high-value documents, use checksums and a managed storage process so later bit-level changes can be detected. A checksum proves that bytes match a known value; it does not prove that a file is authentic, complete or legally compliant by itself. Preservation needs process and metadata as well as a format.

Validation is not a one-time substitute for preservation planning. Organizations should maintain redundant storage, access controls, fixity checks and documented migration procedures. If a repository later needs to migrate formats, the original and the migration record can explain what changed. The file format is one component in a larger records-management strategy.

When ordinary PDF is enough

For informal sharing, web downloads, internal drafts and many everyday workflows, a normal PDF is usually sufficient. It supports broad features and may preserve forms or annotations that an archival profile restricts. If the recipient has not requested PDF/A, converting solely for a label may add work and potentially remove functionality. Conversely, if a contract, regulator or archive specifies PDF/A, follow that requirement and validate the result.

Before submitting an important record, check file naming, page order, embedded fonts, metadata, bookmarks, signatures and the recipient’s size limits. Ask the receiving system about acceptance rules when they are unclear. A validated PDF/A can support preservation, but it cannot fix inaccurate content or replace proper records governance.

Practical checks and workflow recommendations

A preservation plan should identify which file is the source of record, which copy is the archival rendition and which validation report belongs to each version. Use filenames or a records system that links these artifacts without relying only on a folder name. If a conversion fails validation, retain the failure report while troubleshooting so the reason for remediation is documented rather than lost.

Do not confuse PDF/A conformance with accessibility, authenticity or confidentiality. A PDF/A file can still contain inaccurate content, be difficult for screen-reader users, or include information that should not have been disclosed. Conversely, adding a digital signature or encrypting a PDF does not automatically make it PDF/A compliant. Treat format conformance, access control, signature validation and accessibility as separate checks in the workflow.

For color-critical material, confirm that the output’s appearance is acceptable on a calibrated or otherwise suitable display and that required color profiles are present. For text-heavy records, inspect font embedding and Unicode extraction. For documents with forms, attachments or signatures, ask the archive owner which features must be preserved and which conformance profile it accepts before converting a large collection.

If an organization is migrating thousands of files, pilot the process on a representative set before bulk conversion. Include files with different fonts, page sizes, scans, annotations and unusual content. Compare validator reports and visual results, estimate exception-handling effort, and document the approved settings. A controlled migration is more reliable than applying a single default preset to every file.

Examples and edge cases

Example: a scanned contract is converted to PDF/A and passes a validator, but its OCR text contains an incorrect date. The format can be conformant while the document content remains wrong. A complete archive workflow checks both technical conformance and content accuracy. Validation reports should be stored with the exact file they describe, and the original scan should remain available according to retention policy.

If an organization receives PDFs from many departments, establish a documented intake profile: accepted PDF/A version, required metadata, filename convention, validation tool and exception process. Staff should know what to do when a file fails, rather than repeatedly re-saving it until a warning disappears. Consistent handling makes the archive more auditable and reduces silent data loss.

Do not convert signed documents without checking signature requirements. A conversion or optimization step may change the bytes and invalidate an existing signature even if the page appearance remains the same. Preserve the original signed artifact, create a separate archival derivative only when permitted, and record the relationship between the two versions.

A final review checklist

Before an archive conversion, confirm the required PDF/A profile with the receiving repository and identify who owns validation. Test a representative set of documents, including scans, forms, signatures, unusual fonts and color-heavy pages. Keep validation reports linked to the exact output files and define what happens when a file fails. Do not replace the source until the archival copy has been validated, visually reviewed and accepted under the organization’s retention procedure.

Related PDFKaj tools

Use Merge PDF, OCR PDF, Compress PDF or browse the full tool directory where relevant to your task. Tool availability and behavior vary by feature, so read each tool’s privacy notice and verify the output.