BitBrowser logo
Anti-detect browser

BitBrowser

An antidetect browser for running many accounts, each in its own profile. Ten profiles free.

BitBrowser is an antidetect browser that gives every account its own browser profile, with its own fingerprint and its own cookies, local storage and cache, so one person or a team can keep many accounts apart on one computer. It adds RPA automation and a local API, window synchronisation, and groups with team permissions, and it runs on Windows and Mac.

About BitBrowser

BitBrowser is an antidetect browser for managing many accounts. Each account runs in its own profile with its own fingerprint, covering user agent, language, WebGL, canvas, fonts, WebRTC, time zone and DNS, and with cookies, local storage and cache kept apart from every other profile. Teams share the same profiles through groups and permissions. The free plan includes ten profiles.

What it does

  • Isolated browser profiles

    Each profile keeps its own fingerprint, cookies, local storage and cache, apart from every other profile.

  • RPA automation and a local API

    Repeated work runs as an RPA task inside the browser, or through the local API from your own code.

  • Window synchronisation

    Act once and the same action is repeated across the open windows.

  • Groups and team permissions

    Profiles are filed into groups and shared with the team under permissions, so people see only what they should.

Who it is for

Affiliate and social media marketers, e-commerce sellers, ad verification teams, and developers who automate repeated work in a browser.

Good to know

  • The free plan includes ten profiles, enough to test a proxy setup on both sides before paying for either.
  • Test the proxy in the profile before you rely on it: Check Proxy in the profile form reports the exit it sees.

Summarised from BitBrowser's own website, checked on 14 October 2026. Plans and prices change; see their site for the current ones.

Use SocksNode in BitBrowser

Four steps. A sticky port keeps each profile on one address.

  1. 1

    In BitBrowser, create or open a browser profile and go to its proxy settings.

  2. 2

    Choose HTTP or SOCKS5. Host: global.socksnode.com. Port 10000 (HTTP) or 12000 (SOCKS5) for a sticky session.

  3. 3

    Paste your proxy username and password from the SocksNode dashboard. Add the location to the username, for example USERNAME-country-us-city-losangeles.

  4. 4

    Run the proxy check in BitBrowser, then launch the profile.

BitBrowser proxy settings

Host
global.socksnode.com
Port
10000 (HTTP) · 12000 (SOCKS5)
Username
USERNAME-country-us-city-losangeles
Password
••••••••

Ports 9000 (HTTP) and 11000 (SOCKS5) give a new IP on every request.

Why BitBrowser and SocksNode work well together

  • A proxy for every profile

    In a profile's proxy settings, pick Custom Proxy as the proxy method and socks5, http or https as the proxy type, then fill in Host, Port, Username and Password. Every profile can sit on its own SocksNode address.

  • Sticky ports for signed-in profiles

    Ports 10000 (HTTP) and 12000 (SOCKS5) hold one address for a session, which is what a profile that stays signed in needs.

  • A whole list in one import

    Batch Import reads proxies as Host:Port:Username:Password, the shape a SocksNode login already has, so a hundred profiles can be created on a hundred different addresses in one go.

Example: one profile on a Los Angeles address

A profile that should look like a visitor from Los Angeles, from creation to check.

  1. 1

    In BitBrowser, go to Browsers and click Add.

  2. 2

    Under the proxy settings, choose Custom Proxy, set the proxy type to socks5, host global.socksnode.com, port 12000.

  3. 3

    Username: USERNAME-country-us-city-losangeles-session-a8bd381f-lifetime-30, with your password from the SocksNode dashboard.

  4. 4

    Click Check Proxy, save the profile, then launch it and confirm the location.

From BitBrowser

BitBrowser's own SocksNode guide

BitBrowser published a step-by-step guide, in Vietnamese, to running SocksNode inside its profiles. Read it next to these steps.

Open BitBrowser's guide

Questions about BitBrowser and SocksNode

Which port should I use for a profile?

Use 10000 (HTTP) or 12000 (SOCKS5). Both hold one address for the length of a session. Ports 9000 and 11000 change the address on every request, which suits scraping better than a signed-in profile. A -session- part does not belong on those two ports.

How do I choose the country?

Add it to the username: USERNAME-country-us. A city narrows it further, for example USERNAME-country-us-city-losangeles. On the sticky ports 10000 and 12000, also add a session part: USERNAME-country-us-session-a8bd381f-lifetime-30.

Can I set up many profiles at once?

Yes. In Browsers, use Batch Import, fill the template and write each proxy as Host:Port:Username:Password with socks5 as the type. Each row carries its own username, so each profile can take its own country and its own session.

Other partners

Build a tool for proxy users?

List your product here and link to us from yours. Send us your site and a line on what it does.

Become a partner