VisualScraper Screenshot Quality Settings for Retina Displays
VisualScraper’s identity and settings could not be verified. Learn how device scale factor affects screenshot sharpness and how to check the right settings safely.
Direct answer: The available research does not verify which product or version “VisualScraper” refers to, so it cannot support specific VisualScraper setting names, defaults, commands, or menu paths. For retina displays, look in the confirmed product’s documentation for a device scale factor, device pixel ratio, or pixel density setting. Keep that separate from viewport width and height, and from image compression quality.
A scale factor of 2 means that each CSS pixel in the capture viewport maps to two output pixels in each dimension. For the same viewport, that doubles output width and height and produces four times as many pixels. The actual file-size increase depends on the image format and page content.
1. Confirm which VisualScraper you mean
The research did not find authoritative documentation for a screenshot product called VisualScraper. Search results included shot-scraper, a distinct command-line tool, but a similar name is not evidence that its options apply to VisualScraper.
Before changing a setting, identify the vendor, product type (desktop application, browser tool, or API), and version. Then find that product’s own current manual or API reference. Confirm the exact names and supported ranges for:
- Viewport width and height, typically expressed in CSS pixels.
- Device pixel ratio or device scale factor.
- Output format, such as PNG, JPEG, or WebP.
- Compression or quality settings, if available.
- Maximum output dimensions, pixel count, file size, or capture duration.
Until those details are verified, do not copy a command or default from another screenshot tool and label it a VisualScraper setting.
2. Understand viewport size, pixel density, and compression
Viewport dimensions control page layout
The viewport is the browser’s CSS-pixel-wide and CSS-pixel-high area used to render the page. Changing it can trigger responsive breakpoints, alter text wrapping, or switch a site between mobile and desktop layouts. Choose the viewport that matches the intended use of the capture.
Scale factor controls output pixel dimensions
Device pixel ratio (also called device scale factor in some tools) relates CSS pixels to output or display pixels. MDN describes devicePixelRatio as a ratio between physical pixels and CSS pixels; platform scaling can affect the relationship between physical and logical display dimensions.
| CSS viewport | Scale factor | Approximate output dimensions | Total pixels |
|---|---|---|---|
| 400 × 600 | 1× | 400 × 600 | 240,000 |
| 400 × 600 | 2× | 800 × 1,200 | 960,000 |
| 400 × 600 | 3× | 1,200 × 1,800 | 2,160,000 |
These are dimension calculations, not VisualScraper limits or guarantees. A higher factor can preserve more detail when the image is displayed at high density, but it also increases pixel count and may increase encoding time, memory use, and file size.
Compression quality controls a different tradeoff
A JPEG quality value generally controls lossy compression. It does not set the screenshot’s pixel density. PNG is typically lossless, while JPEG reduces file size by discarding image information; available formats and exact quality semantics depend on the product. For example, the shot-scraper documentation describes a separate JPEG quality option and demonstrates 80 as an example, while its retina example uses PNG. These are shot-scraper details only, not VisualScraper instructions.
3. Choose settings for the intended use
- Set the viewport first. Use the CSS dimensions needed to produce the correct responsive layout.
- Choose a scale factor. Start with 1× for ordinary previews or 2× when a sharper high-density image is needed and the target tool supports it. Treat this as a starting point, not a VisualScraper-specific recommendation.
- Select an output format. Use a lossless format when preserving fine UI details matters; consider a lossy format when smaller files matter and compression artifacts are acceptable.
- Check product limits. Verify maximum dimensions, pixel counts, memory, output size, and execution time in the product documentation.
- Capture and compare at intended display size. Inspect text edges, icons, thin borders, gradients, and image detail. Also confirm that the page did not change responsive layout.
- Adjust one variable at a time. Keep viewport and format fixed while comparing scale factors; then tune compression separately.
For a useful comparison, record the viewport, scale factor, format, quality value if applicable, output dimensions, file size, and capture time. Compare both at native size and at the actual rendered size where the screenshot will be used.
4. What can be verified in shot-scraper (not VisualScraper)
If your intended tool is actually shot-scraper, its documentation says --retina is a shortcut for device scale factor 2. Its example uses a 400 × 600 CSS-pixel viewport and produces an 800 × 1,200 image. It also documents --scale-factor for another positive floating-point factor, and says --retina and --scale-factor cannot be used together.
That example illustrates the general calculation, but those flags must not be attributed to VisualScraper unless its identity and documentation establish that it is the same product. Do not use these commands as VisualScraper commands.
5. Common problems and fixes
| Symptom | Likely cause | What to check |
|---|---|---|
| The image is still blurry on a retina display | The capture may be 1×, or it may be enlarged beyond its output dimensions when displayed. | Check actual output dimensions and the documented scale factor. Avoid enlarging the saved image in CSS or another editor. |
| The image is much larger than expected | Pixel count grew with scale factor; lossless formats and image content also affect size. | Verify output dimensions. If acceptable, choose a supported lossy format or lower its documented quality setting. |
| The layout changed between captures | The CSS viewport changed or crossed a responsive breakpoint. | Hold viewport dimensions constant while comparing density settings. |
| A setting or command is rejected | The option may belong to another product or version, have a different name, or be unsupported. | Check the exact vendor’s documentation for your installed version; do not assume shot-scraper flags apply. |
| Capture runs slowly or fails at high density | More pixels can require more memory, encoding work, and transfer capacity; the tool may enforce limits. | Check the product’s dimension and resource limits, then lower the scale factor or viewport if the use case permits. |
| Changing “quality” does not sharpen text | Compression quality and pixel density are separate controls. | Find the documented scale factor or device pixel ratio setting, and judge compression separately. |
6. Performance, reliability, and cost considerations
For a fixed CSS viewport, doubling scale factor produces four times the pixel count. This can increase render, encode, storage, and transfer work, although the precise effect depends on the tool, format, and page. High-density captures can also encounter product-specific limits. When generating screenshots in bulk, validate a representative page and monitor the target tool’s documented limits and failure behavior before scaling up.
Cost depends on the product’s pricing model. Check whether billing is based on captures, output pixels, storage, or compute time, and whether retries or failed page loads count. The available research provides no VisualScraper pricing or reliability figures, so none can be stated here.
7. Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. For a direct image capture, its API accepts one GET request with a URL; see the ScreenshotNeo documentation for supported options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport 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}`);ScreenshotNeo accepts cookie and consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server provides screenshot tools for Claude, Cursor, and other MCP clients.
The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Every feature is on every plan. Create a free ScreenshotNeo account.
8. FAQ
Does retina mean I should always use 2×?
No. Use the density required by the screenshot’s display size and the target tool’s limits. Higher density increases output pixels and resource needs.
Will a higher scale factor make a mobile layout appear?
No. Layout responds to the CSS viewport and page behavior. Set viewport dimensions for the layout you need; scale factor changes pixel density.
Is VisualScraper the same as shot-scraper?
The research does not establish that. Confirm the vendor and product documentation before using shot-scraper options.
What information would settle the VisualScraper settings?
The vendor’s product page or versioned manual, plus the installed version and whether it is an app, browser tool, or API. Those identify the settings that can be recommended accurately.
