Capture a full webpage safely

Enable full-page capture

Set full_page to true. The worker measures the document and captures beyond the initial viewport, up to the configured maximum page height.

curl https://api-screenshot.com/v1/screenshots \
  -H "Authorization: Bearer $SCREENSHOT_API_KEY" \
  -H "Idempotency-Key: docs-full-page-001" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/long-page",
    "preset": "desktop",
    "full_page": true,
    "format": "webp",
    "quality": 82,
    "block_cookie_banners": true
  }'

Expect bounded output

The initial renderer contract caps full-page height at 30,000 pixels. A page may also stop earlier because of render timeout, memory pressure, redirect limits, or oversized responses.

• Prefer WebP or JPEG for large photographic pages.
• Use PNG when lossless text and interface edges matter.
• Do not assume infinite-scroll pages have a stable bottom.
• Read artifact width and height from the completed resource.

Handle client-rendered pages deliberately

Start with wait_until set to load. For sites that paint important content later, use networkidle or a small delay_ms after measuring the target behavior. Avoid arbitrary long waits.