DocsProfile Managementbrowser_download_profile

browser_download_profile

browser_download_profile

Download a saved profile file from the server. Takes the profile_name returned by browser_save_profile and returns the profile content as base64-encoded JSON. The same profile can be downloaded regardless of which context_id was used to save it.

When to use browser_download_profile

Use browser_download_profile when you need to persist and reuse browser identities and fingerprints. It is part of Owl Browser's Profile Management 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

123456789101112
import asyncio
from owl_browser import OwlBrowser, RemoteConfig
# Async usage
async with OwlBrowser(config) as browser:
context = await browser.create_context()
context_id = context["context_id"]
await browser.download_profile(
context_id=context_id,
profile_name="value"
)

Parameters

Required

context_idstringrequired

The unique identifier of the browser context (e.g., 'ctx_000001')

profile_namestringrequired

Name of the profile file to download (as returned by browser_save_profile). Example: 'shopping_account.json'. The .json extension is optional and will be added if missing. Returns base64-encoded profile content.

Response

Returns a JSON object with the operation result.

{
  "success": true,
  "result": <value>
}

Frequently Asked Questions

What does browser_download_profile do?

Download a saved profile file from the server. Takes the profile_name returned by browser_save_profile and returns the profile content as base64-encoded JSON. The same profile can be downloaded regardless of which context_id was used to save it. It belongs to Owl Browser's Profile Management category and is available through the REST API, the Python SDK (browser.download_profile()), the Node.js SDK, and the MCP server.

What parameters does browser_download_profile accept?

browser_download_profile accepts 2 required parameters (context_id, profile_name) and 0 optional parameters. All parameters are sent as JSON in a POST request to /api/execute/browser_download_profile.

Is browser_download_profile detectable by anti-bot systems like Cloudflare or DataDome?

No. browser_download_profile 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_create_profile

Create a new browser profile with randomized fingerprints (user agent, screen size, WebGL, Canvas, etc.). Returns the profile JSON that can be saved for later use. Each profile represents a unique browser identity.

browser_load_profile

Load a saved browser profile from a JSON file into an existing context. Applies fingerprints, cookies, and settings from the profile. Use for maintaining consistent browser identity across sessions.

browser_save_profile

Save the current context state (fingerprints, cookies, settings) to a profile file on the server. Takes a profile_name (not path) and returns the filename. Use browser_download_profile to retrieve the file.

browser_get_profile

Get the current profile state for the context as JSON. Includes fingerprints, current cookies, and all settings. Useful for inspecting profile details.

browser_create_context

Create 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_navigate

Navigate 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.

Browse the full Owl Browser API reference or get started with the Python SDK and Node.js SDK.