Antidetect browser without sign-up: Lite edition

Receive prepared browser profiles

Lite fits a handoff where someone configures a browser profile and a colleague or client uses the copy locally. The recipient does not have to create a client team or rebuild the fingerprint settings. Check the sender, profile and business account so that the received copy belongs to the intended assignment.

You can rename profiles, edit notes, view included usernames, passwords and two-step verification codes, and open or close profiles individually or in a batch. Search names, notes, senders or proxy addresses when organizing received profiles. Details records where each profile came from.

The copy uses the configuration saved when you claim or import it. Later changes by the sender do not update it, and your browsing activity stays local. For people taking turns maintaining a shared profile, review team collaboration before choosing the handoff method.

Claim profiles with a share code

The sender must select Allow Lite claims when creating a code in the full edition. It is not enabled by default for ordinary share codes. Expired, exhausted or revoked codes cannot be used; ask the sender to resolve the reported condition. The sender also chooses which data the share includes.

First use requires an internet connection to verify profile sources, and claiming a code requires a server connection. The preview identifies the sender and profiles and indicates whether login data is included. A successful preview is only the first step: check the final saved and skipped counts after installation.

1. Open Lite, choose Claim profiles, paste the Share code and click Preview profiles.
2. Check the list, select the profiles and choose whether to download local storage. For a profile from the same source already on this computer, choose Save a copy, Replace or Skip.
3. Wait for verification, download, unpacking and saving to finish. Review the result, then use Set proxies if a received profile needs a proxy before opening.

Import an .fgbx file

Lite imports .fgbx files exported by the full edition, and each accepted profile must contain a valid profile credential. It does not accept ordinary JSON, CSV or an archive whose profiles lack those credentials. A matching file extension alone does not establish that the profiles can be installed.

Ask the sender to check that the export result says the file can also be imported in Lite. Choose Import file or drag the file into the window. If it is encrypted, enter File password using the password set during export. Check the profile list and export time before continuing.

Profiles with missing or invalid credentials, or a changed fingerprint, are skipped. Valid entries can still install when another entry fails. Review each reason in a partial result and have the sender prepare replacement entries where needed. See profile sharing and transfer for the sender's options.

Assign proxies and check the exit IP

Choose Set proxy on a profile row and enter the type, host, port and any required username and password. To assign proxies in a batch, select profiles, choose Set proxies and paste one proxy per line. Review Profile to proxy assignment before saving so that each account receives its intended connection.

Common host, port and credential formats are supported, including proxy URLs with a protocol. Check each proxy before saving to see which connections pass or fail. Failed proxies can still be saved, so a successful save does not mean the network connection works.

Fixed proxies and extraction URLs attached to the original proxy can carry over; team proxy sources do not carry into a Lite claim. When a profile shows Proxy required, complete its configuration first. Receiving several copies does not assign different exit IPs or create different fingerprints. Follow the proxy setup guide to verify authentication and the actual exit.

Features available in the full edition

The full edition creates profiles, edits fingerprint settings and provides sync, team and automation features according to your plan and permissions. Lite receives existing profiles through eligible share codes or credentialed files. Its fingerprint details are read-only; it cannot create a profile or turn another browser's JSON export into one.

Lite does not include cloud sync, team collaboration, automation plugins, Local API, MCP, window sync, extensions or page scripts. Choose the full edition for those workflows. Opening a received profile in Lite does not provide the full client's automation entry points.

Both editions can be installed on the same computer and use separate data directories. A Lite copy does not appear in the full edition's team, and full-edition cloud profiles do not automatically appear in Lite. For your own ongoing work across computers, review cloud sync.

Local data after the handoff

After a claim completes, the sender cannot recall the local copy by revoking the share code or use that share to keep monitoring the recipient's activity. Revocation stops future claims. Agree on the profiles and login information being copied before the handoff.

On the first opening, check the website and actual account, then confirm whether the expected login data, credentials and verification codes arrived. An Includes login indicator describes the transferred data. The website still decides whether that session remains valid and may ask you to sign in again.

Settings → Data location shows the local data folder and backup guidance. An old import file does not contain browsing changes made after the import. Prepare local data before reinstalling the system or moving computers. Deleting a profile permanently deletes its local browsing data too; close it and confirm what you still need before deleting.

FAQ