Capture a complete webpage as an image, or convert a live URL into a print-ready PDF straight from your browser. Both tools run on the ScreenshotAPI rendering engine, so what you see in the preview is exactly what the API returns.
Try it in the browser first, then copy the matching code snippet when you are ready to automate it.
Capture an entire webpage (top to bottom)
Paste a URL and get the whole scrollable page as a single PNG, JPG, or WebP. Lazy-loaded images are triggered, sticky headers are handled, and nothing is cut off at the fold.
Turn any webpage into a print-ready PDF
Convert a live URL into a clean, multi-page PDF with real, selectable text. Choose A4, Letter, Legal, A3, or Tabloid, switch to landscape, and download in seconds.
These are not thin wrappers around a browser print dialog. Both tools use the same renderer, the same parameters, and the same output pipeline as the paid ScreenshotAPI endpoints.
Every capture runs in a real headless Chromium instance with full JavaScript execution, web fonts, and CSS. So what you download matches what a visitor sees.
Both tools scroll the full document height before capturing, triggering lazy-loaded images and off-screen sections so the bottom of the page is never clipped.
full_page=trueConsent dialogs and ad slots are stripped before the render, so your screenshot or PDF is clean without any manual editing.
block_ads=trueThe same URL and the same settings produce the same file every time unlike browser print dialogs, which vary by OS, browser, and print preset.
Each tool shows the exact cURL, Node.js, Python, and PHP request that reproduces your settings, so moving from demo to production is a copy and a paste.
When one page is not enough, the same parameters work with bulk captures, scheduled screenshots, and storage integrations on the paid API.
There are four common ways to screenshot an entire webpage, a DevTools command, a browser extension, your operating system's built-in shortcut, and the print dialog. All four work on a simple page and all four fall apart on a modern one. Here is what each method actually captures when you ask it for a long, scrolling screenshot of a real site.
Extensions that stitch a long screenshot together from separate scroll steps capture the fixed navbar in every one of them, so the same header shows up five times in a single capture.
Anything below the fold only loads once it is scrolled into view. A one-shot capture takes the picture before that happens and you get grey placeholders where the images should be.
Saving a webpage as a PDF from the print dialog applies the site's print CSS, which often drops backgrounds, collapses columns, and moves content you needed to keep.
The full page screenshot tool on this page scrolls the whole document first, so lazy images load and the header stays where it belongs. If you need the capture as motion instead of a still image, use a scrolling screenshot, and to turn a list of links into images programmatically, see URL to screenshot.
Most people convert a webpage to PDF the same way: open the print dialog, choose Save as PDF, and hope. It is fine for a receipt. For anything you have to send to a client, attach to a ticket, or keep as a record, it usually returns a document with the layout collapsed, a cookie banner across the first page, and half the images missing.
The URL to PDF generator renders the live page in headless Chromium first, then prints it with the options you picked.
The free tool handles a single link. Once you need a whole list of them, or the same page captured on a schedule, the same parameters move to the API without any rework.
Feed a list of links and download every webpage as a PDF in a single bulk run instead of pasting them one at a time.
Bulk captureSchedule a recurring conversion so you keep a dated PDF archive of a pricing page, a listing, or a competitor's homepage.
Scheduled capturesDeliver finished PDFs to your S3, GCS, or Wasabi bucket so the files land where your app already looks for them.
Read the docsEverything you might want to know about the free ScreenshotAPI tools, how they differ from the API, and what happens to your data.
Don't see your question here?
Browse all help articles