SERVERLESSPDF · HTML-TO-PDF API
Generate PDFs without hitting Vercel limits
Send HTML to ServerlessPDF. We render on our infrastructure, store in S3-compatible storage, and return a download URL. Your app keeps CPU, RAM, bandwidth, and storage for core product flows.
Built for teams shipping documents from Next.js and serverless stacks
const endpoint = "https://serverlesspdf.com/v1/documents/render";
const res = await fetch(endpoint, {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Authorization': `Bearer ${apiKey}`,
},
body: JSON.stringify({ html }),
});
const { documentId, downloadUrl, pageCount, sizeBytes } = await res.json();Offload heavy rendering. Keep your core product resources available.
Do not render PDFs inside Vercel / serverless functions
PDF generation inside serverless runtimes quickly turns into infrastructure drag and unpredictable costs.
CPU PRESSURE
Heavy rendering competes with your core API paths and can slow down user-facing requests.
RAM SPIKES
Chromium/Playwright/Puppeteer workloads create memory spikes and instability under load.
EXECUTION TIMEOUTS
Long documents and complex templates often exceed serverless execution limits.
CHROMIUM COMPLEXITY
Maintaining headless browser tooling in production introduces brittle runtime edge cases.
STORAGE + BANDWIDTH
You still need to build storage, signed URL delivery, and large file transfer plumbing.
SURPRISE BILLS
Render bursts, traffic spikes, and document retention can inflate infrastructure costs fast.
Offload PDF generation instead of running it inside your functions
ServerlessPDF removes heavy PDF infrastructure from your app so your team can focus on product delivery.
When rendering inside Vercel / Next.js functions
- ×CPU and RAM usage hit your own runtime budget.
- ×You own Chromium/Playwright/Puppeteer maintenance.
- ×You build storage, signed URLs, and file lifecycle logic yourself.
- ×Debugging production render failures is slower and riskier.
When rendering with ServerlessPDF API
- ✓Rendering runs on ServerlessPDF infrastructure, not your runtime.
- ✓API-first flow: HTML in → PDF + metadata + downloadUrl out.
- ✓Storage and delivery are already part of the service pipeline.
- ✓Clear statuses and error codes reduce support and incident time.
Short version: don’t render PDFs in Vercel functions — offload that workload to ServerlessPDF.
Get started in 3 API steps
Get started in 3 API steps
Integration
POST /v1/documents/renderHTML + API key
Processing...rendering · validation · storage
GET /v1/documents/:id/downloaddocumentId + downloadUrl + metadata
Built for teams shipping quickly
If you build with AI tools and serverless platforms, ServerlessPDF removes the heavy PDF-infrastructure layer.
Vibe coders and indie hackers
Move fast without spending sprints on PDF infrastructure and browser runtime maintenance.
- •Fast MVP delivery
- •Minimal infra code
- •Better time-to-market
No-code / low-code builders
Need a predictable API contract that drops into automation flows without DevOps overhead.
- •Simple API surface
- •Stable output
- •Clear status states
Founders shipping on Next.js
Stay focused on product and growth, not headless browser operations in production.
- •Lower operational risk
- •Less manual debugging
- •Cleaner support flow
Serverless platform users
Vercel, Netlify, Cloudflare Workers users can offload heavy PDF jobs from app functions.
- •Less function pressure
- •More predictable costs
- •Easier scaling
Start free, upgrade when PDF becomes a recurring workflow
STARTER
$0 / mo
Initial renders and output validation on your own data.
- 25 renders per quota window
- 100 pages per document
- 7 days of document retention
- 5 concurrent renders
- HTML up to 2 MB, PDF up to 100 MB
- API key management and audit
RECOMMENDED
$19 / mo
For teams where PDF generation is a regular product operation.
- 1000 renders per quota window
- 1000 pages per document
- 90 days of document retention
- 30 concurrent renders
- HTML up to 10 MB, PDF up to 100 MB
- Priority queue and full audit
Free is for integration validation. Paid is for stable recurring production document workloads.
Security and Reliability
Your data is protected at every stage of the service
Reliability
Target SLA: 99.9% target uptime
Data region
EU data region
Transparency
Status and key service terms are publicly visible.
Simple integration, predictable result
Use the ready-made API flow for PDF generation of any complexity without setting up your own browser environment.
A simple production API surface
Treat PDF generation as a service: send HTML in, receive verifiable output and a download link.
HTML in → PDF out
One render endpoint instead of running a separate browser runtime in your app.
documentId + checksum + pageCount + sizeBytes
Response metadata helps validate output and wire documents into product workflows.
Signed download URL
Download ready PDFs without building and maintaining your own delivery path.
Statuses and error codes
Predictable diagnostics for faster support and incident handling.
API error codes
// Response code examples
AUTH_FAILED401Invalid or missing API key
QUOTA_EXCEEDED403Render quota exhausted for your plan
DOCUMENT_NOT_FOUND404Document not found or deleted
RATE_LIMITED429Too many requests per second
INTERNAL_ERROR500Internal rendering service error
These are just some of the codes. Full list available in the documentation.
Stop burning serverless resources on PDF rendering.
Create an account, get an API key, and validate the full flow on your own HTML today.