How to Convert HTML to PDF Online Free (URL or File)

Webpages change. A PDF doesn't: give WhizPDF's HTML to PDF converter the page's address, and you get a print-clean snapshot in seconds — rendered by a real Chromium browser, sized for A4, Letter, Legal, A3, or Tabloid. Free, no sign-up, no watermark. Have the HTML as a file instead? Drop it straight into the upload box below — that route needs no copy-paste at all.

Your browser's Ctrl+P → Save as PDF does the same job for pages in front of you, and it's the right call for anything behind a login. What neither the print dialog nor most guides handle well is everything around the capture: images that show up as blank boxes, backgrounds that vanish, cookie banners baked into page one, wide tables sliced at the edge. All of that has causes and fixes — the failure section below covers them, and jumps straight there if you're already staring at a broken capture.

Three routes, and when each one wins

• Paste the URL — best for public pages you want archived as they render: articles, documentation, pricing pages, receipts sitting at a public address. The converter fetches the page with a real browser engine, so modern CSS and JavaScript render before the capture.
• Upload the HTML file — best for pages you own: invoice templates, generated reports, a page you saved with Ctrl+S. No fetching involved, so nothing depends on the live site.
• Browser print (Ctrl+P → Save as PDF) — best for anything you're logged into, and the fastest route when you just need what's on screen. It captures the rendered page as-is, print-stylesheet quirks included.

Convert a web page by URL

1. Copy the address of a page that loads without a login.
2. Paste it into the URL tab of the converter — the URL tab lives on the tool page (use the link or "Open tool" above), since the upload box only accepts files.
3. Convert and download. The page renders in Chromium first, then gets captured to your chosen paper size.

The output options you'll set on the tool page before converting:

• Paper size, orientation, and margins
• Background printing — switch it on if the page uses colored sections
• Layout — Original layout keeps a business document intact; reading mode strips an article down to text

One constraint to know upfront: the converter's server fetches the page the same way you would in a fresh browser — with no cookies and no session. Anything behind a login, a paywall, or a one-time confirmation link comes back as a login screen or an error page. That's not a bug; it's how the web works. Those pages belong to the browser-print route.

And a timing note worth internalizing: a URL capture is a snapshot of one moment. Order confirmations, booking screens, and quote pages are often session-bound — load them once and they're gone. Capture them while they exist; you can't re-run the conversion tomorrow.

Convert an HTML file you have

When the HTML is yours — a template, a generated report, a page saved to disk — skip the network entirely:

1. Get the file. Save the page with Ctrl+S, or use the .html your system already generates.
2. Upload it — the box at the top of this page does it, or the full turn an HTML file into a PDF online tool page if you want the paper-size options in view. HTML and HTM both work, up to 50 MB per file.
3. Pick your output settings (same options as the URL route) and convert.

The one thing that decides whether this works: assets have to be reachable. A self-contained file — styles and images embedded — converts the way it looks in a browser. A file that references images on your localhost, an internal server, or anywhere behind a login will render with those pieces missing, because the renderer can't fetch what it can't reach.

The easiest way to hit that without realizing it: a page saved with Ctrl+S keeps its images and stylesheets as relative paths pointing to a folder on your own disk. Upload the .html alone and none of those paths resolve — images come out blank. Two fixes: save the page with a single-file extension like SingleFile first, which inlines every asset into one self-contained .html, or convert only pages whose assets live at absolute URLs. A folder of files next to the .html doesn't travel with the upload.

Why the PDF doesn't look like the page

Almost every "my PDF looks broken" complaint traces back to one of four causes. Each has a fix.

• Blank boxes where images should be. Modern pages mark most images to load only when you scroll near them — that's the lazy loading behavior built into HTML, and it means a capture taken from the top of the page misses everything below the fold. Scroll the whole page once, top to bottom, then capture. In the browser-print route this is the single most common fix.
• Colors and backgrounds gone. Print dialogs strip background graphics by default to save ink — colored sections, shaded tables, dark headers all come out white. In Chrome's print dialog, open More settings and tick Background graphics. The converter's equivalent is the background printing option — leave it on.
• Cookie banners and chat widgets stamped into the PDF. Anything floating over the page gets captured with it. Dismiss the banners and close the widgets before converting. For articles, Reader mode first gives you a clean page with the clutter already stripped.
• Wide tables sliced at the page edge. Portrait paper cuts anything wider than the page, no matter the settings. Switch to Landscape; if columns still clip, step up to A3 or Tabloid. This one setting change rescues most pricing tables, schedules, and dashboards.

One more trap worth naming: infinite-scroll feeds (social timelines, long comment threads) never finish loading, so no capture method gets the whole thing. Save what rendered, or screenshot the section you actually need.

A cousin of that trap: app-style pages — dashboards, Notion workspaces, admin panels — that pull their content in with background requests. A server-side capture can grab the page shell before the data lands, and what comes back is an empty frame with a header. If a page's content takes a visible beat to appear, or it only makes sense while you're logged in, skip the URL route and print it from your own browser.

After the capture

A few things people ask about once the PDF is on disk:

• The links still work. Because the capture runs through a real browser engine, text stays selectable and hyperlinks stay clickable — a screenshot-based PDF gives you neither.
• Several saved pages can become one file. Capture each page separately, then combine several saved pages into one PDF when you're archiving a set of order confirmations or building a single attachment.
• Image-heavy captures can balloon. A long page with photos prints to a surprisingly heavy PDF; running it through a tool that can compress an oversized PDF takes seconds and usually halves it.

References

• Google Chrome Help — Print from Chrome: the Ctrl+P / Cmd+P flow and the Save as PDF destination, including mobile routes.
• MDN Web Docs — Lazy loading: how the loading attribute defers off-screen images until the user scrolls near them — the mechanism behind blank-image captures.