TL;DR
Online webpage-to-PDF converters work fine for public marketing pages, blog posts, and documentation sites. They fail on anything behind a login: your dashboard, a Gmail thread, a Notion doc, an internal wiki, a paywalled article. The reason is simple — an online converter is a server somewhere fetching the URL you gave it, and that server does not have your cookies. PDFmyURL, PDFcrowd, and PrintFriendly are the three that mostly do what they advertise. Everything else in this space is either broken, laden with pop-ups, or a rebranded shell of one of those three. If you need login-protected pages captured, use a browser extension like Convert Web to PDF, which prints from your logged-in tab.
How online converters work (server fetch)
Every "convert URL to PDF" website works the same way. You paste a URL. Their server — sitting in a data centre in Frankfurt or Ashburn — makes an HTTP request to it. It receives whatever HTML the target site sends to an anonymous, cookie-less visitor, renders it in a headless Chromium, prints to PDF, hands you the file.
That pipeline works beautifully for anything on the public internet: a Wikipedia article, a product page, a marketing site, a blog post, a documentation page. The server gets exactly the HTML you would get in an incognito tab, and the PDF matches what an anonymous visitor sees.
Four technical wrinkles separate the good converters from the bad:
- JavaScript rendering. Older converters fetched raw HTML — fine for server-rendered pages, blank for React/Vue/Next.js sites. Modern converters run a real headless browser.
- Lazy-loaded images. Pages that defer image loading until scroll produce PDFs full of grey placeholders unless the converter programmatically scrolls first.
- Print CSS. Sites can define
@media printstyles that strip nav, sidebars, and ads. A converter that respects them produces cleaner output. - Web fonts. Fonts from Google Fonts or a CDN sometimes fail on server-side headless browsers, producing fallback typefaces.
None of this matters for a static blog post. All of it matters for a complex web application.
The login-protected caveat
This is the part online converters do not put in their marketing copy: they cannot convert anything you need to log in to see.
The server fetching your URL is not you. It has no session cookies, no authentication tokens, no OAuth grants. When it requests https://mail.google.com/mail/u/0/#inbox, Google's servers see an unauthenticated request and return the login page. The converter renders the login page. You get a PDF of a login screen. Sometimes it gets clever and returns an error like "The URL could not be loaded" — which is more honest but equally useless.
The list of pages you cannot convert with an online tool is longer than you might think:
- Gmail, Outlook, or any email thread
- Notion, Confluence, private Google Docs, Slack threads, Jira tickets
- Your bank statement, credit card page, PayPal history, Amazon orders
- Any admin panel, dashboard, or analytics report
- Substack, WSJ, FT, or Medium content behind a paywall
- Anything on a corporate intranet or VPN
- A "share this URL" link generated by an app but tied to your logged-in session
If a friend cannot open the URL in a fresh browser without any of your credentials, an online converter cannot either. This is not a bug in any specific tool — it is a fundamental limit of the "paste URL, get PDF" model. The only way to get a real PDF of a page you had to log in to see is to convert it from your browser, from your logged-in tab. That means a browser extension or the browser's own print-to-PDF.
PDFmyURL
PDFmyURL is the oldest player in this space and probably the most reliable for the "one URL, one PDF" job. The homepage is a single field: paste a URL, click, get a file.
Where it works well. Public content-heavy sites, documentation, blogs, corporate marketing pages. It runs modern Chromium, respects print CSS reasonably well, and produces clean PDFs with working links and selectable text. Output looks close to what Chrome's own print dialog produces.
Where it fails. Anything JavaScript-heavy that also gates content — many news sites, single-page apps, sites with aggressive bot detection. Cloudflare-protected pages sometimes return a challenge page which is what gets rendered. Sites that check the user agent or block known data-centre IP ranges (which most of PDFmyURL's servers are on) will either serve a stripped-down version or block outright.
Pricing. Free for occasional single-URL conversions with a small watermark or size limit. Paid plans start around $9/month for higher volume and API access. They lean heavily into their API — most of their business is developers who want to programmatically generate PDFs of their own pages, which is honestly the use case the tool is best at.
The honest verdict. If you need to convert a public URL every now and then, PDFmyURL is fine. If you need to convert your Notion pages, do not use it.
PDFcrowd
PDFcrowd offers both HTML-to-PDF (paste HTML) and URL-to-PDF (paste URL). The URL side works similarly to PDFmyURL — server fetches, headless browser renders, PDF comes back.
Where it stands out. PDFcrowd tends to handle CSS more faithfully than most competitors. Multi-column layouts, background images, page breaks, and print CSS all work about as well as they do in Chrome itself. Their conversion engine has more knobs to turn than PDFmyURL — you can set page size, orientation, margins, header/footer templates, JavaScript execution delay, and a few dozen other options.
Where it fails. Same fundamental limit: no login-protected content. A more subtle issue is that PDFcrowd is often more aggressive at running JavaScript, which sometimes triggers analytics scripts, consent banners, or lazy-loaded ads that end up baked into the PDF. Cookie banners in particular have a habit of dominating the top of the rendered page, since PDFcrowd's server has no history of "accepting" them.
Pricing. A free tier that works well enough to evaluate but adds a watermark. Paid API tiers start around $9/month. The free web form is fine for a one-off; anything recurring pushes you toward the API.
The honest verdict. Better rendering fidelity than PDFmyURL for complex public pages. Same wall the moment you hit anything requiring authentication. If you are a developer generating PDF invoices from your own HTML templates, PDFcrowd is arguably the best of the three.
PrintFriendly
PrintFriendly is the odd one out. Instead of trying to reproduce the page exactly, it tries to clean it up — the same idea as Safari's Reader View or Firefox's reader mode. You paste a URL, and it extracts the main article, strips out navigation, ads, social buttons, comments, and pop-ups, and produces a PDF that reads like a magazine tear-sheet.
Where it works well. News articles, blog posts, essays, long-form journalism — anywhere the goal is to save the content for later reading, not preserve the exact visual layout. The PDFs are small, print beautifully, and don't waste ink on sidebars. There is a browser extension version that does the same thing but from your logged-in tab (which sidesteps the login caveat for reader-friendly content).
Where it fails. Anything that is not primarily an article. Dashboards, tables, applications, checkout flows, image galleries — PrintFriendly's article-extraction heuristics either produce a blank PDF or grab the wrong thing. It is also more aggressive about stripping content than most users expect; important callouts, images, or footnotes sometimes vanish.
Pricing. Free with ads on the site itself; the extension is free with no watermark. It monetises through ads on their web app and enterprise plans for organisations that want to strip a bit of tracking.
The honest verdict. The best of the three for saving articles to read later. The worst of the three if you need pixel-accurate layout preservation.
Chrome extension alternative
The one thing every online converter cannot do — capture a page you had to log in to see — is exactly what a browser extension can do trivially. It runs inside your browser, sees the page you already have loaded, uses your session, and prints from there. No new fetch, no credentials to hand over, no server on the other side of the world guessing at your cookies.
Convert Web to PDF is the tool we built for this. One click on any tab — including Gmail, Notion, your bank, an admin dashboard, or a private GitHub issue — produces a PDF of what you can see. It runs entirely locally: nothing is uploaded, no account is required, no server sees your page. Because it prints from your tab, cookies and authentication are irrelevant to it in the same way that Chrome's own Cmd+P dialog is unaware of them — it is just printing what is on screen.
The tradeoff is that it does not work if you are not already logged in and on the page. You cannot hand it a list of 500 URLs and walk away. For that job, an online API is the right tool — but for the daily "I need a PDF of this thing I am looking at right now" case, an extension takes about one second and works everywhere.
For a broader comparison of the extension category, see our roundup of the best web-to-PDF Chrome extensions.
Comparison table
| Tool | Public pages | Login-protected | Article cleanup | Layout fidelity | Free tier | Data leaves your browser |
|---|---|---|---|---|---|---|
| PDFmyURL | Good | No | No | Good | Yes (watermark) | Yes |
| PDFcrowd | Very good | No | No | Very good | Yes (watermark) | Yes |
| PrintFriendly (web) | Good | No | Yes | Low (by design) | Yes (with ads) | Yes |
| PrintFriendly (extension) | Good | Yes | Yes | Low (by design) | Yes | No |
| Convert Web to PDF | Good | Yes | No | Very good | Yes | No |
| Chrome print (Cmd+P) | Good | Yes | No | Good | Yes | No |
The pattern is obvious once you lay it out: any tool that runs in your browser can handle authenticated pages; any tool that runs on someone else's server cannot. That is the single most important distinction in this whole category, and it is the one online converters bury the deepest.
For related reading on whether the "your data leaves your browser" column actually matters to you, see Are online PDF converters safe in 2026? and our best free PDF converters roundup for the wider set of local options.
Frequently asked questions
What's the best free online webpage-to-PDF converter?
For a random public URL you need in a hurry, PDFmyURL is the least friction — one field, no signup, downloads immediately with a small watermark. For better rendering of complex layouts, PDFcrowd is a step up but hits the same free-tier watermark. For saving articles specifically, PrintFriendly beats both because it strips the noise around the content. None of them handle login-protected pages, so if that is your use case none of them is "best" and you should use a browser extension instead. All three have paid tiers if you need clean, unwatermarked output or API access.
Can I convert a login-protected page to PDF online?
No. This is the single hardest limit in the category. An online converter is a server fetching your URL from a data centre — it has no way to authenticate as you. When it requests your Gmail inbox or a private Notion doc, the target site returns the login page and that is what gets converted. Some tools obscure this by returning an error instead of a login-page PDF, but the underlying limitation is the same. The only ways to PDF an authenticated page are: a browser extension, your browser's own print dialog (Cmd+P), or feeding cookies to an API — the last requires developer work and is a security minefield.
Why does PDFmyURL fail on some sites?
Three common reasons. First, bot detection — Cloudflare and Akamai flag data-centre IP ranges and serve a challenge page. Second, JavaScript-heavy sites need long render delays; the default timeout may not be enough. Third, region gating — a site restricted to certain countries shows a "not available" page to PDFmyURL's servers. If a URL renders fine in an incognito tab but produces a broken PDF, it is almost always one of these three.
Is PrintFriendly better than PDFcrowd?
They solve different problems. PrintFriendly is a reader-mode PDF generator — it strips everything that is not the main article and gives you a clean, print-optimised layout. PDFcrowd tries to reproduce the page exactly as rendered. For saving a news article to read on a Kindle, PrintFriendly wins. For preserving a marketing page or documentation site as it looks in a browser, PDFcrowd wins. Neither handles login-protected content. If the goal is "capture this page as I see it right now, warts and all," PDFcrowd is closer; if the goal is "save this article to read later," PrintFriendly is closer.
Can I convert a webpage to PDF without an account?
Yes, on all three tools covered here. PDFmyURL, PDFcrowd, and PrintFriendly all let you paste a URL and download a PDF without signing up. The free versions add a watermark, cap file size, or limit daily conversions, but you do not have to hand over an email. Browser extensions like Convert Web to PDF also work with no account. Be suspicious of any "free webpage to PDF" service that demands an email just to convert one URL — that is a lead-generation site, not a tool.
Bottom line
Online converters are fine for the job they can actually do: turn a public URL into a PDF. PDFmyURL is the simplest, PDFcrowd renders the most faithfully, PrintFriendly is the best for saving articles. The moment you need to convert anything behind a login — your inbox, your dashboard, a private doc, a paywalled article — no online tool can help you. The pipeline they use, "our server fetches your URL," breaks the instant authentication is required. For those pages, you need a tool that runs in your browser and prints from your logged-in tab. That is what Convert Web to PDF does, in one click, entirely locally.