Skip to main content

Documentation

PDF Server renders predefined HTML templates to PDF using a headless browser (Chromium) driven over the Chrome DevTools Protocol. You author templates, test them with the built-in tester UI, and ship your own image built on the PDF Server base image.

New here? Start with the Quickstart, then author your first template.

Sections​

Each section is a self-contained answer for one kind of task, in reading order:

  • Template authoring — write one template that renders JSON to a PDF: engines, validation, styling, assets, partials, print timing.
  • Compositions — assemble one PDF from several documents with a data-driven plan.
  • Template workflow — run the server on your templates, preview in the tester UI, validate, and ship your own image.
  • Operations — deploy, size, and observe the service in production.
  • Security — the threat model and the hardening checklist.
  • Reference — HTTP API, CLI, endpoints, and status metadata.
  • Server development — modify or extend the Go server: architecture, internals, and extension points.