PagedPDF vs Browserless for PDFs

Checked: prices and features from browserless.io and docs.browserless.io on 2026-11-11. We haven't run Browserless ourselves, so its side comes from its documentation.

These are different kinds of product. Browserless hosts headless browsers that you drive with Puppeteer or Playwright, for scraping, testing, screenshots and automation, and it has a /pdf endpoint among them. PagedPDF only turns HTML into PDFs.

At most volumes, Browserless costs less per PDF. What you're choosing is how much of the PDF work you want to keep doing yourself.

This page is written by PagedPDF. Check anything that matters to you against Browserless's pricing page.

How Browserless bills

Browserless sells units, not documents. In its words, a unit is "a block of browser time of up to 30 seconds per browser connection", and a longer session uses another unit for every 30 seconds. A PDF that renders in under 30 seconds is one unit, so the tables below count one unit per PDF.

Browserless plan Monthly billing Yearly billing, per month Units a month Extra units
Free $0 $0 1,000 None: requests are rejected
Prototyping $35 $25 20,000 $0.0020
Starter $200 $140 180,000 $0.0017
Scale $500 $350 500,000 $0.0015

Cost per document

Monthly billing on both, taking the cheapest route, overage included:

PDFs a month Browserless Each PagedPDF Each
500 $0 (Free) $0 $15 (Starter) $0.03
2,000 $35 (Prototyping) $0.0175 $15 (Starter) $0.0075
10,000 $35 (Prototyping) $0.0035 $49 (Growth) $0.0049
50,000 $95 (Prototyping plus 30,000 extra units) $0.0019 $149 (Scale) $0.0030

PagedPDF is cheaper only between 1,000 and 2,000 PDFs a month. Below 1,000, Browserless is free. Above 2,000 it's cheaper, and the gap widens with volume.

The units are shared, though. If the same account also runs scrapers or tests, those use the same pool, and a slow PDF that takes 31 seconds costs two units.

What Browserless leaves to you

The /pdf endpoint takes Puppeteer's PDF options and prints with Chrome, so you get Chrome's defaults and Chrome's quirks. These are the ones we've tested in Puppeteer and written guides for:

None of that is hard. It's a few options and CSS rules that you find one bad PDF at a time, and then keep in your code.

PagedPDF has those on by default: rows stay whole, table headers repeat, backgrounds print, "footer": "Page {page} of {pages}" is the whole footer option, and every response lists what failed to load in an X-PagedPDF-Warnings header.

Where Browserless is the better choice

Where PagedPDF is the better choice

The same request on each

Browserless, adapted from the example in its documentation:

curl -X POST "https://production-sfo.browserless.io/pdf?token=YOUR_API_TOKEN_HERE" \
  -H "Content-Type: application/json" \
  -d '{"html": "<h1>Invoice 1042</h1>", "options": {"printBackground": true, "format": "A4"}}' \
  -o invoice.pdf

PagedPDF:

curl https://api.pagedpdf.com/v1/pdf \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"html": "<h1>Invoice 1042</h1>", "footer": "Page {page} of {pages}"}' \
  -o invoice.pdf

Only need PDFs, and want the table and footer fixes done for you? PagedPDF is $15 a month for 2,000 documents. You can try it without a key on the homepage, or get a free key for 50 documents a month.

More comparisons