Convert HTML to PDF,free, in your browser

Drop an .html or .htm file onto the upload card, or click it to browse. You can also skip the file entirely and paste markup into the box below the card. Either way the limit is 25 MB of markup, which is far more than a hand-written page needs.

Click Convert. The markup is laid out on A4 portrait pages with a 14 mm margin, and the finished PDF is offered for download along with a short list of anything that had to be dropped.

This page converts markup you already hold. It cannot take a link, because a browser is not allowed to read another website's page. The URL tool does that job by fetching the page through our server first, which is the one place in this family where a request leaves your machine.

Almost always it is a stylesheet loaded from somewhere else. A <link rel="stylesheet"> tag points at a separate file, and the converter does not go and fetch it, so the page renders with the built-in defaults instead of your design. The tool tells you when it spots one.

The other difference is the typeface. A PDF built this way can only use a fixed set of built-in fonts, so whatever you asked for is swapped for the nearest of Helvetica, Times or Courier. Sizes, weights, italics and colours are kept, but a brand font will not survive the trip.

Move the rules into a <style> block at the top of the file, or onto the elements as style attributes. Both are kept and both are applied. A page whose whole design lives inline converts almost exactly as it looks in the browser, including colours, borders, table styling, and background fills.

Yes. Your words go into the PDF as real characters, not as a picture of the page, so a reader can select them, copy them and find them with Ctrl+F. It also keeps the file small.

The honest limit is the alphabet. Only Latin characters are supported, and that includes accented letters, curly quotes, dashes and the common symbols. Text in Hindi, Chinese, Japanese, Arabic, Cyrillic or Greek comes out as nonsense symbols rather than words, and emoji do the same. There is no workaround for that today.

They are not. An <a> tag renders as blue underlined text because that is how the browser drew it, but there is nothing behind it to click. Print the address next to the link text if the reader will need it, for example "Docs (example.com/docs)".

Images embedded as data URIs always come through, because the picture is already inside the file. That is the reliable route for a logo or a chart. Pictures are re-encoded on the way in, so a screenshot with sharp edges can soften slightly.

Images pointed at the web are fetched by your browser during the conversion, so they only appear if the site hosting them allows cross-origin loading. Plenty do not, and those come out blank. The tool warns you when your markup links remote images so you know to check the result.

Scripts, iframes, embedded objects, form controls, and page-level meta and base tags are stripped before anything is rendered. A PDF cannot run code or submit a form, and letting untrusted markup execute on our page would be a real security hole.

Whatever gets removed is listed after the conversion, so you are never handed a quietly different document than the one you gave us.

CSS page-break rules are ignored here. Pages are split automatically at gaps between lines of text, so a paragraph is never cut through the middle of a line. If a section has to start on a fresh page, give the block before it enough bottom padding to push it over. There is no manual page-break control on this tool.

Everything renders onto A4 portrait at a fixed content width, and there is no landscape option here. A table wider than that column gets squeezed, and content that overflows the column can be cut off at the right edge. For genuinely wide data, a spreadsheet converts to landscape pages instead.

A saved page from a modern web app is usually an empty shell plus a script that draws everything after load. Strip the script and there is nothing left, so the tool stops and says so rather than handing you a blank PDF. Save the rendered page instead: in the browser, use Save Page As and pick the complete option, or copy the finished markup out of the developer tools.

This works well, because an invoice is static markup with inline styling and a table. Fill the values in, keep the CSS in a <style> block, and convert. If you would rather not maintain the template yourself, the invoice generator produces the document and the PDF in one go.

Nothing is sent anywhere. The file is read into the browser tab, rendered there, and saved from there. That matters when the markup is a client report, a payslip template, or anything with real names and numbers in it, because there is no copy on a server and no retention window to trust.

The free plan covers 10 finished files a day across every tool, and no account is needed to convert or download. The finished PDF carries no watermark on any plan, so it can go straight to a client or a portal.