ScreenshotNeo

BlogHow-to

How to Set a Viewport Size in VisualScraper Screenshots

VisualScraper’s viewport-size controls could not be verified. Learn what to check, how viewport differs from image size, and a documented API alternative.

By the ScreenshotNeo team4 October 20265 min read

Direct answer: I could not verify a VisualScraper setting or click-by-click procedure for choosing screenshot viewport width and height. A third-party overview lists screenshot capture among VisualScraper’s actions, but it does not document viewport dimension controls. Do not assume that settings from another screenshot product apply to VisualScraper.

If your version exposes a viewport control, use its own current documentation or interface to confirm the control name and units before relying on it. The practical guidance below explains what to look for, how to distinguish viewport size from output-image size, and a documented alternative if you need a specified viewport now.

1. What is known about VisualScraper viewport settings

The available third-party overview describes VisualScraper as web data extraction software and mentions screenshot capture. It does not establish that VisualScraper lets you set screenshot viewport width or height, nor does it identify a menu, default, or sequence of steps. The exact VisualScraper-specific workflow therefore remains unverified. Third-party VisualScraper overview

That uncertainty matters: a screenshot action does not by itself prove that the browser viewport is configurable. Check the documentation for the exact VisualScraper version you use, or inspect its current capture settings. Look specifically for separate width and height controls, a device preset, or a browser-window size option. Treat those as things to check, not confirmed VisualScraper features.

2. Viewport dimensions versus saved image dimensions

The viewport is the visible browser area used to render a page. Its width can change responsive layout: navigation may collapse, columns may stack, and images may use different sizes. The screenshot’s output dimensions describe the pixels in the saved file. Those can differ from the viewport if capture uses scaling, a device pixel ratio, cropping, or full-page capture.

Term What it describes What changing it can affect
Viewport width and height The browser’s visible rendering area Responsive breakpoints, visible content, and line wrapping
Device pixel ratio or scale How CSS pixels map to screenshot pixels Output sharpness and pixel dimensions
Full-page capture Whether capture extends beyond the visible viewport Output height and inclusion of content below the fold
Crop or resize Post-render output framing or dimensions Final image dimensions, potentially without changing layout

For a responsive-layout check, the viewport is the key value. For a file-size or image-dimension requirement, check scale, crop, and resize behavior as well. A file with the requested pixel width does not prove the page was rendered at that CSS viewport width.

3. How to check your VisualScraper installation

  1. Identify the VisualScraper version or edition you are using, so that any instructions match your installation.
  2. Open the current product documentation or screenshot configuration in that version.
  3. Look for explicit viewport width and height settings, or a named device preset. Confirm units and whether dimensions mean CSS pixels or output pixels.
  4. Capture a test page with obvious responsive behavior at two widths, if the product supports those settings.
  5. Inspect both the page layout and the saved file dimensions. They answer different questions.

If no viewport control is documented or visible, do not infer one from a browser zoom option. Zoom changes page rendering scale and is not equivalent to setting the browser viewport dimensions. The available overview mentions disabling browser zoom, but does not describe viewport width or height controls. Third-party overview

4. When viewport size is configurable: reproducible capture checklist

These are general checks for any screenshot workflow, not verified VisualScraper settings:

  • Record width and height in the units the tool expects.
  • Keep zoom at the intended value, usually the default, when comparing responsive layouts.
  • Wait for the page to finish loading and for dynamic content to settle before capture.
  • Decide whether you need the visible viewport or the entire page.
  • Keep scale or device pixel ratio fixed when comparing output files.
  • Use the same URL, cookies, and page state across captures when you want a fair comparison.

5. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Its documented options include viewport dimensions, device presets, retina scale, full-page capture, and output formats. One GET request can return an image or PDF. See the ScreenshotNeo API documentation for parameters and configuration.

For example, this request captures a page at a specified viewport (adapt the URL and dimensions for your capture):

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

Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

Sign up for 1,000 free screenshots a month.

6. Troubleshooting viewport screenshots

Symptom Likely cause What to check
The page looks like desktop when you expected mobile The viewport may not have changed, or the tool may be changing output size instead Verify the documented viewport value and inspect responsive layout, not only file dimensions.
The screenshot has the right width but the layout is wrong Output resizing or scaling can change pixels without changing the rendering viewport Check viewport dimensions separately from device scale, crop, and resize.
The page appears zoomed or text wraps unexpectedly Browser zoom, device scale, or viewport width may differ from the intended setup Hold zoom and scale constant, then verify the viewport units.
Lower content is missing The capture may cover only the visible viewport Check whether full-page capture is available and enabled in your tool.
Different runs produce different layouts Responsive pages may depend on dynamic content, fonts, timing, cookies, or page state Keep the page state consistent and wait for content to settle before capture.
You cannot find a width or height option in VisualScraper The control may not exist in your version, or its behavior is undocumented in the sources available here Consult current VisualScraper documentation or support. Do not substitute another product’s parameter names.

7. Reliability, performance, and cost considerations

Viewport changes can trigger different page layouts and resource requests, so captures at multiple sizes may take longer than a single capture. Full-page screenshots can also be larger than viewport-only images. For repeatable comparisons, capture the same page state and keep zoom, scale, timing, and full-page behavior consistent.

The available research does not establish VisualScraper’s current viewport capability, capture reliability, performance, or pricing. Check current product materials for those details rather than relying on assumptions. A third-party overview is not product documentation, and documentation for another screenshot API cannot establish VisualScraper behavior. Overview mentioning VisualScraper screenshots · ScreenshotMAX documentation (a different service)

8. FAQ

Can I set a VisualScraper screenshot viewport to an exact width and height?

The available sources do not verify that VisualScraper provides this control. Check the current documentation or interface for your version.

Does changing browser zoom set the viewport?

No. Zoom affects rendering scale; viewport dimensions describe the browser’s visible area. They are separate settings.

Is a screenshot’s pixel width the same as its viewport width?

Not necessarily. Device scale, resizing, cropping, and full-page capture can affect output dimensions independently of the viewport.

Do I need a physical device to capture a mobile-sized viewport?

The research does not support a physical device requirement for setting this software option. Whether VisualScraper offers mobile emulation remains unverified.