.HTML FILE.
Your file never leaves this tab.
Everything runs in JavaScript (and WebAssembly) on your device. We can't see your PDF, and neither can our servers — because your file never touches them.
HOW HTML TO PDF WORKS.
01. Drop
Drag your file onto the box, or click to pick one from your device.
02. Tweak
Set the options in the sidebar. Defaults work for most.
03. Download
Hit the big button. Your file is ready in seconds — never leaves your browser.
ABOUT HTML TO PDF.
Turning a saved HTML page into a PDF is useful for archiving web content, creating a printable version of a styled document, or converting an HTML-based report or invoice template into something that looks the same everywhere it's opened. minipdftoosz's HTML to PDF tool renders your HTML file in an isolated context using html2canvas — a library that walks the rendered DOM and paints it onto an HTML canvas, essentially taking a very high-fidelity screenshot of the page — then places that image onto PDF pages via pdf-lib.
It's important to understand exactly what this means for the output: because the PDF is built from a canvas snapshot rather than from the original text and layout data, the resulting PDF is image-based. Text in the output PDF is not selectable, searchable, or copyable — it's pixels that happen to look like text, the same way a photograph of a printed page looks like text but isn't. Visually, though, fidelity is generally excellent: the layout, colors, fonts (as rendered by your browser), and spacing come through exactly as the HTML displayed.
This trade-off makes the tool a great fit for visual archiving — capturing exactly how a styled page looked at a point in time, including CSS-driven layouts that a text-based converter would struggle to reproduce faithfully — but a poor fit for anything where the recipient needs to select, search, or copy text out of the resulting PDF. If searchable text output matters more than exact visual fidelity, this isn't the right tool for that job; there currently isn't a text-preserving HTML-to-PDF path in this toolset.
External resources referenced by the HTML (remote images, remote fonts, remote stylesheets) may not render if your HTML file depends on network access the browser can't reach in the context this tool runs — self-contained HTML with inline styles and locally-referenced or embedded images will render most reliably.
If you're archiving a page you expect to want to reference again later and search within, consider also saving the original HTML file itself alongside the generated PDF snapshot — that way you retain a text-searchable version of the content even though the PDF export itself is not searchable.
Anyone archiving a styled web page or HTML-based report exactly as it visually appeared — an internal dashboard snapshot, a styled invoice template — is the core audience for HTML to PDF, prioritizing exact visual fidelity over the ability to later select or search the resulting text.
- Keep referenced images and CSS local/embedded in the HTML file for the most reliable rendering — remote resources may not load.
- Remember output text isn't selectable — this is a visual snapshot, not a text-preserving conversion.
- For very long pages, expect multiple output PDF pages as the canvas snapshot is sliced to fit standard page dimensions.
FAQ.
Common questions about html to pdf. Something else on your mind? Ask us.
Yes. Free forever. No sign-up. No credit card. No trial.
Never. Everything runs locally in your browser using JavaScript and WebAssembly.
Only limited by your browser’s memory. Most laptops handle 100MB+ with ease; very large files may be slower.
Once the page and its tool script have loaded, yes — processing runs entirely client-side.