PDF to PDF/A
Processed in your browser. The file never leaves your device.
Frequent questions
It is the flavour of PDF meant to survive decades: everything needed to draw the document lives inside the file itself, with no dependence on installed fonts or external colour profiles. Plenty of public bodies and archives require it for exactly that reason.
Because a browser cannot embed a typeface that the original PDF only named — those fonts are on the machine the document was made on, not on yours. The honest output is to turn each page into an image, which is what the reference tools do too.
Run the document through our OCR tool with the PDF output first, then convert it here — or the other way round. OCR lays an invisible text layer over the page image, and that layer survives.
PDF/A-2b. The "b" is visual conformance: it guarantees the document renders identically, not that its structure is tagged for screen readers, which is what level "a" asks for.
We generate it on the fly from the published sRGB values. On a project whose whole point is that you can see what runs on your files, readable code beats a third-party binary whose licence nobody has read.
No. The whole conversion happens in your browser: drawing the pages, assembling the file, writing the metadata. Nothing travels over the network.