You found an article, a recipe, a research paper online and you need to keep it. Maybe the site will go down. Maybe you want to read it offline on a flight. Or you just need a clean copy for a report.
Whatever the reason, saving a webpage as a PDF is one of those tasks everyone needs eventually. I tested seven different methods over the past few weeks – from browser shortcuts to dedicated online tools – and the results were surprisingly uneven. Some tools produced gorgeous, pixel-perfect PDFs. Others mangled layouts, dropped images, or cut text off mid-sentence.
If you also need to edit the resulting files afterward, check our roundup of the best free PDF editors – several of them handle annotation, merging, and text editing without paying a cent.
Quick Comparison Table
| Method | Type | Handles Complex Pages | Removes Clutter | Batch Support | Free Tier Limit |
|---|---|---|---|---|---|
| Chrome Print to PDF | Built-in | Good | No | No | Unlimited |
| PrintFriendly | Web + Extension | Average | Yes | No | Unlimited |
| PDFCrowd | Web + API | Excellent | No | Yes (API) | 5/month free |
| Firefox Reader Mode | Built-in | Average | Yes | No | Unlimited |
| Sejda HTML to PDF | Web tool | Good | No | Yes | 3 tasks/hour |
| CloudConvert | Web tool | Excellent | No | Yes | 25 conversions/day |
| wkhtmltopdf | Command line | Good | No | Yes | Unlimited |
1. Chrome Print to PDF (The Fastest Option)
Honestly, this handles about 80% of cases. Press Ctrl+P on Windows (or Cmd+P on Mac), change the destination to “Save as PDF,” and hit Save. Done in under five seconds.
Chrome renders the page through its print stylesheet, which most modern sites support reasonably well. I tested it on a long Wikipedia article, a Medium blog post, and an Amazon product page. Wikipedia and Medium came out clean. Amazon was a mess – sidebars overlapping, recommended products spilling into the main content, images scaled wrong.
Tips for Better Results in Chrome
Before saving, tweak the settings in the print dialog:
- Margins: Set to “Minimum” for more content per page. Default margins waste a lot of space.
- Background graphics: Check this box if you want images and background colors preserved. Chrome strips them by default to save ink, but for a PDF you usually want them.
- Scale: Drop to 80% if the layout overflows. Some sites have content wider than A4.
- Headers and footers: Uncheck this unless you want the URL and date printed on every page.
Best for: articles, blog posts, documentation pages. Anything text-heavy with a simple layout.
Weak spots: pages with heavy JavaScript rendering, infinite scroll, sticky navigation that repeats on every PDF page, paywalled content (you get the paywall in your PDF).
2. PrintFriendly – Clean PDFs Without the Junk
Here’s the thing about saving most webpages: you don’t actually want the whole page. You want the article. Not the cookie banner, not the sidebar ads, not the navigation menu, not the newsletter popup.
PrintFriendly strips all that out before generating your PDF. Paste a URL at printfriendly.com, and it extracts the main content – article text and relevant images – into a clean, readable layout. You can also manually delete sections you don’t want before downloading.
I ran the same Amazon product page through PrintFriendly. Night and day difference compared to Chrome’s raw print. It pulled just the product title, main image, description, and specs. No “Customers also bought” noise, no sidebar.
PrintFriendly Pros
- Genuinely removes clutter – not just hiding it, but restructuring the layout
- You can click to delete individual images or paragraphs before saving
- Free Chrome and Firefox extension available
- No signup needed
- Adjustable text size in the preview
PrintFriendly Cons
- Misses content on JavaScript-heavy sites (SPAs, React apps)
- Sometimes grabs navigation text as part of the article
- Tables occasionally lose formatting
- No batch processing
Best for: saving articles and recipes without the visual clutter. Particularly good for news sites packed with ads.
3. PDFCrowd – Most Accurate Layout Reproduction
PDFCrowd produced the most faithful reproductions in my testing. It runs a full Chromium rendering engine on its servers, waits for JavaScript to execute, and then captures the result. The output looked almost identical to what I saw in my browser.
The free plan gives you 5 conversions per month, which is fine for occasional use. Beyond that, plans start at $9.99/month. They also have an API if you need to automate things.
One feature I appreciated: you can set the viewport width. This matters because some responsive sites look completely different at 1200px versus 768px. Being able to control that means you can get the desktop layout even if the tool would otherwise grab the mobile version.
PDFCrowd Pros
- Full JavaScript rendering – handles React, Angular, Vue pages
- Custom viewport, margins, and page size settings
- API available for developers
- Supports HTTP authentication for password-protected pages
PDFCrowd Cons
- Only 5 free conversions per month
- Slow compared to browser print – takes 10-15 seconds per page
- Includes a small watermark on free-tier PDFs
Best for: complex, JavaScript-heavy pages where Chrome print fails. Also good for developers who need an API. If you need to convert raw HTML code instead, see our guide on how to convert HTML to PDF free.
4. Firefox Reader Mode + Print (The Hidden Gem)
Firefox has a built-in reader mode that strips a webpage down to just the text and images. Look for the document icon in the address bar – it appears on most article-style pages. Click it, and Firefox reformats everything into a clean, single-column layout with adjustable font size and background color.
From reader mode, press Ctrl+P and save as PDF. The result is a beautifully formatted document that looks like it came from a word processor, not a web browser. No headers, no footers, no navigation – just content.
I compared the same New York Times article saved through Chrome (cluttered, broken layout) and Firefox Reader Mode (clean, readable, properly paginated). Firefox won by a mile.
The Catch
Reader mode only activates on pages Firefox recognizes as articles. Product pages, dashboards, and web apps won’t trigger it. You also can’t use it on pages that block text selection or use heavy DRM. But for articles, blog posts, and documentation, this is my go-to method.
Best for: long articles, research papers, blog posts. Produces the cleanest output of any free method I tested.
5. Sejda HTML to PDF – Online with Options
Sejda is primarily known as a PDF editor, but their HTML-to-PDF converter handles URLs too. Go to sejda.com/html-to-pdf, paste your URL, and it renders the page and converts it. The free tier gives you 3 tasks per hour with a 50MB file size limit and 200-page cap.
What sets Sejda apart is the output options. You can choose page size (A4, Letter, Legal, or custom dimensions), orientation, margins, and whether to include background graphics. Most online converters give you zero control over these settings.
The rendering quality landed somewhere between Chrome and PDFCrowd in my tests. It handled static HTML sites well and managed basic JavaScript, but complex SPAs with lazy-loaded content produced incomplete PDFs. The pages that did render came out clean, with proper pagination and no visual artifacts.
Sejda Pros
- Multiple output format options (page size, orientation)
- Files auto-deleted from servers after 2 hours (privacy)
- Also handles raw HTML file upload, not just URLs
- No watermark on free-tier output
Sejda Cons
- 3 tasks per hour on free tier
- Struggles with JavaScript-heavy pages
- No batch URL processing on the free plan
Best for: users who want more control over page size and margins than browser print offers, without installing anything. The resulting PDFs tend to be large though – here’s how to compress them afterward.
6. CloudConvert – Best for Batch Conversion
CloudConvert supports over 200 file format conversions, and website-to-PDF is one of them. The interface is straightforward: select “website” as input, “PDF” as output, paste your URL, and convert. You get 25 free conversions per day – the most generous free tier on this list.
Where CloudConvert really shines is batch processing. You can queue up multiple URLs and convert them all at once. I tested this with 10 documentation pages from a software project. All 10 converted cleanly in about 45 seconds total. The PDFs maintained proper formatting, kept images intact, and handled code blocks without mangling them.
The rendering engine is solid. It captured CSS Grid layouts, flexbox, and even some CSS animations (as static frames, obviously). Lazy-loaded images worked in about 70% of cases – it waits a few seconds after page load before capturing, but sites with aggressive lazy loading still produced blank image placeholders.
CloudConvert Pros
- 25 free conversions per day – most generous free tier
- Batch URL conversion supported
- Good rendering quality for modern CSS layouts
- API available for automation
- Integrations with Google Drive, Dropbox, OneDrive
CloudConvert Cons
- No clutter removal – you get the full page as-is
- Lazy-loaded images sometimes missing
- No viewport width control on free tier
- Occasional queue delays during peak hours
Best for: saving multiple pages at once. Documentation archives, research collections, or backing up a whole set of articles. The 25/day limit means you can process a decent amount without hitting a paywall.
7. wkhtmltopdf – Developer Power Tool
Not a point-and-click tool. wkhtmltopdf is an open-source command line utility that uses the WebKit rendering engine to convert HTML to PDF. If you’re comfortable with a terminal, this gives you the most control of any option here.
Install it on Linux, Mac, or Windows, then run:
wkhtmltopdf https://example.com/article page.pdfThat’s the basic usage. But the real power comes from the flags. You can set custom margins, inject CSS, add headers/footers with page numbers, delay rendering for JavaScript to load, set cookies for authenticated pages, and process hundreds of URLs from a text file in a loop.
I used it to archive 50 pages of technical documentation in about 2 minutes. Wrote a quick bash script that read URLs from a file and generated individually named PDFs. Try doing that with any web-based tool.
wkhtmltopdf Pros
- Completely free, open source, no limits
- Scriptable – process hundreds of URLs automatically
- Custom CSS injection for styled output
- Cookie and authentication support
- Runs offline after installation
wkhtmltopdf Cons
- Requires command line knowledge
- Uses an older WebKit engine – modern CSS features sometimes render incorrectly
- No GUI at all
- JavaScript support is limited compared to full Chrome
- Project is in maintenance mode (no new features)
Best for: developers and power users who need to batch-convert pages or integrate webpage-to-PDF into a workflow. Not for casual users.
Which Method Should You Use?
After testing all seven across different types of websites, here’s how I’d break it down:
- Just need a quick save of an article? Firefox Reader Mode. Cleanest output, zero setup.
- Need the page to look exactly like it does in your browser? PDFCrowd or Chrome Print to PDF with Background Graphics enabled.
- Saving a recipe or news article full of ads? PrintFriendly. It strips the junk better than anything else.
- Converting multiple pages at once? CloudConvert or wkhtmltopdf.
- Need an API for your project? PDFCrowd or CloudConvert.
For the resulting files, our free PDF editor roundup covers tools for annotation, signing, and merging if you need to work with the PDFs after saving them.
Common Problems and Fixes
The PDF cuts off content on the right side
The webpage is wider than the PDF page. In Chrome print, set Scale to 70-80% or switch to Landscape orientation. In online tools, look for viewport or page width settings.
Images are missing from the PDF
Two likely causes. First, lazy-loaded images that didn’t trigger before the capture. In Chrome, scroll through the entire page before printing. For online tools, PDFCrowd handles this best because it waits for JavaScript. Second, in Chrome print, make sure “Background graphics” is checked.
Sticky headers repeat on every page
Common problem with modern websites. The fixed navigation bar shows up at the top of every PDF page. Firefox Reader Mode avoids this entirely. For Chrome, you can open DevTools (F12), find the sticky header element, and add position: static !important before printing. Takes 10 seconds once you know how.
The PDF file is huge (20MB+)
Pages with lots of high-resolution images produce bloated PDFs. Use a free PDF compression tool to shrink the file after saving. I’ve gotten 25MB PDFs down to under 3MB without visible quality loss.
Paywalled content shows the paywall, not the article
Most paywall implementations block server-side tools entirely. Browser-based methods (Chrome Print, Firefox Reader Mode) work only if you’re logged in. For public library access or cached versions, check Google Cache or archive.org/web before attempting to save.
FAQ
Is it legal to save a webpage as PDF?
Saving a webpage for personal use is generally fine. Copyright applies to the content itself – you can’t redistribute or sell someone else’s articles just because you saved them as PDF. For personal reference, research, and offline reading, saving webpages is standard practice and no different from bookmarking.
Can I save a full scrolling webpage as one PDF, including below-the-fold content?
Yes. Browser print (Ctrl+P) captures the entire page including content below the fold. Scroll through the page first to trigger any lazy-loaded images. Online tools like PDFCrowd and CloudConvert also capture the full page length. The PDF will simply have more pages.
How do I save a webpage as PDF on my phone?
On iPhone, open the page in Safari, tap the Share button, then “Markup” or “Print.” In the print preview, pinch to zoom on the preview thumbnail to get a full-page PDF, then tap Share to save it. On Android, open Chrome, tap the three-dot menu, then “Share” and “Print.” Change the destination to “Save as PDF.”
What’s the difference between saving a webpage as PDF versus using “Save Page As” in the browser?
“Save Page As” downloads the HTML file plus all assets (images, CSS, scripts) into a folder. The result is a working local copy of the webpage, but it’s messy – dozens of files in a folder. Saving as PDF gives you a single file that’s easy to share, store, and read offline. The tradeoff is that PDF captures a static snapshot while “Save Page As” preserves interactive elements.
Which tool produces the smallest PDF file size?
PrintFriendly generally produces the smallest files because it strips ads, images, and navigation before conversion. A typical news article that produces a 12MB PDF through Chrome print comes out around 400KB from PrintFriendly. Firefox Reader Mode is the second most efficient. For any method, you can always compress the result afterward using a free PDF compressor.