Renditions

free, no signup, no watermark

HTML to PDF, without breaking your design

AI tools write gorgeous HTML decks and reports. Then “Print to PDF” butchers them. This converter renders your file in a real Chromium browser and captures every slide pixel-for-pixel: shadows, gradients, fonts and links intact.

Your file is processed in an isolated browser and deleted immediately after conversion.

Q3 Review

Growth, compond…

+240%

12.4k

98/100

Page 1 of 3

Q3 Review

Growth, compounding.

+240%

12.4k

98/100

this converterbrowser “Print to PDF”
Drag to compare: same HTML slide, two export paths.

What “Print to PDF” does to modern CSS

The browser print pipeline was built for paper documents. The exact features AI-generated designs lean on degrade or disappear on the way to paper.

Screenshot-based rendering sidesteps all of it: what you see is exactly what you get.

  • background-clip: text

    gradient headlines turn black or vanish

  • box-shadow

    cards lose all depth

  • backdrop-filter

    glassmorphism disappears

  • linear-gradient()

    backgrounds stripped to save ink

  • @font-face

    your fonts become Times New Roman

  • height: 100vh

    slides sliced mid-sentence across pages

  • JS navigation

    only the first slide prints

How it works

  1. Drop an .html or .zip

    A single file, or a zip with CSS, images and fonts. The file is served locally to a sandboxed headless Chromium, the same engine as your browser.

  2. Slides are found automatically

    The engine recognizes stacked full-screen sections, Reveal.js, class-toggled and keyboard-navigated decks, then walks through every slide, waiting for fonts and animations to settle.

  3. One crisp page per slide

    Each slide is captured at 2x resolution and embedded in a PDF page of the exact slide size. Long documents are sliced into A4 or Letter pages. Links stay clickable.

Frequently asked questions

Why does my HTML deck look broken when I print it to PDF?

Browsers use a separate print rendering pipeline designed for paper documents. It drops or degrades box-shadows, gradient text (background-clip: text), backdrop filters and background images, swaps web fonts for system fonts, and slices 100vh slide layouts across paper pages. This converter avoids the print pipeline entirely: it captures the screen rendering.

How is this different from wkhtmltopdf or Puppeteer's page.pdf()?

Those tools also go through a print-oriented rendering path, so the same CSS features break. This engine renders your page in headless Chromium with screen media, navigates through slides like a person would, and captures each one as a high-resolution image before assembling the PDF.

Is it really free?

Yes. Free, no account, no watermark, up to 30 conversions per day per user.

What happens to my files?

Files are processed in an isolated headless browser and deleted from the server immediately after the conversion finishes, whether it succeeds or fails.

What input formats are supported?

A single .html file, or a .zip archive containing an HTML file with its assets (CSS, JavaScript, images, fonts). Multi-slide decks, single pages and long documents are all handled.

Are hyperlinks preserved in the PDF?

Yes. The engine detects visible links on each slide or page and re-creates them as clickable link annotations at the same position in the PDF.