§ 01.1
Render + archive in one call
Send a URL or raw HTML. Get back the finished PDF and, when you ask for it, a timestamped snapshot of exactly what was rendered, retrievable by API for the life of your retention window. How the archive works.
Sitepdf · HTML to PDF + Archive API
One API call turns a URL or your HTML into a pixel perfect PDF and archives a timestamped snapshot of the page. No headless Chrome to babysit. Try it below, free, right in your browser.
§ Live demo
Runs in your browser. Nothing is uploaded.
Your HTML
Live preview
Your PDF is downloading. Want this as one API call, with the page archived too?
§ 01
Nearly every PDF API hands you the file and forgets the page. Sitepdf returns the document your user needs and keeps the record your auditor will ask for, from the same request. We compared the whole market, including the tools that beat us.
§ 01.1
Send a URL or raw HTML. Get back the finished PDF and, when you ask for it, a timestamped snapshot of exactly what was rendered, retrievable by API for the life of your retention window. How the archive works.
§ 01.2
Pages render in managed Chromium, not a CSS-subset engine from 2011. Your web fonts load, your JavaScript runs, and wait-for-selector holds the shot until your charts are on screen. Converting live pages.
§ 01.3
Memory leaks, font packages, render drift after every Chrome release, 3am restarts: that is the real price of the "free" library. Replace the fleet with one HTTP call and a flat per-render cost. The honest math.
§ 01.4
Every archived render carries its capture time and source. When legal asks what the page said in March, you answer with a retrievable snapshot, not a screenshot from someone's laptop. Data handling and retention.
§ 02
One POST to /v1/render with the page and your layout options: size, orientation, margins, headers and footers.
Full CSS and JavaScript, web fonts, wait-for-selector for late content. The fleet, the scaling and the patching are our problem.
The response links the finished document and, with archive=true, the timestamped snapshot you can retrieve forever after.
curl https://api.sitepdf.com/v1/render \
-H "Authorization: Bearer $SITEPDF_KEY" \
-d url="https://example.com/invoice/1042" \
-d format=A4 \
-d archive=true
{
"pdf_url": ".../documents/doc_8f3k2.pdf",
"archive": {
"id": "arc_o2m91",
"captured_at": "2026-07-11T09:14:02Z"
}
}
The full request and response walkthrough is on how it works.
§ 03
These are the launch tiers we are building toward. Join early access now and these rates are yours for 12 months after launch, whatever happens to list pricing.
$29/mo planned
10,000 renders / mo
Recommended
$99/mo planned
50,000 renders / mo
$299/mo planned
250,000 renders / mo
Custom
Committed volume, legal hold, DPA
§ 04
A self-hosted rendering fleet bills you in engineer-hours and on-call pages. A managed API bills you a predictable per-render price. The comparison usually ends after the first incident review.
Every render can leave an audit-ready, timestamped snapshot behind. E-discovery, regulatory retention and "what did the page say" disputes get answered from the archive, with retention and deletion you control.
SSO and roles, a 99.9% SLA and data residency are planned for launch; invoicing and a DPA are available from day one. The specifics, stated honestly, are on the security page.
§ 05
More on the full FAQ, including how we compare to DocRaptor, PDFShift and self-hosting.
§ Early access
The API opens to the list first, in order. Early access locks the planned launch rates for 12 months. No card required, launching soon.
Early access ยท no card
Render + archive, one API