FAQ · Capture options
How do I capture a full-page screenshot?
Pass full_page=true to the Screenshot API endpoint. The service scrolls the entire document, stitches the frames, and returns a single tall image.
The one-line answer
GET https://api.snapshotflow.com/screenshot?url=https://example.com&full_page=trueThat single parameter tells the API to scroll the complete page height instead of capturing only the initial viewport.
Useful parameters to combine with full_page
| Parameter | What it does | Example value |
|---|---|---|
full_page | Capture entire document height | true |
width | Viewport width in pixels | 1440 |
format | Output image format | png, jpeg, webp |
wait_for | Wait condition before capture | networkidle |
delay | Fixed delay (ms) before capture | 2000 |
Common full-page screenshot pitfalls
- Sticky headers and navbars. Elements with
position: fixedrepeat across the stitched image. Use a CSS injection parameter to hide them before capture if your vendor supports it. - Lazy-loaded images. Images that load on scroll may appear blank in a full-page capture if the API does not simulate scroll events. SnapshotFlow scrolls the page incrementally before stitching to trigger lazy loaders.
- Infinite scroll pages. Pages that keep loading content on scroll need a
max_heightcap to avoid enormous files. Set a sensible pixel limit. - Animations. Pass a small
delayor set a CSS animation pause to avoid mid-transition artifacts in the screenshot.
Capture full-page screenshots now
SnapshotFlow's full-page mode handles sticky elements, lazy images, and animation pausing automatically.