Full Page Screenshot Tool

Capture the entire scrolling length of any web page in a single image.

We capture the whole page, top to bottom — not just the visible window.

Your full-length capture will appear here

Enter a URL to capture the entire scrolling page in one image.

Need this at scale?

Get it as a single API call. 200 free screenshots/month.

How it works

  1. 1

    Paste the page URL

    Drop in any public http(s) address — a landing page, blog post, pricing page, or docs article. No account or extension needed.

  2. 2

    Choose how it captures

    Pick PNG, JPEG, or WebP and leave cookie-banner and pop-up removal on so overlays do not block the content before the capture runs.

  3. 3

    Scroll, stitch, download

    We load the page in a real browser, scroll it top to bottom to trigger lazy content, then stitch every section into one tall image you can download.

When to use a full-page screenshot

When you need the whole story — not just the top fold — a full-page screenshot captures the entire scrolling length of a page in one image. It is the fastest way to archive a landing page exactly as it shipped, send a stakeholder the complete design for sign-off, or keep a visual record of a long article, changelog, or terms page before it changes.

Designers and QA teams rely on full-length captures to review responsive layouts end to end and to compare a page against a previous version. Marketers use them to build portfolio shots and competitor swipe files, while support and legal teams capture full receipts, invoices, and policy pages as a single, shareable record.

Because the page renders in a real headless browser, web fonts, CSS, and lazy-loaded media all appear just as a visitor would see them. When you need to do this across many URLs on a schedule, the same capture is available as one ScreenshotAPI call with fullPage=true.

Frequently asked questions

What is the difference between a full-page and a viewport screenshot?

A viewport screenshot only captures what fits in the browser window — usually the top fold. A full-page screenshot keeps scrolling and stitches the whole document into one continuous image, so footers, long articles, and everything below the fold are included in a single file.

How tall a page can it capture?

This free tool captures very long pages, but extremely tall pages (think infinite-scroll feeds) are capped to keep the image a reasonable size and the request fast. For unbounded or guaranteed full-height captures on large pages, use the ScreenshotAPI with a paid plan.

Does it capture lazy-loaded images and content?

Yes. We scroll the page from top to bottom before capturing, which triggers most lazy-loading and scroll-reveal animations so images, charts, and deferred sections render into the final screenshot. Content that only loads on click or hover will not appear.

Why are cookie banners and pop-ups removed by default?

Consent banners, newsletter modals, and chat widgets are fixed to the screen and would otherwise repeat across the stitched image or hide the content underneath. Removing them gives you a clean, readable capture. You can toggle either option off if you want them included.

Which image format should I pick?

Use PNG for the sharpest text and UI screenshots. JPEG produces a much smaller file for very long pages where a slightly softer image is acceptable. WebP gives you near-PNG quality at JPEG-like file sizes and is ideal for embedding on the web.

Can I do this automatically for many pages?

Yes. This tool is a free front end for the ScreenshotAPI. Set fullPage=true on the API and you get the same top-to-bottom capture from a single request — perfect for generating thumbnails, archiving pages, or monitoring layouts across hundreds of URLs.

More free tools

Automate this with the ScreenshotAPI

One API call returns the screenshot. 200 free screenshots every month — no credit card required.