How to work with cookies in Undetectable

Cookies help a website remember your session and selected settings. In Undetectable, you can view them in a specific profile, import them from a file, save them for transfer, or delete them. And if you need to collect cookies while visiting websites, you can assign this task to Cookies Bot.

It is best to start with the task. If you are opening a website for the first time and are going to log in to your account, you do not need to look for a cookies file in advance: the website will create the necessary records while you work. Import is useful when you already have cookies from another session. The bot is useful when you need to automate visiting a list of websites.

In this guide, we will go through the entire process: find cookies in a profile, upload a file, check the result, and review the settings that most often cause confusion.

Choose your task

What you want to do	Where to start
Log in to an account for the first time	Open the website in the required profile and log in in the usual way
View already saved cookies	Profile → Cookies → View
Upload cookies from a file or text	Profile → Cookies → Import
Save cookies for transfer	Profile → Cookies → View → Export
Automatically visit multiple websites	Bot: select profiles, a list of addresses, and crawling parameters
Find out why the website asks you to log in after import	Check the records in View, then check the session on the website itself

The button names below are given in English, as in the interface shown in the screenshots.

What exactly is stored in cookies

A cookie is a small record with a name, value, and parameters that determine where and for how long it can be used. For example, a website can save the selected language, cart contents, or an authorized session identifier.

Cookies and saved passwords are different data. To log in, a website usually uses a session identifier in a cookie, not your password. Therefore, transferring cookies can sometimes allow you to continue working without logging in again, but it does not replace a password manager and does not guarantee session recovery. The way these records work is described in the MDN guide to HTTP cookies.

In Undetectable, each profile works with its own set of cookies. If you logged in to an account in one profile, this session is not transferred to another profile automatically. Therefore, before importing, always check the name of the selected profile: a mistake here may lead to opening the wrong account you intended to work with.

There are three more distinctions that will help avoid confusion:

Cookies are not the same as browsing history. Cookie records and the list of opened pages are different parts of browser data.

Cookies do not change the IP or profile configuration. The connection and browser parameters are configured separately.

A cookies file is not a full copy of a profile. You should not expect it to include all settings, extensions, and other browser data.

How to view cookies in a profile

Start by viewing them: this is useful both for checking an import and after the bot has run.

1. In the Profiles list, select the required profile.

2. If its browser window is running, close it before editing cookies. This also prevents a situation where the website updates records at the same time as your changes.

3. Open the tab with the cookie icon — Cookies.

4. Switch to View.

5. Find the required domain in the tree or use Search. Expand the branch using the “+” icon to go to individual records.

Next to the list is a refresh button with circular arrows. Click it if, after importing or visiting websites, you need to reload the displayed list. The list refresh button does not extend the cookie lifetime and does not restore account login.

Focus on the required domain, not only on the total counter. If you transferred a store session, look for that store’s records. A large number of cookies from other websites says nothing about whether the required session was transferred.

The tree may contain domains that you did not enter manually: pages load third-party services. By itself, this does not mean that cookies came from another profile.

How to import cookies from a file or text

Undetectable supports JSON and Netscape. You can upload cookies when creating a profile or later through its settings. These formats and upload methods are listed in the cookies documentation section.

Prepare the file

Use a cookies export from the required account or profile. Make sure that what you have is actually a cookies file, not a list of usernames and passwords, a screenshot, or an export file of the entire browser profile.

The file extension by itself does not determine its contents. If you rename an arbitrary text file to .json, it will not become valid JSON. Similarly, a name=value string from an HTTP header is not equivalent to a full export: it may not contain the domain, path, and expiration time.

If you need another format, use Cookies Converter. Conversion changes the data representation. It does not create missing cookies and does not make an ended session valid again.

Upload cookies to the selected profile

1. Select the profile and close its browser window if it is open.

2. Go to Cookies → Import.

3. Click Browse files and select the file, or drag it into the import area.

4. If you have cookies as text, click Click for text insert and paste the full export text.

5. Check the state of Import expired cookies. For a normal transfer of a current session, leave the checkbox disabled.

6. Wait for the result message. If the program reports a format error, fix it before launching the profile.

7. If the Save button is active after the changes, save the profile. Then go to View and check the required records.

If the profile already has an important working session, export its cookies before experimenting or use a separate test profile. Do not upload several files in a row hoping that one of them will “fit”: after that, it is harder to understand which data you are checking.

Should you enable Import expired cookies

The name means “import cookies whose expiration date has passed.” By default, Undetectable excludes such records from import. The checkbox allows you to include them in processing.

For normal work with a current export, you do not need to enable it in advance. It is useful when you intentionally need to process an old dataset, for example when diagnosing an import. If the task is to restore login, first try to obtain a fresh export from an active session.

Allowing an old record to be imported does not mean that the website will accept it again. A cookie has a storage period in the browser, while authorization has its own state on the website’s server. A session may be ended after logging out, changing the password, or according to the service’s own rules. Changing the local expiration time does not require the server to restore it.

Where the two identical checkboxes are located

In a specific profile: open Cookies → Import → Import expired cookies. Here you check the setting for the profile you are currently working with.

In general settings: open Settings → Profiles → Browser settings → Cookies → Import expired cookies and save the changes. This is the Default settings for new profiles section — default settings for new profiles. Its purpose is confirmed by the documentation for new profile settings.

If you are importing a file into an existing profile, check the checkbox directly in its Import tab. This way you will know the state of the setting with which you are performing the operation, regardless of the previously specified template.

How to check the import result

A successful import message answers the question of whether the program accepted the data. To make sure you can continue working, you need two more checks.

Check the records in Undetectable

Open Cookies → View, refresh the list, and find the domain of the required website. Expand it and make sure the expected records have appeared. If you are checking a specific cookie, compare not only the name but also the domain and path: the same name can appear in different areas of the website.

Do not expect the final counter to always increase exactly by the number of records in the file. For example, some cookies may have expired and not been imported. Checking specific data is more reliable than comparing two numbers.

Check the website itself

Click Open and open the service for which you transferred the cookies. Make sure you are logged in to the correct account and can open the working section: dashboard, settings, or another page you use.

If the website asks you to log in again, this does not necessarily prove an import error. The records may have loaded correctly, but the server may have already ended the session. Some websites additionally use other browser data or require login confirmation.

After a successful check, close the profile’s browser window in the usual way, then open the same profile again and revisit the website. This will help you notice a data-saving problem before starting your main work.

Practical readiness criterion: the required cookies are visible in the selected profile, the website opens the expected account, and restarting does not break your workflow. The number of cookies by itself is not such a criterion.

What else you can do in the View tab

This is where Add new, Edit, Export, Delete, and Copy are located, as well as two separate cleanup commands below. For a beginner, viewing, importing, and exporting are usually enough. Manual editing is needed for a specific task, such as testing your own website.

Add or edit an individual cookie

For a new record, click Add new. To change an existing one, expand the domain, select the required cookie, and click Edit. If the button is unavailable, check whether an individual record is selected and whether the profile is closed.

When editing manually, it is important to understand the purpose of the fields:

Parameter	What it defines
Name and Value	The record name and its contents
Domain	The host or domain area for which the cookie is used
Path	The path on the website to which the record applies
Expires or expirationDate	The expiration time; the label depends on the export format
Secure	Cookie transmission over a secure connection
HttpOnly	Restriction of access to the cookie from the page’s JavaScript
SameSite	Conditions for sending the cookie in requests between websites

These are cookie parameters, not a list of fields that must be present in every editor form. Their meaning is explained in the MDN Set-Cookie reference.

To transfer a working session, keep the original values. Do not change the domain, flags, or date “just in case”: the record may remain in the list but stop matching the website’s requests. A manually invented value also does not replace the session identifier that must be issued by the service itself.

Export or copy cookies

Use Export when you need a file, and Copy when the data needs to be transferred through the clipboard. Before the operation, check the selection in the tree, and after it, check the contents of the result: it should contain exactly the records you intended to save.

Give files clear names, for example project-profile-2026-09-16.json if JSON is selected. The date helps distinguish a fresh export from an old one. Do not store cookies for different work accounts under the same name, such as cookies.json, in one folder.

The file may contain data from an active session. Share it only with those who really need access, and do not publish cookie values in public examples or screenshots.

Delete cookies or clear all data

These actions differ in scope:

Delete — deletes the selected records. First check exactly what is selected.

Delete all cookies — deletes all cookies of the selected profile. This may reset website logins and settings.

Delete all data — a broader cleanup of profile data. Do not use it as a replacement for targeted cookie deletion.

If the problem is only with one website, start by checking its records. A full cleanup will also affect other working sessions in this profile. Exporting cookies before deletion is useful, but it is not a backup copy of all data that Delete all data may remove.

What Cookies Bot is for

Cookies Bot automates website visits in selected profiles. During these visits, websites may write their cookies — just as they do during manual work. The bot saves you from having to open each address yourself.

Here it is useful to distinguish three tools: the generator selects addresses, the bot visits pages, and cookies are saved in the profile when interacting with websites. Clicking Generate by itself does not add cookies.

The bot is useful for preparing multiple profiles and repeatable browsing scenarios. If you simply need to log in to your account, you do not need to run it before every authorization.

Collecting cookies is often called “walking” cookies or part of “warming up.” But there is no universal norm for it: a certain number of records or minutes of work does not guarantee the absence of checks, moderation, or account retention. Evaluate the completion of your task, not a conditional “trust level” by the counter.

How to set up the first Cookies Bot run

To get familiar with it, start with one profile and a short list. This makes it easier to check the setup and notice a mistake than trying to analyze dozens of runs at once.

Select a profile and prepare the connection

Click Bot in the left menu. In the Profiles field, select the profile you want to use. With a large list, filters, folders, and tags will help. If your version has a browser core selection, make sure it matches the required profiles.

Before starting, make sure the website opens manually in this profile. If a proxy is used, it must work. If No Proxy is selected, the browser uses the connection available to it: directly or through a VPN, if the profile’s traffic really goes through it. Selecting a country in the website generator does not change the connection.

Add websites manually or through the generator

For your own list, paste the addresses into the bot field — each URL on a new line — or upload a text file. Use full addresses, for example https://example.com, to avoid ambiguity.

If you do not have a ready list, set Country and Amount, then click Generate. Country determines the geography for selecting websites, and Amount determines how many addresses to get. Review the result and remove pages that are not suitable for your task before starting.

Choosing a country helps get a relevant list, but it does not set the profile language, time zone, or IP. For example, if you are testing work with French websites, separately check the language and connection settings required for that scenario.

The generator is already built into the bot: for a normal run, you do not need to transfer the list between services. The purpose of the tool and its connection with the bot are described on the popular websites generator page.

Choose the visit order

Different scenarios are available in the Script field:

Browse pages in order — each profile visits websites in the order of the list. Convenient for the first run: it is easier to match the result with the task.

Browse pages randomly — the order of website visits is shuffled.

Group pages by profiles — links are shuffled and distributed between profiles. Do not choose it if you want each profile to definitely go through the entire original list.

This difference between scenarios is explained in the Cookies Bot guide. It is especially important when comparing the results of several profiles: different sets of visited websites will produce different cookies.

Configure tabs and time

Tabs sets the number of simultaneously opened pages. For a test run, select 1: this makes it easier to observe what is happening and avoids unnecessary load on the computer and connection. A large value does not guarantee that you will get more useful cookies.

In the Timer field, select Fixed time if you need the same viewing time, or Random interval if the time should vary within a specified range. The timer should be distinguished from the total execution time of the entire list.

To get familiar with the tool, you can start with three available websites, one tab, and a fixed time of 20–30 seconds. This is an example for checking the setup, not a recommended “warm-up” duration. If pages do not have time to load, first check the connection and increase the viewing time.

Understand the additional options

Headless mode launches the browser without the usual visible window. For the first check, it is more convenient to disable it and see which pages actually open. Later, you can use background mode while relying on execution progress and logs.

Do not load images in browser disables image loading. This can reduce traffic usage, especially when paying for proxies by data volume. If you are checking the page appearance or its behavior with images, leave loading enabled.

Use IP Change Link refers to the IP change link specified for the proxy. Enable the option only if your proxy supports this function and changing the address is needed for the scenario. It does not turn a regular proxy into a rotating one and is not a required condition for collecting cookies.

If your version has an Additional actions field, select No Actions for the first run: first check the page crawling itself. Additional behavior should be enabled later for a specific task.

Working with the timer, images, connection, and logs is described in the Cookies Bot documentation. Do not enable an option just because it exists: the initial setup should be fully understandable to you.

Start the bot and check the result

Click Start. Monitor progress and error messages. For details, use View Log File; if you need to interrupt the run, click Stop.

After completion, return to the required profile: Cookies → View → refresh the list. Check whether records from the visited websites have appeared. If you were checking the saving of a specific website setting, open it and check that setting directly.

A successful bot run does not mean that every address necessarily left cookies. The page may have limited itself to another type of data, requested consent, or failed to load the required resource. In visible mode, it is easier to notice a banner, connection error, or verification page.

When a short run works predictably, increase the list and the number of selected profiles. Change one parameter at a time: then it will be clear what affected the result.

How to work with cookies for several profiles at once

For bulk export, open Profile Manager, select the required rows, and right-click to choose “Export cookies”. Do not confuse this item with exporting accounts or the profiles themselves: the result of these operations is different. Bulk export is described in the Profile Manager documentation.

If you are creating many new profiles from prepared data, use bulk creation. Choose creation from a file and the appropriate format; open an example of its structure with the “?” button. Upload the file, click “Generation”, check the preview list, and only then click “Creation”. Undetectable supports creation by cookies and a universal format with multiple parameters. Details are available in the bulk creation guide.

First check a small set. The main thing when scaling is to maintain the match between the account, cookies file, and profile. The same file with an active session in several profiles does not create several independent accounts.

If the task is to transfer the entire working environment to another device, consider importing and exporting profiles. Transferring a single cookies file is suitable for a narrower task.

What to do if the result differs from what you expected (Q&A)

The file does not import

Check the contents and format: JSON or Netscape. Make sure you copied the export completely, without a truncated beginning, extra explanations, or messenger formatting. If you are not sure about the file, export the cookies from the source again and repeat the operation in a test profile.

Import is complete, but the required cookies are not visible

Check the profile name, refresh View, and clear the search filter. Then find the required domain. Make sure its records were actually present in the source file and were not expired while Import expired cookies was disabled.

Cookies exist, but the website asks for a username and password

Check whether you transferred the correct website and account, how fresh the export is, and whether the source session opened. Try logging in to your account normally. If it works, the problem may be with the transferred session rather than the profile connection. Reimporting the same old file usually does not provide new information for diagnostics.

View or edit buttons are unavailable

Close the profile’s browser window. For Edit and Delete, additionally select the required record in the tree. Do not confuse closing the website window with logging out through the website’s own button: logging out may end the session.

After the bot runs, there are few or no cookies

Open the log and check whether the bot went through the list. Then manually visit one of the addresses in the same profile. Check whether the page loaded, whether there is an access check or consent request. The number of addresses in Amount is not the promised number of cookies: different websites have different amounts.

Nothing happens on the screen in Headless mode

The absence of a browser window is expected in this mode. Check the progress and View Log File. For visual diagnostics, stop the current run and repeat a short check with Headless mode disabled.

After cleanup, login to other websites disappeared

Check which command you used. Delete all cookies applies to the entire selected profile, not only to the currently open website. To continue working, you will need to log in again to the affected accounts or restore suitable data if it is saved and the sessions are still active.

If the problem persists, prepare for support the Undetectable version, reproduction steps, the exact error text, and the file format. For the bot, add its settings and the relevant log fragment. Hide cookie values and proxy access data: they are usually not needed for the initial error analysis.

Where to start right now

Open Cookies → View in one profile and find a familiar domain. If you have your own export, upload it through Import, check the records and the website operation. If you want to learn the bot, run a short session with one profile and a few addresses, then return to View.

After that, you will have a clear workflow: select a profile, perform the required operation, check the data, and make sure the website works as expected. You can repeat it both for one account and when preparing several profiles.