Changelog · September 22, 2026

Screenshots capture the whole page

The full-page screenshot the tool always promised, with the images below the fold filled in.

By Roger Campos · Last updated: September 2026

TL;DR

Screenshots now capture the whole rendered page, not only the first screen. The page is scrolled top to bottom before the capture so lazy-loaded images appear, and the capture is bounded at 16,384 px tall so an infinite-scroll feed still answers.

Start free See the API

Free plan, no credit card. 1,000 credits a month.

Lazy-loaded images only load when they scroll into view, so a naive full-page capture of a modern marketing page is a column of empty boxes. The page is walked top to bottom and returned to the top before the capture. On one image-heavy page the same 10,274 px capture went from 1,854 KB to 2,838 KB — the difference was an image grid that had been blank. It costs about a second.

The walk and the image are both bounded, so an infinite-scroll feed answers rather than scrolling for the whole visit. The width stays fixed at 1,350 px unless you choose a viewport: a page that scrolls sideways is nearly always a layout bug, and a fixed width is what lets two captures of a page be compared.

Request

Example

A full-page PNG

curl -X POST https://urlpipe.dev/screenshot \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com", "sync": true}'

Want the first screen only? Set screenshot_options.full_page to false.

Screenshot docs Try it

Endpoints