Pre-launch · early access

HTML to PDF without the 3 a.m. OOM pages

NippyPDF is one API call against a managed Chromium rendering core. No Puppeteer fleet to babysit, no 280 MB Lambda layers, no wkhtmltopdf page breaks splitting your tables mid-row — and pay-as-you-go pricing around $0.003/document.

You’ve probably been burned by one of these

“Puppeteer in production is a nightmare”

OOM crashes under load. A 170–280 MB browser binary blowing past Lambda limits. A full CPU core per page. Memory that creeps up until the container dies.

Fix Puppeteer OOM on Lambda →

“wkhtmltopdf is dead”

Last release June 2020, repository archived. Tables split mid-row, page breaks land wherever they like, Unicode falls apart, and it renders differently on your laptop than on the server.

Fix wkhtmltopdf page breaks →

“The incumbents are overpriced”

DocRaptor’s entry plan is $15/mo for 125 documents — $0.12 per document. Our answer is honest pay-as-you-go around $0.003/doc, with 500 documents/month free.

See planned pricing →

Try it now — in your browser

Edit the HTML, watch the preview, download a real PDF. No signup, nothing leaves your browser.

HTML (editable)
Live preview

Honesty note: this in-browser demo rasterizes with html2canvas. The real API renders on server-side Chromium — selectable text, vector output, and proper CSS page-break support.

What integration looks like

One POST, HTML in, PDF out. Bring your own templates — it’s just Chromium, so if it renders in Chrome, it renders in your PDF.

curl -X POST https://api.nippypdf.com/v1/pdf \
  -H "Authorization: Bearer $NIPPYPDF_API_KEY" \
  -H "Content-Type: application/json" \
  -o invoice.pdf \
  -d '{
    "html": "<h1>Invoice #1042</h1><p>Total: £480.00</p>",
    "format": "A4",
    "margin": "20mm",
    "print_background": true,
    "wait_until": "networkidle"
  }'

Working examples for Node.js, Python, PHP, Ruby, C# and Go.

Why NippyPDF

No OOM crashes

The rendering fleet is our problem, not yours. Your service makes an HTTP call; memory pressure, browser recycling and zombie-process cleanup happen on our side of the API.

Pixel-perfect page breaks

A current Chromium engine with real CSS fragmentation: break-inside: avoid, repeating table headers, running headers and footers, modern CSS (flexbox, grid) that wkhtmltopdf never supported.

Honest pricing

Around $0.003 per document, pay-as-you-go, with 500 documents/month free. No credit maths, no plan cliffs. Compare against DocRaptor and PDFShift.

Who’s building this? An engineer who has spent years working deep inside the Chromium rendering engine — the same core that powers this API. That’s the whole pitch: rendering is the product, so rendering expertise is the moat.

Get early access

Pre-launch. Join the waitlist and lock in early-access pricing — we email once, when your key is ready. No spam.