Reports & statements

Reports and account statements are long. They break into chapters, repeat a band on every page, and get navigated rather than read straight through.

Chapters

break-before: page starts a section on a fresh page. break-inside: avoid keeps a figure with its caption:

import { render } from "takumi-pdf";

const pdf = await render(
  <article>
    <section style={{ breakBefore: "page" }}>
      <h1>Results</h1>
      <figure style={{ breakInside: "avoid" }}>
        <img src="chart.svg" alt="Revenue by quarter" />
        <figcaption>Revenue by quarter</figcaption>
      </figure>
    </section>
  </article>,
);

Takumi has no orphans or widows control. A heading can land alone at the foot of a page. Wrapping the heading and its first paragraph in a break-inside: avoid box prevents that.

See Pagination for the full set of break properties.

Bookmarks

outline: true turns h1–h6 into PDF bookmarks. A reader opens the sidebar and jumps between chapters. Nesting follows heading depth:

import { render } from "takumi-pdf";

const pdf = await render(report, {
  outline: true,
  lang: "en",
  metadata: { title: "Annual report 2026", authors: ["Acme Inc."] },
});

A table of contents with working links is <a href="#section-id"> plus a matching id. See Links, outline & metadata.

Running bands

A report header usually names the document and the period. A footer usually carries the page counter:

import { render } from "takumi-pdf";

const pdf = await render(report, {
  header: (
    <div tw="flex w-full justify-between px-12 text-[10px] text-gray-500">
      <span>Annual report 2026</span>
      <span>Acme Inc.</span>
    </div>
  ),
  footer: (
    <div tw="flex w-full justify-center text-[10px] text-gray-500">
      <span className="pageNumber" /> / <span className="totalPages" />
    </div>
  ),
  margin: { top: 64, bottom: 64, left: 48, right: 48 },
});

Bands draw in the margin, so the margin has to be tall enough. Headers & footers shows how to derive the margin from the band.

Long tables

Takumi lays out tables as flex rows, and a header row does not repeat across pages on its own. Split the rows into groups and give each group its own header:

import "takumi-pdf";

<div tw="flex flex-col">
  {chunk(rows, 24).map((group, index) => (
    <div key={index} tw="flex break-inside-avoid flex-col">
      <HeaderRow />
      {group.map((row) => (
        <div key={row.id} tw="flex break-inside-avoid gap-3 pt-2 text-xs">
          <span tw="flex-1">{row.label}</span>
          <span tw="w-[100px] text-right">{row.amount}</span>
        </div>
      ))}
    </div>
  ))}
</div>;

break-inside-avoid moves a group that no longer fits to the next page, header and all. Pick a group size that underfills a page, or the group stops fitting anywhere and splits again.

Batches

Statement runs render the same template thousands of times. Construct one PdfRenderer and keep it. Fonts register once and are reused for every document:

import { PdfRenderer } from "takumi-pdf";
import { googleFonts } from "@takumi-rs/helpers";

const renderer = new PdfRenderer();
const fonts = await googleFonts(["Inter"]);

for (const account of accounts) {
  const pdf = await renderer.render(<Statement account={account} />, { fonts });
  await save(account.id, pdf);
}

Set tagged: false when nobody reads these with assistive technology. It drops the structure tree and the file gets smaller.

Accessibility

Public bodies often have to publish accessible documents. tagged: "ua1" validates the structure tree against PDF/UA-1 during the render. It builds on the heading outline above. See PDF/A for the rest of its inputs.