ScreenshotAPI.net Screenshots Are Cropped: How to Capture the Full Page
Set full_page=true to capture the whole document with ScreenshotAPI.net. Check viewport, clipping, and lazy-loaded content if the result is still incomplete.
If a ScreenshotAPI.net screenshot shows only the visible portion of a page, set full_page=true in the request. The vendor documents this option for capturing the full document. Keep in mind that viewport width and height are separate settings; also check that the request does not include a clip rectangle or element-specific capture that limits the output.
1. Set full_page=true
Add full_page=true to your ScreenshotAPI.net screenshot request. The vendor’s example uses the /v3/screenshot endpoint and includes width and height as well. Those dimensions set the browser viewport; full_page=true asks for the full document rather than only that viewport.
full_page=trueFor example, if you already have a working request, add this parameter alongside its existing URL and other options. Preserve the endpoint, authentication, and output settings from your current integration. The research available for this guide does not include a complete endpoint URL or authentication syntax, so check ScreenshotAPI.net’s current documentation for the exact request format for your account and API version.
2. Check options that can still constrain the capture
Viewport width and height
Viewport size and full-page mode serve different purposes. Width affects the page layout and height sets the browser viewport. Full-page mode requests document-length output. If the page wraps differently than expected, check the width first. For a spreadsheet or similarly unusual page, ScreenshotAPI.net’s help page advises using an appropriate browser height as well as full-page mode; there is no universal height that fits every page.
Clip rectangles and element captures
A clip rectangle selects a region using coordinates and dimensions. An element-specific capture selects an area, such as a CSS selector. Either can produce an intentionally partial image. Remove or adjust those settings when you want the full document instead.
Lazy-loaded content
ScreenshotAPI.net says its full-page renderer scrolls the document to trigger lazy-loaded content. This is the provider’s stated behavior, not an independently verified guarantee for every site. Pages that load content only after a particular interaction, wait condition, or application state may need additional configuration.
Cookie banners and ads
Overlays can obscure page content even when the capture includes the full document. ScreenshotAPI.net’s help page documents no_cookie_banners=true and block_ads=true. Its full-page tool page uses a different cookie setting name, block_cookie_banners=true. Because those names conflict, verify the current parameter for the endpoint and version you use before copying either cookie-banner option.
3. Capture a full page in a browser for a one-off
If you only need one screenshot, a browser’s built-in capture flow may be enough. ScreenshotAPI.net’s guide lists full-size capture in Chrome or Edge DevTools and a full-page save flow in Firefox. Browser menus and steps can change between versions, so look for the current full-page or full-size capture command in your browser. This method is manual and does not provide a repeatable API request for a capture pipeline.
4. Troubleshoot an incomplete screenshot
| Symptom | Likely cause | What to check |
|---|---|---|
| Only the initial screen appears | Full-page mode is missing or misspelled | Confirm the request includes full_page=true. |
| The image ends at a specific region | A clip rectangle or element capture is active | Remove region-specific capture settings for a document-length screenshot. |
| Spreadsheet rows are missing | The page may need a different browser height or layout | Use full-page mode and choose a browser height suitable for that spreadsheet; no single value applies to all pages. |
| Images or sections that appear while scrolling are absent | Content may load lazily or require site-specific state | Check the provider’s current rendering and wait options. The vendor says its renderer scrolls to trigger lazy-loaded content, but behavior can vary by site. |
| A cookie banner remains visible | The parameter may be wrong for the endpoint version | Check current endpoint documentation: the help and full-page pages use different cookie-banner parameter names. |
| Ads cover content | Ad blocking is not enabled or supported for the request | Check whether block_ads=true is available for your endpoint and version. |
5. Performance, reliability, and cost considerations
A full-page capture can contain substantially more content than a viewport screenshot, so consider output size and processing time when choosing it for a batch or recurring job. The reviewed ScreenshotAPI.net material does not establish a universal maximum page height, a performance benchmark, or plan-specific limits. Do not treat an illustrative page height shown by a vendor as a service limit.
For reliability, verify the output on pages with long content, sticky elements, lazy loading, or application-driven rendering. Check a few representative pages before relying on a capture in an automated workflow. Use the current vendor documentation for any endpoint-specific limits and options.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. Its full-page capture loads lazy images. Cookie banners, popups, and chat widgets are removed before the shot; each cleanup step can be turned off. Bot checks, blank pages, and failed loads are never billed, and responses identify the page verdict and billing status. AI agents can use its MCP server tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Make one GET request with a URL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo API documentation for options such as viewport presets, element capture, waiting, custom CSS, and PDF output. Sign up free for 1,000 screenshots a month, with no card required.
FAQ
What does a full-page screenshot capture?
It requests the document beyond the initially visible viewport, including content farther down the page. ScreenshotAPI.net describes its full-page mode this way.
Does full-page mode capture content that loads while scrolling?
ScreenshotAPI.net says its renderer scrolls to trigger lazy-loaded content. Site-specific loading behavior can still affect what appears in the result.
Why does changing the browser height not replace full-page mode?
Height sets the browser viewport. Full-page mode requests the document-length capture; they are separate controls.
