HTML renderer

Browser-faithful HTML to PDF

Give Jetformat a report, invoice, dashboard, or public URL. It renders the page into a PDF while your agent keeps the workflow deterministic.

One command

Web output without rebuilding the document.

Use the same prebuilt Jetformat binary for Office conversion and HTML rendering. Keep the source page and generated PDF in your existing agent workflow.

CLI
jetformat html to-pdf page.html -o page.pdf --server 127.0.0.1:8080
CLI
jetformat html to-pdf https://example.com/report -o report.pdf --wait-ready ".report-ready"

For product teams

Turn the page customers already approve into the artifact they send.

  • Invoices and statements
  • Dashboards and scheduled reports
  • Contracts and customer portals
  • Charts and data-heavy web pages

The renderer endpoint is configured with --server or JETFORMAT_HTML_SERVER. Office and PDF commands remain fully local and do not need it.

HTML and CSS

Keep the layout rules you already use for reports, invoices, dashboards, and customer portals.

Assets included

Render local images, fonts, charts, and linked page assets in the same PDF job.

Wait for the page

Wait for a selector or a fixed delay before capture when JavaScript finishes the page.

Files or URLs

Pass a local file, a static directory, or a URL to the same command.

Built for the handoff from agent to PDF

Agents can prepare data and ask Jetformat to render the final page. Jetformat handles the browser-facing part, writes the PDF, and returns a concrete path for the next step.

1

Prepare

The agent fills the data or points to a URL.

2

Render

Jetformat waits for the page and captures the result.

3

Verify

The next command can inspect page count or render a preview.

Give the agent a real converter.

Install the CLI, then the GPT Skill or DeepSeek Harness plugin. The model runs jetformat. The PDF lands on disk.