PDF/A for your thesis: what to check before you submit
Most rejections are not about your writing. They are about the file: a font that was not embedded, a document without a title, transparency in a profile that forbids it. Here is what PDF/A actually asks for, and how to confirm your file meets it before the deadline.
What PDF/A actually requires
PDF/A is an ISO archive profile (ISO 19005). A conforming file embeds every font it uses, carries no encryption or password, does not depend on content stored outside the file, and writes its metadata into the file itself. That is why archives and repositories ask for it: the document still renders the same decades later, on a machine that never saw your fonts.
PDF/A constrains how the file is stored, not how it looks. Pagination, spacing and typography should be identical to the version you previewed — if they are not, the renderer changed, not the conformance step.
Which variant does your school want?
- PDF/A-1b — the oldest part of the standard still in common use. No transparency, no JPEG2000 images.
- PDF/A-2b — the revision most tools produce today. It allows transparency and JPEG2000, so charts, logos and shaded tables survive unchanged.
- PDF/A-3b — like 2b, but it also allows embedded attachments (spreadsheets, data files, source code).
- If the requirement only says “PDF/A”, ask which revision their checker enforces. A 2b file is the usual safe reading of a bare “PDF/A” requirement, but that call is theirs.
- Our exporter produces PDF/A-2b natively, which covers the widest range of modern documents without dropping transparency.
Five checks before you hit submit
- Every font is embedded — check the file properties; “embedded” must be true for each font, not just the ones you recognise.
- The file opens without a password, and its permissions do not block printing or copying text.
- The document title and language are set in the metadata. Repositories expect both, and screen readers need them.
- Page size matches what the template asks for. A4 versus Letter is one of the most common rejection reasons, and it is invisible on screen.
- Transparency and annotations behave as the profile allows: 2b keeps them, 1b cannot. A 1b conversion that fails is almost always a transparent image or a highlighted annotation.
Getting PDF/A from Markdown
Markdown says nothing about PDF/A; the export pipeline decides. Ours renders through a print engine that emits PDF/A-2b natively, instead of producing a normal PDF and re-writing it afterwards — so the file you download is the one that was laid out, not a conversion of it.
If your school insists on PDF/A-1b, our exporter does not produce it. The usual blocker is transparency: flatten figures to PNG (or drop the alpha channel), then use a separate 1b converter. That is the single most common cause of a 1b conversion that fails validation.
Questions we get
Is PDF/A the same as PDF/UA?
No. PDF/A is about long-term archiving; PDF/UA is about accessibility — tags, alt text, reading order. A file can conform to both, but they are checked by different tools. If your school names one, produce that one and do not assume the other covers it.
Will exporting PDF/A change my layout?
It should not. PDF/A constrains storage — embedded fonts, no encryption, XMP metadata — not typography. If your pagination shifts, the rendering changed, not the conformance step.
My school asks for PDF/A-1b. Can I send PDF/A-2b?
Ask them. 2b is a later revision of the same standard and most validators accept it, but the requirement is theirs to interpret. We produce 2b (and 3b/3a/4e/4f) today; we do not produce 1b. A 1b file requires a separate converter, and transparency is the usual blocker.