PaperKit

HTML to PDF

Paste a URL and get the page as a PDF, rendered by a real headless browser — styles, fonts and images included.

Paste a URL and the page is rendered to PDF by a real headless browser — the same engine that would display it — so stylesheets, web fonts, images and layout come through as they appear rather than as an approximation. It is the tool for archiving a page before it changes, capturing a receipt or booking confirmation, or turning documentation into something readable offline. Only the URL leaves your device: our server fetches the page, renders it and streams the PDF back, storing nothing. Two limits follow from that arrangement and are worth knowing before you try. The renderer visits the page as an anonymous visitor, so anything behind a login is unreachable. And a page written without print styles frequently produces a PDF with navigation bars and cookie banners embedded in it.

Pages behind a login cannot be captured

Our renderer requests the URL with no session, no cookies and no credentials. A page requiring a login returns the login screen, and that is what gets rendered — which is the correct behaviour rather than a limitation to work around.

For a page you are logged into, use your own browser's Print to PDF, which renders the session you already have. That covers the common cases people reach for this tool with: an order confirmation, a bank statement, an internal wiki page.

What the rendered page looks like

Sites that define print styles convert beautifully, because the site's own authors decided what a printed version should contain — navigation removed, content widened, ink-heavy backgrounds dropped.

Sites that do not are captured as they appear on screen, complete with sticky headers, cookie banners and consent dialogues frozen into the document. Content that loads as you scroll may be missing entirely, since it never had a reason to load. Neither is recoverable from the PDF afterwards, which is why an important capture is worth checking rather than filing unseen.

Archiving a page properly

A PDF captures how a page looked at one moment, which is exactly what you want for a receipt, a published price, a set of terms or anything that may be disputed later. Note the date somewhere in or alongside the file, because the PDF itself will not say when it was taken.

It is a snapshot rather than a copy of the site: interactive elements are static, links leaving the page still point outward, and video is a still frame. For something that must be preserved as evidence, capture it as soon as you notice it — the page you are archiving is one deploy away from being different.

Frequently asked questions

How is my URL handled?

Browsers cannot render another site and capture it as a PDF, so this one runs on our server: the URL you paste is sent to a headless browser, the rendered PDF is streamed straight back to you, and neither the URL nor the PDF is stored afterwards.

Can it convert pages behind a login?

No — the converter sees the page as a logged-out visitor. Save such pages from your own browser with Print → Save as PDF instead.

Can it convert a page behind a login?

No. Our renderer fetches the URL as an anonymous visitor with no session, so a page requiring authentication returns its login screen. Use your browser's own Print to PDF for pages you are signed in to.

What is sent to the server?

The URL. Our server fetches and renders that page and streams the PDF back, storing nothing — so unlike the file-based tools, there is no document of yours involved at all.

More PDF tools

Advertisement