How to Convert a PDF to PDF/A for Long-Term Archival (2026 Guide)
PDF/A is the archival standard that libraries, courts, and ISO-9001 QMS require for 30+ year retention. This guide explains when you need it, how PDFMint prepares PDFs for PDF/A compliance, and how to validate the result.
Your national archive, university library, or ISO-9001 QMS requires all records in PDF/A format for 30+ year retention. PDF/A is strict: it forbids external references, JavaScript, encryption, and requires all fonts to be embedded. Regular PDFs almost never qualify out of the box. PDFMint does not ship a dedicated PDF/A button — true PDF/A conversion requires heavy server-side font and color-space analysis. What PDFMint does provide is a browser-based workflow that handles the common preconditions (font embedding via re-compression, transparency flattening, metadata cleanup) so your PDF is as close to PDF/A-2b as a browser tool can get. You then validate the result with the open-source veraPDF validator before committing to archival. This guide walks you through that workflow step by step and explains when you genuinely need Adobe Acrobat's Preflight or LibreOffice --convert-to pdf instead.
PDF/A validation is not 100% automatic. Highly customized source PDFs may still fail strict auditors like veraPDF. For legal-grade archival, validate the result with veraPDF before filing.
Use This Tool Now
Start by running your PDF through PDFMint's compression and metadata cleanup — these handle most PDF/A preconditions. Then validate with veraPDF.
Open Compress ToolStep-by-Step Guide
- 1
Open the PDFMint tool
Navigate to pdfmint.app/office-to-pdf in any modern browser (Chrome, Edge, Safari, Firefox, or Brave). There is nothing to install and no account to create. When you first open the page the tool library loads once (around 200KB of JavaScript) and then runs entirely on your device for every subsequent operation.
- 2
Add your file
Drop your regular PDF. PDFMint normalizes it first by flattening transparency, embedding all fonts via the compress pipeline, and stripping JavaScript and encryption — all steps PDF/A requires.
- 3
Configure the operation
Configure the compression preset (start with 'Max' to preserve fidelity for archival) and enable 'Embed all fonts' if the option appears. PDF/A requires every font used on every page to be embedded as a subset — this is the single most common reason a regular PDF fails validation.
- 4
Run the operation
Click Compress (the underlying pipeline PDFMint recommends for PDF/A preparation). The compress workflow embeds all fonts as subsets — the single most common PDF/A precondition. After this step, run the result through veraPDF's online validator to confirm PDF/A-2b compliance before committing to your archive.
- 5
Download and verify
Download the resulting PDF. Run it through veraPDF's online validator or CLI to confirm PDF/A-2b compliance. For legal-grade archival, keep the validator report next to the file as proof of compliance.
- 6
Optional follow-up
Optional: after PDFMint's preparation, upload the result to veraPDF's online validator (https://verapdf.org/) to check PDF/A-2b compliance. If it passes, archive the file with the validation report attached. If it fails, note which specific rules were violated and either fix manually or use Adobe Acrobat Preflight for a guaranteed pass.
Tips
- PDF/A-2b is the most common archival target — it is strict enough for legal retention but lenient enough to handle modern PDFs. PDF/A-1 rejects transparency which most 2020+ PDFs use.
- PDFMint Pro runs a PDF/A-2b normalization pass that embeds fonts, flattens transparency, and strips non-compliant objects.
- Adobe Acrobat's PDF/A conversion is reliable but requires a $239/year subscription; most free tools ignore the spec and simply rename the file.
- After conversion, validate with veraPDF (the open-source PDF/A validator) before committing to archival. PDFMint gives you a PDF/A candidate, not a guaranteed pass.
- Bookmark pdfmint.app/office-to-pdf to re-open the tool in one click next time. It works offline after the first load in most browsers.
Frequently Asked Questions
Can PDFMint produce a certified PDF/A that will pass a strict archivist audit?
PDFMint produces a 'PDF/A candidate' — we handle font embedding, transparency flattening, JavaScript removal, and decryption, which covers the common PDF/A-2b preconditions. For a guaranteed pass we recommend validating the result with veraPDF (free, open source). If your archivist uses a stricter PDF/A-2a or PDF/A-3 baseline, use Adobe Acrobat Preflight as the final step.
Are my files uploaded anywhere?
For browser-native features, no. PDFMint Pro runs a PDF/A-2b normalization pass that embeds fonts, flattens transparency, and strips non-compliant objects.
How does this compare to Adobe Acrobat, Smallpdf, or iLovePDF?
Adobe Acrobat's PDF/A conversion is reliable but requires a $239/year subscription; most free tools ignore the spec and simply rename the file.
Why does PDFMint not have a dedicated PDF/A button like Acrobat?
Because true PDF/A conversion requires font subset analysis, color space normalization and embedded ICC profiles — each of which is a heavy server-side operation. Our /compress pipeline handles the most common preconditions (font embedding, transparency flattening) but cannot guarantee spec compliance in every case. For guaranteed PDF/A-2b, use Adobe Acrobat's Preflight or the open-source LibreOffice --convert-to pdf pipeline and validate with veraPDF.
What specifically does PDFMint do to prepare a PDF for PDF/A-2b without claiming full compliance?
Four steps: (1) flatten transparency by rasterizing affected regions, (2) force font embedding via the compression pipeline's font-subset rewriter, (3) strip JavaScript actions and form-submit URIs, (4) remove encryption. What we do NOT do: color-space normalization to DeviceRGB/CMYK with ICC profiles, and tagged-PDF structure generation. That is why we recommend veraPDF validation and, for guaranteed compliance, Adobe Acrobat Preflight.
What PDF/A features does PDFMint NOT handle — and when do I need Adobe Acrobat instead?
PDFMint's workflow does not cover color-space normalization (converting RGB to calibrated DeviceRGB with ICC profiles) or tagged-PDF generation — both strictly required by PDF/A-2a. For PDF/A-2a (accessibility-compliant) or for veraPDF guaranteed passes, you must use Adobe Acrobat Preflight or LibreOffice with the full PDF/A export dialog enabled.
Related Tools
Related Articles
- How to Convert an Excel Workbook to PDF (2026 Guide)You need to ship a 6-sheet financial model as a single PDF, with print areas respected. This guide shows the privacy-first way — entirely in your browser, no uploads, no sign-up.Read more
- How to Completely Strip PDF Metadata for GDPR/APPI Compliance (2026 Guide)Your DPO requires that every PDF shared externally has /Author, /Creator, XMP, and document ID stripped before release. This guide shows the privacy-first way — entirely in your browser, no uploads, no sign-up.Read more
- How to Password-protect a PDF (2026 Guide)You need to send payslips to 20 employees and require each to open their file with a password. This guide shows the privacy-first way — entirely in your browser, no uploads, no sign-up.Read more
Ready to get started?
No sign-up required. Your files never leave your device.
Open Compress Tool →