ScreenshotAPI.net Screenshots Are Cropped: How to Capture the Full Page

Set full_page=true in your ScreenshotAPI.net request to capture the full document instead of just the visible viewport. If the result is still cropped, check for a clip rectangle or element-specific capture setting that intentionally limits the image.

Set the full-page option

ScreenshotAPI.net’s documented /v3/screenshot example uses full_page=true for a full-document capture. The provider’s features page distinguishes full-page mode from width and height: those dimensions set the browser viewport, while full_page=true requests the document beyond that viewport. See the provider’s features page and full-page screenshot tool for its examples and description.

#	Preview	Product	Price
1		Responsive Web Design Toolkit	$57.55	Buy on Amazon

A request shape is:

https://shot.screenshotapi.net/screenshot?token=YOUR_TOKEN&url=https%3A%2F%2Fexample.com&full_page=true&width=1440&height=900

Use your existing endpoint and authentication format if they differ; the key change is enabling full_page=true. The example dimensions are illustrative, not universal recommendations. Choose a viewport appropriate for the page you are capturing.

Check settings that can crop the result

Remove any clip rectangle

A clip rectangle limits the screenshot to a specified area, typically by x and y coordinates plus width and height. If your request includes one, remove it when you want the full document. ScreenshotAPI.net describes this control on its element screenshot page.

#1 Best Overall

Sale

Responsive Web Design Toolkit

$57.55

Buy on Amazon

Disable element-specific capture

If the request targets a CSS selector or otherwise captures a particular element, it is not asking for an unrestricted full-page image. Remove that element-specific setting and request full-page mode instead.

For spreadsheets and unusually long pages

ScreenshotAPI.net’s help page recommends setting an appropriate browser height as well as enabling full-page capture for spreadsheets. There is no single height that fits every spreadsheet or webpage, so adjust it for the layout and content you need. The provider’s help guidance is at ScreenshotAPI.net Help.

The provider says its full-page renderer scrolls through the document to trigger lazy-loaded content. That is the vendor’s stated behavior, not a guarantee that every site will load every item before capture. Pages may defer content in site-specific ways.

Handle banners and ads carefully

ScreenshotAPI.net’s help page documents no_cookie_banners=true and block_ads=true. Its full-page tool page uses a different cookie-banner parameter name, block_cookie_banners=true. Because the provider’s pages differ, verify the current parameter for your exact endpoint and version before adding a cookie-banner option. Do not assume both spellings work interchangeably.

Quick troubleshooting checklist

• Only the visible screen appears: confirm the request includes full_page=true; width and height alone do not request a full-document capture.
• The image is limited to one region: remove or revise any clip rectangle.
• Only one element appears: remove CSS-selector or element-specific capture settings if you want the full page.
• A spreadsheet is incomplete: enable full-page mode and adjust browser height to suit that spreadsheet; the provider does not give a universal height value.
• Lazy-loaded sections are missing: the vendor says its renderer scrolls to trigger lazy loading, but site behavior can vary. Check whether the content appears during a normal page scroll and whether the page requires additional interaction.
• A cookie banner remains visible: verify the cookie-banner parameter spelling against documentation for your endpoint/version; the provider’s help and full-page pages use different names.

Capture a one-off screenshot in a browser

For occasional use, ScreenshotAPI.net’s guide describes full-size capture through Chrome or Edge DevTools and a full-page save flow in Firefox. Browser controls can change between versions; consult the guide for its steps at the full-page screenshot tool page.

Or skip the browser setup

If you need repeatable captures from code, ScreenshotNeo offers a one-request screenshot API. Its clean-shot options accept cookie and consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses include X-Page-Verdict and X-Billed headers. It also provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for AI agents and MCP clients.

Example cURL call (see the ScreenshotNeo API documentation for options):

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

The response can be PNG, JPEG, WebP, or PDF. ScreenshotNeo’s free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Learn about ScreenshotNeo or sign up free for 1,000 screenshots a month, with no card.

Frequently Asked Questions

Does full-page mode capture content that appears only after scrolling?

ScreenshotAPI.net says its full-page renderer scrolls the document to trigger lazy-loaded content, but behavior may vary by site.

What does a full-page screenshot include?

It is intended to capture the document beyond the currently visible viewport, rather than only the browser’s displayed area.

Quick Recap

SaleBestseller No. 1

Responsive Web Design Toolkit

$57.55

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.