About Web to PDF
Web to PDF loads the address you give it in a real web browser, waits for the page to settle, and hands you the result: a print-ready PDF with selectable text, or a pixel-accurate PNG of the whole page.
The device size matters because websites serve different layouts per screen. A phone-sized viewport captures the mobile version, a desktop one the full site, and a custom size fits whatever screen you are designing or testing for.
How to use Web to PDF
- Paste the page address.
- Pick a device size, or set a custom viewport.
- Choose PDF or PNG screenshot and click Save.
Real browser
Pages render exactly as visitors see them, JavaScript included.
Five viewports
Desktop, laptop, tablet, phone, or any custom size from 320 to 2560 px.
PDF or PNG
A selectable document for archives, or a full-page image for reference.
What to expect
The PDF path prints the page like a browser's Print dialog would: backgrounds included, margins trimmed, text selectable and links clickable. The PNG path screenshots the rendered viewport, and by default follows the whole page length, however tall it is.
Pages behind logins, paywalls or aggressive bot protection may fail to render, and nothing here bypasses those walls. Very long pages produce very tall screenshots and equally long PDFs. There is a fair-use limit of 30 renders per hour per visitor.
Tips for better results
- Compare responsive layouts by rendering the same URL at two sizes.
- Archive a receipt or confirmation page as PDF before it expires.
- Custom viewport matching your own screen gives the most faithful capture.
Questions and answers
Does it work with pages that need JavaScript?
Yes. The page loads in a real browser, so charts and dynamic content render before capture.
Can it access pages behind a login?
No. There are no cookies or sessions, only what the public URL serves.
Why did my page fail?
Bot protection, very slow pages, or an unreachable address. Retry, or try the other output format.