URL to PDF
Convert a webpage URL into a high-quality PDF document.
Drag & drop your PDF here
or click to select file
User Guide
Paste the address
There is no file to upload here — you provide a URL and the page is fetched and rendered for you. Include the full address with its https:// prefix so there is no ambiguity about what is being requested.
Make sure the page is public
The page is retrieved by a server that is not signed in as you. Anything behind a login — an order history, a webmail message, a dashboard — will come back as the sign-in screen rather than the content you can see. Use your browser’s own print-to-PDF for those.
Convert to PDF
Press the button. The page is loaded, allowed to render, and captured. Long pages become multi-page PDFs; the height of the page determines the length of the document.
Check what was captured
Open the PDF and compare it with the live page. Cookie banners, consent overlays and adverts are part of the page as delivered, so they can appear in the capture. If one has obscured the content, your browser’s reader mode followed by print-to-PDF usually gives a cleaner record.
About the URL to PDF Converter
Web pages are not permanent. Prices change, articles are edited after publication, terms are quietly revised, and confirmation pages vanish the moment you navigate away. Converting a page to PDF freezes it as it was, which is why this is most often used for things somebody might later dispute.
How the capture is made
A server runs a headless browser — a real rendering engine with no visible window — which requests your URL exactly as an ordinary visitor would, executes the page’s scripts, waits for rendering to settle, and then prints the result to PDF. It is the same print pipeline your own browser uses, driven programmatically.
Three consequences follow directly from that, and they explain almost every surprise people have with tools like this.
Why a logged-in page cannot be captured
The request comes from a server that has none of your cookies and no session. It is not you. A page behind a login therefore returns its sign-in screen, because that is genuinely what an anonymous visitor receives. For anything requiring an account, print to PDF from your own browser, which already holds the session.
Why some content is missing
Many sites load sections only when you scroll to them or interact with them. A capture that renders the page without performing those actions will not include what was never requested. Content-heavy articles convert predictably; interactive applications do not.
Why cookie banners appear
Because they were part of the page as served. The capture reflects what a first-time visitor receives, consent overlay included. That is arguably the more honest record, though if it obscures the content you want, reader mode in your own browser followed by print-to-PDF gives a cleaner page.
As evidence
A capture is a reasonable record for an ordinary dispute with a retailer or service, and far better than a description from memory. It is not a forensic archive: nothing in the file proves when it was made or that it was not altered afterwards. For anything with legal weight, a timestamped third-party archiving service carries considerably more authority.
Frequently Asked Questions
Can it capture a page I have to log in to see?
No. The request is made by a server with no access to your session or cookies, so a protected page returns its login screen. Print to PDF from your own browser, which is already signed in.
Why is there a cookie banner in my PDF?
Because it was part of the page as served. The capture reflects what an ordinary first-time visitor receives, and for most people that includes a consent overlay. Reader mode in your own browser is the quickest way to get a version without it.
The PDF is missing content that appears when I scroll.
Some sites load sections only as you reach them, or after a click. A capture that renders the page without those interactions will not include them. Pages built this way are more reliably saved from your own browser.
Does it work with a single-page app?
Sometimes. If the content is rendered by scripts after load, the result depends on whether rendering completes before capture. Content-heavy pages and articles convert far more predictably than interactive applications.
Is the PDF admissible as proof of what a page said?
It is a reasonable record for ordinary disputes with a retailer or a service, and far better than a description from memory. It is not a forensic archive; for anything with legal weight, a timestamped third-party archiving service carries more authority.
Are links in the page still clickable?
Anchors generally survive as links in the PDF, so you can follow them from the document. What they point at, of course, may itself have changed by the time you click — which is the reason for capturing the page in the first place.