browser_set_timezone
Set or override the timezone for an existing browser context at runtime. Useful for adjusting timezone after detecting proxy exit IP location. The timezone is immediately applied to all frames in the context.
When to use browser_set_timezone
Use browser_set_timezone when you need to give a session a realistic geographic and temporal context. It is part of Owl Browser's Demographics & Context toolset and runs inside a self-hosted, source-level stealth engine, so every call inherits the same undetectable browser fingerprint as the rest of your automation — no separate anti-detect setup required.
Usage Example
Parameters
Required
context_idstringrequiredThe unique identifier of the browser context (e.g., 'ctx_000001')
timezonestringrequiredIANA timezone format (e.g., 'America/New_York', 'Europe/London', 'Asia/Tokyo'). This overrides any previously set timezone including VM profile defaults. Must contain '/' and be between 5-50 characters.
Response
Returns a JSON object with the operation result.
{
"success": true,
"result": <value>
}Frequently Asked Questions
What does browser_set_timezone do?
Set or override the timezone for an existing browser context at runtime. Useful for adjusting timezone after detecting proxy exit IP location. The timezone is immediately applied to all frames in the context. It belongs to Owl Browser's Demographics & Context category and is available through the REST API, the Python SDK (browser.set_timezone()), the Node.js SDK, and the MCP server.
What parameters does browser_set_timezone accept?
browser_set_timezone accepts 2 required parameters (context_id, timezone) and 0 optional parameters. All parameters are sent as JSON in a POST request to /api/execute/browser_set_timezone.
Is browser_set_timezone detectable by anti-bot systems like Cloudflare or DataDome?
No. browser_set_timezone executes inside Owl Browser's Chromium engine, which applies fingerprint spoofing at the C++ source level rather than through JavaScript patches. Every tool call shares the same consistent, human-like fingerprint, so anti-bot systems such as Cloudflare, DataDome, and Akamai see an ordinary browser.
Related Tools
browser_get_demographicsGet comprehensive user demographics and context based on IP geolocation. Returns location, timezone, weather, date/time, and locale information. Useful for location-aware operations and personalizing interactions.
browser_get_locationGet user's current geographic location based on IP address. Returns city, country, coordinates (lat/lon), and timezone. Uses GeoIP database for lookup.
browser_get_datetimeGet current date and time information including date, time, day of week, and timezone. Reflects the server's local time.
browser_get_weatherGet current weather conditions for the user's detected location. Returns temperature, conditions, humidity, and other weather data.
browser_create_contextCreate a new isolated browser context with its own cookies, storage, and optional proxy configuration. Each context acts as an independent browser session. Use this to create multiple isolated browsing sessions, configure proxy/Tor connections, load browser profiles with saved fingerprints, and enable/disable LLM features. Returns a context_id to use with other browser tools.
browser_navigateNavigate the browser to a specified URL. This is a non-blocking operation that starts navigation and returns immediately. Use browser_wait_for_network_idle or browser_wait_for_selector to wait for the page to fully load. Supports HTTP, HTTPS, file, and data URLs. When wait_until is set (load, networkidle, fullscroll, domcontentloaded) and the page declares WebMCP tools, the response includes a webmcp_tools array containing the full tool definitions (name, description, inputSchema). Use browser_webmcp_call_tool to execute any of these tools directly.