HTML to PDF API

How it works

One authenticated call carries the page you want printed:

curl -X POST \
  https://webcapture.io/v1/convert \
  -H "Authorization: Bearer wc_your_key" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/report"}'

200 {"id": "cnv_9f2c01ab", "bytes": 34121, "remaining": 49,
     "download": "https://webcapture.io/v1/conversions/cnv_9f2c01ab.pdf"}

The response carries the finished document. Pass ?wait=false to get a job ticket instead and poll the status endpoint, or subscribe a signed webhook on Pro or Scale. This page is the summary, not the reference; the exact endpoint shape, the full option list, and the error codes live in the API docs.

The engine, stated

Every conversion renders in a real Chromium: a fresh browser context loads the page the way a user's browser would, and only then prints. JavaScript executes before the print, so client-rendered dashboards and single-page apps arrive complete instead of half-hydrated. Web fonts load from the page itself, so the output carries the typefaces the design calls for rather than whatever happens to be installed on the render host. Flexbox and grid print as displayed, because the engine doing the printing is the engine that did the layout. And there is no smart-shrinking to fight: the compensation scales and hand-tuned zoom workarounds that archived tools demanded have nothing to compensate for here, so migrated templates just lose them.

Pricing, legible

Every plan includes the full API, async jobs, polling, the MCP endpoint, and all output formats (PDF, PNG, JPEG, WebP, Markdown). Signed webhooks and higher concurrency start at Pro; Scale extends artifact retention to 30 days. There is no per-document overage: an exhausted quota returns 429 until the month rolls over. That policy is a feature, and its trade-off is named honestly: bursts beyond quota wait instead of billing, so the invoice never surprises anyone. Quotas are per account; when one pool is not enough, email us and we will size a plan.

Where it wins

• Fidelity pages: dashboards, invoices, and statements generated from live app views, where a converter without a browser engine drops the layout, the fonts, or the script-rendered content entirely.
• Scheduled reports: nightly or weekly jobs that print the same URL on every run and need the output to match the last run, which is what a deterministic render pipeline is for.
• Automation of record-keeping: pipelines that archive pages, receipts, or confirmations into a document store through the API and, on paid tiers, its signed webhooks, with nobody clicking print.

See for yourself

The claims above are checked against the alternatives: the best HTML to PDF API weighs the whole field, and the free HTML to PDF API page prices the $0 route in detail. HTML to PDF without losing formatting explains why converted pages break and how browser rendering keeps layout, fonts, and backgrounds intact, while open source HTML to PDF APIs, compared puts real per-document numbers next to the self-hosted routes. Migrating off the archived tool? Start at the wkhtmltopdf alternatives hub. And for engine head-to-heads, the comparisons open with Gotenberg vs Puppeteer.

Method

Checked 2026-09-11 against our published pricing (/pricing), the API reference, and the render pipeline this service runs. Questions or corrections: hello@webcapture.io.