HTML to PDF

Paste HTML, get an A4 PDF of how it renders.

Runs in your browser. Nothing is uploaded — your input is processed on this device and discarded when you close the tab.

Your files

Your HTML

Preview Build PDF

This tool takes an HTML snippet — a formatted announcement, a simple invoice layout, a styled table, a piece of documentation — renders it the way a browser would draw it, and turns that rendering into an A4 PDF. It is for quick, visual jobs: freezing a styled fragment into a file you can email, archiving how a component looks, or producing a simple printable handout from markup you already have.

Read this part before you rely on it: the PDF is a picture of the rendered HTML, not a text document. Each page holds a rendered image of your content, so the words cannot be selected, searched or copied out of the file, links are not clickable, and the result is an approximation of the on-screen render rather than a print-perfect reproduction. For many sharing jobs that trade is fine; for contracts and accessible documents it is not, and a real document editor is the right tool there.

How to use HTML to PDF

1. Paste or type your HTML. Put the snippet in the editor box. A fragment is fine — you do not need the html and body tags around it.
2. Preview it. Choose Preview to see the sanitised render. If something vanished, it was probably a script, an embedded frame or external content the sanitiser removed on purpose.
3. Check the length. Content taller than one A4 page is sliced into further pages at exact page-height boundaries; the Limitations section explains what that means for lines of text near a break.
4. Build the PDF. Choose Build PDF. The snippet is rendered at double scale for sharpness, sliced into A4 pages, and assembled into a single file.
5. Download and inspect every page break. Open the result and look specifically where pages join. If a break cuts through something important, adjust your markup — add spacing or shorten a section — and build again.
6. Iterate freely. Nothing is uploaded and no state is kept, so editing the snippet and rebuilding costs nothing.

Features

• Paste-and-render conversion of HTML fragments with common styling: headings, paragraphs, lists, tables and inline styles all render as they would on screen.
• A sanitiser runs before rendering: script, iframe, object, embed, form, link, meta and base tags are removed, inline event-handler attributes are stripped, and javascript: or data:text/html URLs are neutralised.
• Tall renders are sliced by a deterministic planner: slices start at exact multiples of the A4 page height, and a short final slice leaves white space at the foot of its page rather than being stretched.
• Output pages are true A4 (595.28 × 841.89 points), assembled with the jsPDF library in your browser.
• The preview shows the exact sanitised markup that will be rendered, so there are no surprises about what was removed.
• No account, no upload, and no server: your snippet is processed on your device only.

Worked example

Suppose your snippet renders to a block 794 pixels wide — the width of A4 at 96 CSS pixels per inch — and 2,000 pixels tall. One A4 page at that width is 1,123 pixels tall, so the planner cuts the render into two slices: the first 1,123 pixels and the remaining 877. The PDF gets two pages: page 1 filled edge to edge by the first slice, and page 2 showing the 877-pixel remainder scaled to the page width with white space below it. If the total height were exactly 2,246 pixels, the result would be two completely full pages with no remainder. These slice numbers are asserted by the tool's automated tests, as is the assembly of a real two-page A4 PDF from test images.

Common errors and limitations

• The output is a raster picture of your HTML: text is not selectable or searchable, links are not clickable, and screen readers cannot read the pages.
• Page breaks are blind slices at A4 height. A heading, table row or image that straddles a boundary is cut in two; the tool does not understand your layout well enough to move the break.
• Complex CSS is approximated. Print stylesheets are ignored, some modern layout features render differently than in a full browser tab, and web fonts or externally hosted images that fail to load simply appear as fallback text or empty space.
• Scripts never run — by design, for safety — so content that only appears after JavaScript executes will be missing.
• Very long snippets produce many pages and large files, because every page is a full-resolution image.

• Expecting to copy text out of the PDF. The pages are images. Fix: keep your source HTML if you need the text, or use a document editor's own PDF export for a text-based file.
• A break slices through a table. The planner cuts at fixed heights regardless of content. Fix: add vertical spacing in the markup so the table starts just after a multiple of one page height, or split the snippet into two conversions.
• Images from the web are missing. External images may be blocked by the other site's policies or simply fail to load during rendering. Fix: describe the content in text, or accept the placeholder — this tool does not fetch remote assets for you.
• Pasted page source looks broken in the preview. A full page's markup often depends on its own stylesheets and scripts, both of which are stripped. Fix: paste a self-contained fragment with inline styles instead of a whole page's source.

Frequently asked questions

Related PDF tools

Prefer everything on one page? The original PDF Toolkit merges, splits and rearranges with one shared file list. The full suite is indexed on the PDF Tools hub.