PDF Generation

Turn application data into
a finished PDF

Design reusable templates with HTML, CSS, or our visual editor, pass dynamic JSON payloads, and generate high-fidelity PDFs via REST API, SDKs, or webhooks.

Start Free Read the PDF docs

Free account · No credit card required

Choose the source that already owns the content

Reusable PDF templates

Start with a gallery layout or build a custom template with HTML and Nunjucks. Send JSON for the names, dates, totals, images, and other values that change on each document.

Browse PDF templates

HTML to PDF

Send raw HTML when your application already produces the document markup. Chromium renders JavaScript, Bootstrap or Tailwind styles, custom fonts, and modern CSS layouts into the PDF.

Read the HTML-to-PDF docs

URL to PDF

Render an existing webpage as a PDF instead of recreating its HTML. Loading controls wait for scripts and late content, while cookies or basic authentication open protected pages.

Read the URL-to-PDF docs

Draft a template from a description

Describe an invoice, report, certificate, or other layout and generate a starting template in HTML and CSS. Refine it through the assistant or open it in the visual editor.

See template generation

Start from a template when the layout should stay stable

Start with a ready-made template or design one from scratch in our visual editor. Separate your layout from dynamic data, then trigger document renders on demand via REST API or no-code integrations.

Template gallery: begin with an existing invoice, report, certificate, or other document layout
JSON data: populate names, totals, dates, images, and repeating records without editing the template
No-code automation: connect a template to a Zapier trigger when another application should start the render
Visual editor: change the document structure and styling in the browser
Generated starting points: describe the required layout, then inspect and refine the resulting template

Browser rendering

Use browser layout rules to produce a paged document

Chromium renders the HTML, CSS, web fonts, and JavaScript supplied for the document. That means an application can reuse familiar web layout tools instead of learning a separate drawing format for PDF output.

Choose A4, Letter, Legal, or custom dimensions on the request. Set margins, orientation, repeating headers and footers, page numbers, and print-specific styles for the output that the recipient will download or print.

Use @page, orphan and widow rules, and CSS break-before or break-after when browser flow alone would split the wrong content. Long tables can continue onto another page while retaining the context readers need.

Repeating headers and page numbers

Place page numbers, dates, and document titles in headers or footers that repeat throughout the file.

Print-specific CSS

Use @media print to hide navigation, change colors, and adjust the layout for a paged document.

Controlled page breaks

Allow normal pagination for flowing content, then use CSS break properties where a table, list, or section must stay together.

Standard or custom page sizes

Select a built-in paper size or set a custom width and height, with portrait or landscape orientation per render.

Decide how growing content moves onto the next page

A template that looks right with sample data can fail when a real table or section grows. Rows can split at the paper edge, later pages can lose their column labels, and totals can become detached from the values they summarize. The renderer provides granular pagination controls to manage how flowing content breaks across pages.

Keep each table row on one page Repeat column labels on page 2 Keep the total beside the table

Statement Northwind Ltd.

Date	Reference	Detail	Amount
02 Sep	TX-4411	Storage, September	$148.00
04 Sep	TX-4419	Render volume, tier 2	$312.50
09 Sep	TX-4430	Support retainer	$96.00
14 Sep	TX-4448	Storage, overage	$41.25

Page 1 of 2

Statement continued

Date	Reference	Detail	Amount
18 Sep	TX-4452	Render volume, tier 3	$508.00
23 Sep	TX-4467	Priority queue	$120.00
27 Sep	TX-4471	Storage, October advance	$148.00

Total due $1,373.75

Page 2 of 2

The demo uses standard print behavior: break-inside, a repeated thead, and a rule that keeps one block with the content above it. Write those rules in CSS or let the designer apply them to the template.

The rest of the page setup is explicit on the template or request.

Choose A4, Letter, Legal, or a custom size expressed in inches or millimeters.
Set orientation and margins for the document being produced.
Repeat headers and footers while filling in page numbers, dates, and other values.
Add cover-page treatment, page backgrounds, or a forced break before a new section.

Configure layout and render options directly on the request so page dimensions and formatting match each specific document.

Keep document rules in the template

Invoices and receipts with variable line items

Loop over line items with a Nunjucks for tag, format currency with a filter, and show terms, tax, or discounts only when the data requires them. Repeating table headers keep later pages understandable when the list grows.

Reports and certificates with richer content

Render charts from libraries such as ApexCharts or Chart.js inside the template. Use section-specific headers, conditional branding, cover pages, and a table of contents when the document needs more structure than a single flowing page.

Send the finished PDF to the system that owns it

Receive generated PDFs inline in your API response, store them in our global CDN, or deliver them directly to your own cloud storage buckets without intermediary hops.

Inline binary: stream the PDF bytes in the HTTP response for immediate server-side handling or download
Base64: return an encoded string when the receiving payload or datastore expects one
CDN URL: keep the file in managed storage and return a download URL with configurable expiration
Webhook: notify your endpoint when an asynchronous render is ready
Cloud forwarding: place the generated PDF in your S3 or Google Cloud Storage bucket during the workflow

PDF request controls

Page layout per render

Set margins, orientation, and a standard or custom paper size on the request producing the document.

Merge generated and existing PDFs

Combine documents in one call to add a cover sheet, append supporting files, or assemble report sections.

Asynchronous rendering

Queue a longer render, receive its job ID, and notify a webhook when the document becomes ready.

Dynamic headers and footers

Repeat custom HTML with page numbers, document titles, dates, and separate first-page treatment.

Nunjucks template logic

Use loops, conditions, and filters in one template, then supply different JSON on each request.

Output routing

Return binary, base64, or a managed URL; notify a webhook; or forward the file to S3 or Google Cloud Storage.

Generate the document when the business event happens

A closed deal needs an invoice

Let the CRM trigger a render when the deal closes. The API fills the invoice template from that record, then the workflow can email the customer and file a copy in Google Drive.

New reporting data needs a document

Have a scheduled job send current dashboard data to a report template. Chromium renders the charts and tables, and the workflow delivers the resulting PDF through Slack or email.

A completed order needs a receipt

Use the order webhook to populate line items, totals, and shipping details in a receipt template, then attach the finished PDF to the confirmation message.

Official SDKs

Available on GitHub

Payment gateways

Accept payments on forms

E-signature providers

Triggered from submissions

Batch rendering

Plan for the monthly run, not only one document

One invoice is a single request, but monthly statements create a concentrated batch with a delivery deadline. Published plans support up to 100,000 renders per month, while the job path and concurrency limit determine how that batch moves through the system.

In asynchronous mode, each request returns a job ID without keeping the render connection open. A webhook reports completion, and the plan states how many documents render at once: 2 on the entry tier, 8 on Business, and 25 on Enterprise.

Route each finished file through the channel required by the run: response bytes, a managed URL, or direct forwarding to your S3 or Google Cloud Storage bucket. Included storage runs from 5 GB to 1 TB, with flexible delivery options for routing completed documents.

When one recipient needs several parts, merge generated pages with a cover sheet and an existing appendix before delivery. The result is one ordered file instead of several attachments that the recipient has to interpret.

Track asynchronous work by job ID

Return a job ID, process the document outside the request connection, and report completion through a webhook.

Use the plan's concurrency limit

Model batch throughput against 2, 8, or 25 simultaneous renders, depending on the selected tier.

Configure render retries

Choose retry conditions, attempt count, and delay. If webhook delivery misses, the result remains available through the Jobs API.

Assemble one delivery file

Merge cover sheets, generated pages, and existing PDFs before routing the completed document.

Keep fields interactive when the recipient has more to add

Preserve fillable fields

Generate a PDF with real form fields instead of flattened boxes so the recipient can enter the remaining values in Acrobat, Preview, or a browser. Interactive form fields ensure recipients can easily complete and submit their parts of the document.

Place signature elements in the document

Keep a signature field in the intended document position. Capture it with the form or hand the file to a connected signing provider when that provider's ceremony is required.

Import a PDF that already has the right layout

Upload an existing form, detect its fields, and correct the mapping where needed. Preserve the original layout when recipients need the document they already recognize.

Pair the PDF with a responsive web form

Let someone enter data through a phone-friendly form while the uploaded PDF updates beside it, avoiding direct navigation of a print-sized page on a small screen.

Apply delivery and retention rules to the finished file

Add an open password

Protect the generated PDF with an open password when access to the delivery channel alone should not reveal its contents.

Use one retention policy across document types

Produce regulated and ordinary documents through the same workflow so retention, deletion, and access policies do not depend on a separate generation tool.

Produce several outputs from one submission

Use one set of answers to create a contract, summary, and internal copy, or select a document variant from the submitted values.

Questions about PDF generation

How do I generate a PDF from HTML?

Send HTML to the PDF endpoint and receive the rendered document. The same endpoint also accepts a webpage URL or a stored template ID when raw HTML is not the source.

Can I use CSS frameworks and web fonts?

Yes. Chromium renders Tailwind, Bootstrap, custom web fonts, flexbox, grid, and JavaScript using the same browser standards as a webpage.

How do I add page numbers, headers, and footers?

Include header and footer templates in your request. They repeat cleanly across pages and dynamically insert values such as page numbers, titles, and dates.

What page sizes are supported?

A4, Letter, and Legal are built in, and you can specify custom width, height, margins, and orientation on any request.

How do I generate PDFs in bulk?

Use asynchronous mode. Each request returns a job ID immediately, and a webhook can notify your system when the document is ready instead of requiring a polling loop.

Can I merge several PDFs into one file?

Yes. Send generated or existing documents to the merge endpoint and receive one combined PDF for uses such as statement packets, cover sheets, and multi-part reports.

What controls does the PDF renderer expose?

You can configure full layout and print settings per render. Margins, headers, footers, page dimensions, orientation, scale, and background graphics can all be adjusted on each request rather than fixed in the template.

What does a PDF cost to produce?

One finished document counts as one render regardless of whether its source is HTML, a URL, or a template. Plans start at $9 per month for 1,000 renders, and the free account includes 50 without a card. Page count and file size have separate plan limits.

Can the PDF be filled in after it is generated?

Yes. You can output interactive PDF forms with real input fields instead of flattening values into the page. This is ideal when your application fills out initial data and a customer or partner completes the rest.

How do I get the finished file where it needs to go?

Choose how each document is delivered. Return the PDF directly in the API response, retrieve it from managed storage via the Assets API, or forward it automatically to your S3 or Google Cloud Storage bucket.

Need image output too? Generate it from the same template.

Generate the PDF
from the source you already have

Create an account and render a document from HTML, a webpage URL, or a reusable template.

Start Free

No credit card required.

Turn application data into a finished PDF