PdfLuxe › Tools › Webpage to PDF
Webpage to PDF
Some pages are worth keeping exactly as they look: an article, a receipt page, a documentation entry, a booking confirmation. This tool turns a public web page into a PDF — you paste its address, and the PdfLuxe server loads the page in a real browser engine and prints it to A4, backgrounds included. One honest difference from most PdfLuxe tools: the conversion runs on the server, because your own browser is not allowed to fetch and print another website's page. The address you type is all that is sent: free, with no sign-up and no watermark.
URL → PDFHow to use Webpage to PDF
- Paste the full address of the page (starting https://) — the address is sent over HTTPS to the PdfLuxe server; your browser does not fetch the page itself.
- The server loads the page in a real browser engine, waits for it to finish loading (up to 60 seconds) and prints it to an A4 PDF with backgrounds. One job runs at a time, so a heavy page may take a moment — the heaviest page tested took about 13 seconds.
- Download the PDF — the page as it renders, in a file you can save, print or share.
Good to know
- Price: free. There is no paid plan, no credits and no trial.
- Sign-up: none. The tool opens and works straight away.
- Watermark: none is added to anything you download.
- Where it runs: on the PdfLuxe server. This is one of the few PdfLuxe tools that sends anything to a server: the web address you type goes over HTTPS to api.pdfluxe.com, which loads the page in a real browser engine and returns the PDF. No file of yours is involved — there is nothing to upload.
- Input: a public http:// or https:// page address. Private, local and internal addresses are refused by the server, and pages behind a login cannot be converted — the server has no account or session on the site.
- Output: an A4 PDF with backgrounds printed, capped at 25 MB.
- Part of: the Convert tools in PdfLuxe — 151 free tools in one place.
How Webpage to PDF works
When you press Convert, the address you typed travels over HTTPS to PdfLuxe's own server, where a real browser engine — the same kind of engine that powers desktop browsers — opens the page the way a visitor would. Scripts run, images and fonts load, and the page settles into its final layout. The server then uses the browser's own print-to-PDF step, set to A4 with backgrounds printed, and sends the resulting file back to you. A long page simply flows across as many A4 sheets as it needs.
The reason this happens on a server rather than in your tab is a rule of the web itself. Browsers enforce cross-origin rules: a page open in your tab may read its own site's content, but it may not reach into a different website, fetch that site's page and print it. That rule is what stops a malicious page from reading your banking tab, and it also means no in-browser tool can honestly offer “paste a URL, get a PDF”. The options were a server-side browser or no tool at all — so the server step is stated openly here and inside the tool, before anything is sent.
Because a real browser engine is heavy, the server converts one job at a time. In testing, ordinary pages came back in a few seconds and the heaviest page took about 13 seconds; a page that is still loading after 60 seconds is given up on and returns an error instead of hanging forever.
When to use Webpage to PDF
- Saving an article or announcement before it changes. Web pages get edited and deleted; a PDF keeps the version you actually read, with its layout intact.
- Keeping a receipt, confirmation or invoice page. Checkout and booking flows often end on a page you are told to print. As a PDF it can be filed, emailed or attached to an expense claim.
- Reading documentation offline. Convert the manual or help pages you rely on and keep them with the project, readable on a plane or a site visit with no connection.
- Sharing a page with someone who cannot open it. A PDF opens everywhere, including for people the original page — behind a geo-block or an awkward viewer — does not reach.
Privacy — this tool uses the PdfLuxe server
Most PdfLuxe tools process your files on your own device and send nothing anywhere, and their pages say so. This page says the opposite, plainly: converting a live web page is a server job. When you use this tool, the address you type is sent over HTTPS to PdfLuxe's own server at api.pdfluxe.com, which fetches the page from the site that hosts it, renders it in a browser engine and returns the PDF to your browser for download. Two consequences are worth knowing. The site you name sees a visit from the server, as it would from any visitor. And if an address itself is private — for example a link with a token in it, or an internal company address — do not paste it here: private and internal addresses are refused, and a token-bearing link would travel to the server and to the site. For a page only you can see, open it in your own browser and use its Print → Save as PDF instead.
Why the print dialog is not the same tool
Every browser can already print the tab you are looking at, and for a page you have open — especially one you are signed in to — that is the right method, and it stays entirely on your device. What the print dialog cannot do is start from an address: hand it a URL for a page you are not on, on a site you may not even have visited, and there is nothing to print. Fetching a page from an address is exactly the step cross-origin rules reserve to servers, which is the gap this tool fills. The two routes complement each other: signed-in and private pages belong to your own browser's print dialog; public pages you have an address for belong here.
Tips for a clean result
- Open the page yourself first. If it loads for you without signing in, the server will see the same public page. If you land on a login screen, the PDF will show that login screen too.
- Prefer the print or reader address when a site offers one. Many news and documentation sites have a print-friendly version of a page; its address converts to a cleaner PDF than the full page with its banners and pop-ups.
- Expect cookie and consent banners. The server visits as a fresh, logged-out reader, so a consent banner the site shows new visitors may appear in the PDF — that is the page as a stranger sees it.
- Check the page count afterwards. Long pages make long PDFs. If you only need part of one, crop or extract pages afterwards with the organizing tools.
Honest limits
The input is an address, not a file: http:// and https:// only, and the server refuses private, local and internal addresses — it will not fetch them. Pages behind a login cannot be converted, because the server has no account or session; it sees what a logged-out visitor sees, including consent banners. The server converts one job at a time, so a heavy page — or a busy moment — can mean a short wait; the heaviest page in testing took about 13 seconds. A page must finish loading within 60 seconds: pages that never stop loading, such as live dashboards that poll forever, return an error rather than a PDF. The finished PDF is capped at 25 MB. And if the site itself answers with an error page — a 404 or a 500 — that error page is what gets printed, exactly as printing in your own browser would; only failures to reach the site at all return an error from the tool.
Questions people ask
Is Webpage to PDF really free?
Yes. Every tool in PdfLuxe is free with no premium tier: no sign-up, no credits that run out, and no watermark on what you download.
Is anything uploaded when I use this tool?
There is no file to upload. Instead, the web address you type is sent over HTTPS to PdfLuxe's own server (api.pdfluxe.com). The server loads the page in a real browser engine, renders it and returns the finished PDF to you. Most other PdfLuxe tools run entirely in your browser and send nothing anywhere; this one cannot, for the reason the next answer explains.
Why does this tool use a server when most PdfLuxe tools do not?
Because of the web's cross-origin rules. Your browser is not allowed to reach into another website, fetch its page and print it — a page may only read its own site's content. So no converter for live web pages can run inside your browser tab. A server-side browser can load the page the way a visitor would and print it to PDF, which is why this one tool works on the PdfLuxe server, and says so openly.
Can it convert a page that is behind a login?
No. The server has no account, no password and no session on the site you name, so it sees the page exactly as a logged-out visitor would — usually the login page itself. Anything that needs you to be signed in, or that sits inside an app after sign-in, cannot be converted by this tool.
What will the PDF look like?
The page is printed the way it renders in a real browser: A4 pages, with backgrounds printed rather than stripped, and a long page flowing across as many sheets as it needs. JavaScript runs before printing, so pages that build themselves in the browser — articles, documentation, product pages — come out as you see them on screen, not as empty shells.
What are the limits?
The address must be a full http:// or https:// URL, and private, local or internal addresses are refused — the server will not fetch them. The server converts one job at a time, so a heavy page can take a moment: the heaviest page in testing took about 13 seconds. A page must finish loading within 60 seconds, and the finished PDF is capped at 25 MB.
The page I converted shows an error page — why?
If the site answers with an HTTP error page — a 404 or 500 — the server prints that error page, exactly as your own browser would if you printed it. Only network-level failures return an error instead: a site that cannot be reached at all, or a page that never finishes loading.
What happens if the conversion fails?
The tool answers with a plain message saying why — usually that the page did not finish loading inside 60 seconds (pages that poll forever, like live dashboards, hit this), that the address was refused, or that the site could not be reached. Check that the address opens in your own browser and try again.
Related tools
Questions about this tool? Email support@pdfluxe.com.