The whole document
One flag captures top to bottom rather than the viewport, up to 20,000 pixels tall, with a per-request ceiling when you want one.
Full page screenshot API
One flag turns a viewport capture into the whole document, top to bottom, up to 20,000 pixels tall. Lazy content settles first, overlays come out, and sticky headers behave the way a browser makes them behave.
Create a free accountRead the API docs
ironfang.uk

One flag
Scripted full-page capture is where the edge cases live. Images below the fold have not loaded when the shot fires, a sticky header repeats down the image, a cookie banner covers the first screen, and a page taller than the tool expects comes back truncated.
Renderwolf settles the page first, respects the browser rules for fixed and sticky elements, hides the overlays you name, and captures to 20,000 pixels. The same endpoint gives you a viewport shot, an element or a clip when you want less.
POST /renderwolf/v1/screenshot
Authorization: Bearer rw_live_...
{
"url": "https://example.com/docs",
"full_page": true,
"full_page_max_height": 20000,
"wait_until": "networkidle",
"block_cookie_banners": true,
"hide_selectors": [".site-header"],
"format": "webp",
"quality": 80
}Capabilities
The settling, hiding and sizing that decide whether a tall image is evidence or a screenshot of a spinner.
One flag captures top to bottom rather than the viewport, up to 20,000 pixels tall, with a per-request ceiling when you want one.
Wait for network idle or for a selector that only exists once the page has filled in, so the bottom of a long page is not blank.
Ad blocking, cookie-banner hiding and your own selector list, so a long capture is not a long capture of an overlay.
Set the viewport width so the page lays out the way you want before it is captured, with a device scale factor up to 3 for retina output.
WebP or JPEG with quality control keeps a tall capture small enough to store and send, with PNG when it has to be lossless.
A full-page capture costs the same as any screenshot. Cache hits are free and a failed render is not billed.
Use cases
Anywhere a crop would lose the part that mattered.
Keep the whole page as it read on a date, rather than the first eight hundred pixels of it.
Capture a campaign page end to end for the file, the client or the regulator.
Put the entire page in front of a reviewer without asking them to scroll a staging environment.
Record how a page looked in full, on a schedule, without a person taking the screenshots.
A complete page image with the viewport and date you chose, kept alongside the rest of the record.
Turn a generated report page into one image for a deck, a digest or an attachment.
Full-page capture is one flag on the screenshot endpoint. The same request handles viewport shots, a single element by selector, an exact clip rectangle, and pages behind a login.
The screenshot APIPricing
A full-page capture costs the same as any screenshot. Start with 250 free credits each month and no card required, with paid plans from £9 per month for 5,000 credits. Cache hits cost nothing, failed work is refunded, and reaching a cap pauses rendering rather than billing overage.
Questions
The details that decide whether this fits, without reading the whole reference first.
Up to 20,000 pixels. That covers long documentation pages, marketing pages and most reports in a single image, and you can lower the limit per request when you want a predictable ceiling.
Not if you let the page settle. Wait for network idle, or wait for a selector that only appears once the content below the fold has loaded, and the capture includes it.
They behave as they do in a browser, so a sticky navigation appears once rather than repeating down the image. Hide it with a selector if you would rather it did not appear at all.
Yes, that is the default. Full-page capture is a flag, so the same endpoint gives you a viewport shot, a full-page shot, a single element or an exact clip rectangle.
WebP or JPEG keep the file small on a tall capture, with quality from 1 to 100. PNG is there when you need it lossless.
No. One credit, the same as any screenshot, and failed work is refunded. Cache hits cost nothing.
Create an account, take a key and send one request with the full-page flag set.
250 free credits each month, with no card required, hard usage caps and refunds on failed work.