Turning a Web Page into a PDF: An Online Tool or Browser Printing?

You're about to save a web page as a PDF. The routes: giving a URL to an online conversion tool, using your browser's "Print to PDF" feature, printing in reader mode, or taking a screenshot. Which one is right depends on the type of page and what you want to preserve.

The four methods in brief

An online tool: you give it a URL and the tool visits that address on its own and produces a PDF.

Browser printing: you print to PDF with Ctrl+P in the browser where you already have the page open.

Reader mode plus printing: you first turn on the browser's reader mode to simplify the page, then print.

A screenshot: you take an image of the page and put it into a PDF.

Comparison table

| Criterion | Online tool | Browser print | Reader mode | Screenshot | |---|---|---|---|---| | Pages requiring a session | No | Yes | Yes | Yes | | Dynamic content | Partly | Fully | Fully | Fully | | Selectable text | Yes | Yes | Yes | No | | Page setting control | Good | Good | Limited | None | | Menu/ad cleanup | Depends on print styles | Depends on print styles | Very good | None | | Can be automated | Yes | No | No | Partly | | Clickable links | Usually | Usually | Usually | No | | Long pages | Split automatically | Split automatically | Split automatically | Laborious |

Scenario 1: Archiving a news article

You're turning an article into a PDF to read offline or keep.

Winner: reader mode plus printing.

News sites are the most problematic pages in terms of output: menus, side columns, ad blocks, related story lists, social media buttons, comment sections.

If the site's print styles are well defined, those get hidden. But many sites define no print styles or define them incompletely.

Reader mode solves the problem entirely: the browser extracts the article text and main images from the page and discards everything else. You get a single-column, readable layout. Printing in that mode gives a clean PDF.

Reader mode is turned on from an icon in the address bar in Firefox, similarly in Safari, and in Chrome through a setting that varies by version.

Scenario 2: Saving an order confirmation or account statement

You're keeping your order from an e-commerce site or your banking screen as a document.

Winner: browser printing, no other option.

An online tool can't reach those pages. It goes to the address you give it on its own and doesn't carry your session cookies. The result is a PDF of a login screen or an error page.

In your browser you're already logged in and the page is loaded in its personalized state.

A tip: many e-commerce and banking sites offer well-defined print styles for these pages — the output usually comes out clean. Some also offer a direct "Download PDF" option, which is always best.

Scenario 3: Generating invoices from my own HTML

A system creates invoices from an HTML template and they need converting to PDF.

Winner: an online tool or a programmatic converter.

Your advantage in this scenario is that you control the HTML. With CSS you can determine the page behavior exactly:

@page {
  size: A4;
  margin: 2cm;
}

table { page-break-inside: avoid; }
.total-row { page-break-before: avoid; }

p { orphans: 3; widows: 3; }

Being automatable is also critical: hitting Ctrl+P by hand for every invoice doesn't scale.

Things to watch:

Fonts. Web fonts load from external sources; if the conversion environment has no access, the layout shifts. Embedding the font or using system fonts is safer.

Background colors. They aren't printed by default. If you use colored header bands or highlight areas, you may need print-color-adjust: exact.

Test it. Try invoices of different lengths — a 3-line and a 50-line invoice show different page-breaking behavior.

Scenario 4: Saving a documentation page

You're turning a technical manual into a PDF for offline access.

Winner: an online tool or browser printing.

Documentation sites are usually well structured and their print styles are reasonable.

There's one thing to watch: collapsed content. Many documentation sites present sections as accordions or tabs. Content in a closed state doesn't appear in the PDF at all.

You need to open all the sections before printing. Some sites have an "expand all" button.

Also, if code blocks contain long lines they can get cut off on the right. Printing the page in landscape orientation can help.

Scenario 5: Proving a page's state at a particular moment

You want to record a price, a description or a post.

Winner: browser printing (with headers/footers on).

Browser printing automatically adds the URL, date and time to the top and bottom of the page. Normally that's unwanted, but for an evidentiary record it's exactly what you want.

Make sure the "Headers and footers" option in the print dialog is on.

A screenshot is also defensible in this scenario because it preserves the page's visual state exactly. But the text is lost — it becomes unsearchable and uncopyable. Keeping both is the most robust option.

Scenario 6: A page using infinite scroll

A social media feed or a continuously loading list.

Winner: none of them fully solves it.

Infinite scroll loads content as the user goes down. Neither an online tool nor browser printing can capture all of that content — because the scroll event never happens.

Partial solutions:

Scrolling manually. Scrolling to the end of the page in the browser to load all the content, then printing. Laborious on long pages but it works.

Looking for a printable version. Some sites offer a "print" or "show all" link.

Splitting into sections. Saving the page in pieces and merging them.

The same problem applies to lazy-loaded images: images that never enter the viewport never load and come out blank in the PDF.

Where screenshots fit

We include this method for completeness, but it wins in almost no scenario.

What it loses:

• Text. The writing in an image is nothing but pixels. It can't be searched or copied and screen readers can't access it.
• Resolution. Limited by your display. It looks blurry when printed.
• Page breaking. Long pages have to be taken in pieces and stitched.
• Links. Not clickable.
• File size. Many times larger than a text-based PDF.

Its only legitimate use: when the page's visual state has to be preserved exactly — documenting a design, capturing an error screen.

The online tool's advantages

Browser printing has come out ahead so far, so let's list where an online tool wins:

Automatability. If you regularly convert a lot of pages to PDF, printing by hand doesn't scale.

Consistent settings. The same page size, margins and scaling are applied every time. Browser settings may not be remembered across sessions.

For your own HTML. In generating invoices, reports and certificates, a programmatic converter is the right tool.

Access from a different device. When you don't have a browser to open the page in.

Privacy. A tool that runs in the browser without sending the content to a server is on the same level as a local solution.

Decision summary

• A page requiring a session → browser printing, mandatory.
• A news article, a blog post → reader mode plus printing.
• Your own HTML (invoices, reports) → an online/programmatic tool with CSS control.
• An evidentiary record → browser printing with headers/footers on.
• Batch work → an online/programmatic tool.
• A dynamic page with infinite scroll → scroll manually, then print from the browser.
• If you need visual evidence → a screenshot (accepting the loss of text).

And in every case, open the output and check it: is the content complete, are the page breaks sensible, are the special characters right, do the links work.