HTML to PDF
Paste HTML or a URL, get a clean PDF. 100% in your browser — nothing uploaded.
HTML to PDF works best for simple documents (articles, reports). Complex layouts with floats and CSS grid may render approximately.
Your file is ready
Processed entirely in your browser — the file never left your device.
How to convert HTML to PDF
Three steps. All in your browser.
Pick a mode
Paste raw HTML or enter a URL the browser can fetch.
Pick page options
Page size, body font size, and margins.
Create & download
The PDF is built locally with pdf-lib and offered as a download.
What is "HTML to PDF"?
Converting HTML to PDF means turning a web page (or any chunk of HTML) into a portable, fixed-layout PDF that prints, opens, and archives the same on every device. People usually want this for articles, internal docs, exported notes, or a snapshot of a record page that needs to be filed alongside other PDFs.
imisspdf's HTML to PDF is built for the common case: clean content with headings, paragraphs, lists, quotes, code, and links. It is not a Chromium-style renderer and does not try to reproduce a CSS layout pixel-for-pixel — for that, your browser's built-in Save as PDF is still the best tool. What this gives you instead is a scriptable, paste-friendly, in-browser converter that works on any HTML fragment without leaving your tab.
How HTML to PDF works in your browser
When you paste HTML, the tool parses it locally into a sequence of block tokens (headings, paragraphs, lists, etc.) and inline runs (bold, italic, links). Each block is laid out onto a PDF page with pdf-lib using the standard Helvetica / Courier fonts. New pages are created on demand as content overflows.
For the URL mode, your browser issues a normal HTTP fetch to the target site — exactly the same request your address bar would make. If the site allows CORS, the page HTML is read into your tab and rendered locally. If it does not, you get a clear error and can paste the source manually. Nothing about your URL or its contents is reported to imisspdf.
Common use cases
- Archiving an article. Paste the article HTML and keep the PDF as a long-term reference.
- Exporting note-app content. Notion, Obsidian, or markdown converters all produce HTML — paste it and get a PDF without leaving the browser.
- Sharing a report. Generate an HTML report in your app and feed it through this tool when a PDF is required by the recipient.
- Printing FAQ snippets. A tidy bullet list of FAQs becomes a one-page PDF you can attach to a ticket.
- Filing a transactional email. Save the HTML of a receipt or confirmation as a PDF for accounting records.
Privacy & security
Server-based HTML-to-PDF tools have to ship your HTML (or the URL plus session cookies) to a Chromium instance running in their cloud. That works, but it puts your content on a third party. The imisspdf converter parses and renders everything in your browser with pdf-lib. The only network call ever made is the fetch you explicitly trigger for the URL mode — and it goes directly from your browser to the target site, not through us.
Frequently asked questions
Headings (h1–h6), paragraphs, lists (ul/ol), blockquotes, preformatted code blocks, horizontal rules, plus inline bold, italic, code, and links. The renderer is intentionally simple so a paste from a Notion page, a Google Doc export, or a blog article comes out as a clean PDF without surprises.
No CSS layout — floats, grid, and flex are ignored. No tables (rows are flattened to text). No embedded images. No web fonts — the PDF uses the standard Helvetica / Courier set. If you need pixel-perfect Chromium-style rendering, take a screenshot of the page and use JPG to PDF instead.
Yes — the tool will fetch the HTML directly from your browser, which works for sites whose CORS policy allows it. Many large sites do not. If the fetch is blocked, you will get a clear error. As a workaround, copy the page HTML manually (right-click → View Source → copy) and paste it into the textarea.
Yes for pastes — the HTML never leaves your browser. For URLs, your browser fetches the page directly from its server, exactly as if you visited it; imisspdf never sees the URL or the content. The PDF assembly happens locally in your tab.
Browser Save as PDF uses Chromium's full rendering engine — perfect for pixel-fidelity, but you have to print every page individually and you cannot script it. imisspdf's HTML to PDF is simpler but lets you paste any HTML fragment, automate the conversion, and run it offline. Pick whichever fits the job.
Tips for best results
- Paste the body, not the whole page. Strip nav, sidebars, and footers if you want a tighter PDF.
- Use semantic tags. h2 for sub-heads, p for paragraphs, ul/ol for lists. The renderer follows tags, not classes.
- If CORS blocks a URL, view-source and paste. Most modern sites send cross-origin headers that block direct fetch; copying the HTML manually is the reliable fallback.
- For pixel-perfect output, use the browser's Save as PDF. Then process the result with the other tools on this site.
Related PDF tools
- TXT to PDF — plain text instead of HTML.
- JPG to PDF — combine images (or page screenshots) into a PDF.
- Merge PDF — combine the result with other PDFs.
- Compress PDF — shrink the output if the source HTML had a lot of repeated content.