Does it wait for JavaScript and lazy-loaded content?

Yes. Single-page apps and lazy-image sites get a default render delay so async content loads before the snapshot. You'll be able to bump the delay manually for unusually slow pages.

How do I control page breaks?

Use the standard CSS print rules: page-break-before: always, page-break-after: always, or break-inside: avoid. Sites with proper @media print CSS get clean pagination automatically.

Will my page be uploaded?

URL-based conversions run on our renderer (which has to fetch the page itself). For privacy-sensitive HTML files, upload them directly — the file is processed in memory only, never written to disk.

Convert HTML to PDF

Turn any webpage or HTML file into a clean, print-ready PDF.

Why use this

Real Chromium renderer: We render exactly what a modern Chrome browser shows — flexbox, grid, custom fonts, gradients, SVGs, web fonts and modern CSS all work. No 1990s rendering surprises.
Respects @media print: Sites with proper print stylesheets get dramatically cleaner output — navigation hidden, content widened, ads removed. PDFWix uses the print stylesheet automatically when present.
Waits for lazy content: Single-page apps, lazy-loaded images, and async-injected content need a moment to render. PDFWix waits by default and lets you bump the delay for slow sites.
Page-break control: Honors CSS page-break-before / page-break-after / break-inside so you can force clean breaks at section boundaries. No more paragraphs split across pages.
Header/footer with URL and page numbers: Toggle a header showing the source URL and a footer with page numbers — useful for archived articles where the source needs to be visible on the printed copy.

Use cases

Archiving a long-form article so it survives if the original site goes dark
Generating a printable receipt from an e-commerce thank-you page
Saving a recipe from a food blog without the ads and pop-ups (with print CSS)
Producing a PDF version of a published documentation page for offline reading
Converting a custom-designed HTML invoice template into a sendable PDF

How it works

Open the HTML to PDF tool — When the tool launches, you'll either paste a URL into the input or upload an .html file (with its CSS and images bundled in a folder).
Pick page settings — Choose page size (A4 / US Letter / custom), orientation, margins, and whether to include header/footer with URL and page numbers. Sensible defaults will be pre-selected.
Click "Convert to PDF" — A real Chromium renderer will load the page, wait for lazy content and fonts, apply your @media print CSS, and snapshot every paginated page into the PDF.
Download the PDF — Save the rendered PDF. Open it in any reader to verify pagination — adjust margins or page-break CSS and re-run if a section breaks awkwardly.

Frequently asked questions

Is HTML to PDF available now?

Not yet — it's on our launch list and arriving soon. Join the waitlist on the page to be notified the moment it's live. In the meantime, Chrome's File → Print → Save as PDF produces a passable result for most public pages.

Will it work with modern CSS — flexbox, grid, custom fonts?

Yes. The renderer is built on Chromium, so anything that works in modern Chrome will render in the PDF: flexbox, CSS grid, custom web fonts, gradients, SVGs, and modern selectors.

What about pages behind a login or paywall?

The renderer won't be able to authenticate — login-walled and paywalled pages will fail. The workaround is to save the page locally with your browser's 'Save Page As' feature, then upload the saved HTML file (and its assets) to PDFWix.