ScreenshotMachine CLI Output Is Cropped: How to Fix Full-Page Capture

If ScreenshotMachine output stops at the visible browser area, check the request’s dimension parameter. Its documented format is [width]x[height]; use full for the height, such as 1366xfull, instead of a fixed height like 1366x768. If the page has images or animations that load late, increase delay. Also check that crop or selector is not limiting the result.

The official source documents ScreenshotMachine’s API parameters, but does not establish a canonical CLI command or flag. The exact CLI syntax depends on the CLI or wrapper you are using. Inspect its generated request and map the documented API settings to the wrapper’s actual options. ScreenshotMachine’s API documentation

1. Change the height to full

A fixed height requests a bounded capture. For a full-page screenshot, set the height component of dimension to full. For example, change 1366x768 to 1366xfull. The documented full-page example is 1024xfull.

Keep the width appropriate for the layout you want to capture. ScreenshotMachine documents desktop, phone, and tablet device values and example dimension combinations; choose the viewport based on whether you need a desktop or narrower responsive layout. A full-height request captures the page vertically; it does not make a desktop-width layout equivalent to a phone-width layout.

2. Check the CLI or wrapper request

Run the command with the same inputs that produce the cropped image.
Inspect the outgoing URL, query parameters, or request log.
Find dimension and verify the height is full, for example 1366xfull.
Check whether the CLI translates its own flags into API parameters. Do not assume a flag name based on another wrapper.
If no request is visible, consult that CLI’s help output or documentation for request logging and option mapping.

The API documentation alone cannot determine whether a particular third-party CLI accepts a flag such as --full-page. Confirm that wrapper’s version and syntax before changing a command.

3. Allow late content to load

Full-page capture can include areas that render images or animations after the initial page appears. If content near the bottom is blank or missing, increase delay. ScreenshotMachine gives 2000 milliseconds or more as an example for longer pages with images or animations. Treat that as guidance, not a guarantee for every site.

Increase the wait only as much as the page needs. A longer delay adds time to each capture, and it cannot fix an incorrect fixed-height dimension or an intentional crop.

4. Remove unintended crop and selector limits

crop specifies a pixel rectangle in x,y,width,height form. Remove it if you want the whole page rather than a particular region.
selector captures one DOM element. Remove it if the desired output is the complete page.

These options are useful when you intentionally want a region or a single component. They can make an otherwise correct full-page request appear cropped when enabled by a wrapper default or copied configuration.

5. Example API request

For a direct API request, the relevant settings are a full-height dimension and, when needed, a longer delay. The exact authentication and required parameters should follow your ScreenshotMachine account and current API documentation. The example below shows the documented parameter values; replace the placeholder key and target URL with values for your request.

curl -G 'https://api.screenshotmachine.com' \
  --data-urlencode 'key=YOUR_SCREENSHOTMACHINE_KEY' \
  --data-urlencode 'url=https://example.com' \
  --data-urlencode 'dimension=1366xfull' \
  --data-urlencode 'delay=2000' \
  -o full-page.png

Use the host, authentication format, and output format required by the current ScreenshotMachine API documentation. This API example is not a claim about any specific CLI wrapper’s command syntax.

6. Troubleshooting checklist

Symptom	Likely cause	What to check
Image ends at the viewport bottom	`dimension` has a fixed height	Set the height to `full`, for example `1366xfull`.
Only one region appears	A `crop` rectangle is applied	Remove `crop` unless you want a pixel-region capture.
Only a component appears	`selector` targets one DOM element	Remove `selector` for a whole-page capture.
Lower-page images or animation frames are missing	Content loads after capture begins	Increase `delay`; the docs give 2000 ms or more as an example for long pages with images or animations.
Changing a flag has no effect	The CLI flag may not map to the API parameter, or the wrapper may use a different option	Inspect the generated request and verify the CLI name and version.

7. Performance, reliability, and cost considerations

A full-page image can be taller and larger than a viewport screenshot, so use a fixed height when the viewport alone is what you need. Use full height when the entire document is required. The source gives no universal maximum page length, capture-time guarantee, or cost figure for this behavior, so check your account’s current plan and API documentation for those details.

For pages with late-loading content, an added delay can improve completeness but increases capture time. If results remain inconsistent, record the target URL, requested dimensions, delay, crop and selector values, CLI name and version, and the generated API request. This makes it possible to distinguish a request configuration issue from wrapper behavior.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. Its API supports full-page capture with lazy images loaded; the parameter names used by other screenshot APIs also work, which can make switching easier. See the ScreenshotNeo API documentation.

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

import 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}`);

Cookie banners are accepted like a visitor, and 60+ known consent platforms, newsletter popups, and chat widgets are removed before the shot. Each step can be turned off.
Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers report the page verdict and billing status.
An MCP server lets Claude, Cursor, and other MCP clients use take_screenshot, get_page_info, and capture_pdf.
The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Every feature is on every plan.

FAQ

Does `full` go in the width or height?

In the height component: for example, 1024xfull.

Will a longer delay fix a fixed-height screenshot?

No. Set the height to full for full-page intent. Use delay for content that needs more time to load.

What should I do if the CLI’s full-page option is unclear?

Inspect the outgoing API request and check the wrapper’s documentation for its version. The cited ScreenshotMachine API documentation does not define one canonical CLI interface.