HTML to PDF without breaking your CSS
Most HTML-to-PDF tools go through the browser's print pipeline or a headless print engine. That pipeline was designed for paper documents in 2001, not for modern CSS. Shadows, gradient text, filters and blend modes all degrade. This converter skips print entirely: it renders your page in real Chromium and captures the actual pixels.
Your file is processed in an isolated browser and deleted immediately after conversion.
CSS features the print pipeline breaks
- Gradient headlines (background-clip: text) print as solid black or disappear entirely.
- box-shadow is removed or crudely flattened, killing depth in card layouts.
- backdrop-filter (glassmorphism) isn't supported in print rendering.
- CSS gradients as backgrounds are often stripped by 'save ink' defaults.
- Web fonts are frequently swapped for system serif fonts mid-export.
- transform, position: fixed and 100vh units are reinterpreted for paper, wrecking layouts.
How to convert
- 1.Upload your HTML file or a zip with assets.
- 2.The page is rendered in headless Chromium with screen media, the same rendering path as your browser window.
- 3.The full page is captured at 2x resolution and sliced into A4/Letter pages (or kept as one long page if you prefer).
- 4.Hyperlinks are re-mapped onto the PDF pages so the document stays clickable.
FAQ
Why do screenshots preserve CSS better than print rendering?
Because there is nothing to translate. Print engines re-interpret your CSS for a paged, ink-saving medium. A screenshot captures the exact pixels Chromium already rendered for the screen: shadows, gradients, filters and all.
Is the text still selectable in the PDF?
No. Pages are high-resolution images, which is the trade-off for perfect fidelity. Links remain clickable. A searchable text layer is on the roadmap.
What about pages with lazy-loaded images?
The engine scrolls through the entire page before capturing, which triggers lazy loading, then captures from the top.