Independent profile data
BitBrowser says each profile keeps its own cookies, cache, and extensions. Fingerprint controls also cover device, network, and rendering signals.
BitBrowser creates independent browser profiles with separate cookies, cache, extensions, fingerprint settings, and proxy configuration. Set a proxy for each profile, test the connection in the app, and manage larger workflows with batch tools, RPA, and a Local API.
Partner disclosure: PreProx may earn a commission if you use the BitBrowser link. BitBrowser is a separate product with its own pricing, terms, and support.
BitBrowser documents profile-level controls for cookies, cache, extensions, network settings, and rendering fingerprints such as Canvas and WebGL. Its other tools cover batch profile management, no-code RPA, a Local API, and permission-based team access.
BitBrowser says each profile keeps its own cookies, cache, and extensions. Fingerprint controls also cover device, network, and rendering signals.
Enter a custom HTTP, HTTPS, SOCKS5, or SSH proxy with host, port, and optional credentials, then run BitBrowser's connection test.
Create or import profiles in bulk, then organize them with groups and tags for easier account management.
Build repeatable browser tasks with drag-and-drop steps or templates, and schedule runs from BitBrowser's RPA tool.
Control profiles and browser windows through the Local API. BitBrowser documents integration with Selenium and Puppeteer.
Share browser profiles through sub-accounts, set member permissions, and review activity records for team operations.
BitBrowser stores the profile and its browser settings; its proxy field sets the network route for that profile. A PreProx endpoint is a separate service. Match its protocol and authentication details to BitBrowser's custom proxy options, then test the connection.
Set up separate browser data and fingerprint options, assign a proxy to the profile, and manage profiles with BitBrowser's batch and team tools.
Select a PreProx product that fits your location, session, and traffic needs, then verify the endpoint in your browser setup.
A BitBrowser profile does not include a PreProx subscription. Check the protocol and credentials of the specific PreProx endpoint you choose.
BitBrowser's custom proxy guide shows where to enter an endpoint. Its proxy settings page documents the in-app connection test.
In BitBrowser, open Browsers and choose Add browser to create a profile.
Under Custom Proxy Method, select the protocol that matches your PreProx endpoint: HTTP, HTTPS, SOCKS5, or SSH.
Enter the endpoint host and port, plus a username and password if the connection requires them.
Run BitBrowser's proxy test, launch the profile, and use PreProx's IP check to confirm the visible address.
BitBrowser highlights e-commerce, social media, advertising, SEO, and team operations. The practical value is in keeping profiles, permissions, and repeatable work organized.
Give each storefront or marketplace account its own profile, then group profiles by client or project.
Keep client sessions in distinct profiles while tracking the profile assigned to each account.
Use separate profiles and repeatable browser tasks when checking campaigns or researching different markets.
Use sub-accounts, permissions, and profile sharing when more than one person manages the same project.
Answers drawn from BitBrowser's product pages and help center. You can check the official sources below.
We checked these BitBrowser pages on October 3, 2026. Features and plan limits can change, so confirm the current details before you sign up.
Check BitBrowser's current plans and documentation before signing up. If you need help selecting a PreProx proxy product, use our general Contact Us page.