Can Thumbalizr Capture a Webpage in a Specific Language?

Short answer: Thumbalizr’s published API documentation does not list a language or Accept-Language option. It documents a country option for the capture browser’s location, currently mentioning the US and Germany. That controls browser geography; it does not guarantee a particular page language. Thumbalizr’s API documentation is the source for its published options.

If the target site has a URL that selects its language, try capturing that exact URL. This is a site-dependent workaround, not a documented Thumbalizr guarantee. When you need to send an explicit Accept-Language request header, use a capture service that documents that control.

1. How a website chooses its language

A page’s language can depend on several signals. The target site decides which ones it uses:

• URL: The locale may appear in a path such as /fr/, a subdomain, or a query parameter. This is usually the easiest option to pass to a screenshot API.
• Request header: The site may inspect Accept-Language to choose a translation.
• Cookie or account preference: The site may remember a visitor’s language choice or read a signed-in account preference.
• Browser or IP location: The site may infer a default from the browser’s locale or network location. The target site controls this behavior.
• Client-side selection: JavaScript may load or switch translations after the initial page response.

A screenshot service can only select the language through controls it exposes and the behavior the target site supports. Changing the capture browser’s country is not the same as setting a language header, cookie, or account preference.

2. Try a language-specific URL with Thumbalizr

1. Open the page in a regular browser and select the desired language.
2. Check whether the address changes to a locale-specific URL, such as a localized path or query parameter.
3. Open that URL in a private browser window to confirm it still shows the desired language without relying on a saved cookie or account session.
4. Submit the same URL as Thumbalizr’s target URL and inspect the resulting image.

Thumbalizr’s API requires a target url, so submitting a localized URL is a reasonable first attempt. Whether it works depends on how the particular website serves translations. The reviewed public API documentation does not promise that locale-specific URLs will work for every site.

The country option describes where the capture browser is located. Thumbalizr’s documentation mentions the US and Germany and advises contacting the service about other countries. Do not treat this option as a documented way to set Accept-Language or force a page translation.

3. When the URL workaround is not enough

If the page’s language depends on a request header, cookie, account preference, or JavaScript state, a localized URL may not be sufficient. The Thumbalizr API options reviewed here do not document a custom request-header or language parameter. Its public pages also do not resolve whether a support-only or account-specific mechanism exists, so verify directly with Thumbalizr if that distinction matters to your setup.

For explicit header control, Screenshot Machine’s API documentation describes an accept-language parameter and gives en-US as an example. See its API documentation and check the current service details before depending on the feature. The available research establishes the documented parameter, but not current pricing, reliability for a particular target, or plan availability.

Choose based on the site’s language-selection behavior: use Thumbalizr when the target URL itself selects the locale; use a documented header control when the target requires Accept-Language. In either case, test against the actual page and confirm the resulting screenshot rather than assuming the requested locale was applied.

4. Troubleshooting language mismatches

Symptom	Likely cause	What to try
The screenshot is in the default language.	The site ignores the URL locale or chooses language through another signal.	Open the same URL in a private browser window. If it reverts there too, the URL alone does not select the language.
The localized URL works in your browser but not in the capture.	Your browser may have a saved cookie, account preference, or client-side state that the capture does not share.	Test the URL without signing in and without saved site data. Identify which state is necessary; do not assume the capture service has it.
Changing the capture country has no effect on the language.	Country/location and language negotiation are separate controls, and the site may not infer language from location.	Use a URL that selects the locale or a service that documents the required language header.
The page starts in one language and changes after loading.	Client-side code may switch language after the initial document loads.	Check whether the screenshot service supports an appropriate wait condition. Confirm the final capture shows the translated content.
A page requires a remembered preference or login.	The site relies on a cookie or authenticated account state.	Check whether the capture API supports the needed cookies or authentication, and use only an authorized account. The reviewed Thumbalizr language documentation does not establish such a control.

5. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. For a page whose language is selected by its URL, pass that localized URL to the API. ScreenshotNeo’s documented options also include custom headers and cookies; see the ScreenshotNeo API documentation for configuration. A header or cookie only helps when the target site uses it to select language.

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

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com/fr/"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://example.com/fr/',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

Replace the example URL with the target’s language-specific URL. These examples use the API’s documented request pattern; configure additional options from the docs when the site requires them.

• Cookie banners, newsletter popups, and chat widgets are removed before the shot; each cleanup step can be turned off.
• Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers say which page verdict and billing status applied.
• An MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf.
• 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000 screenshots.

Sign up free for ScreenshotNeo and get 1,000 screenshots a month with no card.

6. Reliability and cost considerations

Locale selection is controlled by the target website, so a successful screenshot request does not by itself prove that the intended language appeared. For a production workflow, capture a known localized page and verify a visible language marker or a representative translated string in the output. If language correctness is critical, treat a mismatch as a failed capture in your own workflow.

Screenshot service plans and features can change. Thumbalizr’s reviewed pages describe free and paid tiers, but this guide does not quote prices or limits. Check each service’s current documentation and plan before selecting it for recurring captures.

7. FAQ

Does Thumbalizr support an Accept-Language parameter?

The reviewed public API documentation does not list one. It documents a browser country option instead.

Will setting Thumbalizr’s country to Germany make a page German?

Not necessarily. The country option describes browser location; the target site determines whether location affects its language.

Can I capture a language selected by a cookie?

Only if the capture workflow can provide the cookie the site expects. The reviewed Thumbalizr documentation does not list a cookie control for this purpose.

What should I test before scheduling captures?

Confirm the exact target URL returns the intended language without relying on your normal browser’s saved state, then inspect a sample capture before automating it.