How to Convert a Website to PDF for Free
Every few weeks something happens that makes you wish you had saved a webpage as a PDF. An article you wanted to cite gets quietly edited. A product page disappears. A receipt page expires. A long blog post you wanted to read offline is suddenly behind a paywall. The web is not an archive — it’s a moving target.
Converting a URL to a PDF is the simplest fix, and there are more ways to do it than most people realize. Each has tradeoffs. This guide compares the four practical methods, explains when each one works (and when it doesn’t), and shows you how to handle the common edge cases — long pages, broken layouts, paywalled content, and pages that load content dynamically.
The four ways to convert a website to PDF
1. Browser print-to-PDF (built-in, free, limited)
Every modern browser can save a webpage as a PDF without installing anything. On macOS, press ⌘ + P and choose “Save as PDF”. On Windows, Ctrl + P and select “Microsoft Print to PDF” or “Save as PDF”. It works on Chrome, Safari, Firefox, and Edge.
When it works well: Short articles, simple pages, single-page documents.
When it breaks: Long pages where content uses lazy-loading, sites with sticky headers that repeat on every page, dynamic dashboards, and any page that uses position: fixed for navigation — those fixed elements often plaster over the content in the output.
The bigger problem is fidelity. Browsers apply a print stylesheet by default, which can strip backgrounds, change fonts, and remove images entirely. You can override this — uncheck “Headers and footers”, check “Background graphics” — but the result still rarely matches what you see on screen.
2. Browser extensions (convenient, privacy-cost)
Extensions like Save as PDF, Print Friendly, or FireShot integrate a “save as PDF” button into your toolbar. They’re fast for one-off captures. The catch is permissions: most of them request access to “read and change all your data on the websites you visit” — which is exactly what it sounds like. For a one-time conversion, that’s a steep trade.
Extensions also add startup time to your browser and tend to get acquired or shut down. The graveyard of dead PDF extensions is long.
3. Server-side converters (best fidelity, no install)
This is what tools like TheToolBus’ URL to PDF converter do. You paste a URL, the converter loads it on a real headless browser server-side, waits for the page to render fully (including lazy-loaded content), and returns the PDF.
The advantage over browser print is fidelity. Because the page is rendered in a clean headless Chrome instance — no extensions, no print stylesheet, no fixed elements bleeding into print mode — the output is closer to what you’d see in your browser. Text stays selectable, links stay clickable, and the full page is captured, not just the visible viewport.
The tradeoff: pages behind a login wall can’t be captured this way. The converter visits as an anonymous guest, so anything that requires a session (Gmail, your dashboard, paywalled articles you’ve subscribed to) won’t work.
4. Command-line tools (wkhtmltopdf, weasyprint)
If you convert URLs to PDFs regularly — for reports, automated archiving, or document pipelines — installing a command-line tool is worth the setup. wkhtmltopdf and weasyprint are the two most common. Both render HTML to PDF and run on macOS, Linux, and Windows.
This is overkill for occasional use, but if you need to convert hundreds of pages in a batch or wire URL-to-PDF into a workflow (a daily cron job that archives competitor pricing pages, for example), the CLI is the right tool.
How to pick the right method
| Situation | Best method |
|---|---|
| One quick article you need offline | Browser print-to-PDF |
| Long blog post or web page you want to archive cleanly | Server-side converter |
| Page behind a login (e.g., your dashboard) | Browser print-to-PDF |
| Page with lazy-loaded images or infinite scroll | Server-side converter |
| Bulk archiving of many URLs | wkhtmltopdf or batch API |
| You don’t want to install anything | Browser print or web-based converter |
How to use TheToolBus’ URL to PDF converter
For most people, the server-side route gives the cleanest result with the least effort. Here’s the actual flow:
- Open the URL to PDF converter.
- Paste the full URL of the page you want to capture, including
https://. - Click Convert.
- Wait 5–15 seconds while the server loads the page, waits for fonts and images to settle, and renders the PDF.
- The file downloads automatically.
The output includes the full page, not just the part above the fold. Links are preserved as clickable anchors inside the PDF. Text is embedded as selectable text, not flattened to an image, so you can ⌘ + F search inside the document and copy passages out.
No signup, no email, no watermark on the file.
Common problems (and how to fix them)
“The PDF cut off my content”
Usually this means the page has lazy-loaded sections that didn’t render in time. Two fixes: (1) try the conversion again — the converter waits longer on retry, or (2) scroll through the page yourself, then use browser print-to-PDF, which captures the fully rendered DOM.
”The layout looks broken in the PDF”
Modern websites use CSS grid, flexbox, and media queries that target specific viewport widths. The PDF is rendered at a fixed width (usually 1024–1280px) and pages that aggressively respond to viewport size can look off. Print-to-PDF in your browser sometimes handles this better because it uses your actual viewport.
For pages where the layout breaks badly, the cleanest fallback is to use the browser’s “Reader Mode” first (Firefox, Safari, and Edge all have one). Strip the page to its core content, then print to PDF. The result is plain but readable.
”Login-walled content won’t capture”
A server-side converter can’t sign in for you. Two options:
- Use browser print-to-PDF after logging in. Anything you can see in your browser, you can print to PDF.
- Open the page in a private/incognito window. If the page requires login but the article is supposed to be free with a registration prompt, sometimes private mode bypasses the wall.
”The PDF is huge”
Pages with high-resolution images can balloon to 20+ MB. If size matters, run the PDF through a PDF compressor afterwards. Reducing image DPI from 300 to 150 typically cuts the file in half with no visible quality loss for screen reading.
”I need the full page including everything below the fold”
The browser print-to-PDF dialog has a “Pages” option — make sure it’s set to “All” rather than the visible page. For server-side conversion, the full page is captured by default.
Use cases worth knowing about
Archiving sources before they change. Journalism, academic research, legal preservation — anywhere you cite a URL, a PDF snapshot protects you against the page being edited or taken offline later. Pair the PDF with a Wayback Machine link for redundancy.
Sharing reports and dashboards. Public dashboards and report pages render well as PDFs. Useful when stakeholders don’t want to navigate the live page or need an offline copy for a meeting.
Saving receipts and confirmations. Most e-commerce confirmation pages live behind a login. Print-to-PDF after the purchase is the easiest way to keep a copy without depending on email.
Reading later, offline. Long-form articles, documentation, and blog posts read better as PDFs on a tablet or e-reader. If you do this often, server-side conversion produces the cleanest result.
Citations and references. Academic citations of web sources are stronger when paired with a PDF snapshot. Many universities and journals now accept PDF archives as part of the citation record.
When PDF isn’t the right format
PDF is good for archiving and sharing — not for editing or restructuring content. If you need to extract just the article text (for a research database, a Notion import, or a markdown archive), use a tool like Print Friendly or your browser’s Reader Mode to strip the page first, then save as plain text or HTML.
For pages where you want a live, navigable snapshot rather than a static document, the Wayback Machine’s “Save Page Now” feature creates a permanent archived copy that retains the original page’s behavior — including working links, video, and interactive elements PDFs can’t preserve.
The bottom line
If you’re saving one page right now, open the browser print dialog — it’s already there. If you’re saving anything you want to look correct, share with someone, or rely on later, use a server-side converter like TheToolBus’ URL to PDF tool. And if you’re converting URLs to PDFs as part of any kind of regular workflow, install wkhtmltopdf and stop thinking about it.
The point isn’t which method is “best” in general — it’s which method matches what you’re trying to do. Most people only need two of these: print-to-PDF for the casual case, server-side for the cases where it actually matters.