Send HTML, get back a PDF with table headers that repeat on every page, running headers and footers, "page 3 of 12" and a working table of contents. No headless Chrome to babysit.
Get early access See pricingRows get cut in half at the page edge, and the header row disappears after page one.
Browser header and footer templates are tiny, unstyled and can't load your fonts or images.
Chrome can't tell you which page a heading landed on, so TOCs and cross-references are guesswork.
Memory leaks, zombie processes, font packages and timeouts. It works until it doesn't.
curl https://api.galleypdf.com/v1/pdf \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"html": "<h1>Invoice #1042</h1>...",
"paged": true,
"footer": "Page {page} of {pages}"
}' \
-o invoice.pdfTurn on paged mode for CSS paged-media support: running headers, page counters, cross-references and TOCs.
Common fonts bundled; bring your own web fonts. What you design in the browser is what prints.
HTML jobs run with network access blocked unless you allow it. Documents aren't stored after delivery.
Annual plans get two months free.
Galley PDF is in development. Reserve a founding spot now and lock in half price on any plan for your first 12 months. Fully refundable before launch and for 30 days after (refund policy).
Reserve a founding spotNot ready to commit? Join the waitlist and we'll email you once, at launch.
We'll only use your email to contact you about Galley PDF. Privacy policy.
You can, and for some teams that's the right call. Galley PDF is for when you'd rather not maintain a browser fleet, and want print layout (repeating headers, page counters, TOCs) working out of the box.
Yes, on paid plans. URL rendering runs in an isolated sandbox that can't reach private networks.
No. PDFs are returned in the response, or held briefly for async jobs and then deleted.
Founding customers and the waitlist get access first. We'll email you when your spot opens.