Turn any public web page into an A4 PDF with selectable text, straight from its URL.
The URL to PDF Converter fetches a public web page in a server-side browser, waits for it to render, and returns the result as a PDF. JavaScript runs, stylesheets and webfonts load, and the finished layout is set on A4 portrait pages that paginate automatically, so a long article becomes a tidy multi-page document rather than one impossibly tall image. Wherever the page uses real text, the PDF keeps a real text layer: selectable, searchable, and readable by screen readers.
Saving a page from the browser menu works until the output has to be consistent. Print dialogs apply print stylesheets, add their own headers and footers, and produce different files on different machines, which becomes a problem the moment a PDF is a record rather than a convenience. This converter renders every page the same way on the server, and the same call is available through the HTML to Image API: post a URL to the screenshot endpoint with format set to pdf and archive the returned file from a script, a cron job, or a compliance pipeline.
Enter the full address of a public page, including the https prefix. The renderer visits the page as an anonymous, logged-out visitor, so what it captures is what a first-time reader would see.
A server-side browser engine fetches the page, runs its JavaScript, and loads its styles and fonts exactly as a desktop visit would. Single-page apps and client-rendered content are captured after they finish rendering, not as an empty shell.
Once rendered, the page is laid out on A4 portrait pages and paginated automatically. Text on the page stays text in the PDF, and vector elements such as SVG stay sharp at any zoom.
The finished PDF is served from the CDN as application/pdf. Download it for filing, or keep the hosted URL and link to it from an order record, a ticket, or an archive index.
Terms of service, pricing pages, and policy documents get edited without notice. Converting the page to PDF freezes its exact content and layout at a point in time, in a format that opens fine even when the original site no longer exists.
Teams in regulated industries keep copies of what was published: a promotion as it ran, a disclosure as it appeared, a claim as it was worded. A server-rendered PDF is a consistent, shareable record of exactly that, produced the same way for every page captured.
Suppliers that only show receipts inside a web portal leave you screenshotting for the accounts folder. Converting the receipt page to PDF produces a document that fits the same filing system as every emailed invoice, with the amounts still searchable.
A long read converted to PDF paginates cleanly, keeps its images, and travels to devices with no connection. Because the text layer is real, highlights and annotations work in any PDF reader.
Release notes, changelogs, and how-to pages often need to travel with an email, a support ticket, or an audit pack. Converting the live page keeps the attachment identical to what was published, with none of the copy-paste reformatting.
A long documentation page flowed onto A4 pages, with the headings and code blocks preserved as selectable text.
A legal page captured as it appeared on a given date, ready for a compliance archive. The wording stays searchable, so retrieving a clause later is a text search rather than a re-read.
An article with images and pull quotes, paginated for reading or printing, produced from nothing but its URL.
Redirects, tracking parameters, and mobile subdomains can land the renderer somewhere other than the page you meant. Paste the final, canonical address from the browser bar and the capture matches what you were looking at.
The renderer arrives with no cookies and no session, so a page behind a login converts as its logged-out state, usually a sign-in form. The same applies to paywalled articles and region-gated content: the PDF shows what an anonymous visitor sees.
A first-time anonymous visit triggers the same consent banners a new reader gets, and they are captured in the PDF. When calling the API you can pass a css parameter that hides the selectors you do not want in the document, which is the cleanest way to remove page furniture.
The converter waits for the page to render before capturing, but apps that load data in stages can still be caught mid-paint. The API accepts ms_delay and wait_for_selector parameters that hold the capture until a fixed delay has passed or a chosen element exists.
The PDF does not stamp a capture date onto the page. If the file is an archive record, store the captured-at time and the source URL alongside it, or put both in the filename, so the snapshot can be placed in time later.
How is this different from the browser's Save as PDF?
The browser print pipeline applies @media print styles, adds its own headers and footers, and varies by browser and operating system. This converter renders the page server-side with its normal screen styles, so the same URL produces the same document for everyone, and the conversion can be scripted through the API.
Does JavaScript on the page run?
Yes. The page loads in a real browser engine, so client-rendered frameworks, charts, and embedded widgets execute the way they do for a normal visitor. Content that only appears after user interaction, such as a tab that must be clicked, is not captured.
Can I convert a page that requires a login?
No. The renderer visits anonymously, so a URL behind authentication converts as its logged-out state, which is usually a sign-in page. For your own application the better pattern is to render the underlying markup directly through the HTML endpoint, which needs no session at all.
What page size does the PDF use?
A4 portrait, paginated automatically across as many pages as the content needs. Other page sizes and landscape orientation are not available yet.
Is the text in the PDF selectable?
Yes, wherever the source page uses real text. The PDF keeps a vector text layer with the page fonts embedded, so text can be selected, copied, and searched. Text baked into images on the source page stays an image.
How do I automate URL to PDF conversion?
Post the URL to the screenshot endpoint of the HTML to Image API with format set to pdf. The response returns a hosted URL for the file, and passing a webhook_url runs the conversion async with the result delivered by callback. Each conversion costs one credit.
How much does it cost?
The converter on this page is free, limited to three renders an hour and ten a day per visitor. A free account includes 25 renders a month with full API access, and paid plans cover archive-scale volumes.
Can I capture just part of the page?
Not in PDF mode: the selector and fullpage parameters apply to image output only, and a PDF always captures the whole document. To keep unwanted elements out of the file, hide them with the API's css parameter instead.
Generate 1200 by 628 X share cards from a title, description, and brand artwork.
Build a 1280 by 720 YouTube thumbnail from a title, a face, and a brand colour.
Generate course completion certificates with recipient name, date, and signature.
The URL to PDF Converter runs on the HTML to Image API. Call the same renderer from your own code with a free account. 25 renders a month on the free tier. See the pricing page for higher-volume plans.