Screenshot API: same engine, next in line

Coming after the PDF API

Everything that makes a good HTML-to-PDF service — a managed, current Chromium fleet with real rendering expertise behind it — is exactly what a screenshot API needs too. So that’s the roadmap: PDF first, screenshots on the same core right after.

What it will look like

curl -X POST https://api.nippypdf.com/v1/screenshot \
  -H "Authorization: Bearer $NIPPYPDF_API_KEY" \
  -H "Content-Type: application/json" \
  -o hero.png \
  -d '{
    "url": "https://example.com",
    "format": "png",
    "width": 1440,
    "full_page": true,
    "wait_until": "networkidle"
  }'

PNG, JPEG and WebP output; full_page or viewport capture
Device sizes and device_scale_factor for retina-sharp captures
wait_until: "networkidle" so client-rendered pages are actually finished
Same pay-as-you-go philosophy as PDF pricing — no credit packs

Want it? The list below is separate from the PDF waitlist — signups here directly decide how fast screenshots ship. If you need PDFs too, join the PDF early-access list as well, or try the live demo.

Get the Screenshot API first

Separate list from the PDF API — one email when screenshot early access opens. Your interest here directly prioritizes the roadmap.