HTML to PDF API FAQ

We are in early access. The converter demo is fully working now, entirely in your browser. The API opens to the early-access list first, in order; join the list and we will email your invite.

No. Early access is free to join: you give us an email address, we send a 6-digit code to confirm it, and you are on the list. Joining locks the planned launch pricing for your first 12 months. You pay nothing until the API is live for you and you pick a plan.

Nothing from a render unless you ask for an archive: by default the PDF is returned and the source discarded. With archive=true, the snapshot is stored under your account with retention you control and delete on request. The in-browser demo stores nothing anywhere: your HTML never leaves your machine. Details on the security page.

Yes. Rendering runs in real managed Chromium: grid and flexbox, custom properties, print rules, web fonts and emoji all behave the way they do in your browser, and wait_for holds the render until your selector exists. The how it works page has the specifics.

One sentence: it is the only PDF API where every render can also be archived, so you get the document and the audit trail from one endpoint. Renderers like DocRaptor and PDFShift stop at the file; screenshot tools stop at the pixels; self-hosting hands you a headless-Chrome fleet to babysit. Our library vs API breakdown runs the self-hosting math honestly.

Both, via the API: it fetches and renders live URLs server side, with wait-for-selector, and takes raw HTML for template-generated documents. The in-browser demo only renders pasted HTML because browsers cannot fetch arbitrary sites cross origin; that is a browser limit, not a product limit. Live-URL rendering plus archiving is exactly what early access unlocks. See URL to PDF API.

Invoicing and a DPA are available from day one on the enterprise tier. SSO and roles, a 99.9% SLA and data residency options are on the launch roadmap, and we mark them planned everywhere they appear because they are not shipped yet. If those are gating requirements, talk to sales and we will scope timing with you.

Three concrete things: a place in line when API invites go out, the planned launch pricing locked for 12 months, and a direct say in roadmap order, because we ship what early access users tell us blocks them. One email when your spot opens; no newsletter.

It goes in one table with your confirmation status and which page you signed up from, and it gets used for exactly two things: your verification code and your invite. No newsletter, no resale, delete on request. The privacy policy is short and readable.