profile
Restore a saved browser profile and save it again when the session ends.
Use it for: Staying logged in between sessions: log in once, then every later launch starts with the same cookies and storage (and, on Camoufox, the same device).
Browsers: Google Chrome, Microsoft Edge, Brave, Opera, Yandex Browser, Chromium, Patchright, Camoufox, Firefox, WebKit.
Details
- Type:
string | object - Default: none
- Example:
{"profile":"shop-login"}
A name ("shop-login", up to 64 letters, digits, -, _) or { "id": "shop-login", "mode": "readonly" }. The first launch with a new name creates the profile; later launches restore its cookies, localStorage and IndexedDB, and the profile is saved when the session ends. Session cookies are kept too; sessionStorage (per tab) is not. Work in browser.contexts()[0] — a context made with newContext() is not saved. "mode": "readonly" restores without saving and can run in parallel; a second normal session gets 409 profile_in_use. On Camoufox the device fingerprint is kept with the profile. See Persistent profiles.
Every browser except Whale and Rebrowser. Keeps cookies (session cookies too), localStorage and IndexedDB; not sessionStorage. 20 profiles per shared thread and 30 per dedicated thread (at least 100), 50 MB each; list and delete with /v1/me/profiles.
Used in
- Case 77: Kasada and AWS WAF on real sites: twelve browsers, four sites, one exit each
- Case 75: HUMAN on real sites: twelve browsers, three sites, one exit each
- Case 73: Akamai on real sites: twelve browsers, three sites, one exit each
- Case 71: DataDome on real sites: twelve browsers, three sites, one exit each
- Case 70: Cloudflare on real sites: twelve browsers, three sites, one exit each
- Case 66: Which fingerprints stay the same across launches: canvas, WebGL, audio and fonts on seven browsers
- Case 67: Akamai and HUMAN: what gets through? Four browsers, three networks, the vendors' own sites
- Case 65: DataDome: what gets through? Four browsers, three networks, DataDome's own site
- Case 64: Cloudflare: what gets through? Four browsers, three networks, four public test pages
- Case 49: The same Camoufox device across relaunches: what a persistent profile keeps, and what it doesn't
- Case 40: Persistent profiles: what a saved browser profile keeps, and what it doesn't
- Chrome that stays logged in between sessions
- Camoufox that keeps the same device and login
- Firefox that stays logged in between sessions
- WebKit that stays logged in between sessions
All options: launch options.