PDF/A

Render a PDF/A document with pdfa.

const pdf = await render(invoice, {
  pdfa: "3b",
});

Conforming output includes an sRGB output intent and XMP metadata. Fonts are always embedded and subset, with or without PDF/A.

Levels

The u levels add no output cost. Takumi always writes ToUnicode maps.

PDF/A-3 allows arbitrary file attachments. ZUGFeRD and Factur-X electronic invoices expect "3b".

PDF/A-1 is not offered. It prohibits transparency.

Validation runs during rendering. When a document cannot conform, the render fails with the violated rule instead of writing a broken file.

Every level, and PDF/UA-1, passes veraPDF, the reference validator.

Tagged output

tagged defaults to true. Tagged output mirrors Chromium's print-to-PDF.

Set tagged: "ua1" to also validate against PDF/UA-1:

const pdf = await render(report, {
  pdfa: "2a",
  tagged: "ua1",
  lang: "en",
  metadata: {
    title: "Annual report",
    creationDate: "2026-08-06",
  },
});

The structure tree comes from the HTML semantics:

Set tagged: false to skip the tree when file size matters more than accessibility.

Invalid combinations are TypeScript type errors. pdfa: "2a" and pdfa: "3a" forbid tagged: false. pdfa: "4" forbids tagged: "ua1", because PDF/UA-1 is PDF 1.7-only and PDF/A-4 is PDF 2.0.

Validators require inputs the renderer cannot supply:

• lang is the document language. A-levels and PDF/UA require it.
• metadata.title is required by PDF/UA.
• metadata.creationDate is required by the a levels. Use UTC "YYYY-MM-DD" or "YYYY-MM-DDTHH:MM:SS". A fixed date keeps output byte-identical across runs.

PDF/UA also requires a document outline. Takumi generates it from headings.