Cookie import in an antidetect browser

Supported cookie formats

You can import JSON exported by Cookie-Editor or EditThisCookie, as well as common cookie JSON fields used by Puppeteer, Playwright, and Selenium. Accepted JSON structures include an array, a single cookie object, or an array inside a cookies field. Each record needs a domain, name, and value. A copied request header with only names and values does not supply all the required information.

Netscape cookies.txt is also supported. Its tab-separated columns describe the domain, subdomain scope, path, secure flag, expiration, name, and value. Preserve the tabs when copying the text. Records with the HttpOnly marker can be read too.

The importer normalizes common expiration and SameSite formats. It skips expired records, records missing required fields, and records with fields that exceed the supported lengths. When several records have the same domain, path, and name, only the last one is kept. Review skipped records if the preview count is lower than the number in your source file.

Import cookies when creating a profile

Select New profile and set its name, platform, and proxy so the destination account is clear. In Cookies, you can prepare the import before the profile exists; the cookies upload after creation. Keep each account's data with its intended profile, including when several accounts use the same website.

For large amounts of text, the client may ask you to use Import from file. Keep the original JSON or Netscape format. Preparing an import does not create the profile, so finish saving and check the result before opening it.

1. Open Cookies and choose Paste to import or Import from file.
2. Review the detected format, valid count, skipped records, and domains. Choose Keep for import when the data matches the intended account.
3. Save the profile and check the import result. If the profile was created but its cookies failed to import, edit that profile and retry there.

Merge or replace cookies in an existing profile

The Cookies area shows the cloud cookie count and update time for an existing profile. Close the profile before changing those cookies if it is running or in use. This also avoids a running session uploading older data while you are checking the import.

Replace overwrites all cookies currently stored in the cloud for that profile. Use it when you intend to restore the complete set from your file. Merge keeps other records and applies incoming values where the domain, path, and name match. It does not create separate sessions for multiple accounts on the same site.

Check the profile name and platform account before applying either option. If you need to retain the previous data, export it first when your plan and permissions allow. For the broader relationship between cookies, storage, and proxies, see multi-account isolation.

Import cookies with profile files or CSV

For a batch migration, cookies can travel in the matching fields of a profile file. Generic CSV and flat JSON imports recognize cookie and cookies headers, and you can also assign the field during column mapping. Keep one profile per row, with the cookie data, account, proxy, and profile name referring to the same account.

Use the Import preview to check cookie counts and errors for each row. JSON inside a CSV cell must remain complete; let your spreadsheet application handle quotes and separators when saving the file. Entering an account name and password does not generate missing cookies.

A full .fgbx backup can include the selected local storage. An ordinary JSON profile configuration does not include it. For files from another browser, check supported sources and field mappings in the browser migration guide before importing the full batch.

Check the website session after import

Check the profile's exit IP, then open the website matching the imported cookie domains. Confirm which account the page displays before continuing work. The proxy setup guide covers connection checks if the profile uses a proxy.

A website may also rely on LocalStorage, IndexedDB, or other session data. A request to sign in again can mean the session expired, other data was not transferred, or the website requires verification. Follow the website's prompts, then close the profile normally to save the resulting session data.

Record the profile, account, and result, especially when migrating profiles with similar names. If the page shows a different account, inspect the source file and its destination before replacing anything. Complete this check for each account you move.

Cookie export and cloud sync

In Cookies, Export offers JSON (EditThisCookie format) and Netscape (cookies.txt). Cookie export depends on your plan. For a full profile export, also check team export permissions and the selected content options. Cookie text alone does not contain the fingerprint, proxy, local storage, or saved website passwords.

When enabled, cookie sync uploads changes and performs a final upload when the profile closes. LocalStorage and IndexedDB are handled in a storage snapshot after closing. Use cloud sync when continuing with the same profile on another computer; choose sharing or file import when transferring a copy to another account.

Finish your website work, close the profile normally, and check the cloud update time before exporting. If cookie sync is off, the cloud record may not reflect the current local session. After restoring an export, check the actual website login in the receiving profile.

FAQ