Skip to content
DevToolKit

PDF to PDF/A Converter

Convert PDF to PDF/A archival format in your browser. Injects XMP metadata, sRGB output intent, and strips JavaScript — files never uploaded.

pdf

Drop your PDF here, or click to browse

Files are processed entirely in your browser — never uploaded

Processed locally
Was this tool helpful?

How to Use

Convert a PDF into a PDF/A-identified archival file in four steps:

  1. Upload your PDF -- Drag and drop a PDF or click the dropzone to browse. The tool scans the file locally and reports the page count, existing PDF/A markers, font embedding status, and how many non-archival items it found. Nothing is uploaded to any server.
  2. Choose a conformance level -- PDF/A-2b is recommended for most archives (it is based on PDF 1.7 and permits transparency and JPEG2000). PDF/A-1b targets PDF 1.4 structure for maximum strictness, and PDF/A-3b additionally allows embedded file attachments such as XML invoice data.
  3. Convert -- Click "Convert to PDF/A". The tool strips JavaScript, document and page action triggers, multimedia annotations, and XFA form data, then injects the XMP identification packet and an sRGB OutputIntent required by the standard. An optional qpdf pass removes unreferenced objects.
  4. Review the archival health check and download -- The report shows exactly what was done: XMP injected, OutputIntent status, items stripped, and an honest warning if any fonts are not embedded. Download the result when you are satisfied.

Everything runs in your browser using pdf-lib and a WebAssembly build of qpdf. Your document never leaves your device, which makes this tool safe for confidential records, legal filings, and medical documents.

About This Tool

PDF/A is the ISO 19005 standard for long-term archival of electronic documents. Where a normal PDF can rely on external resources -- fonts installed on the reader's machine, linked media, JavaScript that may not run in twenty years -- a PDF/A file must be fully self-contained and reproducible. The standard exists so that a document archived today renders identically when it is opened decades from now, on software that does not yet exist. Government registries, courts, libraries, and records-management systems commonly require PDF/A for submissions and retention.

Three requirements sit at the heart of every PDF/A file, and this tool implements all three directly in your browser. First, an XMP metadata packet declaring the file's conformance: the tool injects an XML stream into the document catalog containing pdfaid:part and pdfaid:conformance in the official AIIM identification namespace, while mirroring your document's existing title, author, and dates so the Info dictionary and XMP stay consistent. Second, an OutputIntent describing the intended rendering device: the tool embeds a real ICC v4.3 sRGB color profile (548 bytes, validated through a color-management engine) and registers it on the catalog with the required /GTS_PDFA1 marker. Third, sanitization: JavaScript, document open actions, additional-action triggers, Launch actions, RichMedia and other multimedia annotations, and XFA form data are all forbidden by the standard and are stripped before the marker is written.

The conformance levels differ mainly in which underlying PDF version they target. PDF/A-1b is based on PDF 1.4, so it forbids transparency, JPEG2000 images, object streams, and file attachments -- the tool rewrites the file with a classic cross-reference table and a PDF 1.4 header for this level. PDF/A-2b is based on PDF 1.7, lifts those restrictions, and is the recommended default for most workflows. PDF/A-3b is identical to 2b except that it permits arbitrary embedded files, which is why e-invoicing formats like ZUGFeRD and Factur-X are built on it.

Honesty matters here: this tool produces a conformance-oriented PDF/A file. It adds the identification marker and required structures and removes the most common disqualifying constructs, but it cannot embed fonts that were never embedded in the source (the base-14 fonts like Helvetica are the usual culprit), and it cannot guarantee every content stream is fully color-managed. The health-check report surfaces those gaps rather than hiding them. If your workflow requires certified conformance -- for a court filing or a records system that runs validators on intake -- run the output through veraPDF, the industry-standard open-source PDF/A validator, as a final check.

Why Use This Tool

PDF/A conversion serves archival, legal, regulatory, and institutional workflows:

  • Regulatory and court filings -- Many courts and government portals require or prefer PDF/A for submissions. Converting before upload avoids rejection by automated intake validators that flag JavaScript, missing output intents, or absent archival markers.
  • Records management and compliance -- Retention policies under frameworks like ISO 15489 or industry regulations often mandate a stable archival format. PDF/A is the default choice because it is an open ISO standard rather than a vendor format.
  • Digital libraries and theses -- Universities and libraries require PDF/A for deposited dissertations and digitized collections, guaranteeing the documents remain readable as viewing software evolves.
  • E-invoicing -- European e-invoicing standards (ZUGFeRD, Factur-X, XRechnung) embed machine-readable XML inside a human-readable PDF/A-3 file. Choosing level 3b preserves those attachments instead of stripping them.
  • Stripping hidden scripts -- Even outside formal archiving, the sanitization pass is valuable on its own: it removes JavaScript, document-open triggers, and multimedia hooks that can execute unexpectedly or leak metadata.
  • Vendor-neutral preservation -- Unlike "optimize for archive" features in proprietary editors, this tool shows exactly which structures were added and which were removed, so you can defend the result in an audit.

Related tools: PDF Compress reduces file size for storage-bound archives. PDF Sanitize removes hidden metadata and scripts without adding archival markers. PDF Metadata Editor fixes titles and authors before conversion so the XMP mirrors clean data. PDF Flatten merges form fields and annotations into static page content, which improves archival stability. PDF OCR adds a searchable text layer to scans before archiving.

FAQ

Is the output a fully conformant PDF/A file?
The tool adds everything a PDF/A file needs to declare itself — the pdfaid XMP identification and an sRGB OutputIntent — and strips JavaScript, actions, and multimedia that would fail validation. Fonts that were never embedded in the source cannot be repaired in the browser, so run veraPDF on the result if you need certified ISO 19005 conformance.
What is the difference between PDF/A-1b, PDF/A-2b, and PDF/A-3b?
PDF/A-1b targets PDF 1.4 and forbids transparency, JPEG2000, and attachments — the strictest option. PDF/A-2b targets PDF 1.7, allowing transparency and JPEG2000, and is the recommended default. PDF/A-3b additionally permits embedded file attachments (XML invoices, source data).
What gets removed during conversion?
The sanitization pass strips JavaScript open actions, document and page additional-action triggers, JavaScript name trees, Launch and RichMedia actions, multimedia annotations, and XFA form data. For PDF/A-1b and 2b, embedded file attachments are also removed since those parts forbid them.
Is my PDF uploaded to a server?
No. Conversion runs entirely in your browser using pdf-lib plus an optional qpdf WASM cleanup pass. The file never leaves your device, which makes the tool safe for confidential records.
Why does the report warn about fonts?
PDF/A requires every font to be embedded so the document renders identically decades from now. If the source references fonts by name only (like the base-14 Helvetica), the tool reports the gap honestly — it cannot embed arbitrary font programs it does not have.