Lewati ke konten

Halaman ini belum tersedia dalam bahasa Anda. Anda membaca teks bahasa Inggris.

Export cookies from an ordinary browser and bring them into a profile

Who can use this: All roles · All plans

Export cookies to a file and bring it in with Import cookies, so you do not sign in again.

Export the cookies from a regular browser

Sign in to the account in a regular browser. Cookies exported before signing in carry no sign-in.

An extension like Cookie-Editor saves the site cookies to a JSON or Netscape file.

Bring the cookies into the profile

  1. Launch the ARMANOS Browser profile

    A profile on ARMANOS Browser needs to be running. The built-in engine does not.

    The Launch button.
  2. Choose Import cookies in the profile menu

    Pick the saved file.

    The Import cookies item.
  3. Read the result

    The app reports how many entries were added and how many rejected, with reasons.

    The import result in the notice at the bottom right.
  4. Open the site in the profile

    The sign-in should be there. The exit address of the profile shows on its start page.

    The profile start page.

Supported files

  • JSON: a list of entries

    name, value, domain, path, secure, httpOnly, sameSite and expiry.

  • Netscape, text .txt

    Seven tab-separated fields, as curl and extensions write them.

  • Firefox JSON

    The Host raw, Name raw and Content raw fields.

  • Base64

    Any of the formats, encoded as a whole.

Tip: Exports from other anti-detect browsers are read as well.

If the site asks you to sign in again

  • Cookies exported before signing in

  • The site has a short sign-in lifetime

  • The site tied the sign-in to the device

Important: A cookie file is a live sign-in. Keep it like a password.

Questions

How does the app read expiry dates?
A millisecond expiry is converted to seconds. A session entry with an expiry is saved with it.
Is a Cookie header string read?
No: it has no domain.

Read next

Was this article helpful?

Last updated: Markdown