Turn live URLs into PDF from the same browser stack as Screenshot
PDF Generation API
Generate PDFs from public pages with BrowserSolver screenshot/print pipeline. Wait for the DOM, capture long documents, and archive without standing up a separate headless print cluster.
- URL to PDF via managed Chromium
- Waits for selectors before print
- Full-page capture for long documents
- Same stack as Website Screenshot
out
Wait
selectors
Full
page
REST
API
PDF from the live page
- Step 1
Load
Open the URL and wait for the print-ready state.
- Step 2
Print
Export PDF through the managed Chromium pipeline.
- Step 3
Archive
Store in your bucket or attach to tickets.
PDF without a print cluster
BrowserSolver renders the page and returns a PDF. You store it in your bucket or attach it to tickets. Built for production jobs that need predictable access before brittle parsing.
- Full-page capture when print layout needs the whole document
- Works for SaaS dashboards and statement pages that are HTML
- Print-quality output without running your own headless fleet
- Same API key and credit balance across BrowserSolver scrape modes
Archives that match what users saw
Because PDF shares the screenshot stack, timing and cookies stay consistent with visual QA. Built for production jobs that need predictable access before brittle parsing.
- Pair with Rendering when you also need HTML
- Device profiles when mobile layout matters
- Credit accounting on the shared BrowserSolver balance
- Same API key and credit balance across BrowserSolver scrape modes
PDF from the live page
Print-quality captures without another vendor.
URL → PDF
One API call.
Print CSS
Respect page breaks when present.
Full page
Long docs welcome.
Waits
SPA-ready shutter.
Same stack
Screenshot + PDF.
Archive
Compliance and ops packs.
PDF without a print cluster
Waits
SPA-ready shutter before export
Long docs
Full-page captures welcome
Same stack
Matches Screenshot sessions
Frequently asked questions
Credits, scrape types, and billing before your first production job.
Is this Website Screenshot under another name?
PDF output uses the same screenshot/print pipeline. Use this page when you need a PDF artifact; use Screenshot when you need an image.
Can I pass raw HTML instead of a URL?
Follow the screenshot endpoint docs for supported input modes. URL capture is the primary path.
Are multi-page PDFs supported?
Full-page capture covers tall documents. For multi-URL packs, call the API per page and assemble archives in your pipeline.
Can I combine PDF with HTML extracts?
Yes. Call Website Rendering for HTML and PDF Generation or Screenshot for the archive artifact on the same key.
Pick your next move
Wire up an integration, review plans, or read the API reference before your first job.
Integrations
Trigger BrowserSolver from n8n, Zapier, Make, or any stack that speaks HTTP.
Scrape your first blocked URL
Fetch, render, screenshot, or unlock from one dashboard. Proxies, browsers, and anti-bot lanes stay on our side.
- 500 signup credits
- No card to start
- All scraping modes