PDF to PDF/A produces a copy carrying a basic PDF/A-1b archival identification. The tool first checks whether the font resources of the original PDF are embedded; if they pass, it rebuilds the document in the workspace's current page arrangement, writes pdfaid:part=1 and conformance=B XMP metadata plus an sRGB OutputIntent, sets the PDF version header to 1.4 and turns object streams off.

When unembedded fonts are found, the interface requires “whole-page rasterisation” before it will continue: pages are rebuilt at a fixed 150 DPI with JPEG quality 0.9, and the text layer goes with them. This is explicitly a best-effort basic conversion — it does not fix transparency, complex colour spaces or every other PDF/A rule — so run the result through veraPDF or another validator before submitting it to an archive.

1. 01Open an editable PDFselect the file on the left; an encrypted file needs unlocking first. Switching files makes the tool re-check font embedding in the original automatically.
2. 02Read the pre-conversion checkif all fonts are embedded, or the file has no font dependency, continue straight away; if unembedded fonts are listed, “rasterise whole pages before converting” must be turned on.
3. 03Run the basic conversionclick “Convert to PDF/A (basic)”; the tool fetches the sRGB ICC profile, rebuilds the document in the current page arrangement or rasterises at 150 DPI, and finally writes the XMP and the OutputIntent.
4. 04Validate outside the tooldownload <original-name>_PDFA.pdf and check it with veraPDF or whatever validator the receiving organisation specifies; if the ICC fetch failed, the interface warns that no embedded colour profile was written this time.

Compliance scope

only the PDF/A-1b identification XMP, the OutputIntent, basic metadata and the PDF 1.4 version constraints are written; transparency, colour space, font and other PDF/A violations are not all repaired.

Font gate

when unembedded fonts are found, whole-page rasterisation is mandatory; that mode is fixed at 150 DPI and loses the text layer, links, forms and other interactive structure.

ICC resource

the sRGB ICC profile is read from the browser cache first; if it is not cached, the tool tries the jsDelivr CDN, and a network failure degrades to an OutputIntent declaration with no embedded profile.

Page source

the font check works on the original file bytes while the actual conversion follows the current page arrangement on the right of the workspace, so rearranged, rotated or inserted pages are output as they stand.

What it does not do

it does not issue an archival compliance certificate and does not promise to pass every rule of veraPDF or an archival authority; validate against the recipient's specification before the real submission.

PDF content is always checked, rebuilt and exported locally in the browser and is never uploaded; on the first run or a cache miss the browser requests the sRGB ICC colour profile from the jsDelivr CDN and writes it into the browser Cache API for later use.