PDF to PDF/A

The source PDF's text is extracted page-by-page using smalot/pdfparser, since PDF/A conformance requires rebuilding the document with self-contained fonts and metadata rather than simply relabeling the original file.

That extracted text is reassembled into a structured HTML document — preserving page breaks and using simple heuristics to keep all-caps section titles styled as headings — which is then rendered by mPDF with PDF/A mode explicitly enabled, targeting your chosen conformance level (1-B, 2-B, or 3-B).

mPDF embeds all necessary fonts and metadata directly into the output file to satisfy PDF/A's self-containment requirements, producing a document with the title, author, and subject fields set for archival record-keeping.

Your files are uploaded over an encrypted (SSL) connection. We don't store, read, or share the contents of your files — they're processed to generate your result and are not retained on our servers afterward.

• Preparing a document for long-term digital archiving that meets an institution's preservation standards.
• Submitting a filing to a court, government agency, or institution that specifically requires PDF/A format.
• Future-proofing an important record so it remains readable regardless of future software changes.

• Assuming PDF/A conversion is purely cosmetic — PDF/A embeds fonts and removes certain features (like external links to non-embedded content and encryption) specifically to guarantee long-term readability; some interactive elements may not carry over.
• Not checking whether your recipient specifically requires PDF/A vs. just any standard PDF — it's a specific archival standard, not a general-purpose format.

• If a court, government office, or institution asked for PDF/A specifically, confirm which PDF/A conformance level (A-1, A-2, A-3) they require, since this can vary by requirement.

We respect your privacy. All files are processed securely and are never sold, shared, or used for anything beyond generating your result.