Can CloudConvert Capture a Webpage at a Custom Viewport Size?

Yes. CloudConvert supports custom viewport sizing for website screenshots. Its Website Screenshot API example uses a capture-website task with width set to 1440. That value is an example, not a stated default or maximum. The API task can produce a PDF or a PNG/JPG screenshot; consult the current operation reference or Job Builder for exact current parameter names and supported values beyond the documented example.

What custom viewport size means

A viewport is the browser’s visible layout area while a page is rendered. Setting a viewport width can change responsive behavior: a site may switch navigation, column layout, or other styles at a breakpoint. It is distinct from asking for a full-height or full-page capture. CloudConvert describes full-height captures as the default while also supporting custom viewport sizing; do not assume that setting a width alone makes the output a fixed-height viewport image.

CloudConvert’s online PNG and JPG screenshot tools also describe customizable screen resolution. For automated, repeatable captures, use the API’s website capture task; for a one-off capture, its online tools may be sufficient.

Set a custom width with CloudConvert’s API

Create a CloudConvert job with a capture-website task, provide the target URL and output format, and set the width. The documented example uses 1440. The following illustrates the job structure; use CloudConvert’s current API documentation or Job Builder to confirm the exact request and authentication details for your account before running it.

{
  "tasks": {
    "capture": {
      "operation": "capture-website",
      "url": "https://example.com",
      "output_format": "png",
      "width": 1440
    }
  }
}

The important setting is the width on the capture task. Replace the URL and output format as needed. CloudConvert documents PNG and JPG screenshot outputs, and the operation can also capture a website to PDF. Do not infer undocumented height limits or additional option names from this example.

Choose a width that matches the use case

Responsive layout review: capture at the width where you want to inspect the page’s layout. If you are checking a breakpoint, capture on both sides of the breakpoint.
Consistent reports: keep the width fixed across runs so layout changes are easier to compare.
Full-page output: remember that full-height capture and viewport width describe different dimensions of the capture. Check the output behavior in the current operation documentation.

Practical workflow

Choose the target page and the output type: PNG or JPG for an image, or PDF when a document is needed.
Build a CloudConvert job with a capture-website task and provide the URL.
Set width to the desired viewport width. The published example uses 1440 pixels.
Run the job and retrieve its output using the current CloudConvert API workflow.
Inspect the result at the target width. If the page uses responsive breakpoints, adjust the width and capture again.

For options beyond the demonstrated width, use CloudConvert’s live Capture Website operation reference and operations documentation. They are the right places to confirm current accepted fields, ranges, and job details.

Choosing between the API and online screenshot tools

Need	Practical choice
One-off screenshot with a custom resolution	CloudConvert’s online PNG or JPG screenshot tool exposes resolution customization.
Repeatable or automated captures	Use the API job with a `capture-website` task and a fixed width.
Need exact current option names or limits	Check the live operation reference or Job Builder; the cited example does not establish all values or limits.

Or skip the browser setup

If you want a screenshot API with a single GET request, ScreenshotNeo accepts a URL and returns PNG, JPEG, WebP, or PDF. Its capture options include custom viewports and device presets. For a simple WebP capture:

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

Python:

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)

Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

See the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot, and those steps can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed; response headers report the page verdict and billing status. An MCP server lets AI agents use screenshot tools. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000 screenshots.

Troubleshooting custom viewport captures

The result does not look like the expected responsive layout

Confirm that the width is set on the capture-website task and that the job was created with the intended value. Sites may use breakpoints at different widths; try a width on either side of the breakpoint you are investigating.

The output dimensions do not match the viewport width

A full-height screenshot may have output dimensions that differ from the visible viewport’s height. Full-height capture and viewport sizing are separate behaviors. Review the current operation reference for the exact supported controls; the cited example establishes a width setting but not every dimension rule.

The API rejects an option

Do not assume additional field names or allowed ranges from the width: 1440 example. Check the live operation reference or construct the task in Job Builder, then use the documented field and value for the current API.

The job fails or no image is available

Inspect the job and task status using CloudConvert’s current job workflow, and verify that the URL and output format are supplied. The research materials do not establish particular error codes or retry behavior, so use the operation documentation for the current failure details.

Performance, reliability, and cost considerations

Repeatability: a fixed width makes recurring captures more consistent, though page content itself can change.
Responsive checks: each width can select a different page layout, so one screenshot cannot represent every device size.
Output handling: choose PNG or JPG for screenshot images and PDF for document output, according to the task’s supported options.
Cost and limits: the cited CloudConvert materials do not specify pricing, job quotas, capture-time guarantees, or viewport bounds. Check CloudConvert’s current account and API documentation before estimating a production workload.

FAQ

Can I set a custom screenshot width in CloudConvert?

Yes. The Website Screenshot API example sets width to 1440.

Is 1440 the maximum or default width?

No such limit or default is established by the cited example. It is an example value only.

Does a custom width disable full-height capture?

The available documentation describes full-height capture by default and custom viewport sizing as supported. They refer to different aspects of capture; check the current operation docs for exact behavior.

Can I get a PDF instead of an image?

The capture-website operation is documented for PDF capture as well as PNG/JPG screenshots. Confirm the current output settings in the operation reference.