Import & export cookies

Cookies hold the logged-in state for the sites you visit in a profile. Santiago lets you save a profile’s cookies to a JSON file and load cookies back in later — handy for moving a session between profiles, keeping a backup, or restoring a login without typing your password again.

What you can do

Action	What it does
Export	Downloads all of the profile’s current cookies as a .json file you keep on your computer.
Import	Opens a file picker and adds the cookies from a JSON file into the profile.

Cookies are per profile

Each profile keeps its own cookies, just like its own fingerprint and proxy. Exporting and importing always works on a single profile at a time — nothing is shared between profiles unless you move the file yourself.

The profile must be running

Export and import both read and write the profile’s live browser session, so they only work while the profile is running. Launch the profile first, then export or import.

Export a profile’s cookies

Use export to save a snapshot of a profile’s session — for example before clearing it, or to copy a login into another profile.

1. Launch the profile you want to export from.
2. Choose Export cookies from the profile’s menu.
3. Santiago downloads a .json file containing every cookie currently stored in that profile.

Keep the file somewhere safe. The JSON includes session tokens, so treat it like a password.

Treat the file like a credential

A cookie export can contain active login sessions. Anyone with the file could potentially reuse those sessions. Store it securely and don’t share it.

Import cookies from a file

Import lets you load cookies from a JSON file back into a profile.

1. Launch the profile you want to import into.
2. Choose Import cookies from the profile’s menu.
3. Pick your .json file in the file picker.
4. Santiago reads the file and adds the cookies to the profile.

What import actually does

• Import adds cookies — it inserts each cookie from the file into the profile, one by one.
• It does not clear the profile’s existing cookies first. New cookies are added on top of whatever is already there. If a cookie with the same name, domain, and path already exists, the imported value replaces it.
• The file must be a JSON array of cookies — the same shape you get from an export. Exporting from one profile and importing into another is the most reliable way to move a session.

Round-trip between profiles

The cleanest way to copy a login is to export from the source profile and import that exact file into the target profile. Because the import format matches the export format, nothing gets lost in translation.

Requirements and limits

• The profile must be running. Both export and import act on the live browser session, so launch the profile before using either.
• Import needs an active subscription. Importing cookies is one of the actions gated by your plan, alongside launching and creating profiles. If your subscription has expired or you haven’t chosen a plan yet, import is unavailable until you’re on an active plan. See Plans & pricing and License states.
• Export works even when your subscription has expired — you can always pull your cookies back out, so you never lose access to your saved sessions.

Automate it (for agents and developers)

Everything above is also available through Santiago’s local API on http://localhost:7891, so agents and scripts can read and write a profile’s cookies without clicking through the app. This is the same API the agent skill uses.

Cookie endpoints live on the profile API and work while the profile is running:

Export, import, and clear cookies

# Export all cookies as JSON
curl -s localhost:7891/api/profiles/$PROFILE/cookies | jq .data

# Import cookies from JSON (adds them, does not clear first)
curl -s localhost:7891/api/profiles/$PROFILE/cookies -X POST \
  -H 'Content-Type: application/json' -d '[{...}, {...}]'

# Clear all cookies
curl -s localhost:7891/api/profiles/$PROFILE/cookies -X DELETE

# Clear by filter (any combo of name / domain / path) — exact match
curl -s "localhost:7891/api/profiles/$PROFILE/cookies?domain=.example.com" -X DELETE

Every response uses the standard envelope: { "ok": true, "data": {...} } on success, or { "ok": false, "error": { "code", "message" } } on failure.

Note

Filters on the clear endpoint are exact match, not substring. Many cookies set their domain with a leading dot (for example .example.com) to cover subdomains — include the dot to match them. Check the real domains via the export endpoint first, or omit the filter to clear everything.

For the full automation surface — navigation, forms, screenshots, and the rest — see the HTTP API guide and the API reference.

Related pages

• Session sync — how Santiago saves and restores cookies and tabs automatically across launches and devices.
• Profiles overview — what a profile is and what it stores.
• Automation overview — drive profiles with the local API or the agent skill.