Multi-account isolation in an antidetect browser

Assign one profile to each account

For ongoing work, maintain a list connecting each account to its browser profile. Use names that identify the platform, store, client, or purpose. Check the startup URL and account details when creating the profile, then confirm the signed-in account on its first launch. Window position is an unreliable way to remember accounts after you reopen or rearrange them.

WGBrowser provides platform presets and device templates. Choose a template appropriate for the computer running the profile and reuse its saved fingerprint for routine work. Make changes when there is a specific configuration reason, then restart the profile to apply them. The fingerprint settings page explains the available controls.

• Group profiles by client, store, or responsibility so a teammate can find the intended account.
• Check similarly named profiles and record which account each one is meant to open.

Assign and check each profile's proxy

Give an ongoing account a clearly identified proxy record and check its actual exit IP periodically. An unchanged proxy host and port do not prove that the exit IP stayed the same. If the work requires a fixed exit, confirm that the proxy service supplies one and record any planned changes.

WGBrowser supports HTTP, HTTPS, and SOCKS5 proxies. Select a saved connection from the proxy library or enter a custom proxy for the profile. Follow the proxy setup guide to check the exit before signing in. For extraction sources, choose the extraction timing with the account's needs in mind: requesting a proxy on each launch does not establish a fixed exit IP.

Check time zone, language, and location

A proxy's display name does not establish the region that websites see. Check the detected exit IP, country or region, and time zone, then compare the profile's language and location settings. Repeat this check after creating a profile, changing its proxy, moving to another network, or using another computer. Previous results give you something concrete to compare.

In WGBrowser, Time zone, Language, and Location can use Follow IP, which applies values from the detected exit before the profile opens. Custom settings are also available. WebRTC can use Proxy only or Disabled. Run a browser fingerprint check inside the intended profile and compare its reported values with your settings. A test result describes the configuration the site observed.

Keep cookies and local storage with their account

Cookies, LocalStorage, and IndexedDB can all contribute to a website session. Once accounts have separate profiles, continue signing in and working within the corresponding profile. Do not use one account's cookies as a general starting file for other accounts on the same website. Check the source, destination, and cookie domains before importing.

Each WGBrowser profile uses an independent browser process and data directory. File imports, claimed shares, and cloud sync deliberately move selected data to a destination. The cookie import guide explains what a cookie file contains and when a storage snapshot is relevant.

If you copy an existing signed-in profile, treat that copy as a transfer or backup of the same account. A different profile name does not change the account inside its saved session. Open the website and check the displayed account before you continue.

Profile locks and account copies

When changing computers, continue with the original profile where possible. During a handoff, identify the profile the next person should use and ask the current user to close it. If several copies already exist, check their accounts and intended purposes so members do not unknowingly operate separate copies of the same session.

WGBrowser uses a profile lock to allow one device to open a given profile at a time. The lock applies to the profile, not to the account displayed inside a website. It cannot identify whether a different profile is signed in to the same account. A claimed share creates an independent copy; review profile sharing and keep that copy in your account list.

Assign team access by responsibility

Group profiles by the work members handle, then assign visible groups and the permissions they need. Someone doing daily store work may need different access from the person maintaining proxies or exporting profiles. After assignment, have the member check their profile list and verify the account name before working.

WGBrowser supports members, roles, group access, and permissions for actions such as creating or editing profiles, exporting, managing proxies, and running automation. See team collaboration for the access model. If you use window sync, check the main window and followers for the current task; account-specific text and verification codes still need individual attention.

• For a handoff, record the profile in use and any unfinished work.
• Close the profile normally and wait for sync to finish before the next person opens it.

Check profiles after a move or connection failure

Before switching computers, confirm that the required sync options are enabled. Cookies sync as they change; LocalStorage and IndexedDB upload in a snapshot after the profile closes. On the next computer, open the original profile and check the account, exit IP, and website session. The cloud sync page covers the different upload timings.

Record the actual symptom when something fails. For a connection failure, check the proxy and authentication. For an expired login, inspect the session and website prompts. If a setting is wrong, change that specific setting and check again. Changing the fingerprint, exit, and cookies together makes the cause harder to identify. Update your account record after resolving the issue.

FAQ