What is a full-page screenshot? Definition and how it works
A full-page screenshot is a single image of every pixel a page would render if scrolled top to bottom, produced by the browser in one render pass.
A full-page screenshot is a single image of every pixel a page would render if scrolled from top to bottom, produced by the browser in one render pass.
The distinction from a scrolling screenshot is in the mechanism. A full-page screenshot is rendered by the browser into an off-screen surface and exported as one image — no scroll automation, no stitching. Chrome DevTools, headless Chrome, and Puppeteer all expose this as a one-line operation; many capture tools just delegate to it.
When to use a full-page screenshot
When the layout of the entire page matters: reviewing a landing page top to bottom, archiving a state for a regression report, exporting a long article for offline reference. It is also the right format when the page has parallax or scroll-triggered animation that a scrolling screenshot would render incorrectly.
It is the wrong format when the file size matters more than completeness. A long page can produce a multi-megabyte image; a viewport crop is almost always smaller and faster to share.
Frequently asked questions
How is a full-page screenshot taken?
The browser renders the entire document into an off-screen surface and exports it as one image. In Chrome DevTools, the command is "Capture full size screenshot." Headless browsers and Puppeteer expose the same operation programmatically.
Will it capture content below the fold that lazy-loads on scroll?
Only if that content has been loaded into the DOM when the screenshot is taken. Pages that defer rendering until scroll position changes may produce blank regions in the full-page output.
Capture your first review.
About a minute from open tab to a shareable URL your agent can ingest.
Start capturing