What is PDF/A?
PDF/A is a family of ISO-standardised PDF profiles (ISO 19005) designed for long-term preservation. A normal PDF can depend on things outside the file, such as fonts that are not embedded or content that is fetched from elsewhere. A PDF/A file is meant to be self-contained: everything needed to display it the same way in the future is inside the file, and features that could stop working over time are restricted.
Organizations that keep records for years, such as courts, government agencies, libraries, archives, universities and finance departments, often require PDF/A for submissions or storage.
What the tool does
The converter makes a PDF look and be described more like PDF/A by adding key ingredients:
- XMP metadata and conformance information. This identifies the file as claiming a PDF/A level and carries standard metadata about the document.
- An embedded sRGB colour profile. PDF/A requires consistent colour definition, so an output intent with a standard profile is added.
These are two important building blocks of a PDF/A file, added directly in your browser without uploading anything.
An honest note on compliance
PDF/A compliance has many technical requirements: fonts must be embedded, transparency and certain features are limited, and colour spaces need to be defined. This tool is *best-effort*. It adds the metadata and profile pieces and rebuilds the file, but it does not run the output through a formal validator and cannot guarantee a document is fully compliant. A source file that uses non-embedded fonts or restricted features may still fail validation.
If compliance is a hard requirement, check the result with a dedicated PDF/A validator such as veraPDF, which is a freely available open-source validator. If the file passes, you are done; if not, the validator's report tells you what needs fixing.
When this tool is useful
- Your organization asks for "PDF/A" in general and uses a lenient intake process
- You want your archived PDFs to carry standard metadata and a colour profile
- You are preparing documents for long-term storage and will validate them separately
- You want a quick first step before a formal validation workflow
It is less suitable when a submission portal enforces strict validation and rejects anything that does not pass. In that case, produce PDF/A from the source application (for example, a "Save as PDF/A" option in word processors) and validate the result.
Tips for the best chance of a valid file
- Start from a clean source. Documents created from text with embedded fonts are the best candidates.
- Avoid encryption. PDF/A does not allow it, so remove passwords first.
- Flatten interactive features you do not need before converting.
- Check fonts. If the source PDF references fonts it does not embed, validation may flag them.
- Validate after converting, and keep both the source and converted versions.
Common mistakes
- Assuming "PDF/A" in the file name means it is compliant. Only validation can confirm that.
- Converting a protected PDF. Encrypted files cannot become PDF/A.
- Skipping the check for a regulated submission. Rejected submissions cost more time than validating once.
- Compressing afterwards in Aggressive mode. Re-rendering pages can change structure. If you need both, compress first with Compress PDF and convert last.
PDF vs PDF/A
A regular PDF is designed for flexible sharing and can contain features such as external references, audio, video and JavaScript. PDF/A restricts those features so the file will look the same decades from now. The trade-off is less flexibility in exchange for predictability.
Privacy
Records submitted for archiving are often sensitive. The conversion happens locally, and your document is not uploaded. See PDFHook vs upload-based tools.
Next steps
Related tools for archive-oriented work include OCR PDF for searchable scans, Page Numbers and Merge PDF.