How to set a custom viewport for website screenshots in Zapier Interfaces

Short answer: Zapier Interfaces does not document a native control for setting the browser viewport of a website screenshot. To capture a public website at a custom size from a Zap, use a connected screenshot service action that provides dimension fields, then enter the width and height there. ScreenshotOne and Urlbox list viewport width and height fields; PagePixels lists page width and page height. These are provider action fields, not native Interfaces settings. Zapier’s Interfaces documentation covers building pages and components, including adjusting component width and alignment.

First identify what you are trying to resize

There are two different tasks that can sound like “setting a viewport”:

• Capture a public website: A screenshot action loads a URL in a browser and captures it. Set the dimensions in the screenshot provider’s Zapier action, if that action exposes them.
• Change an Interface’s layout: Edit the Interface page or component. Zapier documents controls for component width and alignment. That changes how the Interface is laid out; it is not a browser viewport setting for capturing another website.

Set dimensions in a Zapier screenshot action

1. Open the Zap that should create the screenshot, or start a new Zap for that workflow.
2. Add the screenshot provider’s website-capture action and connect the account as requested by Zapier.
3. Map the website URL into the action’s URL field.
4. Look for the dimension inputs in the action configuration. ScreenshotOne’s listing names Viewport Width and Viewport Height. Urlbox’s listing also names viewport width and height. PagePixels lists Page Width and Page Height.
5. Enter the dimensions required by your downstream use, save the action, and run a capture. Inspect the resulting image at the actual size your next step will consume.
6. If the fields are missing, check that you selected the screenshot action (rather than a different action from the same provider), and consult the provider’s current Zapier action editor or documentation. Action fields and provider behavior may change.

Zapier’s provider listings establish that these dimension fields exist; they do not establish a universal allowed range, default, or identical meaning for every provider. In particular, the labels “viewport” and “page” may represent different capture behavior. Confirm what the selected provider means before depending on the result.

Choose the right dimension fields

Zapier integration	Dimension fields listed	What to verify
ScreenshotOne	Viewport Width, Viewport Height	Accepted dimensions and how viewport sizing interacts with full-page capture in the current action.
Urlbox	Viewport width and height	Accepted dimensions, output behavior, and any additional capture settings needed.
PagePixels	Page Width, Page Height	Whether page dimensions match your intended viewport semantics and output.

Choose based on whether the action exposes the dimensions you need, whether its other capture options fit the task, and the provider’s current constraints, output, cost, and privacy/security terms. The cited listings support the field names above; they do not establish comparable prices, limits, or privacy terms.

Viewport size, full-page capture, and output size

A viewport is the browser’s visible layout area while a page is rendered. Changing its width can change responsive breakpoints, column layout, navigation, and text wrapping; changing its height changes how much of the rendered page is initially visible. A full-page option, when available, may extend the capture beyond the initial visible area. Do not assume that a full-page image’s final pixel dimensions equal the viewport dimensions: check the provider’s current behavior and inspect an output.

Also distinguish browser viewport dimensions from image output dimensions. A provider may offer separate scaling or resizing controls, but the cited Zapier listings do not establish those options or their behavior. If a downstream app requires a particular image size, verify the generated file rather than relying on the input labels alone.

Make the result dependable

• Use a stable, publicly reachable URL if the capture service must load it without your browser session.
• Test representative pages at the chosen width, especially pages with responsive navigation, long tables, or embedded content.
• Check the saved image for clipping, unexpected mobile/desktop layout, blank content, and whether the capture is full-page or viewport-only.
• For dynamic pages, check whether the provider action offers a wait condition or delay; the dimension listings alone do not document waiting behavior.
• Before building downstream steps around a field, confirm the provider’s current limits and output format. The available evidence does not establish universal dimension limits or a tested configuration sequence.

Troubleshooting

Symptom	Likely cause	What to do
No width or height fields appear	The selected action does not expose dimensions, or you chose a different action.	Confirm the exact screenshot action and inspect its current configuration. Choose an integration whose listing exposes the dimensions you need.
The capture has the wrong responsive layout	The dimensions were not mapped as intended, or the provider interprets the inputs differently than expected.	Review the mapped values and the provider’s field definitions. Capture a test and inspect which layout breakpoint the page used.
The output is clipped or unexpectedly tall	You expected full-page output but configured a viewport capture, or the provider handles page dimensions differently.	Check the action’s full-page options and documentation. Compare the output dimensions with the intended capture behavior.
A dynamic section is missing	The page may not have finished rendering when the provider captured it.	Check for provider-supported wait settings, then run another capture. The cited listings do not specify these settings.
The Zap succeeds but a later step rejects the file	The output format, dimensions, or returned value may not match the next app’s input requirements.	Inspect the action output and downstream field mapping; verify the required format and size with the receiving app.
Provider limits or charges are unclear	The integration listing does not establish current pricing, limits, or terms.	Check the provider’s current plan and documentation before relying on a volume or cost estimate.

Performance, reliability, and cost

Screenshot work adds an external page load and capture action to a Zap. Large or slow pages and waits can affect how quickly the step completes; the available sources do not provide comparable timing or reliability benchmarks. Keep the capture focused on the page and output you need, and account for provider limits and charges using that provider’s current terms. Do not infer a cost per capture from the presence of a Zapier integration listing.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Use it directly from a Zapier-capable HTTP request step when you want to call a screenshot endpoint without configuring a browser yourself. See the ScreenshotNeo API documentation for request options.

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

The API call takes a URL and returns an image or PDF. ScreenshotNeo removes known cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server exposes screenshot, page-info, and PDF tools to AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.

Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.

FAQ

Can I set a website screenshot viewport directly in Zapier Interfaces?

The cited Interfaces help documentation does not describe a native website screenshot viewport control. Set dimensions in a connected screenshot action that exposes them.

Are viewport width and page width interchangeable?

The source listings use different labels, and they do not establish identical semantics. Check the selected provider’s documentation and inspect a capture.

What dimensions should I use?

Use dimensions appropriate to the layout you need to capture, then verify the output on representative pages. The cited sources do not specify a universal recommended size or accepted range.

Does changing a component’s width in Interfaces change a screenshot viewport?

No such relationship is documented. Zapier describes component width and alignment as Interface editing controls; screenshot dimensions belong to the connected capture action.