Why Convert HTML to PDF?

HTML is designed to be flexible and responsive — it adapts to screen size. PDF is designed to be fixed and exact — it looks identical on every device. When you need to share a web-based document as a fixed layout (for archiving, printing, or sending), converting HTML to PDF is the right approach.

Common use cases: generating invoices from web-based billing systems, archiving web pages, creating print-ready documents from email templates, and converting Markdown-rendered reports to PDF.

How Chromium Rendering Works

Our server uses a headless Chromium browser to render your HTML — the same engine that powers Chrome. This means:

• All modern CSS is supported: Flexbox, CSS Grid, custom properties, calc()
• Web fonts (Google Fonts, custom @font-face) load and render correctly
• JavaScript executes before the PDF is captured — dynamic content renders correctly
• External images and assets load if they're publicly accessible URLs
• CSS @media print rules are respected — style the print version separately

Controlling Page Breaks

Use CSS to control where page breaks happen in the PDF:

• break-before: page — force a page break before an element (e.g., each new section)
• break-after: page — force a break after an element
• break-inside: avoid — prevent a block (table, figure) from being split across pages
• orphans: 3 and widows: 3 — control minimum lines at start/end of a page

Setting Up Print Styles

For precise control, add a @media print block to your CSS:

• Hide navigation bars, sidebars, and footers that don't belong in the printed document
• Set explicit font sizes in pt (not px) for print accuracy
• Control margin sizes with @page { margin: 2cm; }
• Remove background colours that look good on screen but waste ink when printed

Generating PDFs Programmatically

Pro users can call our HTML-to-PDF endpoint via API to automate document generation — useful for invoice generators, report builders, and documentation pipelines. See the API documentation for details.