How to Import and Export Cookies (JSON, Netscape, Header)
Move a cookie set between browsers or back it up: which format to choose, how export and import work, and how to keep the file private.
Exporting turns a site's cookies into a file you can back up, inspect, or move into another browser profile; importing writes such a file back into the browser. Cookie Editor supports three formats, JSON, Netscape and header string, and picking the right one depends entirely on what will read the file. One warning up front: an export from a signed-in site can contain session cookies, which are as sensitive as a password. Treat exports like credentials.
Choose the right format
| Format | What it looks like | Best for |
|---|---|---|
| JSON | Structured list of cookie objects with every field | Backups you will re-import into Cookie Editor; reviewing fields in a text editor |
| Netscape (cookies.txt) | Tab-separated lines, one cookie per line | Tools that explicitly ask for a cookies.txt file; many download and testing tools expect this |
| Header string | A single name=value; name=value line | Developers pasting cookies into an HTTP request header for an API test |
Export cookies
- Open the site and the panel
Load the site whose cookies you want, then open Cookie Editor so the list shows that site's cookies.
- Open the export option
Use the panel's export / share control and choose the format the receiving tool expects.
- Save the file somewhere private
Store it outside shared folders and cloud drives that sync publicly. Give it a clear name with the site and date.
- Inspect before reuse
Open the file in a text editor and confirm it contains the site you expected, and notice whether session cookies are inside before sending it anywhere.
Import cookies
- Start on the matching site
Imports apply to a domain, so open that site first, then open Cookie Editor.
- Choose import and pick the format
Select the import control, choose the same format the file was exported in, and load the file or paste its contents as the panel requests.
- Check the result in the list
Search for a name you know the file contains and confirm its value, domain and expiry arrived intact.
- Reload the page
The site reads the imported cookies on the next request. If nothing changed, compare the domain in the file with the site you are on, imports silently “succeed” into the wrong domain more often than any other failure.
Keep exports safe
A session cookie in an export file can let whoever holds the file act as you on that site until the session expires. Never paste exports into chats, tickets, forums or shared documents; delete test exports when you finish; and prefer exporting from a test account. The full reasoning is in why you should never share your sign-in cookies.
Moving a test setup between machines
The most legitimate everyday use of export is carrying your own test states with you. A tester might keep a small library of exported sets: a new-visitor set, a returning-visitor set with preferences chosen, a set with a consent banner accepted. Importing the right set at the start of a session puts the browser into that state in seconds, identically every time, which is what makes test results comparable across days and machines. Keep the library on your own storage, name the files by state rather than by site account, and refresh them when the site changes its cookie names.
Reading an export before you import it
An export is a text file, and ten seconds of reading it before importing is a professional habit worth having. Check that the domains are the ones you expect, that the cookie names match the set you meant to save, and that nothing extra has crept in, a set exported from a busy browser can include cookies for subdomains you forgot were open. If the file contains a session cookie you did not intend to move, delete that entry from the file with a text editor before importing; the format is plain enough for that, and it keeps credentials from travelling further than they must.
When an import seems to do nothing
Work through the boring causes in order. The file's format does not match the format the panel expected, JSON where it wanted Netscape, or the reverse. The browser or profile you imported into is not the one you are looking at. The cookies imported fine but the page was loaded before the import, and a reload shows the new state immediately. Or the site overwrote the imported values on the first request because its server held the real state. Each cause has a different fix, and the export-import pair in the same browser, export a set, delete one cookie, import, see it return, is the quickest way to prove the mechanism itself works.
Formats, one last plain summary
If the three formats blur together, anchor them to their origins. JSON is the modern structured format, readable and exact, and the natural choice between two modern tools. The Netscape file is the veteran text format from the earliest browsers, still spoken by download tools and scripts everywhere. The header string is not really a file format at all; it is the literal line a browser sends, which is why it drops attributes like expiry. Choose by asking what will read the result, not by which looks tidiest, and when both ends are Cookie Editor, JSON every time.
Frequently Asked Questions
Can I move my logins to a new browser with an export?
Technically an import can carry session cookies, but sessions often expire or are tied to other checks, and carrying them around in a file is a security risk. Signing in fresh on the new browser is safer and usually faster.
Why did my import fail or change nothing?
Format mismatch and domain mismatch are the two usual causes: re-export in the format the tool expects, and import while the exact site is open in the active tab.
Does Cookie Editor upload my cookies anywhere?
No. Export creates a local file or text; what happens to it afterwards is up to you, which is exactly why the handling rules above matter.


