Webpage to PDF

Convert a web page via URL to PDF

Free
Online
No limits
Secure

URL of the webpage to be converted to PDF

By using this function, you accept our terms of use

The page is rendered on our server to produce the PDF — this tool isn't fully local like our other tools.

Frequently asked questions

How is this tool different from the others on this site?

It's the one tool that isn't fully local — converting a live web page to PDF requires rendering it on our server, since a browser can't render an arbitrary external page from client-side JavaScript alone.

Is it safe to convert any URL?

We only fetch and render the page you provide in order to generate the PDF; we don't store the page or the resulting file afterward.

Why did conversion fail for a page?

The page may block automated access, take too long to load, or the URL may be invalid — try double-checking the address.

Can I convert a page that requires a login?

No, the tool can only render publicly accessible pages, not ones that need you to sign in first.

Does the PDF look exactly like the web page?

It aims to — the page is rendered the same way a browser would display it, then saved as a print-ready PDF.

Why does this tool upload anything when the others don't?

Because it works on someone else's web page rather than your file. A browser tab isn't permitted to fetch and render arbitrary third-party sites, so the URL is sent to a server running headless Chrome, which loads the page and prints it. The server receives the URL and your page settings — no files, and no cookies from your session.

Can I save a page that requires me to log in?

No. The page is rendered anonymously, so anything behind a login or a paywall appears as it does to a logged-out visitor. For those pages, use your own browser's Print to PDF, which captures what you can actually see because you are already signed in.

Why is there a cookie banner covering my PDF?

Because the renderer never dismissed it — it visits the page fresh, with no stored preferences, so consent dialogs and pop-ups appear exactly as they do on a first visit. This is the most common reason a capture looks wrong. Printing from your own browser after dismissing the banner avoids it.

The page was cut off partway down. What happened?

Almost certainly infinite scroll or lazy loading. Content that only loads as you scroll never loads during rendering, because nothing scrolls, so feeds, galleries and search results capture only what appears initially.

Will the text in the PDF be selectable?

Yes. The page is printed rather than screenshotted, so the output holds real text — searchable, selectable, and with its links still clickable — rather than a picture of the page.

Saving a web page as a PDF captures it as it was: the text, the layout, the images, at the moment you asked. Pages change and disappear, and a link is a promise that the other end will still be there. A PDF is a copy you hold.

This is the one tool on the site that genuinely uses a server, and it is worth being straightforward about why. Rendering a web page means fetching it and running it in a real browser — following redirects, loading stylesheets and images, executing the JavaScript that builds most modern pages. A browser tab cannot fetch arbitrary other sites; the same-origin policy that makes the web safe forbids it. So the URL you enter is sent to a server that runs a headless Chrome, renders the page, and returns the PDF.

That means this tool sees the URL you submit, unlike every other tool here, which never sees anything. It does not see any of your files, and it renders the page as an anonymous visitor.

How to save a web page as a PDF

Paste the URL
Enter the full address of the page, including http:// or https://. It has to be a publicly reachable page.
Choose the page setup
Pick the paper size, orientation and margins the PDF should use. Wide pages generally read better in landscape.
Generate
The page is fetched and rendered in a headless browser. This takes a few seconds — longer for pages with a lot of images or scripts to run.
Download
The finished PDF is returned to your browser. Its text stays selectable and its links stay clickable.

Why this tool needs a server

Every other tool on this site works on files you already have, so the work can happen in your browser and nothing needs to be uploaded. Rendering someone else's web page is different in kind: your browser is not permitted to fetch and read arbitrary third-party pages, and even if it were, rendering a modern page means executing its scripts and waiting for what they build.

So the URL is sent to a server running headless Chrome, which loads the page the way any visitor would and prints it to PDF. The rendering is anonymous — it carries none of your cookies, so pages behind a login render as they appear to a logged-out visitor.

The server is given only the URL and your page settings. It does not receive files, and the rendered PDF is returned to you rather than retained.

What renders well, and what doesn't

Articles, documentation, blog posts: Render close to perfectly. These are the pages the tool is best at — text-led layouts with a clear reading order, often with a print stylesheet that improves the result further.
Pages behind a login: Won't work. The renderer visits as an anonymous user, so anything requiring a session shows the login page or a paywall. There is no way around this without handing over your credentials, which is not something you should do.
Infinite scroll and lazy loading: Captures roughly what a visitor sees before scrolling. Social feeds, image galleries and search results that load more content as you scroll will be cut short, because nothing scrolls during rendering.
Interactive content: Video players, maps, embedded apps and anything requiring interaction render as a static frame or not at all. A PDF is paper; it has no play button.
Content behind consent banners: Cookie dialogs and newsletter pop-ups appear in the render, often covering the content, because nobody dismissed them. This is the most common reason a capture looks wrong.

Page setup and pagination

Web pages are one continuous column of unbounded length; PDF pages are fixed rectangles. Converting means cutting that column into pages, and the cut lands wherever it lands — occasionally through the middle of an image or a table row. Some sites define print stylesheets that control this and come out beautifully; most don't.

Landscape helps with wide layouts and tables that would otherwise be clipped. Smaller margins fit more per page and reduce the number of awkward breaks. A4 and Letter differ enough in proportion to change where breaks fall, so if a capture is breaking badly, changing the paper size is worth trying.

Text in the output is real text, not an image, so the PDF is searchable and selectable and links within it remain clickable.

Limits and alternatives

Rendering runs with a time limit, so a very slow page or one that never finishes loading will fail rather than hang. Retrying often succeeds where the first attempt timed out on a slow third-party script.

Only public pages are reachable. Requests to internal addresses, private networks and non-web schemes are rejected — a necessary guard on any service that fetches a URL on your behalf.

For pages that need a login, your browser's own Print to PDF is the right answer: you are already authenticated, so it captures what you can actually see. For archiving a page permanently and publicly, the Internet Archive's Wayback Machine keeps a browsable copy. For a page you need exactly as displayed including expanded content, take a full-page screenshot and run it through Images to PDF.

Information