URL to PDF API

Point us at a URL and we render the page exactly as Chrome would — scripts executed, fonts loaded, lazy images resolved — then hand you the PDF.

HTML PDF PNG JPEG URL
No credit card required · 500 free renders/month

Swap the html field for a url field

The endpoint and the options are identical. Everything you can do with raw HTML you can do with a live URL, which makes it trivial to migrate an existing integration.

curl
curl -X POST https://api.filecook.com/render/pdf \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/reports/q3",
    "options": { "format": "A4", "waitFor": "networkidle" }
  }' -o report.pdf

JavaScript-heavy pages, handled

Single-page apps do not finish rendering when the document loads — they finish when the last request settles. Filecook lets you say exactly what "ready" means for your page instead of guessing with a fixed sleep.

  • waitFor: "networkidle" — capture once network traffic goes quiet
  • waitFor: "#report-ready" — wait for a specific element to appear
  • waitFor: 2000 — a plain millisecond delay when you need the blunt instrument
  • emulateMedia: "screen" — capture the on-screen layout rather than the print stylesheet

Pages behind a login

Dashboards worth exporting are usually gated. Pass custom request headers, cookies, or an HTTP basic auth pair and the renderer will authenticate before it captures. Combine that with origin whitelisting so only your own domains can be rendered with your key.

Frequently asked questions

Can I render a page that requires authentication?
Yes. Send custom headers, cookies, or basic auth credentials alongside the URL and the renderer will use them for the request.
How do you handle lazy-loaded images?
The renderer scrolls the full page height before capture so intersection-observer-driven images resolve, then waits for the network to settle.
Do you support modern CSS like Grid and Flexbox?
Yes. Filecook renders on the latest Chromium, so CSS Grid, Flexbox, custom properties, and modern selectors all behave exactly as they do in Chrome. If it looks right in your browser, it looks right in the PDF.
Do you store the documents you render?
No. Rendering happens in an isolated memory enclave and the output is discarded as soon as it has been returned to your request. Nothing is written to disk and nothing is retained.
Is there a free tier?
Yes — 500 renders a month, free forever, with no credit card required. That covers the playground, the full API, and both PDF and image output.

Keep reading

Ready to start cooking?

500 renders a month, free forever. No credit card, no sales call.