EU data region
99.9% target uptime
First render in ~10 minutes
Logs, statuses, and retries included
No Chromium headachesNo serverless timeout stressNo surprise infra bills

SERVERLESSPDF · HTML-TO-PDF API

HTML to PDF API | High-Performance Dedicated Rendering

Convert HTML into PDF documents with full CSS support. Integrate our scalable API into your apps in minutes to get instant download URLs without managing servers or infrastructure.

Built for teams shipping documents from Next.js and serverless stacks

TEMPLATE PREVIEW

Preview Document Templates

Review prepared HTML templates and their static PDF previews.

QUICK INTEGRATION

Start generating PDFs in minutes

No complex configurations. Install our lightweight SDK, pass your HTML, and get a ready-to-use secure download link instantly.

  • 01
    Initialize

    Install the SDK and add your API key. It takes less than a minute.

  • 02
    Send Data

    Pass raw HTML or a URL. Our cloud handles all the heavy browser rendering automatically.

  • 03
    Get PDF

    Get a secure, production-ready download URL to serve directly to your clients.

Node.js
const response = await fetch("https://serverlesspdf.com/v1/documents/render", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "Authorization": "Bearer YOUR_API_KEY",
  },
  body: JSON.stringify({
    html: "<h1>Invoice #1024</h1>",
  }),
});

const { downloadUrl } = await response.json();
console.log(`Ready to download: ${downloadUrl}`);
Create Free Account & Get API Key

Includes 25 free PDF generations. No credit card required.

DEDICATED PDF RENDERING

The challenges of rendering PDFs in serverless

Run PDF rendering via a dedicated render service, not inside your serverless functions: browser engines in functions impact app speed, waste development time, and increase infrastructure 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.

WHY OFFLOAD WINS

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.

HOW TO START

Get started in 3 API steps

1

Get started in 3 API steps

01
Create an account and API key
~1 minute
02
POST /v1/documents/render with your HTML
Request
03
Receive metadata and a signed download URL
Done

Integration

POST /v1/documents/render
[request]

HTML + API key

Processing...
[processing]

rendering · validation · storage

GET /v1/documents/:id/download
[ready]

documentId + downloadUrl + metadata

WHO THIS IS FOR

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
PRICING

Start free and move into Pro during our Public Beta

STARTER

$0 / mo

Small limits for first renders, validation, and API onboarding.

  • 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
Start free
PUBLIC BETA

PRO

$0

All Pro features are currently available for free during our Public Beta.

We're collecting feedback and improving the platform before the commercial launch.

  • 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
See beta plan →

Pricing will be introduced after the beta period ends. Existing beta users will be notified in advance.

Need higher limits? Contact us and we'll increase your limits for free if needed.

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.

Service status

24/7 monitoring

Open status
API & INTEGRATION

Simple integration, predictable result

Use the ready-made API flow for PDF generation of any complexity without setting up your own browser environment.

API DETAILS

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.

4xx Error Handling

API error codes

// Response code examples

AUTH_FAILED401 → invalid or missing API key

401 → invalid or missing API key

QUOTA_EXCEEDED403 → render quota exhausted

403 → render quota exhausted

HTML_TOO_LARGE413 → HTML limit exceeded

413 → HTML limit exceeded

LIMIT_EXCEEDED400 → page limit exceeded

400 → page limit exceeded

RATE_LIMITED429 → too many requests

429 → too many requests

CONCURRENT_LIMIT_EXCEEDED429 → concurrent render limit reached

429 → concurrent render limit reached

RENDER_TIMEOUT504 → render exceeded 30 sec

504 → render exceeded 30 sec

DOCUMENT_NOT_FOUND404 → document not found

404 → document not found

DOCUMENT_EXPIRED410 → retention expired

410 → retention expired

FORBIDDEN403 → document belongs to another workspace

403 → document belongs to another workspace

These are just some of the codes. Full list available in the documentation.

QUICKSTART

Stop burning serverless resources on PDF rendering.

Create an account, get an API key, and validate the full flow on your own HTML today.

No credit card required
API key in ~1 minute
First PDF in a short test loop
Clear statuses and logs for support
Create account