HTML to PDF

Most CSS2 and widely-used CSS3 properties render correctly, including flexbox, grid, custom colors, and borders. Web fonts loaded via @font-face or Google Fonts generally render when the conversion has internet access; locally hosted font files may not resolve unless the font data is embedded or base64-encoded in the HTML.

Yes — specify your preference in the prompt (e.g., 'A4 portrait', 'Letter landscape', or a custom width/height in millimetres). If you don't specify, the conversion defaults to A4 portrait.

Images with absolute URLs are fetched and embedded during conversion. Relative-path images and local file references (e.g., src='../images/logo.png') won't resolve unless you replace them with absolute URLs or base64 data URIs before submitting.

The converter runs a headless browser that executes most JavaScript before capturing the page, so dynamically rendered content (React, Vue, Angular output) is typically captured. However, content that loads only after user interaction — like clicking a 'Load more' button — usually won't appear in the PDF.

Very large HTML documents — roughly over 2 MB of markup or pages exceeding around 50 printed pages — may hit processing limits or increase conversion time noticeably. For large reports, consider splitting into sections or compressing embedded images before submitting.

Yes — describe what you want removed in your prompt (e.g., 'remove the sticky navigation bar and cookie consent popup'). The AI will attempt to strip those elements from the DOM before rendering. Results vary by site complexity; tightly coupled JS components may be harder to isolate.