Updates / product

Persistent profiles: log in once, reuse the browser session

Launch with "profile": "name" and the browser restores that profile's cookies, storage and logins, then saves them again when the session ends.

2026-10-12

Until now every cdpfleet session started from a clean browser, and keeping a login meant saving Playwright's storageState to a file and loading it yourself. From today a launch option does it on our side: name a profile, and the session starts where the last one with that name left off.

How it works

• Add "profile": "shop-login" to the launch. The first launch with a new name creates the profile; every later launch restores it.
• Work in browser.contexts()[0] — that context is the profile. A context you create with newContext() is a throwaway one and isn't saved. The code builder and the new recipes already do this.
• When the session ends and the browser has exited, the profile is saved: cookies — session cookies included, so logins kept in PHPSESSID-style cookies survive — localStorage and IndexedDB, without caches. sessionStorage (per tab) isn't kept. On the fleet a freshly used profile saved to 32 KB on Chrome and 48 KB on Camoufox, from about 30 MB of raw browser profile (case 40 shows exactly what comes back).
• "profile": {"id": "shop-login", "mode": "readonly"} restores without saving, so many sessions can share one login in parallel. A second normal session gets 409 profile_in_use.

Camoufox keeps its device

A Camoufox profile stores the fingerprint generated on its first launch — user agent, screen, fonts, WebGL — and reuses it, so a site sees the same computer every time, not just the same cookies. Timezone, locale and geolocation still follow the exit IP, so keep a profile on one country or a sticky residential exit.

Browsers, limits, security

• Google Chrome, Microsoft Edge, Brave, Chromium and Camoufox. More browsers will follow.
• 100 profiles per account and 50 MB per saved profile, included in every plan. List and delete them with GET / DELETE /v1/me/profiles.
• Each profile is encrypted with its own key and stored privately in Germany; the browser servers never hold storage credentials and get one-time links per session.
• A profile is saved only after a clean browser exit, so if a server fails mid-session that session's changes are lost and the previous version stays.

Get started

• The guide: Persistent profiles.
• Recipes in five languages: Chrome that stays logged in, Camoufox with the same device, many scrapers sharing one login.
• The option on every supported browser's page, e.g. Chrome.