Set full_page=true in your ScreenshotAPI.net request to capture the document beyond the visible viewport. If the result is still cropped, check for a clip region or element-specific capture, and for spreadsheets use a suitable browser height as well as full-page mode.
Set full-page mode in the request
ScreenshotAPI.net documents full_page=true as the setting for capturing the full document instead of only the current viewport. Its example uses the /v3/screenshot endpoint and includes width and height too: those values describe the browser viewport, while full_page=true asks for a full-document image. They are separate controls, not alternatives. See the full-page screenshot tool and API features pages.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Responsive Web Design Toolkit | $51.16 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
For example, add the setting to the query parameters in your existing request:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
GET https://shot.screenshotapi.net/screenshot?token=YOUR_TOKEN&url=https%3A%2F%2Fexample.com&full_page=trueUse your existing authentication and URL-encoding conventions. The exact request parameters depend on your endpoint and API version; consult the documentation for the endpoint you call.
#1 Best Overall
Check for settings that intentionally crop the capture
Full-page mode cannot override a request that also limits the output to a region or element. Inspect the request for a clip rectangle or a CSS-selector element capture. A clip rectangle specifies an area using x and y coordinates plus width and height, while selector capture targets one element rather than the whole document. Remove those constraints when the goal is a full-page screenshot. ScreenshotAPI.net describes these controls on its element screenshot page.
Handle spreadsheets and pages with delayed content
Spreadsheets
For a spreadsheet that appears incomplete, ScreenshotAPI.net’s help page recommends using an appropriate browser height together with full-page mode. There is no single height value established as correct for every spreadsheet; choose one suitable for the page and your capture requirements. See the provider’s help page.
Lazy-loaded content
ScreenshotAPI.net says its full-page renderer scrolls the page to trigger lazy-loaded content. That is the provider’s stated behavior, not an independently verified guarantee for every site. Pages that load content only after particular interactions or conditions may need additional handling in your capture workflow. The provider describes full-page output as including content that appears after scrolling on its full-page screenshot tool page.
Free tools Windows power users keep installed
One-click scans. No signup required.
Cookie banners and ads can obscure the image
The provider’s help page documents no_cookie_banners=true and block_ads=true. Its full-page tool page instead uses block_cookie_banners=true for cookie banners. Because the pages give different cookie-banner parameter names, verify the correct spelling for the exact endpoint and version you use before adding it. See the help page and full-page tool page.
Troubleshoot a still-cropped screenshot
- Only the first viewport is visible: confirm the request includes
full_page=true; fixed width and height alone can capture only the viewport. - Only a section or element appears: remove or adjust the
cliprectangle or CSS-selector capture. - A spreadsheet is cut off: use full-page mode and adjust browser height to suit that spreadsheet; the provider does not specify a universal value.
- Content that loads on scroll is missing: the provider says its renderer scrolls to trigger lazy loading, but this is not a guarantee for every page. Check whether the site requires a particular interaction or loading condition.
- A banner or ad covers content: check the current endpoint documentation for the applicable banner-removal parameter; the provider’s pages use conflicting cookie-banner spellings. Its help page also documents
block_ads=true.
Capture a one-off screenshot in a browser
If you do not need an API, ScreenshotAPI.net’s guide describes full-size capture through Chrome or Edge DevTools and a full-page save flow in Firefox. Browser labels and steps can vary by version; refer to the provider’s guide for its instructions.
Or skip the browser setup
For repeatable captures, ScreenshotNeo offers a one-request screenshot API. A cURL example using the documented API base is:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for request options. It removes cookie banners, popups and chat widgets before capture; bot checks, blank pages and failed loads are never billed; and its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo free.
Frequently Asked Questions
Does full-page mode capture content that loads while scrolling?
ScreenshotAPI.net says its renderer scrolls the document to trigger lazy-loaded content, but that behavior is not an independently verified guarantee for every site.
Is there a recommended browser height for a full spreadsheet screenshot?
The provider advises an appropriate browser height alongside full-page mode but does not establish one height that works for every spreadsheet.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
