ShrinkTheWeb Screenshot Quality Settings Explained

ShrinkTheWeb’s available Drupal integration guide documents an optional quality parameter from 1 to 100. Its advanced Drupal 8 example sets the value to 90. That example is not a confirmed default or a tested recommendation. The guide does not document which output formats use the parameter or how changing it affects visual fidelity and file size. The available Drupal guide was last updated on 4 March 2019, so treat these details as documented historical guidance, not confirmation of current ShrinkTheWeb behavior.

What does the ShrinkTheWeb quality setting do?

In the Drupal integration guide, quality is an optional per-request setting for screenshot capture. The documented range is 1–100. Higher numbers are commonly used by image encoders to request a different quality-size tradeoff, but the cited ShrinkTheWeb guide does not explain that tradeoff or say that its parameter works that way. Do not infer a file-size result or visual result from the number alone.

The guide distinguishes two configuration paths:

Basic module usage and field formatters: use the global settings configured in Drupal’s administration page.
Advanced Drupal 8 requests: the PHP example can customize individual screenshot requests, including quality.

The guide describes the setting as optional and available to all accounts. Because the documentation is dated, verify current availability and behavior in ShrinkTheWeb’s current API documentation or by inspecting a current response before relying on it in production.

What value should you use?

The source supports no universal recommended value. Its example uses 90, but that is just an example. Choose a value only after checking what the current service returns for your output format and use case.

Pick representative pages, including pages with text, photographs, gradients, and fine lines.
Capture each page at a few candidate values within the documented 1–100 range.
Compare the resulting images at their intended display size, paying attention to small text, edges, gradients, and artifacts.
Record the response format and file size for each result. The guide does not guarantee that a higher number produces a larger file.
Repeat when you change output format, capture dimensions, or the service integration, since those can affect the result.

If you cannot confirm the current parameter behavior, avoid treating the Drupal guide’s range or example as a live API contract. Check ShrinkTheWeb’s current documentation or contact the service provider.

Drupal configuration: global settings and per-request settings

Basic module use and field formatters

For the basic Drupal integration and field formatters, configure the module’s global options in the Drupal administration interface. The available guide says these paths inherit global settings; it does not provide a current screen-by-screen walkthrough or establish that the present Drupal module behaves identically.

Advanced Drupal 8 requests

The guide’s advanced PHP example illustrates customizing screenshot requests individually, including setting quality to 90. The excerpted source does not provide enough verified detail to reproduce the complete request safely: it does not establish the current class, method, authentication, endpoint, or response-handling requirements. Use the current module/API documentation for a runnable integration rather than copying a partial or guessed snippet.

At a conceptual level, the request-specific configuration is where a per-capture quality value belongs; global configuration is the documented route for basic usage and formatters. Do not assume a per-request value overrides a global setting in a particular way unless the current documentation confirms the precedence.

Does higher quality make the screenshot file bigger?

The available ShrinkTheWeb guide does not answer this. It gives the parameter range and an example value, but does not quantify output size or describe the encoding behavior. Measure the actual returned files if size matters to your storage, network transfer, or page performance.

Keep the comparison controlled: capture the same URL with the same viewport, output format, and other options, changing only the quality value. Compare both file size and the visual details that matter for your use case. Do not generalize results from one page or format to all captures.

Does quality work with PNG?

The cited ShrinkTheWeb guide does not identify the formats affected by quality, so it does not establish whether PNG honors or ignores the parameter. Check current ShrinkTheWeb documentation or compare actual outputs for the format you use.

This is a provider-specific detail. For example, ScreenshotAPI.net says its 0–100 quality setting applies to JPG/JPEG and is ignored for PNG, while ScreenshotOne documents an image_quality option for several formats. Those providers’ rules cannot be transferred to ShrinkTheWeb. See their primary documentation: ScreenshotAPI.net documentation and ScreenshotOne image quality documentation.

Practical validation checklist

Confirm the current API or module accepts quality and the allowed range.
Confirm which output formats use the setting, if any.
Determine whether you are configuring global Drupal settings or individual requests.
Compare visual output at the dimensions where users will see it.
Measure returned file size instead of assuming that the quality number predicts it.
Check error responses and returned content type so an error page is not mistaken for an image.
Revalidate after updating the Drupal module or changing the screenshot service configuration.

Troubleshooting

Symptom	Likely cause	What to do
The request rejects the quality value.	The current service may use different validation or parameter rules than the dated guide.	Check current ShrinkTheWeb API documentation, verify the parameter name and accepted range, and inspect the service’s error response.
Changing quality has no visible effect.	The setting may not affect the returned format, the values may produce similar results for that page, or the per-request setting may not be applied.	Confirm format support and request configuration, then compare controlled captures and inspect the actual response.
File size does not change as expected.	The guide makes no file-size promise; output can depend on format and page content.	Measure the files for representative pages and use current provider documentation to interpret the setting.
The Drupal formatter ignores a request-specific value.	The guide says formatters use global Drupal settings; it does not document per-item overrides for them.	Configure the global module settings for formatter use, or use a documented advanced request path if individual customization is required.
A value of 90 is assumed to be the default.	The advanced example uses 90, but the guide does not call it a default.	Treat 90 only as the example value and explicitly configure a value only after verifying current behavior.

Performance, reliability, and cost considerations

Quality is only one factor in screenshot delivery. The available guide does not provide benchmarks, latency figures, reliability guarantees, current pricing, or a quality-to-size formula. For an application that stores or serves many captures, measure the output size and request behavior in your own workflow, and consult current ShrinkTheWeb service terms for pricing and operational details.

Keep captures reproducible while evaluating the setting: hold the URL, viewport, output format, and other request options constant. For production workflows, record the selected configuration and handle failed requests explicitly rather than assuming every response is a valid image.

Or skip the browser setup

If your goal is to get a screenshot file without building and operating a browser capture flow, ScreenshotNeo provides a screenshot API and MCP server. Its API returns PNG, JPEG, WebP, or PDF; see the ScreenshotNeo API documentation for supported request options and current usage details.

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}`);

Cookie banners are accepted and more than 60 known consent platforms, newsletter popups, and chat widgets are removed before capture; each step can be turned off.
Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing. Responses identify the page verdict and billing status in headers.
An MCP server gives AI agents tools for screenshots, page information, and PDF capture.
The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

Create a free ScreenshotNeo account to start with 1,000 screenshots a month and no card.

FAQ

Is 90 the best ShrinkTheWeb quality value?

The source only shows 90 in an advanced example. It does not establish that 90 is best or recommended.

Is the documented 1–100 range confirmed for the current service?

It is the range in the available Drupal integration guide, last updated in 2019. Current behavior has not been verified by the cited material.

Can I set quality separately for each Drupal field formatter?

The guide says field formatters use global settings. It describes individual request customization in its advanced PHP example, but does not document formatter-specific overrides.

Will quality change image fidelity or file size predictably?

The guide does not quantify either effect. Check the current service documentation and compare actual outputs for your format and pages.