PDF to PDF/A
Add the PDF/A identification metadata archives and records systems look for — entirely in your browser, no upload required.
What Is PDF to PDF/A?
PDF/A is an ISO-standardized version of PDF (ISO 19005) built specifically for long-term archiving. It requires a document to be fully self-contained — everything needed to display it correctly, embedded directly in the file — so it keeps looking exactly the same decades from now, regardless of what software or fonts happen to be available at the time.
This tool adds the metadata identification block PDF/A-aware archives, records systems, and government filing portals look for when checking whether a document is tagged as PDF/A.
Why Tag a PDF as PDF/A?
Ordinary PDFs can rely on things that aren't guaranteed to exist forever — a specific font installed on the viewer's system, external files it links to, encryption that depends on software still being able to read it. PDF/A exists precisely to remove those dependencies for documents meant to be readable indefinitely: court records, medical files, government archives, and other documents with long retention requirements.
Many institutions — courts, libraries, regulatory bodies — require or strongly prefer PDF/A specifically because of that guarantee.
How This Tool Works
This tool runs entirely in your browser. It adds the PDF/A identification metadata (XMP) an archiving system checks for, locally, in your device's memory — your file is never uploaded to any server.
This is metadata tagging, not a full ISO 19005 conversion: it doesn't verify or fix font embedding, convert color spaces, or remove PDF features that full compliance disallows. For a document where full, certified PDF/A compliance genuinely matters, validate the result with a dedicated tool like veraPDF afterward.
PDF/A Metadata Tagging vs Full PDF/A Conversion
"Convert to PDF/A" can mean two different things depending on the tool. Here's how the quick metadata tagging this tool does compares to a full, validated conversion.
| Consideration | This Tool (Metadata Tagging) | Full PDF/A Conversion (Acrobat Pro, LibreOffice) |
|---|---|---|
| Adds PDF/A identification metadata | Yes | Yes |
| Verifies all fonts are embedded | No | Yes |
| Converts color spaces / adds ICC profile | No | Yes |
| Strips disallowed features (encryption, JavaScript) | No | Yes |
| Passes a formal PDF/A validator (veraPDF) | Not guaranteed | Yes, when done correctly |
| Speed | Seconds | Minutes, requires the software installed |
Use This Tool When
- You need a quick, no-install way to add PDF/A identification to a document
- Full ISO 19005 certification isn't a hard requirement for your use case
- You're preparing a document for a system that checks for PDF/A metadata but doesn't run a strict validator
Use a Full Conversion Tool When
- You need a document to pass formal PDF/A validation (a legal filing, a regulated archive with strict acceptance checks)
- The source PDF has non-embedded fonts, transparency, or other features that need to be corrected, not just tagged
- Certified compliance is a contractual or regulatory requirement
Common Scenarios for Tagging a PDF as PDF/A
Submitting to a System That Checks for PDF/A Metadata
Some intake portals and document management systems check a file's metadata for PDF/A identification before accepting it, without necessarily running a full compliance validator. Tagging the file first can clear that check.
Preparing Records for Internal Long-Term Storage
Internal archives that don't require formal certification, but still want documents tagged consistently as intended-for-archival, benefit from a quick pass that marks files as PDF/A without needing dedicated conversion software.
Building a Reference Archive with Traceable IDs
When tagging documents for long-term storage, it often helps to assign each one a unique reference ID for your own indexing, independent of the file's metadata. Our UUID Generator can generate one for each document as you build out an archive.
Getting a Head Start Before Formal Certification
If a document will eventually go through a full, certified PDF/A conversion process, tagging it here first — and fixing any embedding or color-space issues surfaced by a validator afterward — can narrow down what still needs attention in the dedicated tool.
Standardizing Metadata Across a Document Set
When preparing a batch of documents for an archive, consistent PDF/A identification metadata across all of them makes the set easier to catalog and search, even before considering full validation on each one.
Other Ways to Convert PDF to PDF/A
You can also convert a PDF to PDF/A using Adobe Acrobat Pro's "Save As Other → Archive PDF" tool, or LibreOffice's Export As → PDF/A option. FileCast is useful for quick PDF/A metadata tagging without either installed — for full ISO 19005 compliance verification, a dedicated validator like veraPDF is still the authoritative check.
Frequently Asked Questions
Is it safe to use this tool on my PDF?
Yes. This tool processes your file entirely in your browser. Your PDF is never uploaded to any server — everything happens locally on your device.
Does this make my PDF fully PDF/A compliant?
Not on its own. This tool adds the PDF/A identification metadata an archiving system looks for, but full ISO 19005 compliance also requires all fonts to be embedded, a correct color profile, and the removal of disallowed features like encryption or JavaScript — this tool doesn't check or fix any of that. For guaranteed, certified compliance, validate the result with a dedicated tool like veraPDF.
Which PDF/A level should I choose?
PDF/A-2B is a reasonable default for most documents — it's widely accepted and supports more modern PDF features than PDF/A-1B. PDF/A-1B is the most conservative and broadly compatible option. PDF/A-3B additionally allows embedding non-PDF/A attachments, useful if your document needs to carry the original source file alongside it.
Will tagging change how my document looks?
No. This tool only adds metadata — it doesn't alter the visible content, fonts, or layout of your document.
What if my PDF has non-embedded fonts?
This tool doesn't detect or fix that. A document with non-embedded fonts won't reliably pass a strict PDF/A validator even after tagging, since font embedding is a hard requirement for genuine compliance, not just a metadata flag.