Full-page website screenshots
Most screenshot tools capture the visible screen and stop there. We capture the whole page — the header, the footer, and every section a visitor would only reach after scrolling — on each scheduled run, then save it as a timestamped image, a PDF, and the raw HTML. Full-page is the default capture mode here, so the content that tends to matter most (prices below the hero, a reworded clause buried in a policy, the section a competitor quietly added last week) lands in your archive whether or not anyone thought to scroll down to it.
The half you don't see
Here's the trap with viewport-only capture: the screenshot looks finished. You get a clean image of the header, the hero, the start of the next block, and at a glance nothing seems missing. The gap shows up later — when you go looking for the moment a price moved, or a plan disappeared from a comparison table, and the archive has none of it because the camera was always aimed at the top of the page.
Full-page capture closes that gap by default. You don't have to guess in advance which part of a page will matter six months from now, because the whole thing is already saved. That's the difference between an archive you can rely on and one that happens to have caught the right pixels.
What a full-page capture includes
A full-page screenshot isn't a taller crop of the same picture. Our headless browser (a real browser running on our servers with no visible window) loads the page, waits for it to finish rendering, then scrolls from the first pixel to the last and stitches every section into one continuous image. There's no fixed ceiling on height: a short contact page comes back a few hundred pixels tall, while a long sales page can run well past ten thousand.
Each run stores more than the image, too. Alongside the full-page screenshot you get a viewport version (the first screen on its own), a PDF copy, the page's HTML source, and metadata like the page title, HTTP status, response time, and weight. One capture gives you both the visual record and the technical fingerprint of the page at that exact moment.
Turning it on per URL
Capture mode is set for each URL separately, so you can archive one page full-page and another viewport-only without the two interfering. When you add a URL, the Viewport & Capture section already has Full page screenshot ticked — it's the default, so most of the time there's nothing to change. The one control worth a glance is Viewport Size: in full-page mode the width drives how the page lays out, while the height you set is only the starting frame, not a ceiling. The capture grows past it on its own to match the content.
Full-page is the right default for almost any archiving job, but it isn't automatically the best fit for every page. When you're weighing the two modes for a specific URL — a heavy single-page app, say, or a header you're tracking on its own — our breakdown of full-page versus viewport capture walks through where each one earns its place.
Where the whole page earns its keep
The reason completeness matters comes down to where real changes happen, and most of a page's substance sits below the fold. Pricing is the clearest case: the tiers and feature rows almost always live under the hero, so a bumped price or a quietly dropped plan only surfaces if you captured the full thing (we go through this in tracking SaaS pricing changes).
Legal pages raise the stakes further. A single edited line inside a long terms of service or privacy policy can carry compliance weight, and it's rarely anywhere near the top of the document. The same logic holds for anything you might need to stand behind later — the kind of record we cover in screenshots as legal evidence — where a partial capture simply won't hold up. When the goal is the complete state of a page, header-to-footer is the only version that does the job.
Full-page across the rest of your archive
Because the entire page is captured, everything downstream operates on the entire page too. Visual diff compares the whole capture, so a change three screens down gets flagged the same way as one in the header. The PDF export renders that full length into a single document with a SHA-256 certificate (a checksum that proves the file hasn't been altered since capture), which is what turns a long screenshot into something usable as evidence rather than just a picture. And since captures run on a schedule you set, the full page is preserved at every interval without anyone opening a browser.
On Pro plans and above, all of it is reachable through the API, so you can fire full-page captures from your own scripts or a CI pipeline and pull the results back in code.
Common questions about full-page capture
Is there a height limit on full-page screenshots?
Very tall pages capture fine in the overwhelming majority of cases. The practical limit shows up with infinite-scroll feeds and some heavy single-page apps that keep loading new content as the browser scrolls — those can grow without end, or time out before they finish. For pages like that, a fixed viewport or a clipped element is the steadier choice.
Does full-page capture lazy-loaded content?
Yes. Because the browser physically scrolls through the page before capturing, images and sections that only load when they enter view get triggered and rendered into the final image. For content that fades in or arrives a moment after the page settles, the Delay before capture setting holds the shot for a few extra seconds so everything has time to appear. The one case this won't solve is content that waits for a click or some other interaction rather than for scrolling or time.
Can I capture full-page at mobile widths?
Set the rendering width to a mobile size, like 375 pixels, and full-page behaves the same way — it captures the full mobile layout top to bottom. That's useful when a site serves a different structure to phones than to desktops, since the mobile version is the one your visitors actually see.
How much larger are full-page files?
A viewport screenshot usually weighs tens of kilobytes; a full-page capture of a long page runs into the hundreds. It's more storage, but your plan's retention window keeps the history without any manual cleanup, and the completeness is worth the extra weight for most archiving work.
Is full-page available on the free plan?
Yes. Full-page is the default mode on every plan, including the free tier (3 websites, daily captures). There's no upsell to capture the whole page — it's how the product works out of the box.
Can I get the full page as a PDF?
Every full-page capture can be exported to a PDF that preserves the whole length in one document, with the timestamp and SHA-256 certificate attached, so it reads as a single dated record instead of a stack of cropped images.
Every capture runs full-page by default — image, PDF, and HTML, on whatever schedule you choose. The free plan covers 3 websites with daily captures, and you don't need a credit card to start.
Create free account