A browser window shows a slice of a document. A full-page screenshot removes that limit: the page is scrolled from top to bottom, each section is given the chance to render, and the whole thing is stitched into a single tall image. Nothing below the fold is lost.

That completeness is what makes full-page captures the default for records. If you are archiving a terms page, evidencing a promotion, or keeping a dated copy of a product listing, a viewport capture that stops after the first screen is not a record of the page — it is a record of its header.

Why full-page capture is harder than it looks

Modern pages fight back. Content is loaded as you scroll, headers stick to the top of the viewport, animations trigger on entry, and images decode at their own pace. Naive tools produce the tell-tale artefacts: repeated navigation bars, grey boxes where images never loaded, sections cut in half.

• Lazy loading. Images and blocks that only fetch when scrolled into view need the scroll pass to pause long enough for them to arrive.
• Sticky and fixed elements. Anything pinned to the viewport can be drawn at every scroll position unless it is handled deliberately.
• Entry animations. Content that fades in on scroll can be captured mid-transition, at partial opacity.
• Height limits. Extremely long pages hit real limits in image formats, which is one reason PDF output exists on paid plans.

Our scroll and timeout controls and stability settings exist for exactly these cases, and the free tool applies sensible defaults for them.

When to prefer a viewport capture instead

Full-page is not always the right answer. If the question is what a visitor sees before scrolling — whether your offer is above the fold on a phone, how much space a consent banner takes — then a viewport capture at a fixed device size is the honest measurement. The standard screenshot tool is built for that, and the documentation compares the two.

Turning a capture into a record

One full-page image proves what a page said at one moment. A series of them, taken on the same schedule at the same width, becomes something more useful: a timeline you can scan to see exactly when something changed.

That is what an account adds. Set a frequency and timezone, pick full-page capture on the profile, and every run is filed in your history and pushed to your own cloud storage. Teams use it for web archiving, compliance evidence and competitor tracking.