URL to PDF API

URL to PDF API: Convert a URL to PDF and Save Any Link as a PDF

POST a link, get back a document. The Sitepdf API turns any URL into a pixel perfect PDF with one call, and stores a timestamped snapshot of the page in the same request. No headless browsers to run, ever. Convert a URL to PDF with the tool below before you write a line of code.

Early access, launching soon
No card required
Your HTML stays yours

Live demo

Runs in your browser. Nothing is uploaded.

Sample Page size Orientation Margins

Your HTML

Live preview

Your PDF is downloading. Want this as one API call, with the page archived too?

One endpoint, the whole job

Everything is one call to /v1/render. Give it a url, or raw html if you already have the markup, and it returns the finished PDF. Options cover the real world: page size and orientation, margins, header and footer templates, wait_for a selector so client rendered content is on screen, and archive=true to keep a dated snapshot of what was rendered.

Under it all is managed Chromium, kept patched, warmed and scaled by us. Your CSS and web fonts render the way they do in the browser, because it is the browser.

The second thing the call returns

Every other URL to PDF service hands you the file and forgets the page. Sitepdf can also hand you the record: the response includes an archive id and capture timestamp, and the snapshot stays retrievable under your account for the life of your retention window. Invoices, confirmations, published prices, regulated disclosures: the document for your user, the audit trail for whoever asks later.

Want to see the output quality first? The free in-browser converter uses your own browser's engine on pasted HTML, no signup, and the how it works page walks the full request and response.

Built to replace your Puppeteer fleet

If you currently run headless Chrome yourself, you know the bill: memory leaks, zombie processes, emoji and font packages, render drift after every Chrome release, and the 3am page when the pool wedges. The API replaces the fleet with a flat, predictable per render cost. The math is on the pricing page, and our library vs API breakdown runs the honest comparison.

The API shape early access unlocks: link in, document plus record out.

curl https://api.sitepdf.com/v1/render \
  -H "Authorization: Bearer $SITEPDF_KEY" \
  -d url="https://example.com/order/8412/confirmation" \
  -d format=A4 \
  -d orientation=portrait \
  -d wait_for=".order-summary" \
  -d archive=true

{
  "pdf_url": "https://api.sitepdf.com/v1/documents/doc_1kd83.pdf",
  "pages": 2,
  "rendered_in_ms": 2140,
  "archive": {
    "id": "arc_v7x20",
    "captured_at": "2026-07-11T08:02:44Z",
    "retrieve_url": "https://api.sitepdf.com/v1/archives/arc_v7x20"
  }
}

The API is in early access; this is the documented call shape it opens with. Full request and response walkthrough.

Questions about this job

Is the URL to PDF API live today?

It is in early access. The rendering pipeline is what we are building in the open; the API opens to the early access list first, in order. Joining is free, takes an email address, and locks the planned launch pricing for 12 months.

How fast is a render?

A typical page renders in two to five seconds; the long tail is pages that load slowly themselves. Renders run concurrently, so throughput is a function of your plan's concurrency, not of one page's speed.

What happens if a page fails to load?

You get an explicit error with the HTTP status the page returned, not a blank PDF. Failed renders do not count against your quota.

Do I need the archive, or can I just get the PDF?

Archiving is per call: leave archive off and the render is transient, nothing stored. Turn it on for the calls where the record matters. Retention per plan is listed on the pricing page, with delete on request always available.

Index

More PDF and archiving tools

Early access

Get on the early-access list

The API opens to the list first, in order. Early access locks the planned launch rates for 12 months. No card required, launching soon.