Documentation archives
Keep the whole page as it read on a date, rather than the first eight hundred pixels of it.
Capture the entire page, not the first screen
One flag turns a viewport capture into the whole document, top to bottom, up to 20,000 pixels tall. Ask it to load lazy content first, take overlays out, and sticky headers behave the way a browser makes them behave.
Create a free accountRead the API docs
- Up to 20,000 pixels tall
- Counted as one screenshot
- No charge for failed renders
- UK-operated infrastructure
One flag
A long page is where screenshots usually go wrong
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.
Ironfang Render 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 /render/v1/screenshot
Authorization: Bearer if_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
What makes a long capture usable
The settling, hiding and sizing that decide whether a tall image is evidence or a screenshot of a spinner.
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.
Content that loads late
Have the page scrolled to the bottom before the capture so lazy images and sections load, or wait for network idle or a selector, so the bottom of a long page is not blank.
Nothing in the way
Ad blocking, cookie-banner hiding and your own selector list, so a long capture is not a long capture of an overlay.
The size you asked for
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.
Sensible file sizes
WebP or JPEG with quality control keeps a tall capture small enough to store and send, with PNG when it has to be lossless.
One screenshot, however long
A full-page capture counts as one screenshot, the same as any other. Cache hits count nothing and a failed render is not charged.
Use cases
When the whole page is the point
Anywhere a crop would lose the part that mattered.
Landing page records
Capture a campaign page end to end for the file, the client or the regulator.
Design and QA review
Put the entire page in front of a reviewer without asking them to scroll a staging environment.
Competitor and market snapshots
Record how a page looked in full, on a schedule, without a person taking the screenshots.
Compliance evidence
A complete page image with the viewport and date you chose, kept alongside the rest of the record.
Long-form reports
Turn a generated report page into one image for a deck, a digest or an attachment.
Need viewport, element or region captures too?
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. To see a full-page capture before writing any code, the free full page screenshot tool runs the same engine from a URL.
Pricing
One screenshot, however tall the page
A full-page capture counts as one screenshot, however tall the page; failed renders and cache hits count nothing. Every account has a free allowance each month, with no card required. Past it, Pay as you go charges the rates below, within the monthly usage limit you set. Prices exclude VAT.
Screenshots
Each screenshot returned or stored.
500 screenshots free each month
| Paid units after the free allowance | Rate per 1,000 |
|---|---|
| First 10,000 | £1.50 |
| Next 90,000 | £0.90 |
| Next 900,000 | £0.65 |
| Above 1,000,000 | £0.45 |
Questions
Before you integrate
The details that decide whether this fits, without reading the whole reference first.
- How tall can a full-page screenshot be?
- 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.
- Will lazy-loaded images be missing from the bottom?
- Not if you ask for it. With full_page_readiness set to scroll, the page is walked down before the capture, so images and sections that load as they come into view are in the picture, and the response warns if anything was still loading when the walk ended. Waiting for a selector that only appears once the content below the fold has loaded works too.
- What happens to sticky headers on a long page?
- 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.
- Can I capture the visible viewport instead?
- 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.
- Which format should I use for a very long page?
- 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.
- Does a full-page capture cost more?
- No. It counts as one screenshot, the same as any other, and a failed render is not charged. Cache hits count nothing.
Less to operate. More to ship.
Capture your first full page
Create an account, take a key and send one request with the full-page flag set.
500 free screenshots each month, no card required, and no charge for failed renders.