Why Does ScreenshotMachine Capture the Wrong Page Size?

If ScreenshotMachine’s screenshot has the wrong pixel dimensions, check the dimension parameter first. It uses widthxheight, defaults to 120x90, and accepts full as the height for a full-page capture. If the pixel canvas is right but the content looks too large, too small, cropped, or laid out for the wrong device, check device, zoom, crop, selector, and capture timing separately.

1. Set the requested screenshot dimensions

Use a single explicit dimension value in width-by-height order. For example, 1366x768 requests a fixed canvas. The documented width range is 100–1920 pixels; numeric height can be 100–9999 pixels. The documented default is 120x90, so a request that omits the parameter may return a much smaller image than your application expects.

Request	Meaning
1366x768	Fixed requested width and height in pixels.
1024xfull	1024 pixels wide and full webpage height; the result may be much taller than the viewport.
Omitted	Uses the documented default, 120x90.

Keep the terms distinct: viewport is the browser area used to lay out a page; output canvas is the resulting image’s pixel dimensions. A mobile viewport can change responsive layout even when you are expecting a particular output size. Conversely, a full-page height can create a tall output without changing the requested width.

2. Send an explicit dimension in a request

For example, request a 1366 × 768 screenshot. Replace the placeholder key with your ScreenshotMachine API key and URL-encode values when building requests programmatically.

curl -G 'https://api.screenshotmachine.com' \
  --data-urlencode 'key=YOUR_SCREENSHOTMACHINE_API_KEY' \
  --data-urlencode 'url=https://example.com' \
  --data-urlencode 'dimension=1366x768' \
  -o screenshot.png

This example uses the documented API host and parameter names. Check ScreenshotMachine’s current API reference for authentication, response format, and any account-specific settings before adapting it.

3. Separate dimensions from layout, scale, region, and readiness

Once the requested canvas is explicit, inspect the other controls that can make an image seem the wrong size. The official [ScreenshotMachine API reference](https://www.screenshotmachine.com/website-screenshot-api.php) documents these settings and limits; its [online generator](https://www.screenshotmachine.com/website-screenshot-generator.php) also describes device choices and their effect on how modern pages look.

Setting	What it affects	Check it when
dimension	Requested output width and height; full requests full page height.	The image pixel canvas is unexpected or unexpectedly tall.
device	Rendering mode: desktop, phone, or tablet. Desktop is the documented default.	The page uses a mobile or tablet layout despite plausible image dimensions.
zoom	Content scale. The documentation describes 100 as original size and 200 as twice the size at 100.	Content appears too large or small. Zoom may be ignored for screenshots smaller than typical dimensions for the selected device.
crop	A viewport rectangle specified as x,y,width,height in pixels.	The image shows only part of the page or appears clipped.
selector	Targets one DOM element instead of the whole page.	The result contains a component or region rather than the full page.
delay	Wait time before capture.	Long-page images or animations have not finished loading.

Choose a device that matches the layout you want

Use desktop, phone, or tablet deliberately. The vendor’s examples pair desktop with 1024x768, phone with 480x800, and tablet with 800x1280. These are examples, not required pairings. Device mode can affect responsive rendering, so a correct output bitmap size does not guarantee a desktop layout.

Treat zoom as a separate control

Set the viewport dimensions and device first, then adjust zoom if the content scale still needs correction. Zoom is not a substitute for choosing the right viewport, and the vendor says it can be ignored below typical device dimensions.

Remove region restrictions when checking the whole page

Clear crop if the capture should include the full viewport. Clear selector if the intended target is the page rather than one element. A crop or element capture may produce a smaller-looking result even though the requested page viewport was not changed.

Wait for long pages to settle

For long pages with images or animations, ScreenshotMachine recommends a larger delay, for example 2000 ms or more. Delay controls when capture begins; it does not set the image width or height. Choose a wait appropriate to the page, then confirm that the content is present in the result.

4. Diagnose a mismatch systematically

1. Log the exact request your application sent, including the URL and all query parameters. Check for a duplicate or unexpected dimension value.
2. Confirm that dimensions use width-by-height order and that width and numeric height are within the documented ranges.
3. Check whether the height is full. Use a numeric height for a fixed-height viewport capture.
4. Record device and zoom separately. Compare the responsive layout and content scale, not just the bitmap dimensions.
5. Remove crop and selector temporarily if you expect a complete page or viewport.
6. If content is missing on a long page, increase delay and capture again.
7. Inspect the downloaded file’s actual pixel width and height. Save the exact URL and encoded parameters alongside it.

If a valid explicit dimension still produces unexpected pixels, the reviewed public documentation does not identify a vendor-specific cause. Preserve the request and output dimensions so the discrepancy can be investigated without guessing at the rendering engine.

5. Common errors and fixes

Symptom	Likely setting or cause	What to do
Image is only 120 × 90	dimension was omitted, leaving the documented default.	Send an explicit value such as 1366x768.
Image is far taller than expected	Height is set to full.	Use a numeric height such as 768 for a fixed viewport capture.
Canvas dimensions look right, but page is in a mobile layout	device=phone or device=tablet.	Select the intended device mode, usually desktop for a desktop layout.
Text or page content looks scaled	zoom changes content scale or is ignored at a small size.	Set a suitable device and dimension first; then review zoom behavior.
Only a rectangle is visible	A crop rectangle restricts the capture.	Remove the crop or correct its x,y,width,height values.
Only one component appears	selector targets an element.	Remove the selector to capture the page.
Images or animation frames are missing	Capture started before long-page content finished loading.	Increase delay; it affects readiness, not dimensions.
Request appears valid but output dimensions remain wrong	The documented sources do not specify the cause for this residual case.	Keep the exact encoded request and output pixel dimensions for follow-up; avoid assuming an undocumented internal defect.

6. Reliability, speed, and cost considerations

Dimension settings determine what you ask the API to capture; they do not by themselves establish capture reliability or cost. A longer delay can give slow images and animations more time to appear, but it also makes each capture wait longer. Use it where the page needs it rather than treating it as a size correction.

For repeatable diagnostics, keep the URL and parameters together with each saved image, and compare the output file’s pixel dimensions with the requested values. The public sources reviewed here give parameter ranges and examples, but no frequency data for wrong-size results, rendering-engine details, or pricing information. Check the provider’s current account and API documentation for applicable costs and operational details.

7. Or skip the browser setup

If your goal is a clean website capture without managing the browser rendering setup, [ScreenshotNeo](https://screenshotneo.com) provides a screenshot API and MCP server for developers. One GET request returns a PNG, JPEG, WebP, or PDF. Use this example to save a WebP capture; the endpoint and options are documented in the [ScreenshotNeo API docs](https://screenshotneo.com/docs/).

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

ScreenshotNeo accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and each response identifies the page verdict and billing status in headers. Its MCP server offers take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.

Sign up free for 1,000 screenshots a month with no card.

FAQ

What value should I use for a normal desktop viewport?

Choose the width and numeric height you need, such as 1366x768, and make sure the device mode matches the intended layout.

Does full mean the browser viewport is larger?

It requests full webpage height for the capture. Use a numeric height when you need a fixed-height result.

Can I fix a wrong layout by changing image dimensions?

Not necessarily. Layout depends on the device rendering mode and viewport; image dimensions alone do not ensure a particular responsive layout.

What if my explicit dimensions are valid but the output still differs?

Record the encoded request and inspect the saved image’s pixel dimensions. The reviewed ScreenshotMachine documentation does not establish a cause for every such mismatch.