How to Pass Page Width and Height Settings to a Screenshot API in Zapier

Direct answer: In Zapier’s Screenshot API app, open Take Screenshot and set Screenshot Width and Screenshot Height. For a scrolling capture, choose Scrolling Screenshot and set Browser Width and Browser Height. These are separate actions with differently named dimension fields. Zapier’s integration listing does not document their defaults or accepted ranges, so do not assume a particular size is required or supported without checking the current action in your Zap editor. Zapier Screenshot API integration.

Choose the right Zapier action

Use Take Screenshot for a standard capture. Use Scrolling Screenshot when the selected action’s scrolling capture behavior is what you need. The dimension fields are:

Zapier action	Width field	Height field
Take Screenshot	Screenshot Width	Screenshot Height
Scrolling Screenshot	Browser Width	Browser Height

The dimensions are optional in the integration listing. Provide the page URL and output selection required by the action, then set dimensions if you need a particular capture size. Width and height settings alone do not establish whether an action captures a viewport or a full page; check the selected action’s description and output.

Set fixed dimensions in a Zap

Open the Zap editor and add the Screenshot API app.
Select Take Screenshot or Scrolling Screenshot.
Enter or map the page URL and complete the action’s required output fields.
For Take Screenshot, fill in Screenshot Width and Screenshot Height. For Scrolling Screenshot, use Browser Width and Browser Height.
Test the step in Zapier and inspect its response before publishing. This confirms how the current configuration responds; the published integration listing does not specify dimension defaults or limits.

Enter fixed values when every run should use the same dimensions. The dossier does not establish the units or allowed numeric ranges for the native integration fields, so verify those details in the action’s current editor or provider documentation if they matter to your workflow.

Map dimensions from an earlier step

If each record needs a different capture size, use Zapier’s field mapping controls to insert width and height values from a prior trigger or action. For example, a record might contain a requested width and height, which you map into the corresponding dimension fields. Keep the values numeric and make sure both are present when the action needs both dimensions. This is the ordinary Zapier mapping workflow; the integration listing does not document a special dynamic-dimension behavior.

Before enabling the Zap, test at least one representative record with the smallest and largest dimensions your own data will send. The integration listing reviewed here does not state accepted ranges, so do not infer a universal minimum or maximum.

Call a screenshot provider API with API by Zapier

Use Zapier’s API Request action when the native Screenshot API action does not expose a provider option you need, or when you need to call a different provider directly. There is no universal screenshot API parameter schema: consult the exact provider’s endpoint documentation for the HTTP method, endpoint, authentication, dimension parameter names, units, and whether it expects query parameters or a request body.

Add API by Zapier’s API Request action and configure the method and endpoint from the provider’s documentation.
Set the authentication method and credentials required by that provider.
Put query-based parameters in Zapier’s Query string parameters section. Enter the documented width and height names and map or type their values there.
If the endpoint requires a request body, follow the provider’s documented content type and body schema instead.
Test the request and inspect the returned response. Confirm it contains the expected image or a usable download reference before publishing.

Zapier’s API Request instructions say query parameters belong in the dedicated query-parameter fields and can use mapped values. The help article reviewed describes API Request as a beta feature available on paid plans; check the current editor and your plan because availability and labels can change. Zapier’s API Request instructions.

Example: screenshot-api.net raw API dimensions

The following details apply only when calling screenshot-api.net’s raw API, not automatically to Zapier’s native Screenshot API integration or other providers. That vendor documents the raw parameters as width and height, measured in CSS-pixel viewport dimensions, with defaults of 1280 and 800. It documents full_page separately, and says full-page capture height is capped at 4320 pixels. Consult its documentation for the endpoint, authentication, output, and complete request format before configuring API by Zapier.

For that vendor, the parameter mapping conceptually looks like this:

width  = 1440
height = 900
full_page = true  # separate setting, if supported by the selected endpoint

Use the vendor’s exact endpoint and authentication instructions in Zapier. The example values illustrate the parameters; they are not a universal recommendation or a tested live request.

Dimensions, viewport, and full-page capture

Width and height usually describe a browser viewport in screenshot APIs, but the meaning depends on the provider. A full-page option may capture content beyond the initial viewport and can have separate limits or behavior. Do not assume that increasing height is equivalent to enabling full-page capture, or that the native Zapier action uses the same terms and limits as a provider’s raw API.

For screenshot-api.net specifically, its raw API documentation separates full_page from width and height, and documents a 4320-pixel full-page height cap. Those facts must not be applied to another integration unless its own documentation says so.

Or skip the browser setup

If your Zap just needs a screenshot and you do not need to manage a browser session, ScreenshotNeo accepts a URL in one GET request and returns an image or PDF. Its clean-shot flow accepts consent banners like a visitor and removes 60+ known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the page verdict and billing status. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots each month with no card; paid plans start at $5 for 3,000 screenshots. See the ScreenshotNeo website and 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}`);

These examples use the requested target URL and the documented request pattern. Replace YOUR_API_KEY with your key. ScreenshotNeo supports viewport and device settings, full-page capture, and other documented options; see the docs for parameter names and response details.

Troubleshooting

Symptom	Likely cause	What to check
Changing dimensions seems to have no effect	The fields may belong to the other action, or the values may not be mapped into the selected action.	Confirm Take Screenshot uses Screenshot Width/Height and Scrolling Screenshot uses Browser Width/Height. Inspect the tested step’s inputs.
The API request ignores width or height	The parameter names or placement do not match the provider’s API.	Check the exact provider docs. Put query parameters in Zapier’s Query string parameters fields for a query-based endpoint; use the documented body for body-based APIs.
The returned capture is not full page	Viewport dimensions do not necessarily enable full-page capture.	Check whether the action or provider has a separate full-page setting and any associated limits.
Mapped dimensions are empty or invalid	The previous step may not supply the expected value on every run, or the value may not match the endpoint’s expected format.	Inspect sample trigger data, map the correct fields, and verify required units and bounds in the provider documentation.
API Request is missing from the editor or behaves differently	Zapier documents the feature as beta and plan dependent.	Check the current API Request help page and the available actions for your account.

Performance, reliability, and cost

Keep the route simple: use the native action when its fields meet the need. A custom API request adds provider-specific authentication and request formatting to maintain.
Validate dynamic inputs: missing or inconsistent dimensions can make runs behave unpredictably. Check representative records before turning on the Zap.
Plan for provider behavior: render time, full-page limits, and output handling vary by API. Follow the provider’s timeout, response, and retry guidance; the dossier does not provide universal values.
Check task and API costs separately: Zapier plan availability and provider billing are separate considerations. Confirm both against current account and provider terms; no price or performance benchmark is established here.

FAQ

Are Screenshot Width and Screenshot Height required?

Zapier’s integration listing marks the dimension fields as optional. The URL and output fields are marked required for the actions reviewed.

What dimensions should I use?

Use the dimensions appropriate for the page and output you need, then confirm the native action’s accepted values in its editor. Zapier’s listing does not publish defaults or ranges. For screenshot-api.net’s raw API only, the documented defaults are 1280 by 800 CSS pixels.

Can I use a different screenshot provider?

Yes, if its endpoint and authentication details are available to you. Configure API by Zapier according to that provider’s own docs; parameter names and units are provider-specific.

Does a scrolling screenshot mean full-page capture?

The action name alone does not establish all capture details. Review its current description and test the result. Provider raw APIs may expose full-page capture as a separate setting.