Turning markup into a document
HTML describes a document's structure: this is a heading, this is a list, this is a table, this is a link. That structure is exactly what a PDF needs in order to be typeset well — and it survives the trip perfectly, because it is the part of HTML that is actually about the content rather than its appearance.
So this converter reads the structure and sets it properly: headings at their hierarchy, lists with hanging indents, tables with borders and wrapped cells, code in a monospace face, and links as real clickable annotations rather than blue text.
What it deliberately does not do
It does not apply CSS.Reproducing a styled page means running a browser engine and capturing what it paints — the headless-Chrome approach every server-side converter uses. There is no server here, so that is not on the table. What you get instead is the document's content, correctly ordered and cleanly typeset.
It does not fetch anything. Remote images, stylesheets, fonts and scripts referenced by the file are never downloaded. That is a privacy decision as much as a technical one: requesting them would announce to those servers which document you are converting, and from where. Images embedded in the file itself are included.
If you need a pixel-exact copy of a live web page, your browser already does that better than any converter could — Print, then Save as PDF.
When this is the right tool
It is at its best on content-shaped HTML: an exported article, a generated report, documentation, an email saved as HTML, a Markdown file rendered to HTML, or the output of a tool that writes HTML because that was the easiest format to emit.
It is the wrong tool for a marketing page, a dashboard, or anything whose value is in its visual design.
Common uses
- Converting a generated HTML report into something to file or send
- Turning documentation into a printable, paginated document
- Archiving an article as a fixed, readable document
- Getting an HTML export into a system that only accepts PDF
Privacy
The file is parsed by the browser's own HTML parser and the PDF is assembled in memory on your machine. Nothing is uploaded, and — unlike most HTML-to-PDF services — nothing the document references is requested either.