TL;DR

If you save a link-heavy page — a resource roundup, a documentation page, a newsletter, a research bibliography — with a screenshot tool, the links die. They become pixels. To keep hyperlinks and in-page anchors clickable, you need a converter that uses Chrome's real print engine instead of pasting a screenshot into a PDF. Convert: Web to PDF does exactly that: it produces a genuine PDF with selectable text and live, clickable links — all generated locally on your machine, nothing uploaded.

There are two fundamentally different ways to turn a webpage into a PDF, and they produce very different files.

Screenshot-to-PDF. Tools like GoFullPage and many "full page screenshot" extensions do exactly what the name says: they take one long image of the page, then wrap that image in a PDF container. The result looks like the page, but it is a picture. You cannot select the text. You cannot search it (without OCR). And critically, every hyperlink is now part of a flat image — clicking it does nothing. The blue underlined text is just colored pixels.

Print-engine-to-PDF. The other approach hands the page to the browser's actual print pipeline — the same one behind Ctrl+P → Save as PDF. Because the browser understands the page's structure, it preserves the text as text and, crucially, keeps the <a href> links as real PDF link annotations. Click one in your PDF viewer and it opens the destination.

Convert: Web to PDF uses the second approach. It drives the page through the Chrome DevTools Protocol and Chrome's print engine, so you get a real document, not a photograph of one.

The three things you lose with a screenshot

  1. Clickable external links. A bibliography with 40 sources becomes 40 dead blue strings.
  2. In-page anchor links. Table-of-contents entries that normally jump you to a section stop working, because there's nothing for them to jump to inside a flat image.
  3. Selectable, searchable text. You can't copy a quote, Ctrl+F a term, or let a screen reader read it.

A PDF can carry two kinds of links, and a good web-to-PDF conversion preserves both:

  • External (URI) links — point to a web address. In your saved PDF, clicking the author's name in a newsletter opens their site.
  • Internal (anchor) links — point to a location inside the same document. This is what makes a table of contents work. On a long documentation page, the on-page "jump to Installation" link becomes a PDF internal link that scrolls you to that heading.

Because Convert: Web to PDF runs the page through Chrome's print engine, both kinds survive. The anchor links even get remapped to the right page in the PDF, so a 30-page documentation export still has a working contents list at the top.

CapabilityConvert: Web to PDFScreenshot tools (e.g. GoFullPage)Chrome Print → Save as PDF
External links stay clickableYesNo (flattened to image)Usually yes
In-page anchor / TOC links workYesNoOften broken on lazy-loaded pages
Selectable, searchable textYesNo (image only)Yes
Loads lazy images before captureYes (pre-scroll + Load All Images)VariesNo — prints only what rendered
Works on login-protected pagesYes (your existing session)VariesYes
Remove clutter before savingYes (Remove Elements, Article Mode)NoNo
Runs 100% locally, nothing uploadedYesVariesYes

Plain Chrome Print-to-PDF does keep links, which is why we're honest about it — it's a reasonable free baseline. Where it falls down is everything around the links: it prints only what happened to be rendered, so lazy-loaded images below the fold go missing, long pages get awkward page breaks through the middle of link text, and you have no way to strip a cookie banner or sidebar before saving. That's the gap Convert: Web to PDF fills.

A resource roundup or "best tools" list

You found a great curated list of 50 tools with links to each. Save it as a screenshot and you've saved 50 names you now have to re-Google. Save it as a real PDF and the whole list stays navigable offline.

A documentation page with a table of contents

Long docs pages almost always have an on-page contents list. Preserve the anchors and your offline PDF keeps that jump-to-section behavior — invaluable when you're reading a 40-page API reference on a plane.

A newsletter you want to keep

Newsletters are dense with links — the whole point is the outbound references. A flattened image throws away the actual value.

A research bibliography

Every citation with a DOI or URL stays one click from the source. For a literature review you're archiving, that's the difference between a reference list and a dead-end.

How to do it well

  1. Use the default (print) mode for link-heavy or code-heavy pages. Article Mode uses Readability to strip the page down to the main content, which is great for a clean essay — but it can drop things like <pre> code blocks. For a documentation page full of code or a roundup where the layout carries meaning, stick with the default mode.
  2. Pre-scroll / Load All Images first. Many pages lazy-load images and even some links as you scroll. Convert: Web to PDF can pre-scroll and force images to load so nothing is missing from the capture. See output quality tips.
  3. Remove the clutter, keep the links. Use Remove Elements to delete a cookie banner, sticky header, or ad column — with undo if you nuke the wrong thing. The links in your actual content stay intact.
  4. Pick a sane paper size. For wide documentation, Legal or Tabloid in landscape avoids cutting off code. A3/A4/A5/Letter/Legal/Tabloid/Ledger are all available, along with margins, scale, and orientation. More in customization options.
  5. Trigger it fast. Ctrl+Shift+P opens the converter without hunting through menus.

If the page sits behind a login — a paid newsletter archive, an internal wiki, a course page — Convert: Web to PDF uses your existing browser session, so it captures what you can already see. There's more on that in our guide to saving pages behind logins and in the login and private pages FAQ.

Don't take it on faith — a 20-second check saves you a useless archive:

  1. Open the PDF in your normal viewer (Preview, Acrobat, or your browser's built-in PDF viewer), not a thumbnail preview.
  2. Hover over a link. Most viewers show the destination URL in a tooltip or status bar. If nothing appears, the link is dead.
  3. Click one external link near the top and one near the bottom, to confirm links survived the full page and weren't cut off at a page break.
  4. Click a table-of-contents entry if the page had one. It should jump you to that section inside the PDF, confirming the internal anchor mapped correctly.
  5. Ctrl+F for a word you know is on the page. If it highlights, your text is real text, not an image — which also tells you the links are annotations, not pixels.

If a link doesn't work, the usual culprit is that you accidentally used a screenshot tool, or the page rendered the link via JavaScript in a way the print engine couldn't resolve. Re-running in the default print mode with Load All Images fixes the overwhelming majority of cases.

Long pages and page breaks

On a long roundup or docs page, links often sit right where the PDF wants to break between pages. Chrome's print engine handles this correctly — a link that straddles a page boundary stays clickable on both pages. Screenshot tools, by contrast, can slice a link in half visually and functionally, since the whole thing was already a dead image. If your saved PDF has awkward breaks through content, adjust the scale down a notch or switch orientation before re-saving; the links stay intact either way.

Article Mode vs. default mode: which to pick for links

Convert: Web to PDF offers an Article Mode that runs the page through Readability to strip it down to the core content — no sidebar, no header, no ads. It's excellent for a clean, readable essay or blog post. But there's a trade-off worth understanding for link-heavy or technical pages:

  • Article Mode can drop elements that Readability doesn't consider "article content" — notably <pre> code blocks on documentation pages. It may also reshape the layout in ways that matter if the structure itself carries meaning (like a comparison grid of linked tools).
  • Default (print) mode preserves the page as it actually renders, which keeps code blocks, complex layouts, and the full set of links exactly where they were.

The rule of thumb: for a plain article you want to read cleanly, Article Mode; for anything where the links, code, or layout are the point, default mode. When in doubt on a link-heavy page, default mode is the safe choice. You can read more in the output quality FAQ.

A note on what this is (and isn't)

This is a local convenience tool that makes an honest, high-fidelity PDF of a page you can already see. It does not do OCR, it does not upload your files to a cloud service, and it does not bypass paywalls or logins — it simply prints the page you're already authenticated to view. If you need a legally authoritative or notarized document, that's a job for an official service, not a browser extension. For most people, though, "a real PDF where the links still work" is exactly the missing piece.

Convert: Web to PDF works on any Chromium browser — Chrome, Edge, Brave, Arc, Opera, Vivaldi. It does not run on Firefox or Safari, which don't expose the same DevTools print pipeline.

While we're on the subject of saving what matters from the web: if you also watch a lot of long videos and want the ideas rather than the runtime, our sibling project CineMan AI summarizes video into readable notes.

  • Researchers and students archiving a bibliography or a literature review where every citation needs to stay one click from its source.
  • Developers saving API documentation offline, where the on-page table of contents and inline reference links are half the value.
  • Newsletter readers and curators keeping issues whose entire worth is the outbound links.
  • Anyone building a personal knowledge base who wants their saved pages to remain navigable, not just legible.

In every one of these cases, a flattened screenshot quietly destroys the most useful part of the page. A real PDF keeps it.

Frequently asked questions

Will the links in my PDF actually be clickable, or just blue text?

They'll be genuinely clickable. Because Convert: Web to PDF runs the page through Chrome's print engine rather than screenshotting it, external links become real PDF link annotations. Open the PDF, click a link, and it opens the destination.

Do table-of-contents and other in-page anchor links keep working?

Yes. In-page anchor links are preserved as internal PDF links, so a contents list at the top of a long page still jumps you to the right section inside the saved document.

How is this different from GoFullPage or other screenshot extensions?

Screenshot extensions save the page as one long image wrapped in a PDF. It looks right but it's a picture — no selectable text, no working links. Convert: Web to PDF saves a real document with both.

Isn't Chrome's built-in Print → Save as PDF good enough?

It's a fine free baseline and it does keep links. But it prints only what's currently rendered (so lazy-loaded images go missing), gives you no way to remove clutter like cookie banners, and often breaks anchor links on dynamic pages. Convert: Web to PDF handles all of that.

Does it upload my page to a server?

No. Conversion happens entirely on your device using Chrome's local print engine. Nothing is uploaded. See why a PDF converter should never upload your files.

Will the text be selectable and searchable?

Yes. The output is real text, so you can select, copy, and Ctrl+F inside the PDF — no OCR needed, because the text was never turned into an image in the first place.

Which browsers does it work on?

Any Chromium-based browser: Chrome, Edge, Brave, Arc, Opera, and Vivaldi. It does not work on Firefox or Safari.

Bottom line

If the links on a page are the whole point — a roundup, a bibliography, a docs page, a newsletter — don't flatten them into a dead image. Save the page as a real PDF where the hyperlinks and anchors still work, the text is selectable, and nothing leaves your machine. Convert: Web to PDF is built for exactly that, and you can read more on the tool page.