Convert to PDF
What does HTML to PDF do?
HTML to PDF renders an uploaded HTML or HTM file, or a public page URL, into a PDF. Supported visible HTML and CSS and same-origin or CORS-enabled images are kept. Scripts, forms, iframes, blocked remote assets and print-specific behavior are not preserved. URL import first tries a direct browser read; if the site blocks that, this origin fetches the public page so conversion can still run locally. Requests time out after 20 seconds, and scripts are not executed. Output pages are rasterized.
How to use HTML to PDF
- 1Upload saved HTML or paste a page URL
Choose an HTML or HTM file, or paste a public HTTP or HTTPS URL. If the site blocks the browser, this app fetches the public page and then converts it locally. Login-protected or private-network pages will not import.
- 2Wait for the local render
The current browser lays out supported visible HTML and CSS. Scripts are not executed. URL requests time out after 20 seconds.
- 3Export a rasterized PDF
Rendered pages are rasterized. Same-origin or CORS-enabled images can appear; blocked remote assets will not.
- 4Check missing widgets
Forms, iframes and script-driven content will not behave as they did in the live page. For a local file, keep images next to the HTML or expect broken pictures.
Supported files and limits
- Output format: PDF
- Input: HTML, HTM, HTTP or HTTPS URL
- Output options: upload saved HTML; paste a page URL
- URL import fetches a public page for local conversion; URL requests time out after 20 seconds; scripts are not executed
- Files stay on this device and are removed when you close the page.
URL import fetches a public page for local conversion. URL requests time out after 20 seconds. Scripts are not executed. The PDF is a raster of the visible layout, not a live web page.
What the output keeps
- supported visible HTML and CSS
- same-origin or CORS-enabled images
Supported visible HTML and CSS, plus same-origin or CORS-enabled images, are retained in the rendered pages.
What may change or be lost
- scripts
- forms
- iframes
- blocked remote assets
- print-specific behavior
Scripts, forms, iframes, blocked remote assets and print-specific behavior are not preserved.
When not to use this tool
Do not use HTML to PDF to archive an authenticated app behind a login, to capture a private-network page, or to keep working forms and iframes. It is not a print-preview clone of every CSS paged-media rule.
If processing fails
An invalid URL is rejected. If the page cannot be reached or takes longer than 20 seconds, save it as HTML and upload the file. Script-only pages can export nearly blank; provide static HTML instead.
Privacy boundary
HTML files are read locally. A pasted public URL is fetched so the browser can convert it here; the resulting PDF is generated in your browser and is not stored on a PDF Smart Kit server.
Testing evidence
Last tested: · Test browser: Desktop Chrome via Playwright Chromium · Product version: 1.0.0
Sample: Saved HTML file with a heading and a table · 1 pages
What was checked
- A saved HTML file produces a valid PDF with at least one page.
- A public HTML URL can be imported and converted in the browser.
- The source HTML is not required to keep scripts, forms or iframes in the output.
Known failures and limits
- URL import fails when the page is unreachable, private, timed out after 20 seconds, or does not return HTML.
- Scripts are not executed; blocked remote assets and print-specific CSS may be missing.