What HTML to PDF helps you do

Turn a web page into a PDF from its URL. The local path loads the page in an iframe and rasterizes it in the browser, while the server path fetches the URL with a full rendering engine. Both produce a PDF, but only the server path can reach pages that block cross-origin framing.

Browser conversion is local. The high-fidelity option sends the URL to a Haivix conversion service for that request only.

How it works

A PDF stores positioned drawing instructions rather than flowing paragraphs, which is why editing one is different from editing a document. Page content, fonts, images and annotations are separate objects, and a page only carries a text layer if the producer wrote one. Most tools here rebuild or render the file in your browser with pdf-lib and pdf.js; the formats that need a full office engine, such as Word, Excel, PowerPoint, PDF/A and HTML, use the Haivix service and say so in their privacy note. Every tool writes a new file and leaves the original untouched. Because content is placed by coordinates, extraction often returns text runs in visual order rather than sentences, and columns or tables can arrive interleaved.

How to use HTML to PDF

Paste the page URL.
Try the local conversion first for a quick preview.
Use the server option when the local path is blocked by CORS or the page needs more than one screenful.
Download the PDF and check the page breaks.

When to use it

Turn an HTML report or invoice template into a PDF.
Export a self-contained page for archiving or printing.
Produce a PDF from markup without a browser print dialog.
Capture a public page as a fixed document.
Save a receipt or confirmation page for records.
Share a web page with someone who needs a static copy.

When not to use it

Do not use it for pages behind a login; the server cannot authenticate.
Do not expect selectable text from the local path; it exports a raster image.
Do not convert private or internal URLs through the server without approval.

Example

A public article converted locally becomes a single A4 page containing a raster image of the visible page. A long page may be clipped because the local path does not paginate. The server path renders the full document and can produce several pages, but it sends the URL to Haivix and is rate-limited.

What you can do with HTML to PDF

Convert a URL to a PDF.
Use a local iframe preview and raster export.
Fall back to the server for full-page rendering.
Show the remaining server conversions.
Download the result as a PDF.
Keep the local path inside the browser.

Example: work on a copy and check the output

Keep the original file. These tools produce a download rather than editing in place, so a failed operation never damages the source.

Check whether the PDF has a real text layer before relying on extraction. A scan is an image, so text tools return little or nothing until OCR has run.

Unlock encrypted files first. A password-protected PDF cannot be reordered, cropped or annotated until it has been opened with the correct password.

Review the output before sending it on. Fonts can substitute, overlays do not always remove what is underneath, and page boxes can shift content near the edges.

Note the page size and orientation before laying anything out. A mixed document can contain portrait and landscape pages, and a tool that assumes one size may crop or offset the others.

Keep a note of the operation and its settings. If a recipient questions the result, reproducing it from the original is faster than guessing which options were used.

What to know before you start

External stylesheets, fonts and images may not load in the browser path.
Browser rendering differs from a full desktop browser, so pixel-perfect output needs the server option.
The local path rasterizes the page into an image, so its text is not selectable.
The server path sends the URL to the Haivix service and is rate-limited.

Common mistakes

Expecting the local path to capture content below the fold.
Trying a site that sends X-Frame-Options and expecting the iframe to load.
Forgetting that the server fetch sees the page as an anonymous visitor.
Assuming the output has selectable text when it is an image.

Troubleshooting

If the local path reports a CORS error, the site blocks iframe access; use the server option.

If the PDF is blank, the page may render only after a delay or behind a consent wall.

If the result is a single clipped page, the local canvas captured only the visible area.

If the server rejects the URL, the page may block automated fetches.

HTML to PDF