If a ScreenshotAPI.com capture stops at the visible browser area, explicitly enable fullPage=true. The setting defaults to false; increasing the viewport height is not the documented way to capture the entire scrollable page. If full-page mode is already on, check whether your request targets one element, whether missing content needs scrolling to load, and whether the page had time to render.
First, verify which ScreenshotAPI you are using
Several similarly named services have different hostnames and parameter conventions. The steps below apply to ScreenshotAPI.com, whose API reference is at https://screenshotapi.com/documentation and whose API hostname is api.screenshotapi.com. Its reference page displayed “Updated 7 months ago” when reviewed; that is the page’s update marker, not a confirmed API release date.
As an Amazon Associate I earn from qualifying purchases.
Do not copy settings from another provider just because its name is similar. For example, Screenshot API at api.screenshot-api.org documents its own request format, and ScreenshotAPI.net has separate selector and clipping options. The references are https://screenshot-api.org/docs and https://screenshotapi.net/documentation, respectively.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsEnable full-page capture
On ScreenshotAPI.com, fullPage is optional and defaults to false. Set it to true in the request to capture the full scrollable page rather than only the viewport. The API reference documents viewport size separately: GET requests use width and height, while POST JSON requests use viewport.width and viewport.height. A taller viewport changes the browser’s visible area; it is not the documented full-page switch.
#1 Best Overall
For example, if your GET request already has a URL and API key, add fullPage=true as a parameter. Check the final encoded request URL or POST body to confirm that the value reaches the ScreenshotAPI.com endpoint as a boolean true, rather than being omitted or set to false. Use the provider’s current API reference for the exact request format and required credentials.
If full-page mode is already enabled, check what is being captured
Remove unintended element targeting
ScreenshotAPI.com supports capture of a specific CSS selector. If your request selects an element, the result may be limited to that element by design, even when the goal was to capture the whole page. Review the request for selector or element-capture settings and remove them when you want a document-wide screenshot.
Rank #2
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL160_.jpg)
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
Trigger content that loads on scroll
Some pages insert images or sections only after the visitor scrolls near them. ScreenshotAPI.com documents doScroll as a way to scroll before capture and trigger lazy-loaded content. Use that setting if the missing material does not exist until scrolling occurs. A longer wait is not equivalent: waiting gives a page more time, while scrolling triggers a different behavior.
Free tools Windows power users keep installed
One-click scans. No signup required.
Wait for the content you need
ScreenshotAPI.com offers waitUntil options of load, domcontentloaded, networkidle0, and networkidle2, as well as waitForSelector and a post-load delay. Choose based on how the missing section appears:
- Use
waitForSelectorwhen a specific element signals that the needed content is ready. - Choose an appropriate
waitUntilcondition when the page’s navigation or network activity is the relevant readiness signal. - Use
delayfor content that appears after a known additional interval; the reference documents an input range of 0–20,000 ms. That range is an accepted setting, not a guarantee that any particular site will finish rendering in that time. - Use
doScrollwhen loading depends on scrolling; a wait condition or delay does not perform that documented scroll action.
Verify the request and output
- Confirm the hostname is
api.screenshotapi.comif you are following ScreenshotAPI.com’s parameter names. - Inspect the exact outgoing URL or POST body. Confirm
fullPageis true and look for selector or element-targeting settings that could narrow the capture. - If only below-the-fold content is absent, determine whether it is lazy-loaded and configure the documented scroll behavior where appropriate.
- Match the wait condition to the page’s rendering behavior, using a selector when there is a reliable element to wait for.
- Check the resulting image dimensions and compare them with the expected page capture. The reviewed ScreenshotAPI.com reference does not specify a maximum full-page height or a truncation response header; if you suspect an account or plan limit, check the provider’s current, account-specific documentation rather than assuming a particular limit.
Common causes and fixes
| What you see | Likely request-level cause | What to check |
|---|---|---|
| Image ends at roughly the initial visible area | fullPage is absent or false |
Set fullPage=true; do not rely on viewport height alone. |
| Only one section or component appears | A CSS selector or element-capture option narrows the target | Remove the selector if the intended result is the full document. |
| Lower images or sections are missing | Content may load only after scrolling | Check whether the page needs the documented doScroll behavior. |
| Content appears inconsistently or is absent on dynamic pages | Capture may happen before the relevant element renders | Wait for the element, select a suitable waitUntil condition, or use an appropriate post-load delay. |
| Parameter seems ignored | The request may target a different similarly named service or endpoint | Verify the hostname and use that provider’s own API documentation. |
Or skip the browser setup
ScreenshotNeo provides a screenshot API and MCP server for developers. A single GET request can return a screenshot or PDF; its API accepts URL parameters, and its documentation describes the available options. For a basic capture, replace the target URL and provide your API key:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. ScreenshotNeo removes cookie banners, popups and chat widgets before the shot; bot checks, blank pages and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Learn about ScreenshotNeo, or sign up for 1,000 free screenshots a month with no card.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Why is my ScreenshotAPI screenshot cut off?
On ScreenshotAPI.com, the most direct check is whether the request sets fullPage=true; its documented default is false. If it is already enabled, inspect selector targeting, scroll-triggered content, and render timing.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Best Value
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.
