The short answer
Open a regular webpage in Chrome, open PageCapture, and choose full page capture. Decide whether to capture the content already loaded or continue loading toward the end. When capture finishes, save the result as PNG or PDF.
When a full page screenshot is the right choice
A visible-area screenshot records only the current viewport. Full page capture is useful when one article, manual, order summary, or report continues below the fold and you need its top-to-bottom reading order in one capture job.
If only a chat, table, or panel inside the page scrolls, use scroll area capture instead. It avoids including the surrounding webpage when the inner container is the real target.
Capture the full webpage with PageCapture
- Open the regular HTTP or HTTPS webpage you want and confirm that the required content is visible.
- Open PageCapture and choose the full page capture mode.
- If the page appends content while scrolling, choose how far PageCapture should load.
- Start capture and avoid closing the tab, navigating away, or changing the page until it finishes.
- In the result view, save as PNG or PDF and check that the ending content is present.
PageCapture restores the original scroll position afterward. Dynamic layout changes during capture can still affect the result, so limit interaction with the page until the capture job is complete.
Loaded content only versus Keep loading
Should you save the result as PNG or PDF?
PNG works well when you plan to crop, annotate, edit, or place the capture into another document as an image. PDF is usually easier to read, print, archive, or share as a paged document. See how to save a webpage as PNG or PDF for a focused comparison.
Why a long result may be split
Browsers limit the dimensions and memory available to one image. If the full result cannot safely fit in a single PNG, PageCapture preserves the content as numbered PNG files instead of silently cutting it off. PDF output continues the same capture across multiple PDF pages.
What to watch for on long pages
Fixed headers and overlays
A header, footer, banner, or popup fixed to the viewport may repeat while the page moves. Close optional overlays before capture when possible.
Lazy-loaded content
Images or text that appear only after scrolling may not be part of Loaded content only. Confirm the content is present first, or use Keep loading when newly appended material is required.
Infinite scrolling
A feed without a defined end cannot be captured forever. PageCapture stops at safety limits and may return a usable partial result. If you need a specific range, loading up to that point before capture gives the task a clearer boundary.