Full-page screenshots

full_page=true captures the whole scrollable document instead of the viewport.

Lazy content

Most long pages load images as you scroll. full_page_scroll=true walks the page first so that content exists before the capture:

{
  "url": "https://example.com/blog",
  "full_page": true,
  "full_page_scroll": true,
  "full_page_scroll_delay": 400,
  "format": "png"
}

Algorithms

full_page_algorithm chooses the strategy:

• default — one capture of the whole document. Fastest, and correct for most pages. Default.
• by_sections — capture in bands and stitch them. Needed for very tall documents.

Above roughly 16,000 pixels of height, Chromium starts returning truncated or blank images, so default falls back to section capture on its own before that point. You only need by_sections explicitly when you want banded capture on a shorter page.

full_page_slice_height (default 4000) and full_page_slice_overlap_height (default 0) control the bands. The overlap must be smaller than the slice height.

Limits

full_page_max_height stops the capture at a height you choose — the right tool for a page with infinite scroll. Without it, a runaway page is bounded by the engine's own pixel ceiling and fails with resulting_image_too_large.