A CSS-paged-media typesetter: feed it one self-contained HTML document whose CSS carries the print design, and it renders a paginated, print-ready PDF - the "LaTeX-quality output from HTML" workflow, no JavaScript in your document required. The renderer loads your file in headless Chromium in print media mode and prints with page-size-from-CSS on and backgrounds on. Two engines: Paged.js, the open-source (MIT) W3C paged-media polyfill, is the default and implements the parts browsers do not - crop and registration marks (the marks property), bleed, running headers and footers through margin boxes like @top-center with string-set chapter titles, page and pages counters, named pages, generated content for lists and footnotes - it chunks your content into fixed page boxes and draws the marks outside the trim. Native Chromium is the fallback engine: Chrome 131+ implements @page sizes, margins and all sixteen margin-box regions natively, which covers many designs, but mark rendering is limited, which is why the polyfill exists. Use Auto to pick Paged.js whenever the bundled polyfill is available and fall back to native otherwise. Practical notes: keep the document self-contained (inline styles, data-URI images) since the renderer has no network fetches; @page size accepts any CSS length or named size plus landscape; the PDF page box grows by the bleed amount so marks and bleed land outside the trim, ready for the print shop; and complex scripts are laid out with the system fonts of the render host. The report metadata records the engine used and the number of pages Paged.js laid out, so you can verify the pagination before sending it to print.