ShrinkTheWeb screenshot is blank: troubleshooting guide

If your ShrinkTheWeb screenshot is blank, first check the access and secret keys configured in the integration. Then determine whether the image is a cached thumbnail and whether the settings you changed apply to the request that generated it. Those are documented checks for the Drupal integration; they do not prove a particular cause. Timing problems or automation blocking are also possible with screenshot services generally, but the available sources do not confirm them as ShrinkTheWeb-specific behavior.

This guide focuses on diagnosing the legacy Drupal integration and separating documented configuration checks from general possibilities. It does not assume the issue has been reproduced.

1. Confirm the Drupal integration credentials

The ShrinkTheWeb Drupal setup instructions require the profile access key and secret key to be copied into the module configuration. Check that both values are present and that you updated the configuration used by the site currently displaying the blank image.

Open the ShrinkTheWeb module configuration in Drupal.
Compare the configured access and secret keys with the values for the intended ShrinkTheWeb profile.
Save the configuration and request a new screenshot using the same page or field that showed the blank result.

Do not paste secret keys into public issue trackers, logs, screenshots, or support requests. The setup documentation establishes that the keys are required; it does not describe the service’s current credential validation behavior. [Drupal ShrinkTheWeb project page and setup links]

2. Check whether Drupal is showing a cached thumbnail

The Drupal module stores generated thumbnail images and provides a setting for how many days cached images remain unchanged. A blank image may therefore be the stored result rather than a fresh capture. First establish whether the image you see was generated recently.

Inspect the module’s configured cache age and the thumbnail’s age, if available.
Request or trigger a fresh capture through the same integration path.
Compare the refreshed result with the existing thumbnail.

The documentation describes caching, but does not prescribe a specific cache-clearing procedure for blank images. Follow the cache controls available in your Drupal installation; avoid deleting unrelated files or changing the cache age before identifying whether the displayed image is stale. [Drupal ShrinkTheWeb project page]

3. Verify which capture settings reach the request

A setting changed in one place may not affect a capture generated through another configuration path. The Drupal 8 guide says basic PHP examples and field formatters use global settings, while an advanced example can customize an individual request.

Capture path	What to check
Basic PHP example	Review the global module settings used by the example.
Field formatter	Confirm the global settings apply to the formatter displaying the thumbnail.
Advanced per-request example	Inspect the request-specific options; they may differ from global settings.

When a change appears to have no effect, identify the exact path that generates the image before changing more settings. [Drupal ShrinkTheWeb project page, including Drupal 8 documentation]

4. Review documented capture parameters

The Drupal instructions list these capture options:

URL: the page to capture.
Custom width: the requested screenshot width.
Full-length capture: capture beyond the initial viewport.
Maximum height: limit the captured page height.
Native browser resolution: use the browser’s native resolution option.
Widescreen resolution: request a widescreen capture.
Delay after page load: wait before taking the screenshot.
Quality: set output quality.

Some features require an upgraded account according to the integration documentation. Check the current service terms and account access before relying on a particular option; the older setup guides do not establish current availability or pricing. [Drupal ShrinkTheWeb project page]

5. Investigate page timing and automation blocking

If credentials, caching, and the request path check out, consider whether the target page is ready to capture or restricts automated access. Some screenshot services document blank or incomplete output in connection with capture timing. Browserless also lists automation blocking among possible reasons for blank or white output and access-denied pages. These are general diagnostic hypotheses, not confirmed ShrinkTheWeb behavior. [ScreenshotEngine documentation] [Browserless documentation]

Useful comparisons include whether the target URL loads normally in a browser, whether a delayed capture changes the result, and whether the page’s public content is available without a login, bot challenge, or other access restriction. If the page itself is inaccessible to a visitor, changing screenshot dimensions is unlikely to resolve the underlying access problem.

6. Account for the Drupal module’s support status

Drupal.org marks the ShrinkTheWeb project unsupported as of 2022-01-31 and lists no supported stable releases. This status is about the Drupal integration; it does not by itself show whether the separate ShrinkTheWeb service is available. [Drupal project status]

If you maintain a site that depends on this integration, record its Drupal version, module version, configuration path, and the steps that reproduce the blank thumbnail. That information helps distinguish an outdated integration from a setting or target-page issue.

7. Troubleshooting checklist

Symptom or check	What to investigate	Evidence and next step
Blank thumbnail persists after configuration changes	Wrong or missing access/secret key, or settings changed in a configuration path that does not serve the request	Verify the profile keys and identify whether the image comes from global settings or per-request options.
The displayed image may be old	Drupal’s stored thumbnail cache	Check the configured cache age and compare with a newly generated result.
Capture options seem ignored	Global settings versus request-specific options	Trace the exact Drupal usage path and adjust the settings that path reads.
Page is blank or incomplete only in a capture	Capture timing or automation restrictions, as general possibilities	Check the page’s browser behavior and consider whether a documented delay changes the result. Do not treat this as a proven ShrinkTheWeb-specific cause.
Feature is unavailable	Account-level feature access	Check current service terms; the older Drupal guide says some features require an upgraded account.
Integration is difficult to maintain	Drupal project support status	Drupal.org lists the project unsupported since 2022-01-31; assess whether your site should move to a maintained capture workflow.

8. Performance, reliability, and cost considerations

For the Drupal integration, the documented controls most relevant to capture behavior are dimensions, full-length capture, quality, and delay after page load. A longer delay can allow more page content to appear, but it also makes the capture take longer. Full-page captures and larger dimensions can produce more image data than a viewport capture. The sources do not provide ShrinkTheWeb performance benchmarks, current service reliability figures, or pricing, so do not infer them from these options.

For reliability, note whether a result came from cache, which Drupal settings applied, and whether the target page loaded for a normal visitor. For cost, verify current account terms directly before enabling options or increasing capture volume; the available integration documents are historical and do not establish current charges.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request returns a PNG, JPEG, WebP, or PDF. For an API call and the available parameters, see the ScreenshotNeo documentation.

For example, this cURL request saves a WebP screenshot:

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

The equivalent Python request is:

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)

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

Cookie banners and consent prompts are accepted or removed before capture, along with known newsletter popups and chat widgets; each step 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 provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
The free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots.

FAQ

Does a blank Drupal thumbnail prove ShrinkTheWeb is offline?

No. A blank thumbnail alone does not establish whether the integration, service, or target page is responsible.

Does Drupal’s unsupported status mean the ShrinkTheWeb service has closed?

No. The status applies to the Drupal project and does not establish the separate service’s current availability.

Which should I check first: page timing or the Drupal settings?

Start with the documented integration checks: credentials, cached image, and the configuration path. Investigate timing or automation blocking afterward as possibilities.

Are the listed capture options available on every ShrinkTheWeb account?

The Drupal documentation says some features require an upgraded account. Confirm current access with the service before depending on a feature.