Guide

How to Convert a URL to PDF Online — Save Any Webpage Free, No Watermark

Save any public webpage as a PDF — Chromium-rendered, no software, no sign-up, no watermark. Step-by-step guide, what renders well, common problems (login walls, cookie banners), comparison vs Smallpdf and iLovePDF.

8 min readconvertpdfgo teamUpdated

You read a great article and want to archive it before the site paywalls it. You found a Stack Overflow thread with the answer to your problem and want to read it offline on the plane. You need to bundle a few blog posts as a single PDF for an email handoff. Paste, click, download. Here's how, in fifteen seconds.

When you actually need URL → PDF

Real cases: archiving articles before the source paywalls or de-publishes them, saving recipes from a phone-friendly cooking site, capturing a competitor's pricing page as evidence, building offline reading lists for a flight, bundling research sources for a paper, and creating PDF snapshots of dashboards for weekly reports.

Why URL → PDF when every browser has "Print → Save as PDF"? Three reasons: a clean output without browser-print artefacts (ads, sidebars, "print this page" popups stripped), batch conversion for multiple URLs (no clicking through each), and the ability to convert URLs from a phone or tablet where Print to PDF is awkward or unsupported.

When to use HTML → PDF instead

If you have the HTML markup locally (a generated report, a templated invoice, AI output), use HTML to PDF — paste the markup directly, no public URL needed.

How to convert a URL to PDF, step by step

1

Open the URL to PDF tool

Go to convertpdfgo.com/url-to-pdf. No account, no email, no installation.
2

Paste the URL

Paste any public webpage URL — articles, documentation, dashboards, anything that loads in a browser without a login.
3

Headless Chrome fetches and renders

The renderer waits a few seconds for the page to fully load (including lazy-loaded images and JavaScript-rendered content), then snapshots.
4

Download the PDF

The output is a single PDF, A4 portrait by default, with the page rendered exactly as Chrome would show it.

What renders well — and what stays awkward

Works well: articles, blog posts, documentation pages, Stack Overflow threads, GitHub README files, simple landing pages. Any page designed to be readable in a browser also reads well as a PDF.

Works mostly: infinite-scroll feeds (Twitter timelines, Reddit threads), pages with heavy lazy-loading, SPAs that take a few seconds to settle. We wait for the page to settle, but really aggressive lazy-load might leave some images blank.

Hard cases: pages behind login walls (renderer has no cookies), pages that detect headless browsers and serve a different version, video-heavy pages (the video itself can't render as PDF — only its poster image).

For pages behind login

Open the page in your own browser → File → Print → Save as PDF. The result will have your authenticated view, which the headless renderer can't access. URL to PDF works for public pages only.

Common conversion problems and how to avoid them

The page says "You need to log in"

The renderer has no cookies, so authenticated content is invisible to it. Use your browser's Print → Save as PDF instead, or unlock the public version of the page if there is one.

A cookie consent banner covers half the content

European sites sometimes show a GDPR banner that the headless renderer can't dismiss. Workaround: open the page in your browser, accept cookies, then copy the URL — the renderer respects the same cookie state if you re-submit within the same session.

Images come out as broken icons

Lazy-loaded images that hadn't loaded when the snapshot ran. We give a few seconds for the page to settle, but very aggressive lazy-loading might still leave some blank. Scroll the page in your browser before noting the URL, since many sites cache aggressively.

A short word on privacy

Three things to know. One: the URL you paste goes over TLS 1.3. Two: the URL and output PDF are encrypted at rest, then deleted within one hour. Three: we don't log which URLs you converted — the input URL is processed and discarded along with the file.

How we compare to other free URL-to-PDF tools

FeatureconvertpdfgoSmallpdfiLovePDF
RendererReal ChromiumChromiumChromium
Sign-up NoneAfter 2/dayOptional
Watermark None None None
Auto-delete1 hourVague2 hours

Frequently asked questions

Do JavaScript-heavy pages work?

Yes. The renderer waits for the page to settle before snapshotting, so React/Vue/SPA content lands in the PDF.

What about pages behind a paywall?

Only if the paywall lets you read the article first (some sites give 3 free articles before the wall). For hard paywalls, the renderer sees the paywall, not the content.

Can I convert a YouTube video page?

The page renders, but the embedded video can't play in a PDF — you'll get the video's thumbnail.

How long does it take?

2–5 seconds for typical pages. Pages with lots of lazy-loaded images or slow APIs can take up to 15 seconds.

What page size does the PDF use?

A4 portrait by default. The rendered page itself doesn't change size — wider pages just get scaled down to fit.

Can I convert multiple URLs at once?

Right now the tool is one-at-a-time. After converting each, use our merge tool to bundle them into one PDF.

Is there a usage limit?

No. Free, no daily cap, no sign-up wall, no watermark.

What to do next

One-click follow-ups

Convert multiple URLs, then merge them as one PDF, compress, protect, or watermark. All free.

Or browse our full list of 49 free PDF tools.