Cookies
Export and import a profile's cookies, the two formats Ant0 reads and writes, and what to know about sessions.
Updated Sep 7, 2026
Where cookies live
Each profile keeps its own cookies, local storage and logins in its own folder under the data folder. Nothing is shared between profiles, and nothing leaves your computer.
Export
Right-click a profile (or open its ⋮ menu) → Cookies → Export. Choose a format and a file. The bulk toolbar exports several profiles at once, one file per profile.
| Format | File | Readable by |
|---|---|---|
| JSON | <profile>.json | Cookie-Editor, EditThisCookie, Puppeteer, Playwright |
| Netscape | <profile>.txt | curl, wget, yt-dlp, most command-line tools |
The profile has to be running for an export (the browser is asked for its cookies). Start it, wait for Running, then export.
Import
Cookies → Import takes either format; Ant0 detects which one. Cookies are added to the profile’s existing ones; a cookie with the same name, domain and path is replaced. The profile has to be running here too.
Cookies from another tool’s export work the same way. Import them after the profile has been started once with the proxy it will use, so the site sees the session appear from the right place.
Clear
Cookies → Clear removes every cookie of a running profile. Local storage and logins kept by the browser in other ways are not touched; delete and recreate the profile for a completely clean slate.
Command line
ant0 profiles cookies export "Shop DE" --format json -o shop-de.json
ant0 profiles cookies export "Shop DE" --format netscape -o shop-de.txt
ant0 profiles cookies import "Shop DE" shop-de.json
The API endpoints are GET, POST and DELETE /v1/profiles/{id}/cookies
(reference).