HTML to PDF

the in-browser HTML renderer takes the rendered DOM and replicates it pixel by pixel into a canvas, which then becomes a PNG embedded in the PDF. This means the output is a raster image, not selectable text — search and copy-paste do not work on the resulting PDF. Real browser-native print (Ctrl+P in your browser, then 'Save as PDF') produces a true vector PDF with selectable text and crisp rendering at any zoom. For best results when text searchability matters, use your browser's built-in print-to-PDF for full web pages. HTML to PDF is the right pick when you have a snippet of HTML (not a full page), need programmatic control over page size and margins, or want to convert content that does not exist as a live URL.

External stylesheets linked via standard tags load if the URLs are accessible from your browser and serve CORS-friendly responses. Web fonts (Google Fonts, etc.) load similarly, though some fonts may render with fallback if the host blocks cross-origin font loading. Images via tag src URLs load if the host allows CORS for image fetching. The safest approach is to inline everything: paste CSS into a style tag inside your HTML, encode small images as data URIs, and use system fonts or self-hosted web fonts that you know will load. For local file conversions, drop both the HTML and the asset files in the upload area and the tool will resolve relative paths. CORS-blocked assets fall back to placeholders.

the in-browser HTML renderer implements a subset of CSS — most common properties work, but CSS Grid, advanced flexbox behaviors, CSS animations, transforms with 3D, filters, and some pseudo-elements may render incompletely or be ignored. If your HTML uses cutting-edge layout, simplify to floats, tables, or basic flexbox for reliable rendering. Print stylesheets (CSS in a @media print block) are honored, so use them for layout adjustments specific to PDF. Test rendering with the preview before converting — if the preview looks wrong, the PDF will look wrong. For complex layouts where pixel-perfect fidelity matters, use your browser's native print-to-PDF instead, since it uses the full browser renderer rather than a CSS-subset reimplementation.

Use CSS page-break-before, page-break-after, and page-break-inside properties on key elements. For example, h1 { page-break-before: always; } forces every top-level heading to start a new page. Avoid page breaks inside tables or images by setting page-break-inside: avoid on those elements. The tool honors these properties when the in-browser HTML renderer renders the content. If pages break in awkward places, add explicit break hints rather than fighting the auto-pagination. For complex documents with intentional pagination, design the HTML with print in mind from the start — fixed page-height containers, explicit break points, and minimal reliance on auto-flowing content all help produce predictable PDF pagination.

Not directly — browsers block cross-origin fetches for security, so the tool cannot download a URL's HTML on your behalf. To convert a live page, open it in your browser, view source (Ctrl+U or right-click View page source), copy the HTML, and paste it into HTML to PDF. Or better, use your browser's built-in print-to-PDF (Ctrl+P, then 'Save as PDF') which renders the page exactly as you see it including selectable text. For programmatic URL conversion in bulk, a server-side tool with Puppeteer or similar headless browser is needed — which conflicts with PDFChamp's no-upload privacy model. The paste-HTML workflow handles 95% of single-page conversion needs locally.

Limited support. Because the in-browser HTML renderer renders to a raster image, clickable links embedded in the source HTML are lost — they become visual underlined text but not clickable in the PDF. For interactive PDFs with working links, use the browser's native print-to-PDF flow instead, which preserves links. If link interactivity is essential and you must use HTML to PDF, the workaround is to post-process the result with a PDF tool that adds link annotations at known coordinates, but that requires programmatic knowledge and is impractical for one-off conversions. For most archival use cases (saving an article for offline reading, printing an invoice), losing clickable links is acceptable; the visual reference is what matters.