On this page
Prepare semantic HTML before conversion
Use headings, paragraphs, lists and tables for structure instead of relying entirely on positioned screen components. Fixed pages need predictable document flow.
Embed essential images as data URLs and keep a source copy. Remote stylesheets, fonts and images are intentionally blocked by the secure renderer.
- Use valid HTML structure.
- Avoid viewport-dependent layouts.
- Keep tables within printable width.
- Add page-break CSS only where needed.
Choose a render profile and safe CSS
Custom CSS can refine typography, spacing, table borders and page breaks. External imports and unsafe URL resources are removed, so the stylesheet should be self-contained.
| Profile | Behavior | Best for |
|---|---|---|
| Document | Readable 11 pt flow and generous line spacing | Reports, letters and policies |
| Web layout | Slightly denser fixed-page rendering | Saved webpages and product pages |
| Compact | Smaller type and tighter flow | Reference material and long exports |
Proof the PDF rather than assuming fidelity
Preview the generated PDF and compare representative pages with the intended source. Check headings, tables, long links, code blocks, image scaling and page breaks.
The output is structurally reopened before download, but technical validity does not prove that every visual decision is correct.
Put the workflow into practice
Arrange source documents, select the pages you need, and create one PDF locally in your browser. Review the result before choosing any optional next step.
Try HTML to PDFFrequently asked questions
Clear answers before you merge
Does HTML to PDF preserve every browser style?
No. Browser-specific and viewport-dependent CSS can reflow in a fixed-page renderer.
Can I use custom CSS?
Yes. Use bounded self-contained CSS without remote imports.
Are scripts executed?
No. Active content is removed before rendering.
How should images be included?
Embed essential images as data URLs because remote resources are blocked.
