A regular PDF looks permanent, but it quietly depends on things outside itself: fonts installed on whatever machine opens it, scripts that only run while a viewer supports them, encryption that some future software may not honor. For a document that has to be readable in thirty years — a contract, a thesis, a public record — that's not good enough. PDF/A exists for exactly this case, and PDF to PDF/A converts your files to it entirely in your browser.
This guide explains what PDF/A is, who demands it, how the conversion works — and, in keeping with how we do things here, exactly where a browser-based conversion stops short of a guarantee.
What PDF/A actually is
PDF/A is an ISO-standardized version of PDF designed for long-term archiving. Where a regular PDF is allowed to lean on its environment, PDF/A requires the file to be self-contained: the fonts it uses are embedded inside it, no JavaScript is allowed, no encryption is allowed, and nothing the document needs in order to render may live outside the document. A PDF/A file renders the same decades from now regardless of what software opens it — because there's nothing left for the software to improvise.
The contrast with everyday PDF is worth making concrete. A normal report might reference Arial by name and trust your machine to have it; opened somewhere without Arial, it substitutes a different font and the layout shifts. It might carry scripts that animate a form, or a password that a future viewer may refuse. Every one of those is a bet on the future behavior of software. PDF/A is the format for people who don't want to bet.
Who asks for PDF/A
You usually meet this requirement the moment a document stops being correspondence and becomes a record:
- Courts and regulators — filing systems that must render filed documents exactly as submitted, indefinitely, accept archival formats for exactly this reason.
- National and state archives — institutions whose whole charter is opening files in fifty years with equipment that doesn't exist yet.
- Records-management policies — corporate retention schedules that measure document lifetimes in decades, not fiscal quarters.
- Universities and libraries — theses, dissertations, and deposits that become permanent holdings the day they're accepted.
The common thread: the submitting party is told "PDF/A" and handed a deadline. That's the moment you need a converter, not a debate about formats.
How to convert PDF to PDF/A
- Open PDF to PDF/A and drop in your file — up to 100 MB, processed in your browser.
- Confirm.
- Download the converted PDF.
There are no settings to configure — conversion targets PDF/A-1b automatically. One variant, one button, no conformance matrix to study before you start.
What the conversion changes
Three things happen to the file, and all three are genuine fixes rather than cosmetic relabeling. JavaScript is removed — archival documents don't get to run code. Encryption is removed — a record nobody can open is not a record. And PDF/A-1b identification metadata is added, marking the file's conformance claim so archival systems can recognize it.
For most documents that change nothing visible: the pages, text, and images are untouched, because the things being stripped were never part of the visible page in the first place.
The honest limit: fonts
Here is where a browser-based converter has to be straight with you. PDF/A wants fonts embedded in the file. This tool removes JavaScript and encryption and adds the identification metadata — but it can't embed fonts it doesn't have access to in your browser. If fonts in your original PDF weren't already embedded, they stay that way.
Why would a PDF have unembedded fonts? Its creator chose that. Standard system fonts your PDF assumes are installed — like Arial or Times New Roman — are sometimes referenced by name instead of embedded in the file. That decision was made by whatever tool created the original PDF, and it's not something any converter can fully fix after the fact in a browser.
So the tool does the next best thing, which is the honest thing: it tells you how many fonts are embedded, so you know where you stand before you submit anything.
Verify before you submit
If the receiving institution runs strict validation, don't guess — check. A strict validator like veraPDF will flag a file whose fonts aren't embedded, no matter what its metadata claims. The workflow that never fails this check:
- Convert with the tool and note the embedded-font count it reports.
- If fonts are missing, recreate the PDF from its source with font embedding switched on — most document exporters embed fonts by default — and convert that instead.
- Run the validator once on the final file if the submission matters.
Files that were exported properly in the first place — fonts embedded, no scripts, no password — sail through both the conversion and the validation. The closer your source PDF is to archival-grade already, the less there is to fix.
Files that convert cleanest
Since the conversion's one soft spot is fonts, you can predict your result from your source. The cleanest candidates are PDFs exported digitally from a document editor — a report saved from Word, a spreadsheet saved from Excel, a deck saved from PowerPoint. Serious exporters embed their fonts by default, so the file arrives self-contained and the converter has nothing left to fix beyond stripping scripts and encryption and stamping the metadata.
The files to double-check are the other kind: anything produced by an unknown tool, anything that opens with a password, and anything where the font count the tool reports comes back lower than you expected. Each is a reason to run the validator well before the submission deadline instead of the night before it. And if the document is a scan, remember that PDF/A describes how a file is stored, not what's in it: a scan converts as the image it is, and making it searchable is OCR's job, not the archivist's.
From document to record
PDF/A is usually the last step of a pipeline, not the first. The typical chain: write the document, export it to PDF (Word to PDF and Excel to PDF handle the common sources), then convert the finished PDF to PDF/A for the archive. If you also maintain the record's descriptive information, PDF Metadata Editor handles title, author, and dates before filing. And if decades of records are eating your storage, Compress PDF is the tool for the pile — after the archival copy is safely made.