Antidetect browser cloud sync

When cookies, storage, and tabs sync

Cookies, including session cookies, sync after changes, with a final upload when you close the profile. Open tabs sync as a list of web addresses so they can reopen next time. Fingerprint settings, the proxy assignment, and sync options update when you save changes to the profile configuration.

LocalStorage, IndexedDB, extension data, bookmarks, and history use storage snapshots. After the profile closes, the client packages the selected data and uploads it. Before the next launch, it checks for a newer cloud snapshot and downloads it when needed. These storage types do not upload after every individual change.

Select the data you need for each profile. A website may use both cookies and local storage for a session, so the presence of a cookie alone does not establish that all required data arrived. Finish your work, close normally, and wait for sync before switching computers.

Open the same profile on another computer

Only one device can have a given profile open at a time. If the original computer or a teammate still has it open, the client shows occupancy information. Arrange the handoff before starting on the other device; team management explains member access and profile occupancy.

1. On the original computer, check the profile's sync selections. Complete the current website operation, then close the profile normally.
2. Wait for the final cookie upload and selected storage upload to finish. Sign in to the same account on the other computer.
3. Find and open the original browser profile. The client retrieves its cookies and checks the cloud storage version before launch.
4. Review the restored tabs, account identity, proxy exit IP, and website sign-in state. Complete any verification the website requests before continuing.

Choose sync data for each profile

You can turn off sync separately for a profile and keep the corresponding browsing data on that computer. In the profile's Sync settings, the English options include Cookies, Open tabs, Local storage, IndexedDB, Extension data, Bookmarks, and History. Check the selected items against the website data you need to restore.

Turning sync off means new local browsing data is not automatically available on another computer. The saved profile configuration and the website's session data are separate parts of the handoff. If you later need to move the profile, choose sync or an appropriate export and verify the data at the destination.

Storage sync availability and cloud storage capacity depend on your plan. Review plans and pricing before relying on storage snapshots, sharing, or exporting. Profile capacity alone does not tell you whether the plan includes the storage features required by your workflow.

Send a profile with a share code

Select profiles in Profiles and choose Share. Set the contents, validity period, and claim limit, then choose Create code. The recipient opens Profiles → Claim share, pastes the code, and previews the profiles and included data before choosing a destination group.

A claim copies the source profile's state at the time of the claim. Storage comes from the latest uploaded snapshot after a normal close, so close and finish syncing before the recipient claims it. Creating profiles requires the recipient's permission and available profile capacity; copying storage also requires storage sync and enough cloud space.

The recipient receives an independent copy. Later edits do not keep both teams' copies in sync. Share history lets you review claims and revoke a code, but revocation only prevents future claims. For the content choices and recipient checks, read browser profile sharing.

Save a .fgbx backup

Use Export and choose Full backup to save a .fgbx file. Depending on your selections, it can include the fingerprint, cookies, local storage snapshot, platform credentials and 2FA secret, and saved site passwords. Encryption is selected by default when the contents include sign-in data or passwords; importing an encrypted file requires its password.

Close the source profile and finish syncing before export. Review the export result for storage download failures or omitted contents. The file contains the data saved during export; future activity in the source profile does not update an existing backup.

JSON preserves complete configuration without local storage. CSV contains common fields without the full fingerprint. File imports currently do not restore the last open tabs, so reopen the required pages afterward. For supported source formats, see BitBrowser migration and AdsPower migration.

Receive a profile in the Lite edition

Someone who only needs profiles supplied by another person can use the Lite edition without a client account. The sender must enable Allow Lite claims for a share code, or provide a .fgbx file with valid profile credentials. After receipt, the profile and later browsing data are stored on the recipient's computer.

Lite does not provide cloud sync or team collaboration. The sender cannot recall a copy already claimed on that computer. Use the full edition when you need to continue using your own profile across devices, and check the Lite edition's scope before choosing how to deliver a profile.

• Confirm the account, profile name, proxy, and selected credentials before handing over data.
• Check the actual exit IP and website session after opening the received profile.
• Treat a successful copy as a data transfer, then verify that the website accepts the restored session.

FAQ