Save a webpage as PDF — the full guide.

The fastest way to save a webpage as a PDF is the browser's own print dialog: press Ctrl+P (or Cmd+P on Mac), change the destination to Save as PDF, and click Save. It works in every modern browser, produces a text-selectable file, and needs zero setup. For roughly 60% of pages that is the whole answer.

The other 40% is where this guide earns its keep. Print dialogs struggle with sidebars that clip, long articles that lose their last paragraph, dashboards that render half-empty, and any page behind a login wall. Online "URL to PDF" services hit the same walls from the other side — they fetch pages as anonymous visitors and get login screens or paywalls in return.

If you save webpages more than once a week, a dedicated extension pays for itself in about a day. Our recommendation is Convert: Web to PDF — it runs entirely in your browser (nothing uploaded, no account needed), captures pages at their real width, waits for lazy images to load, keeps links clickable, and works on any page you can see in the tab, login or no login. It's free, and the rest of this guide compares it against the alternatives honestly.

Skip ahead: the Chrome cut-off fixsection covers the single most-Googled complaint ("PDF is missing the sides of my page"), and the comparison table lets you match a method to your use case in about ten seconds. Everything below assumes a desktop browser; mobile has a short note in the FAQ.

1. Chrome / Edge / Brave print dialog. Chromium browsers all share the same print engine. Hit Ctrl+P, pick Save as PDF, expand "More settings" to reach paper size, margins, scale, and "Background graphics". This is the workhorse for article-style pages and anything with a print stylesheet. Links stay clickable, text stays selectable, and the file lives entirely on your machine.

2. Safari "Export as PDF".On macOS, Safari has two paths: File → Export as PDF produces a single long page with no pagination — great for reading — while the print dialog produces paginated output like Chrome. On iOS, the Share sheet has a PDF option once you tap "Options" at the top. Safari tends to render the on-screen layout more faithfully than Chrome, but its scaling controls are thinner.

3. A browser extension.An extension runs inside your logged-in tab, so it can see anything you can see. Good ones capture at the page's true viewport width (no clipping), auto-scroll to trigger lazy loads, and let you remove ads or sidebars before generating the file. Convert: Web to PDF is the one this guide walks through; PrintFriendly, SingleFile, and others cover overlapping ground with different trade-offs — see the PrintFriendly alternative comparison for details.

4. Online "URL to PDF" converters. You paste a link, they fetch it server-side, they send you back a PDF. Convenient for one-off public pages, useless for anything private, and the free tiers usually watermark or rate-limit. The safest option in this bucket is our own web tool, which does the rendering in your browser rather than on our servers — same no-upload promise as the extension, without needing an install.

Chrome's print engine paginates by fitting the page into a fixed paper size — Letter or A4 by default. If the page's CSS declares a viewport wider than the paper, Chrome scales it down; if the CSS uses fixed pixel widths that don't fit, Chrome clips them. That is why sidebars vanish, tables trail off, and code blocks lose their right edge. This isn't a bug — it is the paper metaphor doing exactly what paper does.

The three-step fix, in order:

1. Change Layout to Landscape. Wider paper, less clipping. Solves maybe half of cut-off complaints on its own.
2. Set Scale to "Fit to page width". This is the option most people miss — Chrome hides it under "More settings". It tells the print engine to shrink the whole page proportionally so nothing falls off the sides. Text gets smaller, but nothing disappears.
3. Enable "Background graphics". Off by default. Without it, dark themes turn white, colored callouts lose their fill, and code blocks become unreadable. Turning it on nearly always improves fidelity.

If those three don't solve it, the page is fighting the paper metaphor on purpose — dashboards, chat threads, canvas editors, anything with pinned sidebars. That is when you switch to an extension: Convert: Web to PDF captures the tab at whatever width you set the browser window to, so a 1440-pixel-wide dashboard produces a 1440-pixel-wide PDF, no scaling, no clipping. Deeper walkthrough: save a webpage as PDF without cutting off and print a webpage to PDF full page cover the settings screen by screen.

Convert: Web to PDF is a free Chrome extension that solves the page-capture problem end-to-end: full-length pages, real text and links, login-protected support, and no tracking of what you convert. Setup is two clicks and one page reload.

1. Open the Chrome Web Store listing and click Add to Chrome. It works in Chrome, Edge, Brave, Arc, Opera, and Vivaldi.
2. Pin the extension icon (puzzle-piece menu → pushpin) so the button is one click away.
3. Reload any tab where you want to test it, then click the icon. A small popover offers Save current page, paper size, margins, and a "Remove element" picker for cleaning up ads before capture.

The default settings produce a text-selectable PDF at A4 size with all backgrounds preserved. First save takes a second or two while the extension scrolls the page to trigger lazy content; subsequent saves on the same tab are near-instant. Nothing is uploaded, no account exists, and the code is small enough that the whole extension is under 300 KB.

If you want to try the browser-based version first without installing anything, the Convert: Web to PDF tool page links to a hosted web converter that shares the same rendering code. It's a good sanity check on whether the extension will handle a specific site the way you want.

The three page patterns that break naive tools are login walls, infinite scroll, and lazy-loaded images. All three come down to the same root cause: the content you want isn't in the initial HTML response. Any tool that fetches the URL server-side (or captures the DOM before scrolling) will miss it.

Login-protected pages. Webmail, dashboards, Notion docs, subscription articles, internal wikis — none of these are reachable from an online converter, because that converter hits your URL as an anonymous visitor. An extension solves this by capturing the tab you are already logged into. If you can read the page, the extension can save it. That covers everything from a Gmail thread to a Salesforce report to a paid research article.

Infinite scroll.Social feeds, long comment threads, and product catalogs load in chunks as you scroll. Chrome's Save as PDF captures only what has already rendered — so a fresh page with 1,000 hidden comments turns into a nearly-empty PDF. The workaround is to scroll to the true bottom first, wait for the spinner to stop, then save. Convert: Web to PDF automates this: it scrolls the page programmatically, waits for network activity to settle, then captures.

Lazy-loaded images.Most modern sites don't load images until they scroll into view. If you print immediately, half the images will be missing (or worse, replaced by grey placeholders). Manual fix: scroll top-to-bottom slowly before printing. Better fix: let the extension do the scroll, with an image-load check baked in. Result: no missing hero images, no half-loaded thumbnails, no grey rectangles where product photos should be.

Clickable links in a PDF matter more than people realize. A saved article without live links loses half its value: no jumping to citations, no following the "via" credit, no click-through on the CTA you archived for reference. Here is the short checklist for making sure links survive the save.

• Never use screenshot-based toolsif you need live links. A capture that is really a stitched-together image wrapped in a PDF has no clickable regions, period. Test with one page: if you can't select text in the PDF, links are dead too.
• Prefer DOM-based conversion.Chrome's Save as PDF, Safari's Export as PDF, and Convert: Web to PDF all generate the PDF from the page's live DOM, which is what carries the <a href> data through to the file.
• Watch for relative URLs. Some tools resolve relative links (/about) into absolute ones (https://site.com/about) before writing the PDF; others don't. Test one link that points to another page on the same site.
• Check anchor links separately. In-page anchors (#section-2) should either resolve to the correct page inside the PDF, or fall back to the absolute web URL. Broken anchors are a common gotcha in PDFs generated from single-page apps.
• For clickable PDFs from PDFs — say, extracting linkable references out of a research paper — flip the workflow with our PDF-to-link converter, which pulls a shareable link out of any PDF file.

When links must survive at all costs, generate the PDF, then open it and click every link you care about. Ninety seconds of testing beats discovering the archive is dead six months later.

Six criteria that matter for most people, four methods, one grid. Green means it handles this well by default; amber means it works with settings; red means it doesn't.

* The browser print dialog works on login-protected pages because it prints from your logged-in tab — but you still fight the same cut-off, lazy-load, and infinite-scroll issues as any other page.

Match your use case: one-off article, public page → Chrome Print or the free web converter. Daily saves, login pages, or dashboards → the extension. Nothing on this list involves handing your data or your logins to an unknown server.

Ten questions people ask most often about saving webpages as PDFs, answered in one place. If yours isn't here, the extension's help page has a longer list.