How to Test Website Localization with a Cloud Browser
TL;DR
Browser localization testing checks what the user sees under a particular egress location, language, timezone, and application state.
Proxy Country, Browser Language, and Timezone are separate Nstdata settings. Choose them before launch and record each one.
Follow IP applies startup alignment. Verify the actual exit and page-visible settings when a result depends on region.
Compare the browser's language and timezone with the application's visible language, formatting, currency, and route.
Change one signal at a time to identify whether the server, browser, or account preference controls the outcome.
Validate the observed result and end the managed session independently of the browser client's disconnect.
What does browser localization testing verify?
Browser localization testing verifies that an authorized application displays the correct content and formatting for a defined user context. This can include localized copy, date formats, currency, routing, and regional feature availability. The test has to record which signals the site uses. An apparent German network exit and a German browser language are independent inputs, and a profile language preference can override either. Nstdata Cloud Browser.
A developer can prove the test reached its target by asserting a visible localized heading and the selected page language. A browser's locale alone proves configuration, not the UI actually served to the user. If an application offers a user-controlled language switch, verify it separately from its first-visit heuristics. The Playwright emulation guide documents locale and timezone settings for local contexts.
How do proxy country, language, and timezone affect a test?
Proxy country affects network egress, browser language expresses a preference, and timezone shapes browser-side date and time calculations. A site may apply its own rules by checking an account setting, cookie, URL, header, or regional backend. Make the priority order part of your application test contract.
Trusted region check or authorized server-side observation
Routing and geolocation databases can disagree
Browser language
navigator.language and server-observed language preference
Profile settings and the application can override preference
Browser timezone
Intl.DateTimeFormat().resolvedOptions().timeZone
Browser configuration and proxy egress are separate
Page locale
Document lang plus an observable heading
User settings, URL route, or fallback policy
Currency and date display
Known fixture price and fixed timestamp
Locale, market catalog, timezone, and app rules interact
When the workspace supports the setting, Follow IP can align language and timezone at launch. It does not continuously update those fields as the exit changes. Selecting an exit country also supplies no guarantee of a dedicated fixed address. For a reproducible locale-only experiment, use Custom and hold the proxy setting constant across sessions. See the Cloud Browser configuration guide.
How do you build a diagnostic test matrix?
Build a small matrix that changes one input at a time and records the rendered outcome. Start by documenting the expected locale negotiation rule. If your app selects country from an account, keep that account setting constant while evaluating browser language. If it uses regional availability, keep browser settings fixed while varying proxy geography.
Case
Egress
Language and timezone
What to assert
Reference
A permitted US exit
en-US and America/New_York
Expected English copy and known local display
Language variation
Same country as reference
de-DE with the reference timezone
German copy if the application follows browser preference
Timezone variation
Same country as reference
Reference language with Europe/Berlin
Fixed timestamp rendered according to app requirements
Regional variation
Another permitted available country
Same language and timezone as reference
Intended regional feature or catalog response
Account override
Same config as reference
Same config as reference
Saved user preference takes effect if specified
Do not choose a country for which you lack an authorized case. Maintain independent expected values for regional price and language rather than inferring currency from a translation. For date tests, select a stable input timestamp and record the calendar date, time and zone that the feature should display. Add a daylight-saving boundary case only when the application contract requires one. Intl.DateTimeFormat reference.
How do you configure and verify an Nstdata Cloud Browser session?
Configure the network and browser preferences before launch, then verify every signal that determines the expected user experience.
Step 1. Select network egress
Open Cloud Browser → Playground in the intended workspace. Select an available Proxy Country. Use the same country across locale-only comparisons. If testing geography, confirm the effective exit through the authorized server or a trusted region checker.
Step 2. Set a custom browser environment
Open the browser environment settings and set Browser Language and Timezone under Custom where applicable. Use a BCP 47 language tag and an IANA timezone name. Current options determine which values are supported. The dashboard uses a single language input. An API integration can use fingerprint.languages for an ordered list with localeMode: "custom". Query GET /api/v1/cloud-browser/sessions/options for actual options and inspect any effective-configuration warnings.
[Screenshot: Browser Language and Timezone configuration before launch.]
Step 3. Launch and start the test fixture
Click Launch Browser and wait for Running if you are doing a managed test. For a local run, use Node.js 22.12 or later, install playwright-core@1.65.1 and run npx playwright-core install chromium. Save fixture.mjs and run node fixture.mjs. The fixture chooses German output when the request's language preference starts with de. It binds to loopback for a local test. Use an approved reachable deployment for a managed test.
Save the shared modules and locale.mjs. Run TARGET_URL=http://127.0.0.1:4173/locale node locale.mjs for the English fixture. For the German case set EXPECT_LANGUAGE=de-DE, EXPECT_TIMEZONE=Europe/Berlin, EXPECT_PAGE_LANGUAGE=de and EXPECT_HEADING="Regionales Beispiel" on the same command. This local branch uses a fresh Playwright context with explicit emulation. The managed branch reads the existing remote environment and requires NSTDATA_API_KEY and NSTDATA_SESSION_ID for your own workspace. Avoid setting runtime overrides when measuring the provider configuration. See connecting Playwright over CDP.
const root ='https://api.nstdata.io/api/v1/cloud-browser';exportasyncfunctionapi(method, path, body){const key = process.env.NSTDATA_API_KEY;if(!key)thrownewError('Set NSTDATA_API_KEY');const headers ={'x-api-key': key };if(process.env.NSTDATA_TEAM_ID) headers['x-team-id']= process.env.NSTDATA_TEAM_ID;if(body) headers['content-type']='application/json';let response;try{ response =awaitfetch(root + path,{ method, headers,redirect:'error',body: body ?JSON.stringify(body):undefined,signal:AbortSignal.timeout(20_000),});}catch{throwObject.assign(newError('API transport failed; reconcile the original operation'),{retryable:true});}const retryable = response.status===429|| response.status>=500;let result;try{ result =await response.json();}catch{throwObject.assign(newError('Invalid API JSON'),{ retryable });}if(!response.ok|| result.err===true|| result.success===false){throwObject.assign(newError(`Cloud Browser API HTTP ${response.status}`),{ retryable });}if(!result.data)thrownewError('Missing API data');return result.data;}exportasyncfunctionconnection(id){if(!id)thrownewError('Set NSTDATA_SESSION_ID');const path =`/sessions/${encodeURIComponent(id)}`;const session =awaitapi('GET', path);if(session.state!=='ready')thrownewError(`Session is ${session.state}, not ready`);const c =awaitapi('POST', path +'/automation-credentials');if(c.sessionId!== id ||!c.headerName||!c.accessToken||!(Date.parse(c.expiresAt)>Date.now())||newURL(c.cdpUrl).protocol!=='wss:'){thrownewError('Invalid or expired CDP credentials');}return{endpoint: c.cdpUrl,headers:{[c.headerName]: c.headerName.toLowerCase()==='authorization'?`Bearer ${c.accessToken}`: c.accessToken},};}exportasyncfunctionendpoint(){// An isolated local CDP endpoint can test the client without managed credentials.if(process.env.LOCAL_CDP_URL){const url =newURL(process.env.LOCAL_CDP_URL);if(!['127.0.0.1','localhost','[::1]'].includes(url.hostname)){thrownewError('LOCAL_CDP_URL must use loopback');}return{endpoint: url.href,headers:{}};}returnconnection(process.env.NSTDATA_SESSION_ID);}
The local English and German cases assert their language, timezone, document language and text. In staging, add a visible price label and a date with a fixed expected value. Check those user-visible values with role or text locators. A test can pass configuration checks and still reveal missing translations. Playwright assertions documentation.
Step 5. Record the case and stop the browser
Save the configured and observed values beside the expected heading and a safe test case ID. Stop the managed session from the dashboard after the test. Record task acceptance and confirmed shutdown separately. See Cloud Browser session management.
Why can the page still display the wrong locale?
A page can display an unexpected locale when another signal takes precedence or when content has not loaded. Check whether the account or cookie retained a language from an earlier test. Inspect the intended route and final navigation. Verify the app's translations independently of browser preferences.
If browser language is correct and the page uses the wrong language, compare app state, observed request preferences, and the expected server priority rule.
If timezone is correct and dates differ, verify the fixed source timestamp, formatting options, and which time display the assertion reads.
If region appears incorrect, record the selected country and observe actual routing through your approved validation endpoint.
If only some strings are translated, check bundle or data response failures and fallback text. See browser automation debugging.
How does Nstdata Cloud Browser fit regional QA?
Nstdata Cloud Browser provides managed cloud browsers for browser automation and AI agents. Its prelaunch settings let a QA worker make egress and browser preferences explicit. Live View can help reproduce a user-visible discrepancy in the same running browser. CDP lets your automation assert output from that environment. The application still defines which language, date, price and route a user receives.
Integrated proxy routing. Select a supported exit country without wiring a separate gateway for the built-in path.
Browser preferences. Set language and timezone separately. Verify the observed settings and exact app outcome.
Live diagnostics. Inspect the selected page, console, and network when a locale fallback needs investigation.
A localization test is ready when its configuration, observed browser signals, fixture revision, and expected output can be reproduced. Keep the reference and one changed variable beside the evidence. Add targeted cases for new app rules before expanding the matrix. The Cloud Browser automation documentation provides scripts for integrating the managed session with an existing test runner.