Keep Chromium’s output. Drop Chromium’s infrastructure.

A Puppeteer alternative for PDF generation — for teams done running browser fleets

Nobody chooses to run a headless-browser fleet. You needed PDFs, Puppeteer made beautiful ones on your laptop, and six months later your on-call rotation knows the shape of a Chromium OOM crash by heart. The rendering was never the problem — the infrastructure is.

What you’re actually operating

• ~1–2 GB of memory per browser instance under load, and OOM kills when you guessed low
• A 170–280 MB Chromium binary squeezed into Lambda layers or container images
• Roughly a full CPU core per concurrently rendering page
• Memory that creeps until the pod restarts — pages left open, zombie renderer processes, event-listener buildup
• Chromium security upgrades on your calendar, forever

The same render, as one HTTP call

// Before: your service owns a browser fleet
import puppeteer from 'puppeteer';

const browser = await puppeteer.launch({
  args: ['--no-sandbox', '--disable-dev-shm-usage'], // and 12 more flags
});
const page = await browser.newPage();
await page.setContent(html, { waitUntil: 'networkidle0' });
const pdf = await page.pdf({ format: 'A4', printBackground: true });
await page.close();
// ...plus pooling, recycling, zombie reaping, memory alarms, Chromium upgrades

// After: the fleet is our problem
const res = await fetch('https://api.nippypdf.com/v1/pdf', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.NIPPYPDF_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    html,
    format: 'A4',
    print_background: true,
    wait_until: 'networkidle',
  }),
});
const pdf = Buffer.from(await res.arrayBuffer());

NippyPDF runs a managed pool of current Chromium instances — the same print pipeline as page.pdf() — behind POST /v1/pdf. Memory pressure, browser recycling and crash recovery are our pager, not yours. Pricing is pay-as-you-go at around $0.003/document with 500 documents/month free — compare that with the EC2/Lambda line item your PDF service bills you today.

Try your own template in the live demo, or grab a working sample in Node.js, Python, PHP, Ruby, C# or Go.

FAQ