Save a Web Page as PDF
URL to PDF fetches a public web address with WeasyPrint and saves the page as a PDF. JavaScript does not run, so pages that need scripts or a login come out empty or incomplete.
Fill in Webpage URL to continue.
URL to PDF passes `urlInput` to WeasyPrint and downloads `output.pdf`. There is no file upload. WeasyPrint fetches the URL itself; this is not headless Chrome and not a screenshot service.
JavaScript does not run. SPAs, bot walls, cookie gates, and pages that need a logged-in session usually print empty or incomplete. HTTPS errors and private network targets fail.
Only send URLs you are allowed to retrieve. Do not use this to bypass paywalls or authentication. The server sees the URL you typed.
If you already have the HTML, HTML to PDF is more predictable because you control the bytes.
Before rendering, the server checks `urlInput`. Only `http://` and `https://` addresses are accepted, URLs that embed a user name or password are refused, and loopback, private, link-local and other internal addresses are rejected. The same public-address rule is applied again each time WeasyPrint opens a connection, so a redirect to an internal host is refused too. Stylesheets, images and fonts that the page references are fetched under the same rules, which is why a page that pulls its CSS from a public CDN still prints with styling.
The fetcher follows a limited number of redirects, waits a short time for each resource, and gives up on pages or assets that are too large. When a fetch fails you get a plain-language message such as the page returned an HTTP status, the address could not be found, the site took too long to respond, a secure connection could not be established, or the URL redirects too many times. Those messages describe the main page; a single missing image usually just leaves a gap in the PDF.
WeasyPrint lays the page out with print CSS, not screen CSS. Rules inside `@media print` apply, `@page` rules can change margins and size, and long pages break across pages. Layouts that depend on viewport width, sticky headers, lazy-loaded images or cookie banners injected by script will look different from what you see in a browser tab.
Features
- Server refuses non-HTTP(S) schemes, embedded credentials and non-public addresses, including after redirects
- Print-CSS layout: `@media print` and `@page` rules are honoured
- WeasyPrint fetches `urlInput`; no file upload
- No JavaScript, no Chrome, fixed download name `output.pdf`
- Not a screenshot or authenticated-session printer
- Anonymous API at /api/v1/convert/url/pdf
When to use this tool
- Print a public static article to PDF
- Archive a CSS-based page that does not need JS
- Turn a simple documentation URL into a file
- Keep a dated copy of a public policy or terms page for your records, remembering the PDF is only as complete as the static HTML
- Produce a printable version of a public changelog or help article to attach to a support ticket
How do I save a web page as a PDF?
- Paste a public HTTP(S) URL you are allowed to fetch.
- Click Process. There is no paper-size field.
- Download `output.pdf`.
- Check whether CSS printed. JS-only sites will not.
- Copy the full address from the browser bar, including `https://`; a bare `example.com` is rejected as not a full URL.
- Open the PDF and scroll to the end: if only a header and footer appear, the content was injected by script and you should save the page HTML and use HTML to PDF instead.
- If you see an error message, read it before retrying: an HTTP status means the site answered with an error, a not-allowed message means the address is private or has credentials in it.
Limits and edge cases
- No JS, no cookies, no auth
- Not Chrome print
- Download name is always output.pdf
- Only public http/https hosts; loopback, private ranges and credential URLs are refused
- One URL per run; no paper-size, margin or viewport settings
Examples
- A public static blog post often prints as a readable PDF
- A JavaScript dashboard URL often prints blank
- Entering `http://192.168.1.10/report` is refused with a message that private and internal addresses are not allowed
- Entering `https://user:[email protected]/page` is refused because the URL contains a user name and password
- Entering `example.com` without a scheme is refused with a prompt to enter a full http:// or https:// URL; adding `https://` fixes it
Privacy for this tool
Files are uploaded over HTTPS, processed in memory or a short-lived temporary directory on our servers, and deleted when your result is ready. We do not keep copies for later browsing, training, or advertising profiles. See the Privacy Policy for retention details and AdSense cookie disclosures.
Frequently asked questions
- Why is the PDF blank?
- The page is built in JavaScript, blocked bots, or redirected to a login. WeasyPrint only sees the HTML it could download.
- Can I print a page I must log into?
- Not through this tool. Save HTML locally while logged in, then use HTML to PDF.
- Does it execute Chrome?
- No. It renders the page with WeasyPrint, which does not run JavaScript.
- What is the file name?
- Always output.pdf. The URL is not used as the name.
- Why does it say private or internal addresses are not allowed?
- The server only fetches public web hosts. Loopback addresses, addresses such as 192.168.x.x or 10.x.x.x, and hostnames that resolve to them are refused so the tool cannot be pointed at a network it should not reach. To print a page from your own machine or intranet, save the HTML and use HTML to PDF.
- Can I put a user name and password in the URL?
- No. URLs with embedded credentials are rejected. The tool also sends no cookies, so it cannot print pages behind a login.
- What does 'The page at that URL returned HTTP 403' mean?
- The site answered but refused the request, which is common for bot protection and paywalls. Retrying will not help. Save the page from your browser and convert the file with HTML to PDF.
- Why does the layout differ from my browser?
- WeasyPrint applies print styles and does not run scripts. Sites that hide content until JavaScript runs, or that only style well on screen, print differently. Check the page's print stylesheet or convert saved HTML.
- Can I convert several URLs at once?
- No. One `urlInput` produces one `output.pdf`. Convert each address separately and join the results with Merge.
Last updated:
Call this from code
Every tool on this site is a plain REST endpoint - no account or API key needed for anonymous use. Built for AI agents and developers as much as for browsers.
curl -X POST "https://pdf123.xyz/api/v1/convert/url/pdf" \
-F "urlInput=your-urlInput" \
-o output.pdfAlso available as an MCP tool for agent clients that speak Model Context Protocol (JSON-RPC 2.0 over POST /mcp). Full API reference
Use it from an AI agent
SkillClaude Code, Codex, Cursor and other AI agents can run URL To PDF for you with this skill: /skills/pdf123-url-to-pdf.md
Files are used only for this processing job and deleted automatically afterward.