Thumbalizr Not Working in Chrome: Website Screenshot Fixes

If Thumbalizr is not working in Chrome, first identify whether you are using Thumbalizr’s website, its API or embed code, or a separate Chrome extension. Those are different workflows with different failure points. For API captures, inspect the X-Thumbalizr-Status and X-Thumbalizr-Error response headers: QUEUED means the capture is still processing, OK means Thumbalizr reports it completed, and FAILED means it failed. A crop or watermark may be a free-plan limit rather than a Chrome problem.

1. Identify the workflow and capture the exact error

Thumbalizr is an online website screenshot and thumbnail service with a web interface and API. It is not inherently a Chrome extension. Start by recording the URL you entered, the action you took, what appeared, and the exact error text. Do not share API secrets or account credentials while asking for help.

Website: Does the problem happen while submitting a URL on Thumbalizr’s site, waiting for the result, or downloading it?
API or embed: Record the HTTP status and the X-Thumbalizr-Status and X-Thumbalizr-Error headers.
Separate extension: Confirm its name and whether Chrome says it is blocked or cannot access a page. Extension-specific advice below applies only if you actually use one.

Also try a second public page that does not require a login. If one target fails but another works, the problem may relate to the target page’s availability or behavior rather than Chrome generally. This is a diagnostic comparison, not proof of a specific cause.

2. Read the Thumbalizr API result

Thumbalizr documents three capture status values in X-Thumbalizr-Status: QUEUED, OK, and FAILED. The X-Thumbalizr-Error header reports its failure reason. Check these headers before changing browser settings; they distinguish a pending or failed service capture from a result-display problem in Chrome.

Header value	What it indicates	Next step
`QUEUED`	Processing is ongoing.	Wait for completion and retrieve the result according to the API workflow you use. Avoid treating a pending result as a completed image.
`OK`	Thumbalizr reports that the capture completed.	If Chrome still does not show it, inspect the returned response, image URL or embed markup, and browser console/network errors.
`FAILED`	The capture failed.	Read `X-Thumbalizr-Error`, then verify the request, credentials or token, target URL, and account allowance.

The headers report Thumbalizr’s status; they do not on their own establish why a failure happened. Save the exact error string for support or further diagnosis.

3. Validate URL encoding and Embed API authentication

Thumbalizr warns that API parameters must be encoded correctly, especially the target URL. A URL passed as a query parameter must be encoded as a parameter value, so its own query delimiters do not accidentally become delimiters for the outer API request. For example, a target like https://example.com/search?q=blue sky&sort=recent must have its embedded query characters encoded when placed in the API query string.

The Embed API token is calculated from the query string plus the account secret. If you build embed URLs yourself, make sure the token corresponds to the exact query string required by Thumbalizr’s documentation. Changes to parameter content, ordering, or encoding can make a locally generated token differ from the required one. These are request-level checks, not a diagnosis of your specific failure.

Compare your endpoint and parameter names with the current Thumbalizr API documentation.
Encode the target URL as a query parameter using your HTTP library or a URL-encoding function; do not concatenate an unescaped URL into a query string.
Regenerate the embed token from the exact query string and the account secret as the documentation specifies.
Check that the key and secret belong to the account you intend to use. Keep secrets private; do not paste them into public tickets, screenshots, or browser console snippets.
Retry with a simple public URL, then add your original URL and options back one at a time.

The source material does not enumerate every possible API error string, so use the returned error header and current documentation rather than guessing what an undocumented error means.

4. Check whether a plan limit explains the result

Thumbalizr’s published features page lists the free tier as 100 captures per month. It lists a fixed 1280×1024 browser viewport, screen-size captures rather than full-page captures, and a watermark for free accounts. These limits can explain quota exhaustion, a cropped-looking page, or a watermark. They do not explain every blank or failed capture.

Symptom	Plan-related possibility	How to distinguish it
No more captures are available	The free monthly allowance may be exhausted.	Check account usage and the current plan details in Thumbalizr.
Only the visible area appears	The free tier is listed as screen-size capture, not full page.	Check the selected capture size and the plan’s current feature list.
The image has a watermark	The free tier is listed with a watermark.	Confirm the account tier; do not assume Chrome added it.
Viewport is smaller or different than expected	The free tier is listed with a fixed 1280×1024 browser viewport.	Compare the output dimensions and selected options with the published plan features.

Plan features and pricing can change. Verify the current details on Thumbalizr’s [features and pricing page](https://thumbalizr.com/pricing/). The listed limits are product-plan details, not a universal explanation for screenshot failures.

5. Consider the service’s backend transition as context

Thumbalizr announced on 2026-04-08 that it was migrating screenshot rendering from Browshot to ScreenshotCenter in phases. The announcement says new accounts move first and existing accounts move in batches, and that existing integrations, API calls, embed codes, and settings should remain unchanged. It describes faster processing and fewer errors or timeouts as goals, and mentions a newer Firefox rendering option on the new backend.

This announcement is context, not an incident report. It does not establish that there is a current outage or that the transition caused your particular failure. If your issue began recently, note when it started and include the response status and error when contacting Thumbalizr.

6. Check Chrome only when the workflow points to Chrome

If Thumbalizr’s hosted website works in another browser but not Chrome, note the browser version, extensions, and whether the device is managed by an organization. Try an ordinary browser window with extensions disabled only if your organization’s policy allows it, and check Chrome’s site permissions and the developer tools Console and Network panels for a concrete blocked request or page error. A browser-side display problem is more plausible when Thumbalizr reports OK but Chrome cannot render or download the returned result.

If you use a separate Chrome extension

Chrome enterprise policies can restrict extensions that use the debugger API, including debugger attachment or screenshot capture under some managed-device and data-loss-prevention policies. This consideration applies to an extension using that API; it is not evidence that Thumbalizr’s hosted website or API uses it.

Check chrome://policy on a managed device and ask your administrator whether an applicable extension, host, debugger, or screenshot policy blocks the workflow.
Confirm that the extension is installed and enabled, and note its exact error. Extension developers should surface network timeouts and HTTP 400 or 500 responses clearly.
If you maintain the extension, verify the package and referenced files and handle failed network requests explicitly, following Chrome’s extension guidance.

Do not assume that clearing Chrome data, reinstalling Chrome, or changing extension settings will fix a hosted API capture. First establish that the problem is actually browser-side.

7. A compact diagnostic sequence

Identify the path: Thumbalizr website, API/embed, or a separate extension.
Copy the exact visible error; for API calls, record HTTP status plus both Thumbalizr headers.
If status is QUEUED, wait for processing. If FAILED, use the error header to guide request checks. If OK, investigate result delivery or Chrome rendering.
Verify URL encoding, parameter names, credentials, and embed token construction against current documentation.
Check monthly usage and whether capture size, viewport, or watermark matches the plan.
Compare with a simple public target and another browser, changing one factor at a time.
For a confirmed extension on a managed device, check applicable Chrome policies with the administrator.
When escalating, provide the workflow, timestamp, target domain, status/error, and steps to reproduce. Redact keys, secrets, cookies, and private URL parameters.

Or skip the browser setup

If you need a screenshot API instead, [ScreenshotNeo](https://screenshotneo.com) takes a website URL in one GET request and returns an image or PDF. Its [API documentation](https://screenshotneo.com/docs/) covers the request options. For a quick test, replace the example URL and key:

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

With 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)

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

ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up free and get 1,000 screenshots a month with no card.

FAQ

Is Thumbalizr a Chrome extension?

Thumbalizr is an online screenshot service with a web interface and API. A separate extension may be part of an individual workflow, but it should be identified separately.

Does an `OK` header guarantee Chrome will display the image?

It means Thumbalizr reports the capture completed. The browser still has to receive and display the result or load the embed correctly.

Does the migration announcement mean Thumbalizr is down?

No. The announcement describes a phased backend transition and says existing integrations should remain unchanged; it does not report a current outage.

What should I send support?

Send the workflow type, approximate time, target domain, HTTP status, Thumbalizr status and error headers, and reproducible steps. Remove secrets, cookies, and private query values first.