Profiles define the browser identity and protected environment used by BotBrowser. Use a profile package that matches the BotBrowser major version.
| Channel | Release line | Access |
|---|---|---|
| stable | v150-v151 subscription profiles; v148-v149 legacy demos | BotBrowser 150 and newer packages are available through subscription or support. |
| canary | None published | Reserved for explicitly published pre-stable packages. |
| archive | v135-v147 | Older public demo packages outside the current support window. |
BotBrowser 150 and newer profile packages are not published as public demos. Contact support@botbrowser.io or @botbrowser_support for access.
The BotBrowser binary and profile package must use the same major version. A v151 binary requires a v151 profile package.
A profile represents a reusable hardware and browser model. It is not a browser process, account, user-data-dir, or one-time slot. For example, an M5 Max-class profile describes one hardware model and its browser-visible characteristics. Multiple real machines can share the same model characteristics, and using the profile does not bind it to the first launch.
The profile supplies:
| Area | Examples |
|---|---|
| Browser | Browser family, version, Client Hints |
| Display | Screen, window, pixel ratio, color depth |
| Hardware | CPU, memory, graphics properties |
| Rendering | Fonts, Canvas, WebGL, WebGPU, audio |
| Platform | OS and device behavior |
| Media | Codecs, media devices, speech voices |
The same .enc file can be used by multiple browser processes and BrowserContexts. Use another profile only when a different base hardware or browser model is required.
The same profile can be passed to multiple launches. Each browser process uses a different user-data-dir. See Same Profile, Multiple Browser Processes for commands and session configuration.
Both browsers expose the same base hardware model. Their storage and session state remain independent because they use different data directories. Proxy, timezone, locale, cookies, history, and other session settings can also differ per browser.
Use the profile for the base model and CLI flags for session-specific settings. For multiple identities inside one browser process, see Per-Context Fingerprint.
| Profile type | Use |
|---|---|
| Legacy demo | Evaluation on published Chrome 149 and earlier lines. No headless, automation framework, or extension support. |
| Subscription | Current release lines, headless workflows, automation frameworks, extensions, and licensed capabilities. |
- Profile Management: launch, version matching, profile types, and troubleshooting
- CLI Flag Directory: per-session configuration
- Profile Configuration: fields for configurable subscription packages
- Per-Context Fingerprint: multiple isolated identities in one browser process
- Playwright and Puppeteer: framework setup
Legal Disclaimer & Terms of Use • Responsible Use Guidelines. BotBrowser is for authorized fingerprint protection and privacy research only.